Bad dates and times in exported GPX files

[Kris Buelens]

As I'm exploring more of the GPX tracks I keep , I detected strange problems.  In quite a few tracks some track points have a wrong date but correct time.  Or both date and time are wrong, but the GPS position is fine.  Here an example (still with the <rtept> instead of <trkpt>)

<rtept lat="51.121967" lon="2.678361"><ele>51.0</ele><extensions><x:speed>7.7599998</x:speed></extensions><time>2024-07-19T09:51:54.000Z</time></rtept>
<rtept lat="51.121613" lon="2.6785731"><ele>50.0</ele><extensions><x:speed>8.47</x:speed></extensions><time>2024-07-19T09:51:59.000Z</time></rtept>
<rtept lat="51.121227" lon="2.6788328"><ele>50.0</ele><extensions><x:speed>9.08</x:speed></extensions><time>2024-06-10T10:29:34.230Z</time></rtept>
<rtept lat="51.120846" lon="2.6790764"><ele>51.0</ele><extensions><x:speed>9.12</x:speed></extensions><time>2024-07-19T09:52:09.000Z</time></rtept>

After changing <rtept> to <trkpt> I can display the GPX file using GPS Track Editor (GTE).  GTE lists the trackpoints found in the GPX file and displays a map.  Points with a bad date are listed a bit grayed out as shown in the screenshot that I attach.

I selected such a bad point, and GTE then shows a white circle on the map, this way you can see that the position is correct, only date and time are bad.

Remark as well that GTE shows clean arrows for "normal" trackpoints, and a little .  for places with bad dates. And see then how many dots are shown in the orange track arrows.

I can't reproduce the problem at will, it happens now and then, like 19 July, but it didn't happen on August 10.

Attached a screenshot of GTE showing an area with lots of bad date&times and both the original GPX extract, and the GPX where I changed <rtept> into <trkpt>

[mic...@mictale.com]

Thanks for the detailed feedback. The element name will be fixed in 4.5.25 (this time for real). Apologies for the late fix, it must have slipped through the cracks.

In terms of the timestamp: Could you please open the stream in GPS Essentials and check the timestamp? You can tap on every element of the stream and then tap on Properties to see all properties. I am interested to see if the date problem is there already. Please also (if there are no privacy concerns) export the stream as MFT and post it here. I could use this data to validate that there is no date formatting issue.


Regards, Michael
mictale.com/ms
--

> --
> You received this message because you are subscribed to the Google Groups "GPS Essentials" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to gpsessential...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/gpsessentials/0fa090e2-454f-43bc-bc45-9d9ba61e027en%40googlegroups.com.
> <Track-240719-114037-original.gpx><badDates shown in GTE.jpg><Track-240719-114037-rtept fixed.gpx>

[Kris Buelens]

Hi, thanks for your quick response.  I'm a bit late as I had to start digging...

I don't have any privacy issues with my tracks.

> You can tap on every element of the stream and then tap on Properties to see all properties

I may not fully understand how this works: I don't see something named "properties" when I tap on a point.  But, I can then tap on a small arrow near the top of the screen, and then I see a kind of popup window with time etc.  I guess it is what you expected to see.

But, it took me some time to find a better track to illustrate the problem, the one I included earlier doesn't suit well: I passed 4 times on the street where the bad timed points appear.  So I changed my Visual Basic Windows App to have it scan for tracks with the problem. and I found a very good one: Track-230906-090145

While collecting my screenshots, I did forget to adapt G¨S Track Editor's Timezone: it displays UTC, so 7 AM etc.  GPS E uses local time, so around 9 AM 

Quite some bad dates: one for point 142 and many around 230.  The first one is a lucky catch: right at a street crossing, easy to find it back on GPS E's display.  

And, yes indeed: the time in GPS E seems correct, for point 1: 6/9/2023 9:21:55 In the GPX file it became 20/7/2023 14:02:50

Point 2 is a bit harder to surely tap on the same trkpt.  But it seems OK: GPS E shows 9:34:33 and in the GPX file, the good points jump from 07:34:00  to 07:34:43, the bad points in between are dated 20/07/2023 14:xx:xx

I'll attach also the MFT formatted extracts of  6/9/2023 and 19/7/2024

And, if you find the bug, I hope it is also the the cause illustrated in by my own Windows App: sometimes only the time is bad.  Screenshot Sometimes time bad.jpg records 342 and 360 have only the bad time.  I just verified with GPS E: record 361 is bad, it should be 11:39, but in the GPX it is 11:19 (My App cannot know what is wrong: 360 or 361)

[mic...@mictale.com]

Can you send me your GPX export for Track-230906-090145 please? Not sure if I have it. I imported the MFT file and here is what I see around #142 in my GPX export (which looks ok)

<trkseg lat="50.781418" lon="4.5234213">
<ele>134.0</ele>
<extensions>
<x:speed>14.69</x:speed>
</extensions>
<time>2023-09-06T07:21:45.000Z</time>
</trkseg>
<trkseg lat="50.781036" lon="4.5226545">
<ele>138.0</ele>
<extensions>
<x:speed>13.759999</x:speed>
</extensions>
<time>2023-09-06T07:21:50.000Z</time>
</trkseg>
<trkseg lat="50.78067" lon="4.5219016">
<ele>138.0</ele>
<extensions>
<x:speed>13.48</x:speed>
</extensions>
<time>2023-09-06T07:21:55.000Z</time>
</trkseg>



Regards, Michael
mictale.com/ms
--

