Talk:Key:surface:lanes

How should surface:* tag be mapped in cases where surface:lanes=* is used?

For example, if surface:lanes=concrete|asphalt, should surface inherently be tagged using semicolon delimiter (e.g., surface=concrete;asphalt)? Adding tagging suggestions for broader surface=* tag would benefit readers of this page. Osmedit (talk) 15:52, 20 October 2024 (UTC)

It's mapping for the router/renderer, but I'd suggest using the "highest/best" value in the surface tag, as this will likely be the one affecting your driving preferences and speed? -- Pbnoxious (talk) 10:44, 6 December 2024 (UTC)

I see merit in that thought but was moreso wondering if surface:lanes=* entirely supersedes having the surface=* tag such that surface=* should be removed entirely, or should both surface and surface:lanes tags be included? Osmedit (talk) 01:10, 12 December 2024 (UTC)

How well do renderers parse surface:lanes?

Also, I'm curious if anyone has observed how well various renderers currently interpret this tag? Seems like a highly useful tag so I plan to begin mapping cases I am aware of but was wondering if others have seen how well it is rendered, particularly for running/cycling (e.g., Strava, Komoot, etc.) Osmedit (talk) 15:54, 20 October 2024 (UTC)

Really include lanes that are not in the lanes-tag?

The current version says: Note that all surfaces, including bicycle lanes and similar should be included (unlike in say lanes=* tag).
I would like to hear a rationale for that, because if no mapping from the lanes to the surface:lanes tag is possible anymore (like it is suggested here) doesn't the whole tagging become ambiguous and it's not clear what lane has what surface? Shouldn't we stick to the established *:lanes=* tagging? -- Pbnoxious (talk) 10:44, 6 December 2024 (UTC)