[Tagging] barrier=kerb + kerb=lowered

[Justin Tracey]

For one, kerb=lowered does not mean the footway is level with the 
roadway, that's kerb=flush. Secondly, as the wiki page states, this 
information is important for the visually impaired. Knowing 
approximately how far the curbs are in a crossing (barrier=kerb) and 
whether the curbs can be felt (kerb=*) can be important. It's arguable 
that kerb=* implies barrier=kerb, and therefore both shouldn't be 
tagged, but but all presets I'm aware of (iD and StreetComplete; AFAICT 
JOSM doesn't support kerb=* in its presets) apply both. This is useful, 
because it allows armchair mappers to tag where curbs are located via 
high res aerial imagery, and on the ground surveyors to tag what kind of 
curb it is (e.g., via StreetComplete). In any case, barier=kerb does not 
imply a raised curb, it's where the sidewalk or path meets the road, so 
should exist independently of what kind of curb it is.

  - Justin

On 2021-06-06 10:50 p.m., Jmapb wrote:
> What do folks here think of the barrier=kerb + kerb=lowered combo? I've
> started seeing it a lot with mappers micromapping crosswalks.
> 
> Offhand, it seems like textbook troll tagging to me, negating a tag with
> its own subtag. If the kerb has been lowered so that the footway is
> level with roadway, then not only is there no kerb but there's no
> barrier at all. Exactly the opposite.
> 
> Currently the wiki doesn't indicate that kerb=lowered and other kerb=*
> values are intended to be subtags of barrier=kerb. But it doesn't say
> they shouldn't be, either.
> 
> https://wiki.openstreetmap.org/wiki/Tag:barrier%3Dkerb
> https://wiki.openstreetmap.org/wiki/Key:kerb
> 
> Thanks for your thoughts, Jason
> 
> 
> _______________________________________________
> Tagging mailing list
> Tagging at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/tagging