<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>May 22, 2020, 03:09 by miketho16@gmail.com:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div dir="ltr"><div class=""><div class="" dir="ltr"><div>On Thu, May 21, 2020 at 4:52 PM Martin Koppenhoefer <<a target="_blank" href="mailto:dieterdreist@gmail.com" rel="noopener noreferrer">dieterdreist@gmail.com</a>> wrote:<br></div><div><br></div><div>> If the driveway is too rough, it maybe isn’t a driveway any more, it will depend on the other driveways in the area what is acceptable as a driveway, and when you would consider it track, that’s why there isn’t a clear limit on a global level.<br></div><div>This seems to contradict what <span>Mateusz said. "</span>Way used solely to access a private residence is always highway=service, service=driveway no matter<br></div><div>whatever it is short, long, paved, unpaved, lit, unlit, ugly or 22 lanes wide."<br></div><div><br></div><div>So you are saying that the highway=* tag depends not just on its function, not just on its physical condition, but also on its physical condition relative to the other ways in the vicinity?! <br></div></div></div></div></blockquote><div>It is probably the same case again.<br></div><div><br></div><div>1) there are two roads that can be used as access road<br></div><div>2) one is high quality, one is terrible<br></div><div>3) therefore better one is solely used as driveway, while terrible is used solely<br></div><div> to access field/forest along it<br></div><div>4) one used as driveway is tagged as driveway, one used as field/forest access<br></div><div> is tagged as highway=track<br></div><div><br></div><div>In this case physical characteristics impacted functional charateristics<br></div><div>what changed highway classification.<br></div><div><br></div><div>But highway=* should consider solely character.<br></div><div><br></div><div>Some interpret this as "all unpaved is highway=track". This is wrong.<br></div><div><br></div><div>Similarly reasoning going like<br></div><div><br></div><div>1) in my country roads forming national road grid (highway=trunk) are<br></div><div> all dual carriageway<br></div><div>2) therefore all trunks must be paved dual carriageway<br></div><div><br></div><div>is similarly broken.<br></div><div><br></div><div>functional and physical and administrative classification often match<br></div><div>and it is tempting to pretend that there is an exact match.<br></div><div><br></div><div>But sooner or later you run into weird cases like road ranked high<br></div><div>in official classification but of low quality.<br></div><div><br></div><div>Poland has for example case of road that used to lead to a bridge <br></div><div>(destroyed in WW II, not rebuild).<br></div><div><br></div><div>It is still officially highly ranked, but as it leads solely to riverside fields it is<br></div><div>highway=track. It does not matter at all that it is "droga krajowa"<br></div><div>or "droga wojewódzka".<br></div><div><br></div><div>Extremely high-quality logging rod through forest is still highway=track.<br></div><div><br></div><div>Extremely low quality driveway is still highway=service + service=driveway<br></div> </body>
</html>