-
Notifications
You must be signed in to change notification settings - Fork 31
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
osrmIsochrone(): 'loc' is too far from the OSRM network but loc is not too far... #119
Comments
Hi! I'm having the same issue, also i noticed that only happens when you add a negative coordinate to the loc requirement, if you type positive positive coordinates it works. |
@gmachin11 Thanks for the hint! |
You're welcome, i tried for each combination of positive and negative, only worked for the positive positive one, like in here:
|
I think that this problem comes from the demo servers (http://router.project-osrm.org/r & https://routing.openstreetmap.de/). It seems that they do not manage the point encoding in google polyline format very well. Solutions:
|
Should be fixed in the dev version of the package. remotes::install_github('riatelab/osrm') |
Yes ! 👍 In fact I had inverted the coordinates of latitude and longitude in my first example and it was the reason why it did not work (the point was in the middle of the sea). 😞 |
@ACouillet |
@rCarto In fact, I deduced that among the 15000 points to be treated, some are connected to the network but on portions defined in OSM as roads not accessible to cars so logically the "car" isochrones cannot be calculated... Also, in some cases, it seems that portions of the network are poorly defined (after verification with IGN data, they should accept an iso calculation which is still impossible). It is therefore more a problem of characterization of the network in OSM than a malfunction of the program ! |
See:
Created on 2022-11-29 with reprex v2.0.2
The text was updated successfully, but these errors were encountered: