You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Did a recording on an airplane last week, with an interval of 30 s between points.
The gpx export file has wierd timestamps.
The first timestamp is just for one single position, the next is 9:15 minutes later and repeated for 7 positions, next is 8:48 later and repeated for 16 positions, next is one second later and repeated for 5, and so on.
Total of 300 points for a 2.5 hour trip so that adds up, but the timestamps are all wrong.
A graph of the elevation points gives a smooth curve so the position intervals is correct.
First points:
68,000 2023-12-18T05:05:50Z65,336 2023-12-18T05:15:05Z66,277 2023-12-18T05:15:05Z63,706 2023-12-18T05:15:05Z63,706 2023-12-18T05:15:05Z....
The text was updated successfully, but these errors were encountered:
I think you've uncovered a really silly bug in the code, I'm assuming that getting a GPS fix in an airplane is really tough so the system is sending a bunch of location updates in batches. (like in your example, 7 at once, 16 at once, etc.) The app receives these updates all in one batch and applies the current time to all of them. The app should be offsetting the timestamp by the age attached to each individual location object.
Thanks for opening this issue! I will work on getting a fix out soon.
Did a recording on an airplane last week, with an interval of 30 s between points.
The gpx export file has wierd timestamps.
The first timestamp is just for one single position, the next is 9:15 minutes later and repeated for 7 positions, next is 8:48 later and repeated for 16 positions, next is one second later and repeated for 5, and so on.
Total of 300 points for a 2.5 hour trip so that adds up, but the timestamps are all wrong.
A graph of the elevation points gives a smooth curve so the position intervals is correct.
First points:
68,000 2023-12-18T05:05:50Z65,336 2023-12-18T05:15:05Z66,277 2023-12-18T05:15:05Z63,706 2023-12-18T05:15:05Z63,706 2023-12-18T05:15:05Z....
The text was updated successfully, but these errors were encountered: