Closed tytoalba99 closed 2 years ago
Please provide a sample GPX file, otherwise there is nothing I can do about it.
Please find attached a sample file. Note the original date and origin coordinates have been altered for privacy. GP3610B.lrv EDITED.gpx.zip
The provided data file does not contain any sub-second time info. It only contains broken data with multiple positions at the same time. If an application does display the data in some way, than it must do some "magic guessing" instead of working with the actual data.
The creator of the file is however gpxgo, not Gopro Hero according to the header, so it is hard to say, if the data was already broken in the original source or was crippled during some conversion. Anyway, you should report the issue to the creator of the data, that shall use proper time fractions as specified in xsd:dateTime/GPX specification and not produce broken files with multiple positions at the same time.
Indeed: I also think that the original correct GPX of Gopro Hero has been corrupted by editing it incorrectly afterwards. Out of the 1722 position-timestamps, only 95 are unique. If you remove the timestamps (with a macro in Notepad++) it works fine, see screenshot. @tumic0: is it officially allowed to remove the timestamp per position from a GPX-file?
I know the GPX may be not very well formed (i’m not the author). And the high frequency of samples the Gopro creates at low speed may difficult it even more. But all my GPS related applications handle them very well: Garmin Basecamp, Trailrunner,….
Indeed: I also think that the original correct GPX of Gopro Hero has been corrupted by editing it incorrectly afterwards. Out of the 1722 position-timestamps, only 95 are unique. If you remove the timestamps (with a macro in Notepad++) it works fine, see screenshot. @tumic0: is it officially allowed to remove the timestamp per position from a GPX-file?
Just changed year and month, and highest degree values.
GPXSee can also display the file "correctly", but you have to set the pause detection parameters manually (with min. speed 0.1km/h you get the same results as on your images). It's just that the default auto-adjust algorithm based on data statistics fails, if your data is garbage like in the sample file.
If you wonder, why pause detection matters, than it is because GPXSee filters all the movements during the pause period, so your distance/route gets not affected by the "GPS error movements" during that time.
Solved changing the speed settings ! Thank you
Hi,
The application has problems to render 10 Hz (samples per second) GPX files. When I extract the coordinates from a Gopro Hero 5 video straight lines are rendered. See the comparison from the same GPX file in GPXsee and Adze Lite. Imagery is different (Google vs OSM) but you can see the different path.
Congratulations for the application as I use a lot.