-
Notifications
You must be signed in to change notification settings - Fork 16
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
Update bicycle weighting profile? #200
Comments
brouter actually only generates that impressive-looking route because it has a default to absoultely follow long-distance cycling routes where they exist. That alone makes it very european-centric, and such performance is not likely to be generally repeatible in other locations. Removing that bit of the code reverts to actually worse-looking routes than current dodgr, so profile will be left as, is for the moment at least. |
For reference, these were the modifications I made to weighting profiles to compare: Current bicycle profile
Equivalent brouter profileThese are roughly the equivalent values from
|
The [
.
brouter
algorithm] includes some really detailed profiles, and generates very good routing. One quick check for routing in Muenster along the promenade was perfect;In comparison, graphhopper is okay:
![image](https://user-images.githubusercontent.com/6697851/227921046-7a390e94-9e38-41c8-9704-d01f4819c394.png)
but initially goes along a road rather then promenade, whereas both OSRM and Valhalla are rubbish, and just route along car roads instead of the Promenade. Current
dodgr
algorithm for bikes still gives way too much weighting to car-laden roads. The cost factors are far more variable and sensitive to different types of ways than current dodgr equivalents. Plus another issue with this package is that the actual weighting profiles are all contained in a binary and not a text file, so are not directly accessible outside this package. That should also be changed.The text was updated successfully, but these errors were encountered: