Am Donnerstag, 13. Februar 2025, 20:58:03 CET schrieb Snusmumriken via Tagging: > On Thu, 2025-02-13 at 18:23 +0100, Manuel Binias wrote: > > It's simply a conversion error where some EOF characters are included > > in the > > link for some reason (don't know if the client or the mailing list is > > broken, > > I think it's the list's fault). The raw text is a valid link, though, > > and I > > presume the link in the quote too. > > > > Am Donnerstag, 13. Februar 2025, 17:51:31 CET schrieb Snusmumriken: > > > On Thu, 2025-02-13 at 17:42 +0100, Manuel B. wrote: > > > > A proposal to define a highway median in detail: > > > > https://wiki.openstreetmap.org/wiki/Proposal:Median_strip > > > > > > Seems like a broken link > > https://wiki.openstreetmap.org/wiki/Proposal:Median_strip > I guess this is the correct link. > > About the proposal, I think to model it as an area would be much more > natural and not to combine it with a highway tag, as you're not > supposed to drive on a median strip > > _______________________________________________ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging The thing is that I'm suggesting this because I want to describe the ways themselves, not just how they're rendered. It's like claiming highway=* is inferior because you can use area:highway=* just as much and it'll be more detailed (same deal with all the properties like shoulders, especially because these are like medians but to the side). No, most data consumers process highway=* only (especially because these are linear features and easier to process) while area:highway is primarily a rendering feature.
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
