Opened 10 years ago

Closed 8 years ago

#3378 closed defect (fixed)

Nominatim county wrong

Reported by: David Earl Owned by: geocoding@…
Priority: minor Milestone:
Component: nominatim Version:
Keywords: Cc:


Nominatim is reporting the wrong counties in some cases.

I investigated a few where I got mismatches against a database I was comparing with for the UK. For example:

Alfold Crossways is in Surrey, but N reports it in West Sussex. It's not a map bug: you can see it is in Surrey on OSM.

Amport is in Hampshire (really, and on OSM) but reports Wiltshire

Appleton Roebuck is in North Yorkshire, but reports South Yorkshire

Braceborough is in Lincolnshire but reports Rutland

and so on.

Change History (4)

comment:1 Changed 10 years ago by Tom Hughes

If you look at the detail page, like this:

then you will be able to see that both counties have been represented as nodes rather than polygons, so nominatim has had to guess the extent of the county.

If there is a boundary polygon for Surrey then it looks like there is something wrong with it as Nominatim isnt recognising it. Equally if there is a polygon then the node should be removed to avoid causing confusion.

comment:2 Changed 9 years ago by ponzu

TomH, your comment helps with my research into the same or similar issue and the recommendation to remove the county node echoes the advice I received elsewhere. However, is there a working alternative to using county node (in addition to countyt polygon, that is) as a method of generating a level-appropriate label on the slippy map? Currently, if there is no place node for county (city, suburb, village, hamlet), there will be no label - unless I'm missing some tagging rule.

comment:3 Changed 9 years ago by Tom Hughes

Owner: changed from openstreetmap@… to geocoding@…

comment:4 Changed 8 years ago by Sarah Hoffmann

Resolution: fixed
Status: newclosed

Parenting problem. Fixed now.

Note: See TracTickets for help on using tickets.