> To view this discussion on the web visit https://groups.google.com/d/msgid/gpsessentials/da4e4af6-3f17-49ce-96f9-df9a74f7a0c1n%40googlegroups.com.
> <Track-230906-090145.mft><Screenshot Essentials point 2.jpg><BadTime Point 1.jpg><BadTime Point 2.jpg><Track-240719-114037.mft><Screenshot Essentials point 1.jpg><Sometimes time bad.jpg>

[Kris Buelens]

Hi Michael,

I'll send you two copies: 

Track-230906-090145.gpx  the one as it comes out of GPSE (but with <rptpt>), not very readable as it is one long string

Track-230906-090145-fixed.gpx there I changed rtept to trkpt and I split the long string at certain points.  Line 148 is where the lat/long of you extract is present

(and be assured, the bad dates are present in the original gpx)

Kris Buelens,
     --- VM/VSE consultant, Belgium ---
-----------------------------------------------------------------------

Op vr 16 aug 2024 om 20:54 schreef <mic...@mictale.com>:

To view this discussion on the web visit https://groups.google.com/d/msgid/gpsessentials/83FC604A-1FEC-415F-8EAD-4250E183521B%40mictale.com.

[vengatesh A]

Gps is not working sir kindly help me

To view this discussion on the web visit https://groups.google.com/d/msgid/gpsessentials/CAHyxymJfgVeMKe7qVmBYdG0bPGbb9%2B0dCDPkX0EAwNy8m%2BvJZw%40mail.gmail.com.

[Kris Buelens]

With such a too short problem description, I think nobody can help you.

[vengatesh A]

Sir ,direction (compose) is not working

To view this discussion on the web visit https://groups.google.com/d/msgid/gpsessentials/e6aa5148-536c-40ea-a889-0cf9878a91b8n%40googlegroups.com.

[mic...@mictale.com]

I just found something that may cause this issue. To cross check, if you export the same file again, the wrong timestamps should be different. If so, the next version will fix this issue.


Regards, Michael
mictale.com/ms
--

> To view this discussion on the web visit https://groups.google.com/d/msgid/gpsessentials/CAHyxymJfgVeMKe7qVmBYdG0bPGbb9%2B0dCDPkX0EAwNy8m%2BvJZw%40mail.gmail.com.
> <Track-230906-090145.gpx><Track-230906-090145-fixed.gpx>

[vengatesh A]

I have completed bsc statistics. Any job vacancy

To view this discussion on the web visit https://groups.google.com/d/msgid/gpsessentials/CF265094-1B23-45F8-88F4-4FD5779A8E12%40mictale.com.

[vengatesh A]

[Kris Buelens]

Hello,

I extracted 230906 again, and now all timestamps are OK.  The wrong ones are different indeed, they now are perfect.

So I guess you found the bug.

Kris Buelens,
     --- VM/VSE consultant, Belgium ---
-----------------------------------------------------------------------

Op di 20 aug 2024 om 03:55 schreef <mic...@mictale.com>:

To view this discussion on the web visit https://groups.google.com/d/msgid/gpsessentials/CF265094-1B23-45F8-88F4-4FD5779A8E12%40mictale.com.

[mic...@mictale.com]

It is fixed in version 4.5.26, I would be surprised if you already have it on your device, rollouts typically hit devices in days not hours.

Assuming that I actually fixed the bug, it was a long standing one, and since it has never been observed, there must be something that you did different when you observed it. The bug has to do with multiple part of the app formatting dates at the same time, e.g. you were tracking while exporting. It would be interesting to know how you did it :-)

In any case, please wait for 4.5.26 and let me know if the issue is fixed. Also, you should see valid GPX files now including <trkpt> elements.

Regards, Michael
mictale.com/ms
--

> To view this discussion on the web visit https://groups.google.com/d/msgid/gpsessentials/CAHyxymKUe_BFQo5da9df1VdghUrPPiUY6n1%2BKD8anQoyWtXNpA%40mail.gmail.com.

[Kris Buelens]

Sometimes indeed I start an extract while the trzcking is still active, not often though.

I´m glad it is fixed.

Op di 20 aug. 2024 18:48 schreef <mic...@mictale.com>:

To view this discussion on the web visit https://groups.google.com/d/msgid/gpsessentials/508A4462-7510-45E6-8E6D-99BF24D94DA3%40mictale.com.

[Stef V]

That bug sounds very much like something I have been encountering for about 2 years now and why I had to switch to a different program. Most of the time when starting a new track I get immediately displayed some 5000km and an average speed of 59000 km/h.

I have mentioned and tried to call attention to that issue on this very list, but it never was taken up.

I still can't see version 26 on Play, but I sincerely hope I can once again use GPSE :)

To view this discussion on the web visit https://groups.google.com/d/msgid/gpsessentials/508A4462-7510-45E6-8E6D-99BF24D94DA3%40mictale.com.

[Kris Buelens]

I manually upleveled GPS Essentials from Google Store, but still got  4.5.24.

Kris Buelens,
     --- VM/VSE consultant, Belgium ---
-----------------------------------------------------------------------

Op di 20 aug 2024 om 18:48 schreef <mic...@mictale.com>:

To view this discussion on the web visit https://groups.google.com/d/msgid/gpsessentials/508A4462-7510-45E6-8E6D-99BF24D94DA3%40mictale.com.

[mic...@mictale.com]

The new version isn't rolled out to 100%. If you want new versions earlier, I recommend that you join the Beta program. Check out the aoo's detail page to find out how to join.

--Michael
mictale.com/ms
--

> To view this discussion on the web visit https://groups.google.com/d/msgid/gpsessentials/CAHyxymLRsN%3Droshzc%3D5LSJt9oxX8DujixsK8nMt%3D4fDYBu0TSw%40mail.gmail.com.