-
Notifications
You must be signed in to change notification settings - Fork 66
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
Question about route_dodgr #331
Comments
Although it would be hacky, I wonder if there is a way for me to split all the lines in my network into smaller lines before doing the routing. That would stop this happening I think. Maybe I can use |
Thinking out loud, what the |
Yeah, you're right that snappping first to line, then to node in line, would be the way to go, but that is waaaay more computationally complicated, and so currently beyond the scope of dodgr, unfortunately. |
Fair do, thanks for the clarification. |
Hi @Robinlovelace and @mpadge ,
More a question, than an issue. When using
route_dodgr
with coordinates, does the function automatically snap the location to the nearest node on the network before starting the routing? I guess it probably does? I've been going around in circles trying to understand strange routing results, and I think that this must be the reason.For example ....
The text was updated successfully, but these errors were encountered: