[OSM-talk-be] My first attempt at a boundary
Bart Van Lancker
bart at vlweb.net
Thu Dec 5 16:19:35 UTC 2013
<I used the place= node as admin_centre. That's also the one that I moved.
Should there be a difference between the two ?
<As for the two relations: I'm still fighting nominatim. I want all the
street(segments) within the Muizen area to return 2812 as post code. In
Germany they use the dedicated boundary=postal_code. This is also what <was
recommended by someone on a similar question on help.openstreetmap.org.
<So I tried that.
That's what I'm trying to do in Ghent, and it doesn't work. I've defined the
"deelgemeenten" with their postal code (actually as a
boundary=administrative), but there seem to be some postal codes "hardcoded"
in Nominatim, which seem to have preference over the postal code
bounbdaries.
Examples :
Waterkluiskaai in Sint-Amandsberg still has postal code 9050, although in
reality it has 9040 :
http://www.openstreetmap.org/search?query=waterkluiskaai#map=17/51.04681/3.7
5473
Sint-Amandsberg has 9040, which is correct :
http://www.openstreetmap.org/search?query=sint-amandsberg#map=17/51.04681/3.
75473
9040 is NOT hardcoded in Nominatim :
http://www.openstreetmap.org/search?query=9040#map=17/51.04681/3.75473
9050 is :
http://www.openstreetmap.org/search?query=9050#map=17/51.04681/3.75473
So everything near the 9050 "node" will get the postal code 9050, regardless
of boundaries :
http://www.openstreetmap.org/search?query=tarbotstraat#map=17/51.04557/3.746
83
while Tarbotstraat is within the 9000 boundary, but close to the "9050
virtual node"
The only solution is to add the postal_code on street level.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-be/attachments/20131205/a8d56bbd/attachment.htm>
More information about the Talk-be
mailing list