Is the sidewalk going down, need a incline tag with kerb=no on the node.
There is not a lowered kerbstone, buried in the ground,
How is this called?
with a corner.
with the same paving_stones, but not a lowered kerb in the ground.
It is different then a burried kerb one or a wider kerbelement with a incline.
There’s kerb=sloped: it’s in use but not documented on the wiki. StreetComplete has a separate answer option “curb ramp” but it adds kerb=lowered when you select it (maybe because it’s similar: no obstacle for wheelchairs but sensible for the blind).
In Denmark it’s quite common to have asphalt ramps from the curb down to the road. Every driveway has one and they also exist at intersections (where they can be quite steep). I’ve been tagging these as kerb=lowered but they dont really have anything to do with the kerb. Kerb doesn’t usually go down where the ramps are (which is why they are often steep)
How to tag this properly?
aren’t these all or most of them kerb=flush?
That is the problem, there is no kerb there.
To descibe it properly, we should not use kerb.
I used lowered also, but I am not sure, it is right.
But how?
Way barrier=kerb tagging?
In the US, we would tag all of these as kerb=lowered. The barrier=kerb node represents more than just the details of the curb itself:
“How does one travel from the sidewalk to the roadway?”
→ Slope from sidewalk level to street level = lowered
→ No elevation difference = flush
→ Vertical drop-off = raised
Yes, even if there is technically no actual curb. That’s the cost of abstraction - almost no one wants to map all of the details: transfer topology, edge type, lip height and shape, alignment, gutter slope, landing details, etc. in OSM.
The edge characteristics you’re pointing out are, on the directional ramps, called “returned edges” and, on your example of a blended transition, called “flared edges” - I had tagged some in this way but Taginfo returns no results so I guess someone removed them 
the question with abstraction is for which use case you are doing it. A blind person would be interested to know whether there is some kind of sensible edge (lowered or raised, …) or not (flush). Around here, “kerb” does represent the actual edge, you cannot see from “kerb” whether there is a slope or not.
Is there a barrier, a incline is not a barrier, a kerb is. Can you map it as a barrier?
But it is small, a part of, does this make it a barrier. (just like an entrance) How to map the width for vehicle use. Not disabled people can use it, next to it, a step on the raised kerb. The way width is wider, then this part. This mixed, is a kind of barrier.
These used concrete blocks, kerb slope blocks (entry kerb), in different measurments, I tag them as kerb:type=NL:45-10 or NL:75-10, standaard measurements used. These are used for foot, bicycle and car. 45-10 45 centimeter 10 centimeter high, is very limited for wheelchair. tag wheelchair=limited
Tagged them for knowing, where they are. Get a overview, to see problem situations, I asked the municipality, to change some and they did. Crossing a road, busy with taking the kerb, not watching the traffic is not a safe crossing.
Your comments give me the idea of wider the kerb:type and still use lowered.
kerb:type=returned edges worldwide usable
kerb:type=flared edges
or
returned edges=yes
flared edges=yes
I use a preset to set with One Cick multiple tags.
Only, with this, I can get some workflow done. Tag a city more correctly, disabled, blind, needs a higher quality, quantity, where we as pedestrian can step over it, take a shortcut.
I am wrestling with the width tag, which is more important for some tranportation mode.
Thinking about it how to do this in such a situation.
I am also conservative, but we need some data to get it done, in quality, quantity to make it work. For one use more then the other. But when you can set it with One Click.
The biggest problem is time, the reason for “almost no one” and the concern about usability. Understandable.
One thing led to another, and I look forward to hearing your views.
When tagging kerb=*, I think we should have in mind which map end users we are tagging them for, i.e. wheelchair users and the blind. Is the transfer from road to sidewalk passable by wheelchair, and sensible by the blind? If both are yes, then kerb=lowered, if wheelchair=no then kerb=raised, if not sensible then kerb=flush
I am frequently tagging kerb=flush tactile_paving=yes , which as a tag set directly contradicts your classification in this post - it is both level for wheelchairs and detectible for low vision.
To me, kerb=no means that there is no pavement transition at all in a location that a remote mapper might expect one to exist. A surface change between asphalt and concrete is flush to me.
I’d say that the flush kerb is still not sensible for the blind, it’s the tactile paving that makes it sensible.
The wiki pictures for kerb=flush suggest that there should be a kerb stone, and that’s how I map it. There are sticks for the blind with a ball at the end that rolls over the pavement (my mother has one). With this tool, the blind can sense a change of pavement roughness (from asphalt to paving stones, for instance).
You need to know, that in the US, those ramps looks usually like:
Usually there is a groove and if you cycle there, you will clearly notice it → kerb=lowered
Compared to below situation, where you still can feel a difference, but there is no bumb → kerb=flush
And here, you don’t feel and see anything → kerb=no
to me this is kerb=no because there is no kerb, just a change in surface
I totally agree, it must be yes or no, if there is a kebstone, especially for the blind, what to expect.
Yeah… and there is the problem. None of the pictures above have an actual, european kerb. If you value the visual more…
first picture would be flush, as the concrete section of the sidewalk is exactly matching the concrete section of the kerb and that is exactly matching to the road. The other 2 would be no as you pointed out there is no kerb.
Though if you go by how it feels if you use them, my above are the ones coming closer to reality.
What is the difference between kerb=flushand flush=yes , is it flush, there is no need to make it a kerb as there is no kerb.
Here the kerbstone (in ground) include a gutter.
They use this combinationstone gutterkerb. Or they use a brick to make the gutter.
about gutter, and height, what to use.
Here I have a situation with a kerb:type=returned edges there is no kerbstone in the ground, in front is a brick (paving_stones) this is the gutter, and then the carriageway (asphalt) is higher.
A lot of elderly with a stroller (bag full of grocery) walk from the store to there homes (elderly facility). This edge give them troubles. I see them wrestling with it, pushing 3-5 times against it, annoyed, not paying attention to the traffic. Or there is traffic, trying to take a cross on the right moment and then wrestling with this edge. (I have lodged a complaint with the local council)
I can not use kerb:heigth there is no kerb, if I set kerb=flush this partly true, but there is this edge. That is the main reason I started thsi topic, how to express it properly.
The transition from to carriageway makes the problem. What tag to use?
'street_gutter` and height of the edge?
What about the blind, how to give them the right tags, the warning for a edge. So it match what they feel.
For any data consumer or map user I can imagine, there is no practical difference, so there is no problem. Better spend our time on mapping than to discuss this ;)
I’d tag it kerb=lowered because it has an edge that causes trouble for wheel users, even though it’s unusual that it is the road that is higher instead of the sidewalk. Let’s hope you can soon tag it kerb=flush !
Exactly that’s my point. whether the last row in your picture is made of paving stones or one long, thin kerb stone makes zero difference to the user.
Though you could argue that in your case the sidewalk is lower than the road. Not being but I would expect a different information in such a case, as it’s a tripping hazard going onto the road. Usually that hazard would occur when leaving it.
The sidewalk is about 8-10 cm higher then the road, a small incline (sidewalk) lowers it.
I gave it a kerb=lowered kerb:height=0.01 0.001 is not correct ( I tagged it because to give it somekind of a edge), because it is not a kerb, there is no kerb. So there can not be a kerb:height it is the road gutter a part of the road, that give a edge on the road. I am not happy with my tagging.
Normally, when you go off the sidewalk to the road, it is easier to take a edge, drop off. But from the road to the sidewalk it is more of a effort.
This edge is the other way around. Not a expected behaviour, you expect at kerb:height
I tag these entrance kerb blocks, but how they work. kerb=lowered
The kerb:heightis not 0.1. but 0.03, is that correct?
kerb:height or =0.I make a preset, one click to set multiple tags, the choice, which do you click.
With one click use, I do a lot of more work mapping in the same time. With better quality and more quantity. Especially in urban area, with often returning tag combinations.
Because sitewalk is going down it stays kerb=lowered in some way you must express the lowering.
As earlier mentioned, not happy with it.
flush means on both side of the kerb it is flush.
