- 1 Consolidation and Enhancement of disability tags
- 2 Use british English
- 3 Say how to make the words on the map bigger (for crying out loud)
Reason: The tags to describe information relevant for disabled persons are divided on some wiki pages and are not coordinated in all cases. We want to collect them at this page, tag them and discuss about possible tag-variations and missing tags.
traffic island for pedestrians crossing a street
Situation: There are traffic islands for pedrestian crossing a steet without a traffic signal or in the middle of large streets.
Discussion (please feel free to participate!)
- In which cases should the street be divided by lanes to build the room for the traffic island?
- I would say, it's better to divide the street than to use more complicated tags. It's better to have more nodes describing single entities than to have one node for the crossing describing two single (lane-) crossings and the island in between. User:Jongleur
- Always devide where devided. This is also helpful for visual representation and for avoiding "turn here" orders in navigations software for use in cars.--Lulu-Ann 15:57, 9 May 2010 (UTC)
- Should the traffic island be build as a node or as an area?
- How can the walking area on the crossing island be declared, that it can be identified by blind person with their blind stock.
- My interpretation highway:crossing is, that nodes where two systems cross are tagged with it. So it's the intersection point between the car's lane and the pedestrian crossing. The Node at the island should in this meaning be tagged as "highway:footway; crossing:island;" or something like that (not sure at the moment) User:Jongleur
- Which information is needed: "Is there a tactile difference between driving land and traffic island? Is there even a tactile paving guiding line for the blind? Is the curb lowered or high? Is it at 3cm, which is detectable for the blind and crossable for a wheelchair? Is there another pedestrian traffic signal, or is the first signal valid for both sides of the traffic island (usually not)? --Lulu-Ann 15:57, 9 May 2010 (UTC)
- Sloped_curb=yes is not enough for wheelchair-routing. At least we should prefer a distinction between zero curbs (ideally together with tactile paving to prevent danger for blind people), sloped curbs (in Germany that should be 3cm high) and non-sloped-curbs (aproximately 8-12cm, I think). The best would be real measuring, but I fear, that's far from reality because of the measuring problems. User:Jongleur
- sloped_curbs should get an extra node at each side of the island (and at the borders of the street). Benefits: User:Jongleur
- it's possible to calculate the depth of the island as distance between the nodes.
- the part between the two sloped_curves can be seen as "save area"
- we don't need to distinct between sloped_curb:left and sloped_curb:right, sloped_curbs are seen as a kind of barrier on the way.
- sloped_curb:left and :right does not work here anyway, because sloped curbs are at the end of a way and a the beginning at another (change of surface forces splitting of ways).
- How can we give the information if there is a bike lane along the pedestrian crossing? --Lulu-Ann 15:57, 9 May 2010 (UTC)
Pictures and current tagging
node on traffic island: node highway=crossing crossing=unmarked;island surface=asphalt sloped_curb=both tactile_paving=no wheelchair=yes nodes on both footways, where the crossing way starts and ends: sloped_curb=yes
|1b||* how to tag the sloped curb at the crossing island? Its about 0.02 to 0.03 high, a single cross row of cobble stones.|
|1c||detailed view of the surface of a different crossing island||way from footway to footway crossing street: way||* how tag the sloped curb at the crossing island?|
future models (for discussion)
Situation: Tram platform with relevant elements
pictures and sample tagging
|2a|| tram platform: way
tram entry point: node Template:Railway 
| * key crossing correct value or define a new value island or unmarked_island?
crossing ways between vehicles and pestrians, with traffic signals
placeholder: This issue will be filled in short time
highway=traffic_signals should be used only between ways, where the crossing ways will be used by vehicles. This key-value combination is used wrong, when a way for vehicles is crossing a way for pedestrian. In this case, the tagging should be: highway=crossing crossing=traffic_signals, crossing_ref=*
This wrong tagging could be found automatically by quality assurance tools, like keepright. In this case, the rule would be (in normal language):
-- check, if the node is only used by one way. If it is not permitted for vehicles, its incorrect.
-- check, if the node is only used by one way. If it is permitted for vehicles, but has no tags like crossing=*, its probably for crossing traffic, but has a wrong position (is has to be at the crossing node instead).
-- check, if the node is used by more than one way, but only one way can be used by vehicles. If there is the additional tagging crossing=traffic_signals, it should be instead: highway=crossing crossing=traffic_signals
-- check, if the node is used by more than one way, but only one way can be used by vehicles. If at least one of the other ways is for pedestrians, its correct tagging is probably highway=crossing crossing=*
In the cases, where we can define roles, we should make sure to bring this information into quality assurances tools like keepright.
Use british English
"Curb" is AE, in BE use "kerb". Please change this in the whole wiki where you can find it for consistency reasons. -- Dieterdreist 12:17, 21 September 2010 (BST)
Say how to make the words on the map bigger (for crying out loud)
The older user rolls his mouse wheel to zoom in... and the words momentarily become large enough to read... and then shrink back again to their small size with no choice for anybody in the matter. Jidanni (talk) 16:32, 20 April 2013 (UTC)