[openstreetmap/openstreetmap-website] GPX files not following standard (#2208)

bjoeni notifications at github.com
Sun Apr 14 12:43:13 UTC 2019

#### Followup of #2046

When downloading public GPX traces through the API, all waypoints of non-trackable traces are randomized (or rather sorted by lat/lon) and delivered as one trackSegment for privacy reasons.

That however is violating the [GPX standard that clearly states](https://www.topografix.com/GPX/1/1/#type_trksegType):
> A Track Segment holds a list of Track Points **which are logically connected in order**. To represent a single GPS track where GPS reception was lost, or the GPS receiver was turned off, start a new Track Segment for each continuous span of track data.

The API should return a valid GPX file, i.e. by using a custom extension, so that unordered waypoints are never in a trackSegment. That would also have avoided [JOSM ticket #16963](https://josm.openstreetmap.de/ticket/16963) (when JOSM tried to display all unordered waypoints as a continuous  track), though I see how that situation required an immediate fix for privacy reasons, but it should imo not be a permanent solution.

Also related: [JOSM ticket #17569](https://josm.openstreetmap.de/ticket/17596) (JOSM now fails to display lines for local GPX tracks without timestamps because of the hack for the non-standard GPX tracks from OSM)

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20190414/2333374b/attachment.html>

More information about the rails-dev mailing list