trackwork:system_stories
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
trackwork:system_stories [2015/12/04 00:27] mikeclapp |
trackwork:system_stories [2015/12/11 01:49] (current) mikeclapp [Trackwork Concepts] |
||
|---|---|---|---|
| Line 30: | Line 30: | ||
| Nature of Edits | Nature of Edits | ||
| * Trim - changes the Default view setting - It doesn't actually change the track but changes what's shown by default when downloaded by the server. | * Trim - changes the Default view setting - It doesn't actually change the track but changes what's shown by default when downloaded by the server. | ||
| - | * | + | * Edits just affect views of data. |
| + | Views | ||
| + | Time & Geo slicing of data (tracks) for reporting | ||
| + | A track only exists once on a customer's server. He can have many views including copies of views to simulate additional machines. | ||
| + | |||
| + | In most cases we don't upload track data points from Trackwork. Upload should be removed from the right-click track listing menu. Instead a Save/Publish (think of better name) should push changes to the viewsThe exception would be a G-Ray or other non-connected sensor. We save modifications and View settings. | ||
| + | |||
| + | |||
| + | Upload is probably wrong terminology for reporting/view saving function. Tech terminology is Publish but not user appropriate. Save ????? which saves view segmenting, cycle lines, stat areas up to the server is probably a better descriptor | ||
| + | |||
| + | ===== Trackwork System Story 1 (1st release) ===== | ||
| + | |||
| + | |||
| + | ==== Trackwork ==== | ||
| + | |||
| + | Save ( changes to vehicle association, vehicle properties, Cycle lines?) | ||
| + | |||
| + | |||
| + | ==== TrackManager ==== | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | ===== Trackwork System Story 2 ===== | ||
| + | |||
| + | Second Release Point | ||
| + | |||
| + | |||
| + | ==== Trackwork ==== | ||
| + | |||
| + | * Copy Track (View) - Create a virtual track clearly denoting it's a copy of an existing track. The View settings can be published to the server clearly denoting it's a copy. This implies that machine associations can be somehow linked to track views (Should all machine associations actually be done at the view level?) | ||
| + | * Statistic Region View - A geographic view saving statistics as a location | ||
| - | Views | ||
| - | Time & Geo slicing of data (tracks) for reporting | ||
| - | Track-one machine on server. | ||
| - | In most cases we don't upload track data points from Trackwork. The exception would be a G-Ray or other non-connected sensor. We save modifications and View settings. | ||
| - | Views are what track work creates | ||
| - | When we save we're really saving is a view. | ||
| - | Upload is probably wrong terminology for reporting/view saving function. Tech terminology is Publish but not user appropriate. Save ????? which saves view segmenting, cycle lines, stat areas up to the server is probably a better descriptor | ||
trackwork/system_stories.1449188847.txt.gz · Last modified: 2015/12/04 00:27 by mikeclapp
Page Tools
