[Tagging] Feature Proposal - RFC - footway=link

Allroads allroadsworld at gmail.com
Fri Nov 22 20:24:07 UTC 2019

The variation of drawing and setting tags.
1. People draw in the carriageway road as a wayline. Wayline middle of the road. Exactly, where it is.
1.1 Then they decided that there is a sidewalk, on the right, tagging sidewalk=right, this says there is somewhere a sidewalk on the right next to the road. But not exactly, where it is.

2. People want to drawn in the sidewalk as a wayline next to the road, in the middle of the sidewalk, safe walking route. tag it: highway=footway footway=sidewalk. Best is to connect it !! correctly for routingpurpose!!, that was there goal. (kids routing on the sidewalk, the routing track line lays in the middle of the sidewalk, no complaints parrents.)
2.1 On the carriagewayline, the tag sidewalk=right is changed to sidewalk=separate. Because, routing is drawn in correctly on the sidewalk, routing could use that, then not  on carriage road  for pedestrian.
2.2 Also on the road wayline, foot=use_sidepath is set. !! All when routingconnections is well done !! Or when traffic_sign foot prohibited, foot= no. The routing know now it is more legal.

3. People want to draw in the sidewalk as a area. then the tag: area:highway=footway footway=sidewalk is set. Topographic visualisation.

All these variation of drawing must fit together.

What I wrote: inside the drawmethod 3 polygon:  (area:highway=footway footway=sidewalk ) only  drawmethod 2 lines can be drawn in with that specific tag: highway=footway footway=sidewalk, because the way line is drawn in the middle, there is a perpendicular part from the middlewayline to the outline of the polygon, where the barrier kerb is.
At this point you step on the road, there comes this new tag in operation, tag: highway=footway footway=link or better *=connection, you walk further on the road. These are T connections !!

There is one exception: 
A.  When you have a cross X connection, we speak of a crossing.
     When the polygon is crossed with a wayline by a road crossing! (mind turning)

Your problem drawing at a service (driveway). @ Markus

The choice, at the polygon, is it an area:polygon =service or a area: polygon =footway.

drawmethod 3 polygon:  (area:highway=footway footway=sidewalk ) 
Now you must set your mind to a new thinking, 180 degrees, what we used to do.
Normaly, the pedestrian crossed the road. We set footway=crossing.
image example: https://images.mapillary.com/3qPJ4v8tao8cVmYzTbuoJg/thumb-2048.jpg
location :https://www.mapillary.com/map/im/3qPJ4v8tao8cVmYzTbuoJg
What you see is that the sidewalk footway surface at the driveway has been extended, on-going. Same paving as all the footway. 30x30 paving stones. It is the footway.
Then the polygon is drawn in as a area:highway=footway footway=sidewalk
But at a service (driveway), there the car crosses the footway. The car must always give priority to the pedestrian.
The footway is more important then the service way.
So the wayline highway=service  gets “service=crossing” inside this polygon (area:highway=footway footway=sidewalk). That is the exception !

The driveway construction is here with a driveway kerb. But could be else too. Decision of the mapper.
The on-going pavement of the footway but also on a cycleway, priority of way, gives a different relationship to each other, ending up in saying service=crossing

In the Netherlands we have the privilege, to use Goverment data, license agreed with OSM.
(Site under construction) Sitemap with layers where we have a agreement on.
Zoom in, then check on, BGT standaard V2, we could use these polygons for Openstreetmap.
See the pink colors polygon these are mostly sidewalks in a village town.
Then you see where sidewalks are on-going, and where a pedestrian must cross the road.
We now use these BGT layers to line out Openstreetmap highways waylines, this is more accurate then doing it with aerial 
(note: use map overpass uncheck with much panning and zooming)

Combining these variation of drawing in, these wayline footway=* connecting (link) could be used for T connections. From kerb to middle carriage road wayline.

perpendicular: footway=sidewalk, go on the footway left to the kerb. The outline of the polygon.
At the kerb a disabled person must get the message, step on the road and follow the road to the right. Is there, this new value helping? You do not want that a audio message say, step on the footway and follow the footway. (this is only at a crossing)

Tagging mailing list
Tagging at openstreetmap.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20191122/7b0f8349/attachment-0001.html>

More information about the Tagging mailing list