-
For all tracks stored in the internal track database: Please export / share also the timestamps. Currently all timestamps are missing (coord and elevation are available). See example for an entry:
Testet with Cruiser 5.1. And something like this is the expectation:
BTW: The second entry (directly exported from current track) is more accurate (e.g. 7.5354227 versus 7.53542). |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 1 reply
-
@printmaps Thanks for the suggestion. There is already an existing thread on this topic: |
Beta Was this translation helpful? Give feedback.
-
About the precision of coordinates, please see here:
These at the equator, as at other latitudes, are more accurate. Web apps / routers use 5 decimals precision in their responses, |
Beta Was this translation helpful? Give feedback.
-
I would save the recorded values unchanged. This gives downstream analyses all possibilities. If the data has to be shortened, the coordinates and heights should have an accuracy of at least 1 mm. The time stamps should be accurate to a hundredth of a second. |
Beta Was this translation helpful? Give feedback.
-
I would like to use the internal track database to manage all my tracks. At the moment, the feature is still quite rudimentary and can't really be used for this purpose without the timestamps in the tracks. However, I hope that it will continue to develop into a first-class feature. |
Beta Was this translation helpful? Give feedback.
@printmaps Thanks for the suggestion.
There is already an existing thread on this topic: