Intersections of Sidewalks and Driveways

[Woazboat]

@Langlaeufer

it would be crossing:continuous=yes - the cars have to wait.

The wiki page gives the impression that crossing:continuous=* is only intended for ‘actual’ crossings over streets and not for driveway intersections (i.e. in combination with highway=crossing).

@Lumikeiju

I would definitely consider all of these to be “eligible” for mapping as crossings. They’re not at the same priority as the major roadbed crossings, obviously, so I expect that most people would not put in the effort - especially to map them as ways with curb nodes and all - but they are important to pedestrians (especially those with low vision or low mobility) and I usually map them.

@Langlaeufer

Then we need better tag to differentiate between crossings. It does not make sense to put all unmarked or all marked “crossing” in one class, even they have complete different rules.

@ezekielf

It is also worth considering whether a tag is necessary at all to identify such intersections. With a bit of processing, it should be possible for a data consumer to identify any node that is part of both a highway=footway + footway=sidewalk and a highway=service + service=driveway.

Driveway intersections like that should absolutely not be tagged the same as regular street crossings. It pollutes the data set and makes it impossible to accurately find the ‘real’ crossings. The primary purpose of the tag is not just simply signalling that this is a point where pedestrians and drivers might come into conflict, it has important additional implications.

Like @ezekielf said, finding intersections between pedestrian paths and other highway=*s can be done automatically just from the existing highway tags. If there is no other meaning in the tag besides that such an intersection exists, it doesn’t really provide any useful information.