|
I thought this had come up before but couldn't locate relevant past questions. Nominatim takes address info for POIs from their associated streets. This sometimes leads to incorrect results. I have two cases in mind:
|
|
Even if Nominatim or other services fail at assigning multiple addresses to objects crossing administrative boundaries you should not split them at these points. As you already mentioned this is tagging/mapping for a specific service and consequently should be avoided. The only valid solution is to improve these services and fix such problems on the data consumer side. |
|
If I understand this page right, the indexing goes bottom-up. So i's invoked by the addresses itself and uses the tagged/closest road and the polygone/place radius area. So a road that crosses multiple boundaries can also be found in both cases and we don't need to split it. (but please may nominatim experts call me wrong) Based on some observations searching at nominatim.openstreetmap.org, this doesn't appear to be the case.
(05 Jan '14, 12:04)
Paul_012
1
Maybe then a post (and updating the docs in the wiki) here might be a good choice: https://lists.openstreetmap.org/listinfo/geocoding
(05 Jan '14, 12:22)
iii
iii, the page you mention also states "During the indexing process an address is also calculated using the first feature found for each level. Where an is_in value is provided it is used to filter the address." So, it's always located in "the first"
(06 Jan '14, 12:01)
escada
|
