Track Editor tool

• Change Track Day
• Copy Track data (Create new track)
• Shift Track location?
• Trim Track - True deletion (implies some visual editing (time bar, geographic)
• Copy Pieces of track data

Track points aren't actually edited by Trackwork or TrackManager. The internal Track editor is actually capable of editing/copying/creating tracks.

Edits in Trackwork, TrackManager, Web are actually just view objects applied to the original track.

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.
• 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

Save ( changes to vehicle association, vehicle properties, Cycle lines?)

Second Release Point

• 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

The view concept is a powerful idea that translates to all programs and web. For example the report area concept in track work is really a view. We don't save it now but this would be away.

Things I can imagine storing in a view object. Not all are required for the object

• The base track it points to
• The time range of the base track it represents (the time slice/segment)
• Is it the Default track. The Default track is the broadest view of the track and the default view that Trackwork/Trackmanager would show for example. There could only be one Default track for an object.
• Is it a virtual track (copy)
• Cycle line geometry (polyline)
• Statistic/report area geometry (polygon)
• Do we store statistics here too? I think so. And it could be used for time slice or geo based statistics
• Labels- for segmenting/tagging a track