Proposal for sidewalk tagging
Mapping as a separate way
Rationale for this is: with the ever-growing precision of GPS units, and the need of particular users when routing (e.g. blind people), a more precise mapping is needed when possible. In particular, for blind people, it's important to have precise information when walking: to understand on which side of the street they are, for example. This is not possible when just adding tags to the main way (see below) -- a separate way ought to be mapped.
These tags must be used:
When no crossing is marked, but it's common to cross the street at that point, crossing=unmarked should be used at the intersection between the sidewalk and the street. Most of the times this should be used on minor, low-traffic roads.
- height=* / est_height=*
- width=* / est_width=*
Tagging the main way (DEPRECATED)
When the sidewalk is just a painted lane on the street, it's possible to attach tags to the main way.
This tag is compulsory:
- sidewalk=side, where side is one of (depending on the direction of the way): left, right, both.
|sidewalk:side:barrier=*||Describes whether the sidewalk is physically segregated from the street, and how.|
Not every value described in barrier=* is suitable. Accepted values are: hedge, fence, wall, bollard, block, chain. As you can see, this is a subset of barrier=*: if you need one of the others, you'd better tag the sidewalk as a separate way.
|sidewalk:side:barrier=*||When tagged as a node, this tag means something a barrier transversal to the sidewalk, rather than alongside the street.|
Every value described as a node barrier in barrier=* is suitable.
|Width / Estimated width of the sidewalk lane.|