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

Discourage access=destination, access=customers #161

Open
graue opened this issue Aug 23, 2024 · 0 comments
Open

Discourage access=destination, access=customers #161

graue opened this issue Aug 23, 2024 · 0 comments

Comments

@graue
Copy link

graue commented Aug 23, 2024

I got a route that clownishly uses the Flower Mart parking lot to avoid a mixing zone on 5th Street:

image

This passes through a gate with access=customers set, which, along with access=destination, we should preferably not use for through traffic. We can approximate that by weighting the way as REACH_DESTINATION.

The easier subtask which wouldn't help in this specific case would be to weight ways with access=customers or access=destination (or the equivalent values more specifically for bicycles, e.g. bicycle=customers) that way. (Currently, it looks like those values of access aren't considered for bicycle routing at all.) Likely more complicated is to take into account the barrier=gate with those access values as well.

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

No branches or pull requests

1 participant