Opened 7 years ago

Closed 7 years ago

#4247 closed defect (fixed)

Address contains a suburb/county of a neighbouring area

Reported by: scillystuff Owned by: geocoding@…
Priority: minor Milestone:
Component: nominatim Version:
Keywords: suburb Cc:

Description

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

gives

<reversegeocode timestamp="Sun, 26 Feb 12 13:01:43 +0000" attribution="Data Copyright OpenStreetMap Contributors, Some Rights Reserved. CC-BY-SA 2.0." querystring="format=xml&lat=53.722468&&lon=-1.781888&zoom=18&addressdetails=1"> − <result place_id="51995012" osm_type="way" osm_id="46876064" lat="53.7182409210839" lon="-1.78463327256477"> Smith House Lane, Low Moor, Calderdale, West Yorkshire, Yorkshire and the Humber, England, United Kingdom </result> − <addressparts> <road>Smith House Lane</road> <suburb>Low Moor</suburb> <city>Calderdale</city> <county>West Yorkshire</county> <state_district>Yorkshire and the Humber</state_district> <state>England</state> <country>United Kingdom</country> <country_code>gb</country_code> </addressparts> </reversegeocode>

Suburb should be Lightcliffe, or council ward of Hipperholme and Lightcliffe. Node for Lightcliffe is present and is nearer to (but not covering) location than node for Low Moor, so I don't know why wrong suburb is returning.

Change History (4)

comment:1 Changed 7 years ago by Sarah Hoffmann

This is another incarnation of the problem of missing administrative levels.

When making up an address, Nominatim tries to relate a place to as many administrative levels as possible. Because Calderdale does not have suburbs, Nominatim adds the closest suburb it can find, which in this case happens to be a suburb of Bradford.

Nominatim needs a detection that excludes place nodes that are outside the area of a lower administrative level polygon in the same address.

comment:2 Changed 7 years ago by Sarah Hoffmann

Summary: Nominatim problem: Location in Calderdale is returning suburb in Bradford, a neighbouring metropolitan countyAddress contains a suburb/county of a neighbouring area

comment:3 Changed 7 years ago by Sarah Hoffmann

Note: the current solution with linked places does not solve the bug in cases where the suburb/county node does not have an administrative boundary. Those nodes still need to be excluded explicitly.

comment:4 Changed 7 years ago by Sarah Hoffmann

Resolution: fixed
Status: newclosed

Nominatim now also excludes nodes outside the parent area. This should fix all known cases.

Note: See TracTickets for help on using tickets.