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

New Quest: Do these traffic lights have a button? #574

Closed
hsimpson00 opened this Issue Aug 30, 2017 · 20 comments

Comments

Projects
None yet
7 participants
@hsimpson00
Copy link

hsimpson00 commented Aug 30, 2017

Hi, this is a series of new possible Quests to give more details for pedestrian traffic signals. Since there are already quests for these crossings, it shouldn't be hard to implement these (I'm not a programmer, but I guess so).
The point is, that it's a good thing for disabled, especially blind people, to now, if the traffic light is button_operated, has a sound, etc. But these informations are very rare on OSM, because you don't notice them as a normal person.

Necessary Tags on the Node:
highway=crossing + crossing=traffic_signals
Sould also work for:
highway=traffic_signals + crossing=traffic_signals

General

Affected key(s) (or tags) to be modified: button_operated=yes/no
Question asked: Is this crossing button operated?

Affected key(s) (or tags) to be modified: traffic_signals:sound=yes/no
Question asked: Are there sound signals for visually impaired people?

Affected key(s) (or tags) to be modified: traffic_signals:arrow=yes/no
Question asked: Is there a tactile arrow available at the traffic light pole? (mostly unter the button)

I think these are the most common supports for blind people at traffic signals, the other ones are too rare to make an own quest for them.

Checklist

Checklist for quest suggestions (see guidelines):

  • [x ] 🚧 To be added tag is established and has a useful purpose
  • [x ] 🤔 Any answer the user can give must have an equivalent tagging (Quest should not reappear to other users when solved by one)
  • [x ] 🐿️ Easily answerable by everyone from the outside
  • [x ] 💤 Not an overwhelming percentage of elements have the same answer (No spam)
  • [ x] 🕓 Applies to a reasonable number of elements (Worth the effort)
@rugk

This comment has been minimized.

Copy link
Contributor

rugk commented Aug 30, 2017

Also traffic_signals:vibration could be nice/useful. It is strongly correlated to traffic_signals:arrow=yes/no as it is the same place. So with a simple image you can also point user, who have never heard about that to the position "under the button" (as you said).

AFAIK it is quite common in Germany, I've actually never heard of the arrow, but I'll take a look touch next time whether it is just the button or there is really an arrow.

@rugk

This comment has been minimized.

Copy link
Contributor

rugk commented Aug 31, 2017

Okay, so maybe traffic_signals:arrow and traffic_signals:vibration is often combined. (And BTW, they should of course only be asked if the crossing is button_operated=yes) I mean combing them makes the most sense…

@hsimpson00

This comment has been minimized.

Copy link

hsimpson00 commented Sep 2, 2017

And BTW, they should of course only be asked if the crossing is button_operated=yes

+1

I didn't know that vibration is used that open. The only problem I can see is, that it's maye not that obvious to find out.

I mean combing them makes the most sense…

I would seperate the questions, but make them dependent of each other:
-Arrow only if button=yes
-vibration only if arrow=yes

@rugk

This comment has been minimized.

Copy link
Contributor

rugk commented Sep 2, 2017

Yeah, maybe. For vibration you just have to press the button at the bottom (the one with the arrow). And both the arrow and the vibration need an image showing the user where to press/touch.

@hsimpson00

This comment has been minimized.

Copy link

hsimpson00 commented Sep 11, 2017

Hi,
I have to correct myself:
Of course, there are Traffic signals which are not button operated, but do have an arrow, sound and so on.
These devices (the newer ones) naerly look the same as the normal buttons, but they don't have a touch sensor and also no display. Instead they are only yellow withe the three black dots which mark the Infrastructure for blind people.
Regards

@rugk

This comment has been minimized.

Copy link
Contributor

rugk commented Sep 12, 2017

Instead they are only yellow withe the three black dots which mark the Infrastructure for blind people.

Yeah, of course… That's the thing nearly everyone "pressed", because one thinks it goes faster, then… 😉 😆

@matkoniecz

This comment has been minimized.

Copy link
Contributor

matkoniecz commented Jul 14, 2018

Is there a tactile arrow available at the traffic light pole? (mostly unter the button)

Can you give an example photo? I have no idea what is described here.

Not an overwhelming percentage of elements have the same answer (No spam)

