<div dir="ltr">Maybe I should start using the fixaddresses plugin<div style>I've been using the plugins terracer, building tool, etc. for over 1 1/2 year. I even wrote a page on it: <a href="http://wiki.openstreetmap.org/wiki/User:Escada/JOSM_and_Housenumbers">http://wiki.openstreetmap.org/wiki/User:Escada/JOSM_and_Housenumbers</a> :-) </div>
<div style><br></div><div style>But now that I have a python script to convert my GPX trails, they do not fit perfectly in my workflow. I start from nodes that are tagged with building=house and addr:housenumber=XXX (after importing my modified GPX trail). I still use the terrace plugin to split though. I do use the stylesheets too.</div>
<div style><br></div><div style>Did you try looking up businesses represented as nodes in buildings with address information ? Nomatim does not understand this (I think). Should we map for Nomatim, not sure ...</div><div style>
<br></div><div style><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Apr 16, 2013 at 10:48 AM, Glenn Plas <span dir="ltr"><<a href="mailto:glenn@byte-consult.be" target="_blank">glenn@byte-consult.be</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 04/16/2013 10:08 AM, Marc Gemis wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I never put address details on sheds or garages.<br>
</blockquote></div>
Didn't mean to sound like you did. I actually did in the past by not paying enough attention to the plugins, I'm in the process of fixing this btw :)<div class="im"><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
The building=house is on the <a href="http://wiki.openstreetmap.org/wiki/Map_Features#Building" target="_blank">http://wiki.openstreetmap.org/<u></u>wiki/Map_Features#Building</a> page. That's as official as it can get for me.<br>
</blockquote></div>
Sorry, I had to check before talking. The building key is open for free tagging I think anyway, so it would not be an error anyway if it's not on there (yet).<div class="im"><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Also use building=apartment whenever I can/remember/wrote down.<br>
</blockquote></div>
nice suggestion, I'm going to start doing this too.<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
I did use AGIV for some of my more recent "expeditions". Unfortunately, it did not help me in a few cases. I had numbers from mailboxes on the street, but didn't know the houses (in private area). AGIV had none of them.<br>
</blockquote></div>
you probably know this , I noticed only the deepest zoom level has all the numbers they know about. But I second that it's not the address bible I first thought it would be.<div class="im"><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
With my new workflow (address nodes generated from GPX waypoints), I first have them in a separate layer. I use the lasso tool to select all nodes in 1 street. Then add street (but could easily add city, country, postcode) as well to the whole selection.<br>
</blockquote></div>
I pretty much do the same using nodes. But then I use the terracer plugin, it's not only awesome to split houses in 1-2-n pieces but you just select a street + an addr node and a building and press SHIFT-T. It will put the street name in the the building tags.<br>
<br>
Next I use fixaddresses to complete the other tags, some logic is used to auto-guess the streets, which sometimes fails miserably but all the rest is filled out for you and most of it is correct, it just needs a human to apply the guesses/changes.<div class="im">
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
No need for any of the plugins. But I used them before (for the work in Aartselaar e.g.).<br>
</blockquote></div>
Not convinced yet I see :)<div class="im"><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
A question regarding houses without numbers (e.g. churches, libraries, ...) The official address is e.g. Kerkstraat z/n<br>
How is that mapped ? addr:housenumber = z/n does not sound correct to me.<br>
</blockquote>
<br></div>
I would omit the housenumber, that's what I do. tagging it as 'z/n' is the same as putting an imaginary number on it, e.g. it's an error. What I find difficult is buildings with an address containing a business (shop/amenity) with a separate address from the building (or the same sometimes, but the building itself has several numbers). There I see the merit of not duplicating data... I eventually settled for tagging the adress information on the building (less likely do disapear) and putting the amenity within the building border (and try to remove existing duplicate address data on that node).<br>
<br>
Businesses are far more likely to be gone in 10 years than buildings, when you put the address data on the node instead of the building, chances are great that the address info will be deleted too in the process. But putting the same address info on both (I tried some localy - it's ugly and I need it fixed soon) is very ugly on the map (duplicate housenumbers visible). It makes sense for me, when the shop is gone, you can remove the node entirely, and all address info related to the building is still there.<div class="HOEnZb">
<div class="h5"><br>
<br>
Glenn<br>
<br>
<br>
______________________________<u></u>_________________<br>
Talk-be mailing list<br>
<a href="mailto:Talk-be@openstreetmap.org" target="_blank">Talk-be@openstreetmap.org</a><br>
<a href="http://lists.openstreetmap.org/listinfo/talk-be" target="_blank">http://lists.openstreetmap.<u></u>org/listinfo/talk-be</a><br>
</div></div></blockquote></div><br></div>