You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 12, 2022. It is now read-only.
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.
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).
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
The text was updated successfully, but these errors were encountered: