GPX File Export

[drtbyk]

I created a route on the OSRM Routing map and tested the GPX File download of my generated route. The GPX file is coded as a GPX Direct Route. This can yield thousands of route points. In addition, any intermediate destinations are also coded in to the route as a route point and as such their importance is lost.

This GPX coding is problematic for any stand alone GPS device as the route will be interpreted as a Direct Route and will have more points in it than most GPS devices can accept for a Direct Route. A more productive GPX export would be to code the path as a GPX Track where point count is not as limited and code the Start, Stop and Intermediate Destinations as GPX Waypoints there by preserving their importance to the route on any GPX capable device.

[DennisOSRM]

Thx for flagging this.

[drtbyk]

My pleasure.

Cheers,
Dan

[DennisOSRM]

What are reasonable bounds on the number of points these devices can manage?

[drtbyk]

Dennis,

Most GPS devices today can manage Tracks with upwards of 10,000pts. Many of the newer devices can manage Tracks with 15,000pts. But, even if you wanted to cap the export at 5,000pts it should be sufficient for most routes under 300mi.

Cheers,

Dan

On 2014Oct16, at 4:56 AM, Dennis Luxen notifications@github.com wrote:

What are reasonable bounds on the number of points these devices can manage?

—
Reply to this email directly or view it on GitHub.

[daniel-j-h]

GPX support was removed, also see ticket #1489.

[kolesar-andras]

I'm missing GPX output. Is there a chance to implement it again? Can I help you?

[TheMarex]

No we are not looking to support other formats in the backend. If you want to help, it would be great to have something that can transform an OSRM JSON response into GPX on the client. Maybe as Javascript library?

[daniel-j-h]

hint hint https://github.com/tyrasd/togpx :)