Reading https://github.com/a-b-street/osm2lanes/issues/79, I was wondering what a similar ticket would look like for an easier tagging topic (than width), like surface (and very similarly smoothness).
Goal
Each lane should have a fallback or direct(ly taggeg) surface tag. Including separator-"lanes".
This has different fallbacks IMO, that is why I list it separately. Only PBL could fall back to the highway-surface IMO, but those are not mapped explicitly via one tag, so we have no way of identifying them.
cycleway:<Side|none>:surface
Local default
paving_stones in Germany, I would say – at least for the existing, old infrastructure we have now. In Berlin the mobility law defines asphalt for new cycleways AFAIK.
Reading https://github.com/a-b-street/osm2lanes/issues/79, I was wondering what a similar ticket would look like for an easier tagging topic (than width), like
surface
(and very similarlysmoothness
).Goal
Each lane should have a fallback or direct(ly taggeg) surface tag. Including separator-"lanes".
Links
surface
andsmoothness
from StreetComplete https://docs.google.com/spreadsheets/d/1-JiRgPPSByqyt7qQagFYJ3O7OvVh2DTJY_2-x9oeExs/edit#gid=0smoothness
Gallery https://wiki.openstreetmap.org/wiki/Key:smoothness/GalleryLanes
What tags to consider…?
Sidewalk
sidewalk:<Side|None>:surface
11,300 Left https://taginfo.openstreetmap.org/keys/sidewalk%3Aleft%3Asurface 14,800 Right https://taginfo.openstreetmap.org/keys/sidewalk%3Aright%3Asurface 6,400paving_stones
in Germany, I would sayParking
parking:lane:<Side>:surface
124 Left https://taginfo.openstreetmap.org/keys/parking%3Alane%3Aleft%3Asurface 149 Right https://taginfo.openstreetmap.org/keys/parking%3Alane%3Aright%3Asurface 0highway=*
.surface
Cycleway Lane
cycleway:<Side|none>:surface
3,300 Left (all cycleway types) https://taginfo.openstreetmap.org/keys/cycleway%3Aleft%3Asurface 7,300 Right (all cycleway types) https://taginfo.openstreetmap.org/keys/cycleway%3Aright%3Asurface 48,200highway=*
.surface
Cycleway Track
This has different fallbacks IMO, that is why I list it separately. Only PBL could fall back to the highway-surface IMO, but those are not mapped explicitly via one tag, so we have no way of identifying them.
cycleway:<Side|none>:surface
paving_stones
in Germany, I would say – at least for the existing, old infrastructure we have now. In Berlin the mobility law definesasphalt
for new cycleways AFAIK.Cycleway separately mapped
The combination
highway=cycleway + surface=*
has 750,000 objects https://taginfo.openstreetmap.org/tags/highway=cycleway#combinations.Highway lanes
highway=
.surface
track
>ground
asphalt
in GermanyFor a local analysis, I used this mapping to provide fallback values for missing data: https://github.com/FixMyBerlin/osm-scripts/blob/main/ZESPlus/Highways-SurfaceData/utils/assumedSmoothnessBasedOnHighway.ts#L3-L24. However, this is part of a script that adds
smoothness
values to all highways using multiple layer of fallbacks, so that is what it is optimized for.todo: buffers
To complete this list, I should look at the types of buffer and other lanes, that osm2lanes creates …
I will update this based on feedback and what comes to mind later.