From OpenStreetMap Wiki
Jump to: navigation, search

"(Note: may be considered normal or yes pending discussion.)"

Where is this discussion? URL? Surely not "normal" as usually in France or Germany, lowered is rather the norm at crossings and the page seems to be related to crossings (as nodes are referred in the first sentences).

Yes is descriptive. Normal is not. Normal compared to what? —Preceding unsigned comment added by Nospam2005 (talkcontribs) 22:41, 26 May 2016‎

Words are meaningless. Use kerb hight in SI unit


every wheelchair user knows the kerb hight he/she can pass for every used wheelchair. In Centimeters for 99% of the countries on this planet. 0 % of wheelchair users know the table on this page. Stop inventing words for hights. Use centimeters. Allow routing algorithms for wheelchair users to accept user entries in cm and route exactly the needed way.

A good cm estimation is better than a bad word. --Lulu-Ann (talk) 14:18, 18 July 2016 (UTC)

Kerb:raised at bus stops "implies wheelchair=no"?

I am a bit confused. The paragraph "raised" states that it can be added to bus stops, but it also states, that it implies wheelchair=no. On the other hand Key:wheelchair#Bus_stop states "wheelchair=yes (if there is a high level kerb [...])"... what is correct now? I don't think that you get around tagging the actual height of the kerb for public transport. --Raffael (talk) 20:56, 2 June 2017 (UTC)

Found a reference: Talk:Tag:highway=bus_stop#kerb.3Draised

