Skip to content
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

car profile - Parse width as float and make a multi-step penalty out of it #6766

Open
flohoff opened this issue Jan 9, 2024 · 0 comments
Open

Comments

@flohoff
Copy link

flohoff commented Jan 9, 2024

Currently we only have one step for penaltys of width which is <3m or lanes=1 on a bidirectional way.

It makes a difference if a higher class road is 4m or 6m as with 4m you wont be able to pass other cars so you will have some reduction in average speed.

So introduce more steps in the penalty for width e.g. <6m which is a small penalty as there be issues with trucks passing, below 5m which is you wont be able to pass trucks without going out to the shoulder 4m which is you wont be able t
o pass a truck with a car, and 3m where basically one has to go back to let the other pass, or find some passing spot.

I ran this change with >1 Mio routes on top of changes in issue #6762 #6757 and checked for issues.

Overall observation is that now routes tend to slightly stay longer on the higher class road network.

Route quality in areas where width has been tagged more increases.

Here is a commit on top of the other changes - see branch

https://github.com/flohoff/osrm-backend/tree/routeqa

and this addon change

https://github.com/flohoff/osrm-backend/tree/width-penalty

Here is the commit:

flohoff@7a2b089

Flo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant