User Tools

Site Tools


access:trackwork_server

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
access:trackwork_server [2009/04/21 23:31]
mmatthews
access:trackwork_server [2012/10/10 17:12] (current)
Line 1: Line 1:
-[[main|Main Page]] 
 ====== Trackwork Server ====== ====== Trackwork Server ======
  
Line 12: Line 11:
 several of these jobs running in parallel on several systems. Since all the GPS data lives in the several of these jobs running in parallel on several systems. Since all the GPS data lives in the
 database it would be hard if not impossible to rebuild the DB if it were to become corrupt. database it would be hard if not impossible to rebuild the DB if it were to become corrupt.
-We could try and fallback to a backup (are we running backups?).+We could try and fallback to a backup (are we running backups)
 + 
 +  No backups - Mike Clapp
  
 If we re-implement the server I would think moving to a system where the GPS data was stored If we re-implement the server I would think moving to a system where the GPS data was stored
Line 32: Line 33:
  
 ===== Compatibility ===== ===== Compatibility =====
- (this may not be the correct spot for this) + 64 bit Vista compatibility ​has tested ok on view and download as of V 2.05C (4-10-09). 
-   ​- ​64 bit compatibility ​- Initial testing shows TMM lib doesn'​t work on 64 bit Vista (UNCONFIRMED,​ may be operator error) +  * should test upload ​(G-ray
-     Verify latest version +            
-     Check to see if Vista has a 32 bit compatibility flag +
-     - If confirmed, evaluate fix option +
-          - Trackwork server (tough+
-          - Client library settings ​(32 bit compatibility mode?) +
-          ​Installer options? (if Vista has compatibility mode+
- +
-           +
  
  
Line 67: Line 61:
     - Improved log messages     - Improved log messages
  
 +===== Track Server Functions (Current)====
 +This is the current Trackwork functionality. It does not have the API functions being called and that should probably be added. These are all currently contained within the Server Tab of the Import dialog with the exception of Upload.
 +
 +==== Projects ====
 +  * Delete Project (RM menu)
 +  * Add (Name, Description(O),​ Bounds(O), Start Date)
 +  * Modify (Name, Description,​ Status (inop), Bounds, Start Date)
 +  * Delete Project (Button)
 +
 +=== Potential ===
 +  * Partial download of tracks from a single project
 +
 +==== Tracks ====
 +  * Read Tracks
 +  * Download Points (based on selected tracks)
 +  * Delete (RM Menu)
 +  * Move to other Projects)
 +  * Select (and Download)
 +
 +==== Vehicles ====
 +  * Add New Vehicle
 +  * Rename Vehicle
 +  * Delete Vehicle
 +  * Assign to GPS Device (Association)
 +      * Set Time Range
 +  * Modify Time on Association
 +  * Delete Association
 +
 +
 +==== Outside of Tab ====
 +  * Upload Tracks
  
  
  
  
access/trackwork_server.1240356685.txt.gz · Last modified: 2012/10/10 17:12 (external edit)