Closed gnusupport closed 3 years ago
Please export same track directly from mobile device and post here.
Please export same track directly from mobile device and post here.
I have tried it, now I see that time is correctly recorded. But this is definitely not always. This is track that I did not yet finish.
<?xml version='1.0' encoding='UTF-8' standalone='yes' ?>
We still don't know if it happens on the client or on the server. Next time you encounter incorrect timestamps on server check the timestamps in client export.
This could be old GPS chipset rollover bug. Generally it shouldn't happen as I fixed it in version 3.3. Maybe the fix does not work in all cases? Was your last test track (with good timestamps) recorded on the same device as previous ones?
We still don't know if it happens on the client or on the server. Next time you encounter incorrect timestamps on server check the timestamps in client export.
This could be old GPS chipset rollover bug. Generally it shouldn't happen as I fixed it. Maybe the fix does not work in all cases? Was your last test track (with good timestamps) recorded on the same device as previous ones?
Last test track was recorded from same device, but now I am uploading from other devices, I used Motorola E and E LTE mobile phones. What I think is that I maybe did not update the software from F-Droid, and that after update it started working well.
Do you know formula to use to add time to incorrect times? Should I just add 20 years? I will experiment with it.
Please keep this issue open until I confirm that in new versions of µlogger I do not get this problem.
You must add exactly 1024 weeks. The problem was most probably not updated version of µlogger.
You must add exactly 1024 weeks. The problem was most probably not updated version of µlogger.
I have made some Emacs Lisp functions to add 1024 weeks, and to
replace the line with it. Then it can be automated by using macro F4,
F4, and there could be different other ways to replace it with sed
for example or other tools.
You may close this issue as now I do not see problem taking place any more.
(defun rcd-sql-time-add-1024-weeks (timestamp) (let ((sql (format "SELECT '%s'::timestamp + interval '1024 weeks'" timestamp))) (rcd-sql-first sql cf)))
(defun rcd-gpx-replace-time () (interactive) (let ((line (thing-at-point 'line t)) (match (string-match " ((start (+ 6 (string-match "" line))) (when (and start end) (let* ((timestamp (substring line start end)) (new-time (rcd-sql-time-add-1024-weeks timestamp)) (first-part (substring line 0 start)) (last-part (substring line end (length line))) (new-string (string-trim (concat first-part new-time last-part)))) (beginning-of-line) (kill-line) (insert new-string)))))))
Hello,
I can see this error since quite some time. You can observe it below. Though the track names say they were made in 2021, the actual timestamp is in 2001. This has been obtained by downloading the GPX from the server. Now where is exactly the error, I do not know. Maybe the mobile application makes the error, maybe server, maybe download of GPX makes the error with timestamps.