I think you're confusing kerb=raised preventing a wheelchair crossing the road at that point, and kerb=raised at a bus stop to aid access to the buses (though as the reference above states, it doesn't say anything about whether accessible buses stop at that stop, so can't really be taken to imply wheelchair=yes or no when used on a bus stop for bus accessibility - just that it wouldn't be possible to cross the road there. Re-reading the page I suspect kerb=raised implies wheelchair=no when used on highway ways that aren't bus stop nodes - read the second paragraph on the page for the type of highway ways that I suspect are the "general method" mentioned lower down, when it mentions bus stop as an exception before then going on about what is implied for the general method. -- EdLoach (talk) 07:07, 3 June 2017 (UTC)
Yes, it needs a bit of rewording for clarification. If a company/municipality raises the kerb at a bus stop it's to help people to get into and out buses. It doesn't not mean that all buses at this stop will be accessible but the purpose being to make the transport route(s) accessible it implies that the platform is intended to be accessible (and therefore the road can't be crossed). --Nospam2005 (talk) 09:01, 5 June 2017 (UTC)

Lowered flush kerb

Is "lowered" intended to mean lower than the rest of the kerb, or does it mean lower than a normal kerb (low enough to be traversed using wheelchairs)? If there's a dip at a crosswalk (perhaps just a slight dip) and the kerb is flush with the pavement there, should it be marked kerb=lowered or kerb=flush? Germyb (talk) 22:59, 8 September 2017 (UTC)

kerb=lowered means a low kerb that can be traversed by someone in a wheelchair. – If you think a blind person with a stick notices the difference in height between the carriageway and the kerb/pavement, tag it kerb=lowered, if not, tag it kerb=flush. Hope I could help. --SelfishSeahorse (talk) 16:48, 28 December 2017 (UTC)


JOSM makes a distinction how kerbs are drawn based on the direction of the way. There's a description on the wiki page for natural=cliff, on how to draw a cliff to indicate which side is higher than the other. Should similar text be included to this wiki page, to indicate which side a kerb rises or lowers? —Preceding unsigned comment added by Mrbrown8 (talkcontribs) 04:33, 19 December 2017

It seems you confuse kerb=* with barrier=kerb. For barrier=kerb, right is bottom, left is up. --SelfishSeahorse (talk) 16:48, 28 December 2017 (UTC)

Open issues and suggestions how to solve them

1. Common high kerb
2. Square kerb of low height
3. Kerb ramp
4. Sloped kerb
5. Semi-mountable kerb
  1. Contradicting informations whether common high kerbs (see image 1) can be tagged raised or if this value is reserved for very high kerbs at public transport stops
    I think it makes sense to tag them raised too, as it doesn't make a difference for wheelchair users if the kerb is 12 or 30 centimetres high.
  2. kerb:left=* and kerb:right=* for asymmetric kerbs tagged on a crossing node
    This doesn't make sense, because a node has no directionality. I think this comment should be removed from the wiki.
  3. Undocumented how to tag kerbs along roads or sidewalks
    Suggestion: kerb:left=* and kerb:right=*
  4. No default unit for kerb:height=*
    As the default unit for height=*, which is also used for barrier=kerb, is metre, it would be very confusing to use a different unit for kerb:height=*.
  5. No distinction is made between square kerbs of low height (ca 2–4 cm; image 2) and kerb ramps / sloped kerbs (images 3 and 4)
    Suggestion: use sloped for kerb ramps and sloped kerbs, leaving lowered for kerbs of low height
  6. No value for kerbs that are traversable by vehicles and bicycles, but not wheelchairs, due to too high degrees (image 5).
    Suggestion: new value stronly_sloped

Alternative kerb=* value scheme:

  • mountable: mountable for wheelchairs and vehicles
  • semi-mountable: not mountable for wheelchairs but mountable for vehicles
  • non-mountable: neither mountable for wheelchairs nor vehicles

--SelfishSeahorse (talk) 18:43, 28 December 2017 (UTC) (edited 16:12, 7 January 2018 (UTC))

Here's my take on the open issues:
  1. Wheelchair users may not be interested in the difference, but other data consumers will be. So I believe should be possible to distinguish these two types. This was already brought up as an issue back in 2011 when the key was proposed. The suggestions included introducing the value normal (for kerbs like in image 1), the value bus (for those very high public transport kerbs), or both.
  2. Crossing nodes must always be part of a road, and the left/right tagging simply refers to the direction of that way. Works fine in practice.
  3. How about sidewalk:left:kerb=* and sidewalk:left:kerb=*? This tagging scheme is already mentioned at Key:sidewalk#Additional_tags.
  4. I agree that the default unit should be metre.
  5. We should distinguish them, but to me, images 2 and 4 seem much more similar than 3 and 4. Can you clarifiy the criteria you would use here?
  6. Sounds ok to me.
--Tordanik 18:01, 15 January 2018 (UTC)
Thanks for your feedback!
  1. normal might not have the same shape and height everywhere ... Meanwhile, I think it's best to tag the kerb shape (rectangular/sloped/rolled/flushed), height and incline (for sloped kerbs), as this information is unambiguous and universal.
  2. Now, I understand. But isn't this a bit unstable if the direction of the road way is reversed? And what if the crossing node is connected with a footway?
  3. I was thinking of sidewalks tagged as separate ways.
  4. ...
  5. The criteria would be difference in height (rectangular) vs no difference in heigh (sloped), or slope (sloped) vs no slope (rectangular).
  6. Tagging the kerb shape would make kerb=stronly_sloped unnecessary. A sloped kerb of 45° cloud simply be tagged kerb=sloped + incline=100%.
--SelfishSeahorse (talk) 20:58, 17 January 2018 (UTC)
  1. Tagging these facts – height in particular – would indeed make things unambiguous. But people will have a hard time giving kerb height in metres without measuring it, so there's still value in a basic height-based classification. (Right now, this key mixes height and shape, which makes things a bit more tricky.) I agree that "normal" is somewhat unclear, though. So maybe it makes sense to use a special value for the higher ones then, such as "bus_stop" or "Kassel"? Not sure how to call it.
  2. JOSM will warn you when you reverse a way containing a node tagged kerb:left, and will offer to change it to kerb:right for you (and the other way round, of course). Not sure about other editors. Footways connecting to crossing nodes are common, but I don't think that's a problem: The left/right has the same meaning as if the footway wasn't there (i.e. it refers to the road way, not the footway way).
  3. Oh, nevermind then.
  4. ...
  5. Maybe the issue is that I haven't seen anything close to the situation depicted in "kerb ramp" in real life, but it would really stand out to me, whereas I would probably barely notice the subtle incline on the stones in the "sloped kerb" image. So intuitively, I'd consider this a separate case from the ramp. Would be interested to get other mappers' impressions.
  6. incline is only usable on ways, though. Do you intend to use kerb:incline with special semantics?
--Tordanik 20:40, 23 January 2018 (UTC)
  1. bus_stop seems fine, although not all kerbs at bus stops are higher than common high kerbs. kassel, however, couldn't be used for all kerbs at bus stops.
  2. There's no warning in iD. But this might not be a big issue, because pedestrian crossings with different kerbs on either side seem to be rare.
  3. ...
  4. ...
  5. You're right, a kerb ramp is quite a bit different from a sloped kerb. Actually, a kerb ramp isn't a feature of the kerb but of the pavement (sidewalk). Maybe ramp for kerb ramps and sloped only for sloped kerbs as depicted in image 4? When mapping pavements as ways, it may make sense to map them as a way too, maybe tagged footway=kerb_ramp.
  6. According to Key:incline, this key can also be used on nodes, but kerb:incline=* seems to be fine too.
--SelfishSeahorse (talk) 18:29, 25 January 2018 (UTC)