4 ms·
The only thing I don't like about OSRM (the public facing version, not sure if the Docker one has this limitation) is that the route planning is limited in the
by denysvitali 3y ago
The only thing I don't like about OSRM (the public facing version, not sure if the Docker one has this limitation) is that the route planning is limited in the number of waypoints.
I'm planning a trip to the west coast and have 50 POIs (coordinates) collected from Wanderlog that I want to visit. I just run a small TSP algorithm over that list and have an ordered collection of points for which I want to calculate the route for.
Unfortunately it seems like OSRM doesn't like my 50+ waypoints, thus I can't really plot the trip.
I'll probably give it another try locally, and then make a PR. It also looks like the only way to get a route across waypoints is to make a GET request, so just imagine how long the request path will be with 50 points :'(
That calls out for a new POST endpoint.
- Doctor_Fegg 3y agoThat’s the public instance. It’s a runtime flag to osrm-routed so if you set up your own instance, you can configure it how you like. (Or use the Node or upcoming Python bindings.)
- denysvitali 3y agoStill, most likely passing 50+ waypoints in the URI might cause other issues
- Doctor_Fegg 3y agoI can't speak for the most recent version, but I regularly pass 200+ waypoints to a fork of OSRM 4.9 and it works fine. If you were to use the Node/Python bindings and hence avoid any webserver limitations you should be ok.
- denysvitali 3y agoAwesome, thanks!