|
I've tried searching and reading the source code, sorry if I've missed something obvious. The address for way 504486363 is associated with the Thamesmead place:suburb node 27485890, and that's good. But the address for way 5181163 does not include the Thamesmead suburb, even though I think it is closer to the Thamesmead node (952m as opposed to 1096m for the park). Can someone explain why it is using it one case and not the other? Thanks. |
|
Thamesmead only exists as node (https://www.openstreetmap.org/node/27485890) so Nominatim can only guess the boundaries. If you click 'display child places' on https://nominatim.openstreetmap.org/ui/details.html?osmtype=N&osmid=27485890&class=place you will see all streets associated with the suburb. The column 'distance' indicates that the cut-off is 1 kilometer. Nominatim takes one node of the street to look up the parents, that can fail when streets cross e.g. city or state boundaries, long streets or I'd say here it's off by a couple of 10 meters. I could point you to lib-sql/functions/ranking.sql for the diameter related logic but it's complex to debug. Best option forward is to create a suburb relation. The wikipedia article of the place seems quite descriptive about the extend of the surburb. |
