[Geocoding] Technical questions about building Nominatim instance
Teemu Ikonen
teemu.ikonen at iki.fi
Tue Sep 21 10:36:47 BST 2010
Hi,
Replying to myself in case somebody finds solutions useful.
On Thu, Sep 2, 2010 at 9:21 AM, Teemu Ikonen <teemu.ikonen at iki.fi> wrote:
> Q2. For some reason reverse geocoding results from my own instance
> (I've tried with whole Planet import and country extracts) do no
> always match the ones from main site (nominatim.openstreetmap.org).
> Especially the high level data like country and county are sometimes
> missing. What could be the reason for this?
Root reason turned out be buggy postgis 1.3.6 version that threw
exception when gazetteer-loaddata.sql script was loading relation data
(insert into placex select * from place where osm_type='R'). The
insert did get rolled back and not relation data was inserted into the
database and therefore especially high level data was missing.
I did upgrade to postgis 1.5.1 and everything went fine.
> Q4. When I'm indexing the database (using util.update.php ..) I keep
> getting these errors on Postgres log when accessing the /reverse.php
> reverse geocoding from my app. Is this something I should be worried
> about? These do not appear when indexing is not running.
>
> .......
> ERROR: permission denied for relation place_boundingbox
> CONTEXT: SQL statement "DELETE FROM place_boundingbox where place_id = $1 "
> PL/pgSQL function "placex_update" line 60 at SQL statement
> SQL statement "UPDATE placex set indexed = true where indexed
> = false and place_id = $1 "
> PL/pgSQL function "get_address_by_language" line 16 at SQL statement
....
Some grants were missing from SNV version
grant SELECT on country_name to 'www-data'
grant DELETE on place_boundingbox to 'www-data'.
Br Teemu
More information about the Geocoding
mailing list