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

UK speed limit quest inaccurate in built up areas #1037

Closed
mwild1 opened this issue Apr 29, 2018 · 8 comments
Closed

UK speed limit quest inaccurate in built up areas #1037

mwild1 opened this issue Apr 29, 2018 · 8 comments
Assignees

Comments

@mwild1
Copy link

mwild1 commented Apr 29, 2018

The speed limit quest explicitly asks the user about signs, however not every road will have a sign. This is especially true in built-up 30mph areas where street lighting is present.

Currently the quest let's you answer 'no sign' but then appears to assume this means national speed limit applies.

Sources:

@westnordost
Copy link
Member

westnordost commented Apr 29, 2018 via email

@mwild1
Copy link
Author

mwild1 commented Apr 29, 2018

That's something I'm not 100% clear on (I'm no OSM expert, just trying to contribute casually), which is why I limited my issue to the problems with what the user sees.

The wiki is not exactly clear with "Recommended tagging" listing multiple different incompatible ways of tagging!

There was a long discussion in #492 which led to the current implementation, but focused on issues with the national speed limit (which varies on different types of road, as well as different types of vehicle).

I notice this quote though from #492 (comment):

The UK consensus was to always add a numeric value in maxspeed, use maxspeed:type to clarify whether the value was absolute (explicitly signed as such) or a national speed limit (denoted by the black bend on white sign).

However all of the above seem to agree that there should be a numeric value, which for 30mph often means there is no sign in the immediate vicinity (30mph areas typically have street lights, and street lights legally mean 30mph if there is no sign).

@westnordost
Copy link
Member

I read your links. The second link you posted contains the following paragraph (not the sentence in bold):

Any road with regular street lighting has a default speed limit of 30 mph unless signs indicate otherwise. The entry to a 30 mph zone must be marked by a "30" sign on both sides of the road, but no repeater signs are permitted within the zone (on the grounds that they might be confusing if some roads had them and others didn't). "30" roundels on the road surface are however permitted, with a special dispensation.

This sounds like the sections within a built-up area with "implicit" speed limits actually do have a sign at the very beginning of the road.

@mwild1
Copy link
Author

mwild1 commented Apr 29, 2018

That's correct. There is always a sign upon entry to the 30mph area. However that does not mean that any given road will have one at either end, which is what the quest currently asks the user.

I was on a road in a residential area and the app asked about the speed limit sign - it made me not answer, because I didn't want to accidentally imply that a sign existed where one didn't (this was before I began the research into what the app currently does, and what the correct tags ought to be).

The nearest sign in my case would have been several minutes walk, crossing several road junctions. The app did not make it feel right to answer "30" (which is what I knew the limit to be) when there was no sign at either end of the road I was surveying.

So ultimately I think there are two possible solutions:

  1. Make the quest about speed limits, and not ask specifically about signs - it's fairly obvious when you're in a 30mph area.

or

  1. Add a bit more logic to the "There is no sign" answer, which asks if the road has street lights. A single track road with no signs and with street lights would automatically be 30mph.

@westnordost
Copy link
Member

2 would be an option, but it seems inconsistent to not tag a maxspeed:type on an implicit speed limit within a built-up area in UK but use a completely different tag to infer an implicit speed limit.
After all, the maxspeed:type tagging is an invention of the British OSM community.

My concern is additionally, that it might make things more complicated for data consumers who will have to infer the implicit speed limits then because then they not only have to look at road type and maxspeed:type (et al) but at theoretically any tag.

Anyway, this is something that the community should decide. I will post a question in the forum or on the British mailing list in the next days.

@westnordost westnordost self-assigned this Apr 29, 2018
@westnordost
Copy link
Member

westnordost commented May 1, 2018

By the way, 1 is not an option because of the reasons discussed in #457

@westnordost
Copy link
Member

So I posted to the mailing list, one reply was especially helpful: Someone extensively researched the legislative situation in the UK and wrote it down here: https://wiki.openstreetmap.org/wiki/User:Jamicu/UK_Speed_Limits

The quest will now ask after the user confirmed that there is no sign whether the street is lit or not. If it is lit, maxspeed:type=nsl_restricted will be tagged. If not, it will ask the usual "are the carriageways segregated?" question.
In case that the road is already tagged with lit=yes or no, it will skip the "is the road lit" question.

@SomeoneElseOSM
Copy link

For completeness, the mailing list post is https://lists.openstreetmap.org/pipermail/talk-gb/2018-April/021319.html

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

3 participants