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
The track was actually recorded on Aug 12.
At the beginning of the csv file, there are a few entries with the incorrect date (before the GPS was properly initialized). After that, the entries have the correct date.
So maybe the portal should look for the first entry with a GPS position?
(Not sure why this happened on the sensor side. The sensor was also running the day before and recorded the correct date, so the GPS should have known the correct time.)
The text was updated successfully, but these errors were encountered:
This is an issue with the GPS module we use which sometimes reports the wrong date. There is a corresponding issue on the firmware side. There's debugging in place to allow diagnosing it more. I'm not sure that waiting for dates with a GPS position will fix it.
One option would be to report both start and end dates on the portal side.
For this track, the recording date ("Aufgezeichnet am") is incorrectly shown as "6. Aug. 2023, 02:02":
https://portal.openbikesensor.org/tracks/2jqdpvxb
The track was actually recorded on Aug 12.
At the beginning of the csv file, there are a few entries with the incorrect date (before the GPS was properly initialized). After that, the entries have the correct date.
So maybe the portal should look for the first entry with a GPS position?
(Not sure why this happened on the sensor side. The sensor was also running the day before and recorded the correct date, so the GPS should have known the correct time.)
The text was updated successfully, but these errors were encountered: