Open hugovk opened 5 years ago
Just my two cents: Since you will invariably have to prepare gpx files these days anyway, i'm afraid the solution of cleaning up bogus trackpoints is outside the scope of this script. A trackpoint with no coordinates is pointless (sorry about that 💃 ).
I have a GPX from my Strava ZIP that looks like this (I've snipped away most of the track points), where the first
<trkpt>
has nolon
orlat
attributes:Putting that at
/tmp/test/test.gpx
and running:It probably happens because the first track point doesn't have latitude or longitude attributes (see GPX above).
Can such track points be skipped?
About the data: the problematic file was generated by combining two files using this tool, which is recommended by Strava so will be quite widely used. I don't have the original pre-merge files handy to check if the same issue occurs there or if it was introduced by the merge tool.