This object is in archive! 

Locus-Brouter gpx out dynamic wpt timestamps

0709 shared this question 6 years ago
Answered

Locus V 3.18.7. Locus B-router "Route and Measure function. In gpx export all navwaypoints have a fix timestamp.

Is it possible to attach dynamic timestamps as in system tcx ? Navtrack export by gpx 1.0 (remove extension) for external program and app where exact ordered wptlist is important. By timestamps, a manipulated wptlist can more easily be (re)sorted if exact order was broken by user mistake.

For external use, so not in Idea but in Question. Regards.

Replies (3)

photo
1

Good day Willy,

in current system, GPX and TCX exports use exactly same technique, so results should be identical.


Anyway when you create a track that is then exported (so this track has no times), Locus generates times for all trackpoints, but times for waypoints remains old. So I've improved it and times for waypoints now should be set to times of attached trackpoint.


I've also realized, that currently Locus use 1 meter per second as average speed for optimized track for export. But currently it is possible to define "activity" for every track. So I should define average speeds for every activity and exported track optimize with average speed from activity and not with 1 m/s. Hmm ...

photo
1

Thank you ! And about the Hmm... that should be even more optimal indeed.

photo
1

Is suppose it would consider also vertical speed contained in the activity profiles. As for e.g. bicycle activities it is essential. 50 km on the Haná flats is not like 50 km on Beskydy mountains.

photo
1

Well, I'm still not sure about usefulness of generated timestamp for tracks. It is currently only place where this feature is used (export), so I do not think it is too important. And everything is better then currently used 1 m/s in all cases.

photo
1

I would already be "super happy" with some more realistic timestamps representing "flat terrain 18kmh" cycling speed replacing 'turtle" speed, ;-) The actual virtual speed in use is a lot SLOWER than 3.6 kmh !

photo
1

Sure, anything is better than 1 m/s.

The usefulness of the timestamps would be revealed if a sophisticated ETA was implemented in future.

The stored track nominal time profile could be compared to real time profile and the nominal track ETA could be adjusted to conditions of the user.

As ETA based on ( long or short term ) avg speed and remaining distance can be easily fooled.

Edit: Instead of exponential filter of the current speed, as used now, there would be exponential filter of ratio of real/nominal time per distance, ( orreal/nominal distance per time). Then remaining time would be fineestimated from the nominal remaining time and this filtered ratio.

Replies have been locked on this page!