The only way to do it properly is - define a new tag "lanes_for_all_transportation_modes" - deprecate lanes (during this period data-consumers should use "lanes_for_all_transportation_modes" and fallback on "lanes" if the former is not there) - wait until all highways with a lanes tag also have "lanes_for_all_transportation_modes" - drop "lanes"-tag - rename "lanes_for_all_transportation_modes" to "lanes"-tag
but that is only if you want a definition for lanes that no non-OSM'er understand. As pointed out before, traffic rules and most people understand lane as something on which you can drive with a car. m. On Fri, May 11, 2018 at 7:16 PM, Paul Johnson <ba...@ursamundi.org> wrote: > This honestly sounds more of gatekeeping through laziness than an actual > barrier. > > On Fri, May 11, 2018, 11:25 Tod Fitch <t...@fitchdesign.com> wrote: >> >> >> > On May 11, 2018, at 8:40 AM, Paul Johnson <ba...@ursamundi.org> wrote: >> > >> > Why the almost religious doctrine level of resistance to change? Even >> > the Linux kernel rewrites entire subsystems from time to time when a >> > superior approach comes around. >> >> The difference between having a small group of core developers who are all >> communicating with one another lead by a single individual (Linux kernel) >> and a community of tens of thousands, maybe millions, of contributors with a >> multitude of different communication channels and with no single leader >> (OSM). Changing core features/functionality in the former is much easier >> than in the later. >> >> >> >> >> _______________________________________________ >> Tagging mailing list >> Tagging@openstreetmap.org >> https://lists.openstreetmap.org/listinfo/tagging > > > _______________________________________________ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging > _______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
