On Thu, May 10, 2018, 00:29 <[email protected]> wrote:
> The “lanes=count” key gives the number of full lanes for motorized > traffic. This gives a good estimate for total carrying capacity for vehicle > traffic on this road for software that isn’t too concerned about the > details, or simply older software that doesn’t know about the :lanes suffix. > Conflating lane count with lane access is both inaccurate and confusing. > If there are keys with the :lanes suffix present, then number of lanes > specified by all of them must be the same, and the total number of lanes > (including cycle lanes and such) is given by the number of lanes defined in > the tags, there is no need to repeat the same number again in the > lanes=count tag. If you simply make the lanes=count tag always represent > the same number as the lanes specified in the :lanes suffix keys, then you > could simply omit it completely, as it’s just redundant > Every editor that handles lane tagging will (quite correctly) ensure your lane counts square up to the lanes tagging or loudly complain. > Changing the meaning of the lanes=count tag after many millions of them > have already been created makes the key useless as it can’t be relied on > anymore. > I'd argue this has always been the case thanks to this glaring omission. Just because someone doesn't think all lanes should count just because bicycle thought that was a smart idea doesn't mean that it actually is, or that leaving this information out makes lane guidance easier (it doesn't, it makes it wrong). >
_______________________________________________ Tagging mailing list [email protected] https://lists.openstreetmap.org/listinfo/tagging
