[Tagging] Feature Proposal - Voting result - Pedestrian lane

Markus selfishseahorse at gmail.com
Thu Dec 5 07:50:26 UTC 2019

On Wed, 4 Dec 2019 at 13:06, Marc Gemis <marc.gemis at gmail.com> wrote:
> On Tue, Dec 3, 2019 at 9:36 PM Markus <selfishseahorse at gmail.com> wrote:
> >
> > In my opinion, footway[:left/right]=lane isn't a good idea for the
> > following reasons: 1. footway=lane is a contradiction, as a lane (part
> > of a road/path) isn't a footway (separate path).
> But isn't this exactly the same as we do for cycleway=lane?

Yes, it is, and it doesn't make much sense either, as a cycle lane
isn't a cycleway. (Oddly enough, the very similar US term bikeway
includes cycle lanes according to some definitions, while it excludes
them according to other definitions.)

I would have chosen cycle_lane=left/right/both instead, also because
"lane" (the type) is more important than left/right/both (the detail)
and would therefore belong to the key instead of the value. (Besides,
cycleway is already a value in highway=cycleway.)

> I would love to see consistency between cycleway and footway mapping.

There's already an inconsistency: separated footpaths are tagged
sidewalk=left/right/both while separated cycle paths are tagged
cycleway[:left/right]=track. Therefore i think it would be better to
not introduce more inconsistencies in pedestrian infrastructure



More information about the Tagging mailing list