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

Road usage ignores cycleways #280

Open
gluap opened this issue Sep 22, 2022 · 3 comments
Open

Road usage ignores cycleways #280

gluap opened this issue Sep 22, 2022 · 3 comments

Comments

@gluap
Copy link
Contributor

gluap commented Sep 22, 2022

Currently we only import ways where we consider the possibility that a bicycle can be overtaken. This excludes cycling ways, and for the evaluation of overtaking events that is good.

Hovever to evaluate the road usage meaningfully we would sensibly consider all cyclable ways - otherwise we will not faithfully show where OBS have driven. Oftentimes this does not appear as a problem, but for instance here the "laerer landweg" is an integral part of the cycling infrastructure - its usage gets overlooked in the road usage because it is cycling/walking only.

image

@opatut
Copy link
Member

opatut commented Sep 22, 2022

I am a bit torn here.

We should allow the track to be matched as "someone cycled here". Especially for these cases where we want to see whether people take detours to avoid bad roads.

However, if you press the button there, how should that count? What if there are service vehicles allowed and you happened upon one? What if people regularily drive their car on a road restricted for motor vehicles? I know at least one of these in my town.

I think outright ignoring these roads where cars shouldn't exist is not the solution. Likewise, ignoring roads where bicyclces shouldn't cycle is also not true to the real world. We might need to introduce a scoring system to guess what actually happened. In this case, nobody pressed the button, so it is more likely that the cyclist crossed the trunk road on the cycleway that is forbidden for cars.

@gluap
Copy link
Contributor Author

gluap commented Sep 22, 2022

I agree - for button presses on cycling-only ways there is no easy solution. Long-term we might flag them as "ask the user before counting it". I think finding an automatic way answering the question "what did the user press the button for" is hard and the first step might be to ask people about specific button presses - maybe the openstreetmap is wrong (cycling way absolved from mandatoryness), maybe there's service vehicles - hard to tell just from a track, the openstreetmap and a button press.

But I'd claim that for the road usage allowing all roads that can be cycled will be mostly right.

@opatut
Copy link
Member

opatut commented Sep 26, 2022

allowing all roads that can be cycled will be mostly right

"can" (not "is allowed to") is the key here, I'd say let's ignore motorways and state highways if those are generally restricted, and ignore other tags. In urban areas, people will always be cycling where they are not supposed to, such as service roads (e.g. bus and tram lanes), footpaths, and the like. Let's try to reduce matching to those ways if there are better alternatives though, e.g. if the bus lane is parallel to a normal road, then probably the cyclist used the normal road, even if the GPS track is more aligend with the service road.

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

2 participants