Skip to content
This repository has been archived by the owner on Mar 12, 2022. It is now read-only.

User-uploaded gpx traces need to use trkType #513

Open
meghanhade opened this issue Oct 31, 2017 · 1 comment
Open

User-uploaded gpx traces need to use trkType #513

meghanhade opened this issue Oct 31, 2017 · 1 comment

Comments

@meghanhade
Copy link
Contributor

trkType (for a track, as apposed to a route or a series of waypoints) should be used. rteType and 'wptType` will appear to work in the UI, but will throw errors in the console.

See gpx docs on trkType: http://www.topografix.com/GPX/1/1/#type_trkType

@rmglennon
Copy link
Contributor

This came up through support (see Desk 1194). The user sent a link to a Google Maps point dataset, which I converted to a Map Matching API call (through find and replace and regex), and to a CSV --> geojson --> GPX (via some random online converter).

In Mobility Explorer, when attempting to match, the UI does nothing/gives no error, but there are some generic console errors. It uses a wpt format, which are waypoints.

Here is the GPX file I using so we will have it for future testing (it is a zipped gpx file, as gpx cannot be uploaded directly).

<wpt lat="-23.5711158" lon="-46.6546438">
  <extensions>
    <ogr:lat>-23.5711158</ogr:lat>
    <ogr:lon>-46.6546438</ogr:lon>
  </extensions>
</wpt>

brazil.gpx.zip

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants