<div dir="ltr">I once read your proposal on the wiki. The main drawback that I see is that one will get an awful lot of "layers" (or whatever you want to call them). For each property you add to a street a need to create a new layer. After verifying of course that there isn't already a layer with that property. In that case you have to split the layer at the right place.<div><br></div><div>I try to imaging how a UI to edit that would look like. Or software that uses that data. I wonder whether it would much easier to work with such a structure. hard to tell. You are probably to much ahead of your time with this proposal.</div><div><br></div><div><br></div><div>regards</div><div>m</div><div><br></div><div><br></div><div>PS, it is indeed pretty confusing that something with one 'l' in one language has two in the other, and has another meaning in the second language with one l.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Jan 3, 2015 at 2:34 AM, André Pirard <span dir="ltr"><<a 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 bgcolor="#FFFFFF" text="#000000">
<div>On 2015-01-02 19:01, Marc Gemis wrote :<br>
</div><span class="">
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra"><br>
<div class="gmail_quote">2015-01-02 17:11 GMT+01:00 André
Pirard <span dir="ltr"><<a href="mailto:A.Pirard.Papou@gmail.com" target="_blank">A.Pirard.Papou@gmail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">J'ai
un jour écrit un article décrivant une méthode pour ne
plus devoir découper les chemins mais ça n'a intéressé
personne.</blockquote>
</div>
<br>
I've read somewhere that navigation software will split all
ways at a crossing in order to be able to calculate all
possible routes. So the merging is only needed for rendering
(in order not to show the name over and over again).</div>
</div>
</blockquote></span>
Obviously.<br>
With my method, there is no merging necessary because there is no
splitting.<br>
If a part of a way has different tags, a sort of "patch" dummy way
is created that overlays that part of the way and that contains the
tags that are different. Difficult to explain in 2 lines.<br>
<tt>--------------------------------------------------- </tt><tt>real
highway with common tags<br>
------------- dummy way
(patch) with bridge=yes<br>
</tt>If the consumer wants that, it can split the real highway,
merge the tags and get the current situation. But it doesn't have
to. <br>
In a further step, with slight software changes, the patch could be
the element of a relation and relations would stop splitting the
ways everywhere.<br>
Also, a turning restriction and other things could be done with very
simple patches instead of complicated relations.<br>
All in all very powerful and easy to use, but, alas, it needs
software changes. Nothing complicated but in the essential parts.<span class=""><br>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">Nominatim only shows the same way when
the classification is different, see [1] for a split street
showing multiple results, and [2] for one showing only one
segment</div>
</div>
</blockquote></span>
If you click on <span></span><span>(<a href="http://nominatim.openstreetmap.org/details.php?place_id=152179547" target="_blank">details</a>)</span>
of [2] you see that it's only a split of Molenstraat and if you
click on <a href="http://nominatim.openstreetmap.org/search?format=html&exclude_place_ids=152179547,90789266,57800141,152183937,58188920,57651969,89772878,126246678,2642012399,50709423,118353426,2642012397,2642012398,58361979,98773793,57793661,50786385,80736363,123201401,100889764,15832600&accept-language=en,fr;q=0.8,wa;q=0.6,ru;q=0.4,nl;q=0.2&viewbox=4.38%2C51.11%2C4.41%2C51.09&q=Molenstraat%2C+rumst" target="_blank">Search
for more results</a> you get another split and <a href="http://www.openstreetmap.org/search?query=molenstraat%20rumst#map=16/51.1009/4.3920" target="_blank">it's
not very clear at all how that street is split</a>, it looks like
Nominatim is only showing parts of the splits.<br>
It would obviously work better if there were no splits but patches.<span class="HOEnZb"><font color="#888888"><br>
<br>
<table>
<tbody>
<tr>
<td>André.</td>
</tr>
</tbody>
</table>
</font></span><br>
PS: Oops, I first thought that "molen" were moles and I wondered if
they were under the street and <a href="http://www.openstreetmap.org/way/166577477" target="_blank">drinking a cup
of coffee</a> <span><span> ;-) </span></span>
They are in fact mills <a href="http://www.openstreetmap.org/node/259975902#map=19/50.52639/5.52305" target="_blank">like
this water mill</a> that I just mapped and that's probably the
best known in Belgium.<span class=""><br>
<br>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">regards</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">m.</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">[1] <a href="http://nominatim.openstreetmap.org/search.php?q=steenweg+op+waarloos&viewbox=-112.33%2C46.38%2C112.33%2C-46.38" target="_blank">http://nominatim.openstreetmap.org/search.php?q=steenweg+op+waarloos&viewbox=-112.33%2C46.38%2C112.33%2C-46.38</a></div>
<div class="gmail_extra">[2] <a href="http://nominatim.openstreetmap.org/search.php?q=Molenstraat%2C+rumst&viewbox=4.38%2C51.11%2C4.41%2C51.09" target="_blank">http://nominatim.openstreetmap.org/search.php?q=Molenstraat%2C+rumst&viewbox=4.38%2C51.11%2C4.41%2C51.09</a></div>
<div class="gmail_extra"><br>
</div>
<br>
</div>
</blockquote>
<br>
</span></div>
</blockquote></div><br></div>