Did the same (duplicate the admin relation, change into a postal-code
relation) for Bornem and there it works as well. Sas & Nattenhaasdonkstraat
now show the correct 2880 postal code. It took several minutes though
before all street segments were updated.

Since in Belgium the postal code areas coincide with village borders, we
have to double them. This 1-to-1 mapping might not be the case in other
countries. When we use those postal code boundaries, we do not have to put
the postal code on streets or admin relations anymore. At least not for
applications that understand those boundaries.

regards

m


On Thu, Dec 5, 2013 at 9:25 PM, Marc Gemis <marc.ge...@gmail.com> wrote:

> Bart,
>
> I just added a postal_code boundary for 2840 Rumst. And  yes, both the
> Hondstraat and Steenweg op Waarloos now get the correct postal code: 2840.
> They had 2550 (from Kontich) before. So postal_code boundaries are the
> solution for my nominatim problems.
>
> regards
>
> m
>
>
> On Thu, Dec 5, 2013 at 5:19 PM, Bart Van Lancker <b...@vlweb.net> wrote:
>
>>
>>
>>
>>
>> <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.75473
>>
>>
>>
>> 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.74683
>>
>>
>>
>> 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…
>>
>>
>>
>> _______________________________________________
>> Talk-be mailing list
>> Talk-be@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-be
>>
>>
>
_______________________________________________
Talk-be mailing list
Talk-be@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-be

Reply via email to