<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">We should stick to the current well
known scheme, thinking about this renderer issue... it makes no
sense to manoevre around a faulty renderer, being it nominatim or
a tileserver. If a search for a street + housenumber, city
returns nothing, but a search for that same street, city without
the number does return fine, who's fault is that? Search engines
are suppose to be 'best effort' . The correct behavior should be
to drop the housenumber from the search parameters (no exact match
is found), and then lower the resolution of the result set to
encompass the street (visually). In nominatim that would
translate to bunch of hits when searching for an address, when
reverse searching for a coordinate that would just return :
streetname , postalcode, city, country no housenumber.<br>
<br>
That proposal ,I mentioned that in a earlier comment already, (to
be aware of it's existance) but it's flawed as you noticed. Also,
there are 203 occurences in the whole database like this:<br>
<br>
<a class="moz-txt-link-freetext" href="http://taginfo.openstreetmap.org/keys/addr%3A1%3Ahousenumber">http://taginfo.openstreetmap.org/keys/addr%3A1%3Ahousenumber</a><br>
<br>
Safe to say, it would be a lost effort following this scheme. But
also, we would be the only ones using it imho .... We should just
keep tagging the karlsruhe way.<br>
<br>
Glenn<br>
<br>
On 2013-10-21 14:40, Marc Gemis wrote:<br>
</div>
<blockquote
cite="mid:CAJKJX-QMBm=waoayJxvfNKYYOKPzRhHqSyjEqGaz4QePVzWCYQ@mail.gmail.com"
type="cite">
<div dir="ltr">And I'm not the only one: see <a
moz-do-not-send="true"
href="http://wiki.openstreetmap.org/wiki/Talk:Proposed_Features/Multiple_addresses">http://wiki.openstreetmap.org/wiki/Talk:Proposed_Features/Multiple_addresses</a>
none of the comments was in favor of this proposal.</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Mon, Oct 21, 2013 at 2:38 PM, Marc
Gemis <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:marc.gemis@gmail.com" target="_blank">marc.gemis@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 dir="ltr">
<div class="gmail_extra"><br>
<div class="gmail_quote">2013/10/21 Pierre Parmentier <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:pierrecparmentier@gmail.com"
target="_blank">pierrecparmentier@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<li> <a moz-do-not-send="true"
href="http://wiki.openstreetmap.org/wiki/Proposed_Features/Multiple_addresses"
target="_blank">Proposed Features/Multiple
addresses</a></li>
</blockquote>
</div>
<br>
<br>
</div>
<div class="gmail_extra">I don't like this proposal too
much. This is a relation in disguise. So why not use a
real relation instead ? A building relation (which
already exists) with multiple address node members. --
I know it's not your proposal, so I won't shoot the
messenger :-)</div>
<div class="gmail_extra">This is a mess to maintain if you
have to manually make sure that all numbers behind a
addr: are there. I would vote against it.</div>
<span class="HOEnZb"><font color="#888888">
<div class="gmail_extra">
<br>
</div>
<div class="gmail_extra">m.</div>
</font></span></div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Talk-be mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Talk-be@openstreetmap.org">Talk-be@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/talk-be">https://lists.openstreetmap.org/listinfo/talk-be</a>
</pre>
</blockquote>
<br>
</body>
</html>