[Geocoding] Fresh Nominatim different than nominatim.openstreetmap.org

[Sarah Hoffmann]

Hi,

On Tue, Apr 15, 2014 at 12:32:12PM +0000, Anders Gunnarsson wrote:
> > > > > 1). Hits in Norway and Australia get the country code aq
> > > > > (Antarctica)
> > 
> > The change is now pushed[1]. You can simply update to the latest version
> > and install the changes with:
> > ./utils/setup.php --enable-diff-updates --create-functions --create-
> > partition-functions
> > 
> > You then have to find the place_id of the affected countries. They are
> > in the URL of the details page. Then log into your database and run:
> > 
> > select place_force_update(<place_id>);
> > 
> > followed by: ./utils/update --index --index-instances 2
> > 
> > This will take a very long time.
> 
> I've tested updating the three countries I've found so far, Norway, Australia and Argentina. I see no change though, addressdetails=1 and the details page give cc aq. The data in placex for each country have correct country code, but incorrect calculated country code.

place_force_update() is indeed confusing. I've changed it now so that 
it also updates the object itself.

> > > > > 2). Differences in importance
> > >
> > > How can I verify that the import of wiki data was successful?
> > 
> > The table wikipedia_article should be aroung 6GB.
> 
> Ok, size seems correct.
> 
> > 
> > > Is it easy to back trace the calculations for importance, to see what
> > the importance data is based on??
> > 
> > There is an entry in the details page that states which wikipedia page
> > has been used. If that entry is missing, then importance is simply based
> > on the rank of the object.
> 
> I see that Wikipedia Calculated is missing for the example I have (Zagreb), while set where Importance is correc. Maybe the wiki data has changed?

The wiki link should have come from the linked place nodes. There were
two different bugs in the code that prevented that. Thanks for spotting
that.

Fixed in https://github.com/twain47/Nominatim/commit/76a83b91d7946a38c3757e21d7906d437b9dea49

Importance can simply be corrected by reindexing the affected placex
entry (i.e. set indexed_status=2 and reindex).

> > > > > 3). Places not found using structured address search
> > > > >
> > > > > Query:
> > > > > http://nominatim.openstreetmap.org/search.php?format=json&city=tao
> > > > > %20y
> > > > > uan%20xian&country=taiwan
> > > > >
> > > > > 10 places found on nominatim.openstreetmap.org vs 0 on our server.
> > 
> > Do I understand right? node 60655807 is marked as a county on the
> > details page on your server?
> 
> No, the search term referred to a "taoyuan county" with osm_id 2770986. Though searching for city=taoyuan county&country=Taiwan get hits on osm.org including 60655807, but not on our server. Maybe nothing worth spending time on.

It seems that it is found as place=town but not as place=city, I'll have to
look why. The bad match betwwen xian and shi is due to a hack that removes
all the shi for Japanese place names:
https://github.com/twain47/Nominatim/blob/master/sql/functions.sql#L379
and xian getting removed from the search term as a frequent word.

Sarah