Where traffic_signals:sound would not be overwhelmingly no? Maybe ask only for major roads, maybe only in some countries...

@ENT8R

This comment has been minimized.

Copy link
Contributor

ENT8R commented Jul 14, 2018

I found the following picture:
Traffic light button
The button is also explained in the following article: https://digitalcosmonaut.com/2013/berlin-traffic-lights-youre-using-wrong/
And it seems like it is a thing which exists only in Germany...

@goldfndr

This comment has been minimized.

Copy link
Contributor

goldfndr commented Jul 14, 2018

I've seen some newer pelican crossings here in the US where the large pushbutton had a large embossed arrow on it indicating the direction of travel; I don't have a photo, sorry. The older pushbuttons are a bit less than fingernail size, not the best feel for pushing.

@goldfndr

This comment has been minimized.

Copy link
Contributor

goldfndr commented Jul 15, 2018

Here are a couple of snapshots I took today.

overview
closeup

matkoniecz added a commit to matkoniecz/Zazolc that referenced this issue Nov 19, 2018

@matkoniecz

This comment has been minimized.

Copy link
Contributor

matkoniecz commented Nov 19, 2018

I started testing one of ideas from this issue - adding traffic_signals:sound tag in #1268

I see no real value in collecting button_operated as there is no easy way to check what exactly the button is doing. In many cases buttons are left as placebo/to save money necessary to remove them despite that pressing button is changing nothing.

traffic_signals:arrow seems to be present only locally and I see no good reason for collecting this data anyway.

matkoniecz added a commit to matkoniecz/Zazolc that referenced this issue Nov 20, 2018

@rugk

This comment has been minimized.

Copy link
Contributor

rugk commented Nov 20, 2018

In many cases buttons are left as placebo/to save money necessary to remove them despite that pressing button is changing nothing.

"[citation needed]" 😉 At least this is the first time I hear this, but nevertheless, I agree with your conclusion and guess the "sound" thing is really the most important value.

@westnordost

This comment has been minimized.

Copy link
Owner

westnordost commented Nov 20, 2018

I read the last article you linked. After reading, it is clear that surveyors will have to survey what they find on the ground: whether there is a button or not.

It is not really possible to find out how exactly or if at all and at what times the button does anything, because it is software controlled. So even if the exact behavior can be found out, it may change at any time in the future. Same thing with street lamps - that's why we survey if there are street lamps or not, not if they are on during all the night.

So, this ticket is now about button_operated. I agree that the rest can be ignored.

@westnordost westnordost changed the title New Quest: More informations on crossing=traffic_signals New Quest: Do these traffic lights have a button? Nov 20, 2018

matkoniecz added a commit to matkoniecz/Zazolc that referenced this issue Nov 20, 2018

@rugk

This comment has been minimized.

Copy link
Contributor

rugk commented Nov 20, 2018

Don't know though whether the information "button_operated" does provide any real enhancement to the OSM data/has a use case. I mean the other things are obviously about accessibility, but whether I can press a button – is this something I care about as a blind or not blind user – I doubt so?

@westnordost

This comment has been minimized.

Copy link
Owner

westnordost commented Nov 20, 2018

@matkoniecz

This comment has been minimized.

Copy link
Contributor

matkoniecz commented Nov 20, 2018

It also can be helpful in routing for blind people to mention that it may be necessary to press the button at a given crossing to get green light.

westnordost added a commit that referenced this issue Dec 2, 2018

Merge pull request #1269 from matkoniecz/button
ask whatever traffic lights have button, fixes #574 [change icon background]
@call-me-matt

This comment has been minimized.

Copy link

call-me-matt commented Dec 25, 2018

Hi there. Good idea, useful addon! Concerning sounds, should this distinguish between yes, walk, and locate as described in the wiki?

@matkoniecz

This comment has been minimized.

Copy link
Contributor

matkoniecz commented Dec 25, 2018

If you think that it is necessary - please open a new issue with https://github.com/westnordost/StreetComplete/issues/new , comment like this may be easily missed.

@call-me-matt

This comment has been minimized.

Copy link

call-me-matt commented Dec 25, 2018

If you think that it is necessary - please open a new issue with https://github.com/westnordost/StreetComplete/issues/new , comment like this may be easily missed.

OK, done

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