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

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


> So your solution [...] to return a totally invalid response?

Where exactly did I say that? In this ticket I just stated the problem, not a solution (yet).


In the JOSM ticket I suggested either the one-point-per-segment solution (but I have some concerns that the response would get quite huge) or an own extension that would allow waypoints to be unordered. So we'd still have the waypoint type and could use it inside some type that replaces "trackSegment" - therefore perfectly valid and unordered.

Something like this (with an appropriate XSD file linked)
``` xml
<gpx>
  <!-- metadatastuff -->
  <trk>
    <trkseg>
      <!-- all the trackable traces / waypoints as is -->
    </trkseg>
  </trk>
  <extensions>
    <osm:points unordered="true">
      <!-- all non-trackable waypoints -->
    </osm:points>
</gpx>
```

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/2208#issuecomment-482972558
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20190414/47847da8/attachment.html>


More information about the rails-dev mailing list