access:access_server_database_schema
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
access:access_server_database_schema [2010/02/22 19:43] mmatthews |
access:access_server_database_schema [2012/10/10 17:05] (current) |
||
|---|---|---|---|
| Line 99: | Line 99: | ||
| |rejected_dop |The number of positions that have been rejected because the position accuracy was poor | | | |rejected_dop |The number of positions that have been rejected because the position accuracy was poor | | | ||
| |rejected_time |The number of positions that have been rejected because the position time was invalid | | | |rejected_time |The number of positions that have been rejected because the position time was invalid | | | ||
| + | |cleared_time |The last time the statistics for this entry were cleared (0 if never cleared) | | | ||
| + | |||
| + | ==== RTK Statistics Table (rtk) ==== | ||
| + | The RTK statistics table maintains statistics for each RTK GPS device the customer has received data from. | ||
| + | |||
| + | ^Column ^ Description ^ Comments ^ | ||
| + | |serial |The GPS serial number |This has been expanded to 32 characters instead of 8 | | ||
| + | |time |The last time the RTK system connected to the server | | | ||
| + | |total_points |The total number of positions uploaded from the GPS | | | ||
| + | |last_Northing |The last valid Northing received from the GPS | | | ||
| + | |last_Easting |The last valid Easting received from the GPS | | | ||
| + | |last_Elev |The last valid elevation received from the GPS | | | ||
| + | |last_time |The last valid time received from the GPS | | | ||
| |cleared_time |The last time the statistics for this entry were cleared (0 if never cleared) | | | |cleared_time |The last time the statistics for this entry were cleared (0 if never cleared) | | | ||
| Line 127: | Line 140: | ||
| |end_time |The time of the last point in the track | | | |end_time |The time of the last point in the track | | | ||
| |discovery_time |The time the first valid data associated with this track was received | | | |discovery_time |The time the first valid data associated with this track was received | | | ||
| + | |total_points |The total number of points the track contains | | | ||
| + | |gap_count |The number of gaps in the track | | | ||
| + | |largest_gap |The size of the largest gap in seconds | | | ||
| + | |||
| + | ==== RTK Track Table (rtktrack) ==== | ||
| + | The track table contains information about RTK GPS tracks. A track is supposed to correspond to the work done during a single work period, typically a day. The server does not know what the customer's work day is so it attempts to create tracks by grouping together all GPS data that is within a specified maximum "gap" time. That time is currently defined as four hours. (note: this behavior follows the GPS track model with specific exceptions for finding projects) | ||
| + | |||
| + | ^Column ^ Description ^ Comments ^ | ||
| + | |handle |An integer value that uniquely identifies the track| | | ||
| + | |project |The handle to the project the track belongs to, 0 if not associated with a project | | | ||
| + | |serial |The serial number of the GPS that generated the track | | | ||
| + | |start_time |The time of the first point in the track | | | ||
| + | |end_time |The time of the last point in the track | | | ||
| + | |discovery_time |The time the first data associated with this track was received | | | ||
| |total_points |The total number of points the track contains | | | |total_points |The total number of points the track contains | | | ||
| |gap_count |The number of gaps in the track | | | |gap_count |The number of gaps in the track | | | ||
| Line 145: | Line 172: | ||
| The GPS data is stored in flat files rather than an SQL database for scalability. | The GPS data is stored in flat files rather than an SQL database for scalability. | ||
| + | |||
| For each GPS position the following information is stored: | For each GPS position the following information is stored: | ||
| + | |||
| + | ^ Description ^ Comments ^ | ||
| + | |Time of position |GMT timestamp as seconds offset from unix epoch | | ||
| + | |Latitude |Integer (latitude * 10000000) | | ||
| + | |Longitude |Integer (longitude * 10000000) | | ||
| + | |Altitude |Integer meteres (meters * 1000) | | ||
| + | |Horizontal accuracy |Integer (accuracy * 1000) | | ||
| + | |Vertical accuracy |Integer (accuracy * 1000) | | ||
| + | |||
| + | ===== RTK File Contents ===== | ||
| + | |||
| + | The RTK data is stored in flat files rather than an SQL database for scalability. | ||
| + | |||
| + | For each RTK position the following information is stored: | ||
| + | |||
| + | ^ Description ^ Comments ^ | ||
| + | |Time of position |GMT timestamp as seconds offset from unix epoch | | ||
| + | |Easting |? Float Integer (range is +/- 99,999,999.9999) | | ||
| + | |Northing |? Float Integer (range is +/- 99,999,999.9999) | | ||
| + | |Elevation |Integer feet (range is +/- 32,000.0000) | | ||
| + | |Units |Boolean? (Assumed feet if Yes ?) | | ||
| + | |Quality |Integer (0,1,2,3,4,5 corresponds to common NMEA flag standards) | | ||
| + | |||
access/access_server_database_schema.1266867806.txt.gz · Last modified: 2012/10/10 17:05 (external edit)
Page Tools
