<h4>Followup of <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="377993833" data-permission-text="Issue title is private" data-url="https://github.com/openstreetmap/openstreetmap-website/issues/2046" data-hovercard-type="issue" data-hovercard-url="/openstreetmap/openstreetmap-website/issues/2046/hovercard" href="https://github.com/openstreetmap/openstreetmap-website/issues/2046">#2046</a></h4>
<p>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.</p>
<p>That however is violating the <a href="https://www.topografix.com/GPX/1/1/#type_trksegType" rel="nofollow">GPX standard that clearly states</a>:</p>
<blockquote>
<p>A Track Segment holds a list of Track Points <strong>which are logically connected in order</strong>. 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.</p>
</blockquote>
<p>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 <a href="https://josm.openstreetmap.de/ticket/16963" rel="nofollow">JOSM ticket #16963</a> (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.</p>
<p>Also related: <a href="https://josm.openstreetmap.de/ticket/17596" rel="nofollow">JOSM ticket #17569</a> (JOSM now fails to display lines for local GPX tracks without timestamps because of the hack for the non-standard GPX tracks from OSM)</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/openstreetmap/openstreetmap-website/issues/2208">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABWnLZDg_j84EMLNe3mhcyQ1H7c92J6Jks5vgyJhgaJpZM4cumDx">mute the thread</a>.<img src="https://github.com/notifications/beacon/ABWnLWbCS8uxrVLa2FzxJLPztW-UUlYmks5vgyJhgaJpZM4cumDx.gif" height="1" width="1" alt="" /></p>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/openstreetmap/openstreetmap-website","title":"openstreetmap/openstreetmap-website","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/openstreetmap/openstreetmap-website"}},"updates":{"snippets":[{"icon":"DESCRIPTION","message":"GPX files not following standard (#2208)"}],"action":{"name":"View Issue","url":"https://github.com/openstreetmap/openstreetmap-website/issues/2208"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/openstreetmap/openstreetmap-website/issues/2208",
"url": "https://github.com/openstreetmap/openstreetmap-website/issues/2208",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>