<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 2014-04-09 10:47, Pieren wrote :<br>
</div>
<blockquote
cite="mid:CAPT3zJqyr0B-Cw4on5UDJ09Kvf62Npfj-nUDPNBp1P-8O=jrAA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On Tue, Apr 8, 2014 at 6:38 PM, André
Pirard <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:A.Pirard.Papou@gmail.com" target="_blank">A.Pirard.Papou@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<div>
<ol>
<li>noexit cannot be used on ways because that does
not show what end "cannot pass"<br>
</li>
</ol>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>eeh, what "what end" ? Either the highway line is
linked to another highway at both ends, then "noexit" is a
tagging mistake. Or the highway line is not linked to
another highway on both ends and then the "noexit" can be
helpful (confirming tha'ts really an isolated highway and
not some connection missing)<br>
</div>
<div> <br>
</div>
</div>
</div>
</div>
</blockquote>
??? Let's explain in details. We let alone the Xmas trees.<br>
Assuming real noexit, <a
href="http://overpass-turbo.eu/map.html?Q=%3C%21--%0AThis%20has%20been%20generated%20by%20the%20overpass-turbo%20wizard.%0AThe%20original%20search%20was%3A%0A%E2%80%9Cnoexit%3Dyes%E2%80%9D%0A--%3E%0A%3Cosm-script%20output%3D%22json%22%20timeout%3D%2225%22%3E%0A%20%20%20%20%3Cquery%20type%3D%22way%22%3E%0A%20%20%20%20%20%20%3Chas-kv%20k%3D%22noexit%22%20v%3D%22yes%22%2F%3E%0A%20%20%20%20%20%20%3Cbbox-query%20s%3D%2250.66839555058174%22%20w%3D%225.717890262603759%22%20n%3D%2250.67569820203223%22%20e%3D%225.731172561645508%22%2F%3E%0A%20%20%20%20%3C%2Fquery%3E%0A%20%20%3C%21--%20print%20results%20--%3E%0A%20%20%3Cprint%20mode%3D%22body%22%2F%3E%0A%20%20%3Crecurse%20type%3D%22down%22%2F%3E%0A%20%20%3Cprint%20mode%3D%22skeleton%22%20order%3D%22quadtile%22%2F%3E%0A%3C%2Fosm-script%3E">the
typical cases</a> <b>look like</b> two normal junctions at each
way end but one of them <b>is in fact </b>a dead end.<br>
Why would we tag noexit on the way and request the beholder to zoom
in each end to determine which is dead if we can tag the information
clearly on the end node? What about T shaped ways where the top way
contains 2 dead ends? "gotcha, there were 2"?<br>
Now, instead of a vertical bar, what about a small (or larger) mesh
like <i>rue Grétry</i>: are we going to tag as dead ends all the
segments of the mesh up to the normal junction even if they're not
directly related with a dead end? And, BTW, are we speaking (in
Subject:) of ways or of roads? Must we apply noexit=yes to both
ways of the same road when we split one? How would the brave
contributor splitting a way cope with that if he hasn't got the
faintest notion of what noexit is (no blame on him!)?<br>
These are [probably a part of] the questions that raise and should
be settled and that no one advocating noexit on ways mentioned.<br>
Frankly, noexit on nodes (as designed) is much more logical and
simple (than on ways, of course).<br>
<br>
Cheers,<br>
<br>
<table>
<tbody>
<tr>
<td>André.</td>
</tr>
</tbody>
</table>
<br>
<br>
</body>
</html>