Time stamp of recorded-then-edited tracks
For recorded tracks to be kept as a record of the trip, the track's time stamp should have the actual trip date and time even after manipulation of the track. I think the first track point's date and time is the best for recorded-then-edited track's time stamp.
When a track is copied or modified by Split, Remove all before/after and etc., the time stamp of the track is changed to current time. It's OK for route planning tracks as suggested here. However, for recorded tracks to be archived, it's not good at all because it breaks track list ordering by trip date and time with 'sort by created time'.
Possible solution would be to introduce:
(a) a new sort option 'sort by recorded time' which is a sort method by first track point's date and time.
(b) a function to override track's time stamp with first track point's date and time.
(c) any other good idea?
Could you please consider for good solution?
I just came across a similar requirement and I currently think the easiest way forward (and probabyl the most flexibale one as well) would be to add the option to edit the date and time of the first track point of each track. This would allow everyone to edit the tracks and move any track on the timeline where he or she wants to have it.
Of course all other track points shold "move" on the timeline as well. Depending on how the rest of the track points of a track are stored in the database it causes of course more or less follow-up calculation. Ideally for each trackpoint only the time difference elapsed since the previous trackpoint should be stored. Then entire tracks could be moved on the timeline as desired.
I just came across a similar requirement and I currently think the easiest way forward (and probabyl the most flexibale one as well) would be to add the option to edit the date and time of the first track point of each track. This would allow everyone to edit the tracks and move any track on the timeline where he or she wants to have it.
Of course all other track points shold "move" on the timeline as well. Depending on how the rest of the track points of a track are stored in the database it causes of course more or less follow-up calculation. Ideally for each trackpoint only the time difference elapsed since the previous trackpoint should be stored. Then entire tracks could be moved on the timeline as desired.
Hi Forum,
no additional thoughts or comments?
Hi Forum,
no additional thoughts or comments?
I was trying to understand the issue once again and here is a report.
When I say 'time stamp' of the track, it means the date written with blue color in the track manager as shown in the image here. Since the time stamp is a parameter to be used for track ordering and filtering in the track manager, I want to keep it at actual track's recorded time even after track manipulation.
Now, I've tested and confirmed that the time stamp does NOT change by:
- 'copy to' and 'move to' operation in track manager.
- track manipulations with 'Edit on map'.
I also noticed that the time stamp is set to current time only if a track is copied by 'Create copy' operation.
@menion So, what I'm asking on this topic seems already fulfilled. Thank you. But I don't know when the issue was solved.
@Bernhard Thank you for your post. It makes me to re-confirm the things and my issue seems gone. I hope the report above is useful to solve your issue too.
I was trying to understand the issue once again and here is a report.
When I say 'time stamp' of the track, it means the date written with blue color in the track manager as shown in the image here. Since the time stamp is a parameter to be used for track ordering and filtering in the track manager, I want to keep it at actual track's recorded time even after track manipulation.
Now, I've tested and confirmed that the time stamp does NOT change by:
- 'copy to' and 'move to' operation in track manager.
- track manipulations with 'Edit on map'.
I also noticed that the time stamp is set to current time only if a track is copied by 'Create copy' operation.
@menion So, what I'm asking on this topic seems already fulfilled. Thank you. But I don't know when the issue was solved.
@Bernhard Thank you for your post. It makes me to re-confirm the things and my issue seems gone. I hope the report above is useful to solve your issue too.
I would also like ability to correct date time of trackpoint. At least a start one. I am using locus tracker for a a month and already got two cases:
Forgot to start track recording and started it a bit later on. Then after finishing recording I added missing beginning f the track by using track planner. And now my track time shows that my trip took 425586 hrs and 02 mins
I would also like ability to correct date time of trackpoint. At least a start one. I am using locus tracker for a a month and already got two cases:
Forgot to start track recording and started it a bit later on. Then after finishing recording I added missing beginning f the track by using track planner. And now my track time shows that my trip took 425586 hrs and 02 mins
Replies have been locked on this page!