[OSM-talk-be] Geocoding met foute postcode's

[Kurt Roeckx]

On Mon, Jul 22, 2013 at 05:20:07PM +0200, Glenn Plas wrote:
> Vandaag volgende tegengekomen:
> 
> http://nominatim.openstreetmaps.org/reverse.php?format=json&lat=50.9420900&lon=4.7305583&zoom=18&addressdetails=1&email=glenn@byte-consult.be&accept-language=nl,en;q=0.8,fr;q=0.5
> 
> resultaat:
> 
> {"place_id":"12246533","licence":"Data \u00a9 OpenStreetMap
> contributors, ODbL 1.0. http:\/\/www.openstreetmap.org\/copyright","osm_type":"node","osm_id":"1156867059","lat":"50.9424155","lon":"4.7310233","display_name":"Station,
> Stationsstraat, Rotselaar, Leuven, Vlaams-Brabant, Vlaanderen,
> 3012KA, Belgi\u00eb, European Union","address":{"bus_stop":"Station","road":"Stationsstraat","city":"Rotselaar","county":"Leuven","state":"Vlaanderen","postcode":"3012KA","country":"Belgi\u00eb","country_code":"be","continent":"European
> Union"}}
> 
> Daar komt als postcode uit: 3012KA

Looking at postal codes, it seems most of them are wrong and not
tagged?  You probably now get whatever is closest by?

The only information I can find now is the place= nodes,
which ussually have openGeoDB:postalcode, and sometimes
also postalcode.

Does it make sense to move that information to relations
instead?  I guess they ussually fall together with
administrative boundaries.  But I'm not sure about
cities that have multiple postcal codes.


Kurt