<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div><br></div><div><br></div><div><br></div><div>Dec 12, 2020, 18:27 by baloo@ursamundi.org:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div dir="ltr"><div dir="ltr"><br></div><div><br></div><div class=""><div class="" dir="ltr">On Sat, Dec 12, 2020 at 11:22 AM Jan Michel <<a href="mailto:jan@mueschelsoft.de" rel="noopener noreferrer" target="_blank">jan@mueschelsoft.de</a>> wrote:<br></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class=""><div>On 12.12.20 17:47, Paul Johnson wrote:<br></div><div> > On Sat, Dec 12, 2020 at 10:46 AM Jan Michel <br></div><div> > <<a target="_blank" href="mailto:jan@mueschelsoft.de" rel="noopener noreferrer">jan@mueschelsoft.de</a> <br></div><div> > <mailto:<a target="_blank" href="mailto:jan@mueschelsoft.de" rel="noopener noreferrer">jan@mueschelsoft.de</a>>> wrote:<br></div><div> > <br></div><div> > On 12.12.20 17:25, Paul Johnson wrote:<br></div><div> > <br></div><div> > > Sure, if you manually torque tag it to match the incorrect<br></div><div> > > documentation. As soon as you open the lane editor, it rightly<br></div><div> > corrects<br></div><div> > > it to lanes=5, since you have 2 lanes in one way and 3 in the other.<br></div><div> > <br></div><div> > The "incorrect documentation" was voted on and it was approved.<br></div><div> > <br></div><div> > <br></div><div> > I'm pretty sure it was done without consideration for reserved lanes as <br></div><div> > lane access tagging wasn't something yet available. Now it is, and it's <br></div><div> > time to reconsider that.<br></div><div> <br></div><div> I'm refering to the proposal of exactly this: the :lanes extension. It <br></div><div> was clearly and unambiguously taken into account:<br></div><div> <a target="_blank" rel="noopener noreferrer" href="https://wiki.openstreetmap.org/wiki/Proposed_features/lanes_General_Extension#The_issues_with_the_lanes_tag">https://wiki.openstreetmap.org/wiki/Proposed_features/lanes_General_Extension#The_issues_with_the_lanes_tag</a><br></div></blockquote><div><br></div><div>That specific anchor says it's completely sidestepping the issue while highlighting the shortcoming of lanes=* as it stands now. We need to fix lanes=* to mean all lanes. This isn't a hard change to make<br></div></div></div></blockquote><div>It would redefine widely used tag.<br></div><div><br></div><div>So we would need to resurcey all places where lanes tag is used.<br></div><div><br></div><div>And MapRoulette is not an answer in this case. It would only work if all <br></div><div>11 millions tags would be in places where aerials is highly detailed, <br></div><div>up to date and road is not covered by trees.<br></div><div><br></div><div>See <a href="https://taginfo.openstreetmap.org/keys/lanes">https://taginfo.openstreetmap.org/keys/lanes</a><br></div><div><br></div> </body>
</html>