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

Kurt Roeckx kurt at roeckx.be
Mon Jul 22 21:24:36 UTC 2013


On Mon, Jul 22, 2013 at 11:21:05PM +0200, Glenn Plas wrote:
> On 2013-07-22 23:13, Kurt Roeckx wrote:
> >On Mon, Jul 22, 2013 at 10:44:51PM +0200, Ben Laenen wrote:
> >>On Monday 22 July 2013 22:24:09 Kurt Roeckx wrote:
> >>>On Mon, Jul 22, 2013 at 09:22:47PM +0200, Marc Gemis wrote:
> >>>>The only good solution is to create post code polygons. This is stated
> >>>>e.g. on the nominatim FAQ page:
> >>>>http://wiki.openstreetmap.org/wiki/Nominatim/FAQ#postal_codes
> >>>>I don't know hpw we can do this.
> >>>So basicly most administrative boundaries (relations) should also
> >>>be turned into a polygon?
> >>Boundary relations are polygons, the same kind as a multipolygon relations. So
> >>no need to change anything
> >I tried adding it to the boundary relation 1 hour ago, but it's still showing
> >a wrong result here.  My expierence is that nominatim updates
> >after like a few minutes already.
> >
> It takes about an hour to 2 hours to index the minute diffs/updates,
> I've setup a few nominatim instances this weekend and I came across
> that in de documentation I absorbed.  The extracts are loaded pretty
> fast but it's the reindexing part itself that takes a while to run.
> They also aggregate as you cant index 2 hours for each minute diff,
> so there is some aggregation.
> 
> As always, the wiki can be outdated, biggest problem with wiki's in
> fast moving scenes.  It can be faster however, it just depends on
> the data size.

Looking at the wiki, it says how to check that it's loaded, and it
seems to have been loaded.  I'll check later if it works properly
or not.


Kurt





More information about the Talk-be mailing list