-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Distance matrix API #665
Comments
Usually we limit to ~20 locations to keep the request under few hundred milliseconds. You could do several requests then run ortools locally but I think using the manhattan distance as first approximation could be a reasonable choice as first approximation. note: if you don't have one way road you could only request half part of the matrix since you'll have a symmetric matrix... |
Seems like the OSRM folks are about to pull in distance-table functionality into the main branch. It's not the fastest way to do it but it's publicly available and supported. You can run your own server against a smaller map-set that should give you better performance than the figures quoted in the pull request: |
my 5 cents for OSRM |
»Or let the distance callback issue request for every single origin-destination pair. Never ever think about it |
Thank you very much all. OSRM was easy to setup and use. I haven’t tried it on a larger set of coordinates. However on a smaller set it works fine. |
@Mizux how do I go about using the API for 100 locations? Even after sending 25 locations in each request how do I take the values from the resultant matrices in a 100x100 matrix? |
Hi,
As most of you here are working on routing problem. I need a suggestion.
Bing, Google and other APIs are only providing 25x25 origin-destination matrix in one request. (for example: https://developers.google.com/maps/documentation/distance-matrix/usage-limits)
In our case, we have approximately close to 1000 locations. What would be the suggestion? shall we go with Manhattan distance or issue 25*25 request. Or let the distance callback issue request for every single origin-destination pair.
Thanks,
The text was updated successfully, but these errors were encountered: