Voyage data validation

Every voyage, there may drift GPS data points, using this method validation.

The examples do with the 35th Antarctic route data. Customer GPS data exists new library, and the old library. Since no new library west longitude data, so the use of the old library data. Table CJ_TEMP_GPS old library.

 

1, PLSQL exported to the local operation. Export CJ_TEMP_GPS of UTC data to 2019-3-13 2018-11-2 period.

2, into the local Oracle.

3, ArcMap new empty GDB.

4. Conversion Table traditional relational tables for point layer Feature table.

 

     

Remember, Output using GDB as a carrier, do not use Shp. Shp time accuracy because only accurate to date, no minutes and seconds

 

5, the dot layer into line layer, LineField is to distinguish between the different lines, since only 35 of these derived data, it is here empty, i.e. only one generating line.

SortField is the same point of order within a line, we use UTC column.

 

 

GDB time here with a precise second, if only the roughly Shp to day, where there will be problems. The following figure shows the time to the nearest second GDB, the following is shp time, accurate to Day.

 

 

 

Blue dot layer using a wire GDB generated green dot layer is generated shp line, out of order evident. Yellow GPS points.

 

Guess you like

Origin www.cnblogs.com/wigis/p/10955471.html