Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#4995 closed enhancement (invalid)

Reverse geocoding wrong state

Reported by: emilio.mejia@… Owned by: geocoding@…
Priority: minor Milestone:
Component: nominatim Version: 2.0
Keywords: Cc:

Description

On my local server the xml result query show wrong state.

Tested:

http://nominatim.openstreetmap.org/reverse?format=xml&lat=10.3116016666667&lon=-84.1814116666667&zoom=18&addressdetails=1

Result: (OK) <state>Alajuela</state>

On my local installation:

http://192.168.1.117/nominatim/reverse?format=xml&lat=10.3116016666667&lon=-84.1814116666667&zoom=18&addressdetails=1

Result: (Wrong) <state>Heredia</state>

The local server is update to : Data: 2013/09/25 19:13 GMT

I need to make some additional changes to my server or in osm?

Change History (6)

comment:1 Changed 6 years ago by Sarah Hoffmann

If it works on osm.org, there should be no changes necessary but hard to say without knowing more about your installation. Are you using extracts and updates from Geofabrik or a full planet?

If you use the 2.0 version of Nominatim, you should do a reimport with the latest code from github.

comment:2 Changed 6 years ago by emilio.mejia@…

I use the lastest code from gtihub and extracts updates from Geofabrik with central-america-latest.osm.pbf. Check on http://192.168.1.117/nominatim/search.php?q=Alajuela and the boundary no exist, how to import boundary ?

comment:3 Changed 6 years ago by Sarah Hoffmann

You can add a single relation with the update script by doing something like:

./utils/update.php --import-relation 3222933 --index

The boundary was published in the diff of Sept 22nd, so it should be there. Could you confirm that the diff was imported without errors?

comment:4 Changed 6 years ago by emilio.mejia@…

The diff was imported without error. I did another install Nominatim server downloading of Geofabrik today however the problem persists even importing the relations (7) of the admin_level 4. In the new server install also wikipedia data and result is same, wrong state and boundary do not appear in the query local wiki.

comment:5 Changed 6 years ago by Sarah Hoffmann

Resolution: invalid
Status: newclosed

The relation was broken, it did contain one of the boundary ways twice. After fixing that, the relation imports fine. The osm.org instance happened to import one of the intermediate versions that was ok. Check the other relations for similar duplicates.

comment:6 Changed 6 years ago by emilio.mejia@…

Perfect!!! Works! Tks!

Note: See TracTickets for help on using tickets.