Opened 6 years ago

Closed 6 years ago

#4273 closed defect (invalid)

Croatia gets a "state" field when I do a reverse geocode

Reported by: Janjko Owned by: Janjko
Priority: major Milestone:
Component: nominatim Version:
Keywords: Cc:

Description

In this XML:

http://nominatim.openstreetmap.org/reverse?format=xml&lat=45.48209&lon=15.935122&zoom=18&addressdetails=1

I see that by reverse geocoding I get a county (<county>Karlovačka županija</county>), which is ok because we have those, but also a state (<state>Zagrebačka županija</state>), which Croatia doesn't have. Where do you get information about which administration levels does a country have?

The name it got for a state is actualy a neighbouring county.

Change History (3)

comment:1 Changed 6 years ago by lonvia

The county Karlovačka županija comes from the place node 549260451 and is wrong (see bug #4247). The state comes from boundary relation 226241 and is actually correct. It is confused as a state because Croatia seems to use admin_level=4 for its counties instead of the customary admin_level=6.

To fix this, we'd need an address localisation in Nominatim that maps the admin_levels to place types on a country basis.

comment:2 Changed 6 years ago by Janjko

  • Owner changed from geocoding@… to Janjko
  • Status changed from new to accepted

Thank you very much!

I have talked to Croatian mappers and they agree to change the borders to admin_level=6.

If the borders are admin_level=6, and the nodes are place=county, will it still be a problem? If so, I'll delete the nodes too, we don't need ways and nodes for the same thing (except for countries I guess, because of rendering.)

We'll see how it goes.

comment:3 Changed 6 years ago by lonvia

  • Resolution set to invalid
  • Status changed from accepted to closed

You can leave the nodes. (In fact, they are currently needed by the renderer to put the label of the county on the map.) Nominatim should find out that place nodes and boundaries belong together.

I'll close the ticket as you have fixed the issue in the OSM data.

Note: See TracTickets for help on using tickets.