<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div style="16px" text-align="left"><br></div><div style="16px" text-align="left"><br></div><div style="16px" text-align="left"><br></div><div style="16px" text-align="left">Mar 15, 2019, 10:03 AM by richard@systemed.net:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div style="16px" text-align="left">Mateusz Konieczny wrote:<br></div><blockquote><div style="16px" text-align="left">Yes, one of main points of StreetComplete is to allow editing <br></div><div style="16px" text-align="left">without knowing how objects are tagged, similarly iD.<br></div><div style="16px" text-align="left"><br></div><div style="16px" text-align="left">It means that to count "how many people decided to use tag <br></div><div style="16px" text-align="left">XYZ" all iD users and all StreetComplete users count as say <br></div><div style="16px" text-align="left">4 people because not each mapper is deciding on its own <br></div><div style="16px" text-align="left">but it is decision of whoever makes the software.<br></div></blockquote><div style="16px" text-align="left"><br></div><div style="16px" text-align="left">Oh, come on. Just because iD has an actual user interface doesn't mean that<br></div><div style="16px" text-align="left">every single iD user is unaware of the tags used. There are plenty of<br></div><div style="16px" text-align="left">experienced mappers (I'm one) who choose not to use JOSM because they just<br></div><div style="16px" text-align="left">don't like JOSM, believe it or not!<br></div></blockquote><div style="16px" text-align="left">Thanks, I was unaware about it! I was always really frustrated by iD<br></div><div style="16px" text-align="left">hiding tags and requiring scrolling to get it (and really slow performance).<br></div><div style="16px" text-align="left"><br></div><div style="16px" text-align="left">I admit that I was unaware that it is used as a primary editor also by people <br></div><div style="16px" text-align="left">editing tags directly.<br></div><div style="16px" text-align="left"><br></div><div style="16px" text-align="left">Sorry for spreading misinformation.<br></div><div style="16px" text-align="left"><br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div style="16px" text-align="left">On topic: I don't have a great preference for either tagging scheme (they're<br></div><div style="16px" text-align="left">both a bit ungainly, I've found them both a bit of a PITA to support in<br></div><div style="16px" text-align="left">cycle.travel's tag parsing). cycleway=opposite_lane is concise but unclear.<br></div><div style="16px" text-align="left">Regardless, both are in widespread use so the wiki should document both.<br></div></blockquote><div style="16px" text-align="left">Yes, if both are in a widespread use then both should be described.<br></div><div style="16px" text-align="left"><br></div><div style="16px" text-align="left">Claim that opposite_lane is a value that has no meaning with cycleway:left<br></div><div style="16px" text-align="left">that appeared on Wiki (in edit description) is completely untrue.<br></div><div style="16px" text-align="left"><br></div><div style="16px" text-align="left">Maybe some people dislike this tag and it is more confusing than it should be<br></div><div style="16px" text-align="left">but it has a known meaning.<br></div> </body>
</html>