access:trackwork_server_tables
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
access:trackwork_server_tables [2009/06/22 15:58] mmatthews |
access:trackwork_server_tables [2012/10/10 17:11] (current) |
||
|---|---|---|---|
| Line 5: | Line 5: | ||
| - | ===== Loc table ===== | + | ===== Location Table (loc) ===== |
| In the future this table should go away and be replaced with device/day based file system for scalability | In the future this table should go away and be replaced with device/day based file system for scalability | ||
| Line 13: | Line 13: | ||
| |lat |latitude (integer – latitude * 10*7)| | | |lat |latitude (integer – latitude * 10*7)| | | ||
| |lon |longitude (coded like latitude)| | | |lon |longitude (coded like latitude)| | | ||
| - | |alt | altitude (integer)| | | + | |alt | altitude (integer)|I think this value is decimal altitude in meters * 1000 | |
| |hacc |horizontal DOP value| | | |hacc |horizontal DOP value| | | ||
| |vacc |vertical DOP value| | | |vacc |vertical DOP value| | | ||
| |TMM_serial |device serial number (8 char max)| | | |TMM_serial |device serial number (8 char max)| | | ||
| - | ===== Track_Data table ===== | + | ===== Track Table (track_data) ===== |
| ^Name ^ Description ^ Comments ^ | ^Name ^ Description ^ Comments ^ | ||
| Line 34: | Line 34: | ||
| - | ===== Projects table ===== | + | ===== Projects Table (projects) ===== |
| ^Name ^ Description ^ Comments ^ | ^Name ^ Description ^ Comments ^ | ||
| Line 53: | Line 53: | ||
| |modified | The date this entry was last modified| | | |modified | The date this entry was last modified| | | ||
| - | ===== Association Table ===== | + | ===== Associations Table (association) ===== |
| ^Name ^ Description ^ Comments ^ | ^Name ^ Description ^ Comments ^ | ||
| Line 63: | Line 63: | ||
| - | ===== Vehicles table ===== | + | ===== Vehicles Table (vehicles) ===== |
| This table will probably change to set more vehicle properties as global values. Color is a no-brainer and I could see other values used for haul planning, vehicle type (scraper, paver, etc.). First step is probably only color. | This table will probably change to set more vehicle properties as global values. Color is a no-brainer and I could see other values used for haul planning, vehicle type (scraper, paver, etc.). First step is probably only color. | ||
| Line 74: | Line 74: | ||
| |type| what type of vehicle (Scraper, Paver, Truck)| proposed, we could use this to set behaviors| | |type| what type of vehicle (Scraper, Paver, Truck)| proposed, we could use this to set behaviors| | ||
| - | ===== RTK table ===== | + | ===== RTK Data Table (rtk) ===== |
| The RTK table exists in the current server but has no method of summarizing (tracks) or downloading the data. It's also missing the key field of quality. | The RTK table exists in the current server but has no method of summarizing (tracks) or downloading the data. It's also missing the key field of quality. | ||
| Line 119: | Line 119: | ||
| - | ===== Modules table ===== | + | ===== Modules Table (modules) ===== |
| This is mostly about TMM's. My proposal is that we don't touch this because it's fairly small and doing so might create problems with the TMM's that we don't have much control over. | This is mostly about TMM's. My proposal is that we don't touch this because it's fairly small and doing so might create problems with the TMM's that we don't have much control over. | ||
| Line 152: | Line 152: | ||
| |rej_pwr_time| | | | |rej_pwr_time| | | | ||
| |stats_cleared | time statistics last cleared| | | |stats_cleared | time statistics last cleared| | | ||
| + | |||
| + | This table is really three sub-tables: | ||
| + | 1. A list of known GPS devices. | ||
| + | 2. Operating parameters for TMM devices. | ||
| + | 3. Data collection statistics for known GPS devices. | ||
| + | --- //[[mikematthews@agtek.com|Michael Matthews]] 2009/06/22 09:34// | ||
| ===== A2D Table (a2d) ===== | ===== A2D Table (a2d) ===== | ||
| Line 181: | Line 187: | ||
| ===== Asset ID Table (asset_ID) ===== | ===== Asset ID Table (asset_ID) ===== | ||
| + | |||
| + | This table contains at most one row which is the last asset ID assigned to a vehicle. | ||
| ^Name ^ Description ^ Comments ^ | ^Name ^ Description ^ Comments ^ | ||
| |handle |Unique integer value|Is this used to generate unique asset ids?| | |handle |Unique integer value|Is this used to generate unique asset ids?| | ||
| + | ===== AGD Serial Number Table (agd_serial_numbers) ===== | ||
| + | |||
| + | According to the comments in the server code this table is only valid on the master server and is accessed in response to an upload request that has the aux code set to AUX_CODE_AGD_SERIAL_REQUEST. The current time is inserted into the table and MySQL auto fills the serial column with a unique integer value. The unique integer value is returned to the calling application. | ||
| + | |||
| + | ^Name ^ Description ^ Comments ^ | ||
| + | |serial|Unique integer value| | | ||
| + | |time| | | | ||
| + | |||
| + | ===== Module Groups Table (module_groups) ===== | ||
| + | |||
| + | ^Name ^ Description ^ Comments ^ | ||
| + | |handle|Unique integer value| | | ||
| + | |group name|Group name (64 characters max) | | | ||
| + | |ref_time|Time of....?| | | ||
| + | |||
| + | ===== Group Members Table (group_members) ===== | ||
| + | |||
| + | ^Name ^ Description ^ Comments ^ | ||
| + | |group_handle|The handle to the associated module group| | | ||
| + | |serial|The device serial number (8 characters max) | | | ||
access/trackwork_server_tables.1245686316.txt.gz · Last modified: 2012/10/10 17:11 (external edit)
Page Tools
