-
Notifications
You must be signed in to change notification settings - Fork 8
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
When a road has different cycling facilities in each direction #3
Comments
cycleway=shared_lane should not add any weight probably? Every road is a shared lane really. (it is not required to use the dedicated bike lanes). |
Probably, yes |
The model currently looks to see if a cycleway=lane is present in order to classify the way as "having a bike lane". Then it applies the rules for the bike lane such as speed, #lanes, parking, etc. to determine the LTS level. In the above case, it doesn't really make any difference if the cycleway=shared_lane tag is there or not. If we take a worse case approach, then we have to ignore any cycleway:left or cycleway:right tags unless they are both there (and then it's going to get tricky depending on the tag value). |
When I did the CRD (Victoria, BC) bike map, we would default to the lower comfort/separation when it came to these situations. We figured that it be better for somebody to come across a bike lane and be pleasantly surprised than the other way around. |
Do we handle this somehow? I guess we should take into account the worse of the two.
For example, O'Connor South of 417 has
cycleway=shared_lane
NB andcycleway=lane
SB: https://maps.bikeottawa.ca/lts-map/?&lat=45.40771305197882&lng=-75.68707579843912&id=way/591035923It has LTS-1 but IMO should be LTS-2. Is it because the model thinks there is a dedicated lane on either side?
The text was updated successfully, but these errors were encountered: