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/03/03 20:01] mikeclapp |
access:access_server_database_schema [2012/10/10 17:05] (current) |
||
|---|---|---|---|
| Line 101: | Line 101: | ||
| |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) | | | ||
| - | ==== RTK Statistics Table (gps) ==== | + | ==== RTK Statistics Table (rtk) ==== |
| The RTK statistics table maintains statistics for each RTK GPS device the customer has received data from. | The RTK statistics table maintains statistics for each RTK GPS device the customer has received data from. | ||
| Line 144: | Line 144: | ||
| |largest_gap |The size of the largest gap in seconds | | | |largest_gap |The size of the largest gap in seconds | | | ||
| - | ==== RTK Track Table (RTK track) ==== | + | ==== 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) | 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) | ||
| Line 182: | Line 182: | ||
| |Horizontal accuracy |Integer (accuracy * 1000) | | |Horizontal accuracy |Integer (accuracy * 1000) | | ||
| |Vertical 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.1267646493.txt.gz · Last modified: 2012/10/10 17:05 (external edit)
Page Tools
