-
Notifications
You must be signed in to change notification settings - Fork 1
Wrong street name for house number in AssociatedStreet relation #4619
Comments
Author: lonvia This is an issue with the update process that did not update the house's address after you added the missing street member to the associatedStreet relation. The address will get corrected the next time the house is reindexed (e.g. because it is changed). A proper mechanism for propagating associatedStreet updates would be nice but I'm not sure it can be done as long as the associatedStreet relations are only saved in the slim tables. |
Author: g.idema[at]zonnet.nl Thanks for quick response. I'll change the house and see what happens to the search results. |
Author: lonvia Working around Nominatim bugs this way might get you into trouble with your fellow mappers. I've invalidated the area now. Street should be correct for the houses around Reinier Roeststraat. |
Author: g.idema[at]zonnet.nl Replying to [comment:3 lonvia]:
Thanks for invalidating this area. The street is correct now. Gertjan Idema |
Author: lonvia Nominatim would be perfectly happy if you added only addr:street tags and got rid of the associatedStreet relations. The relations mostly don't carry any additional information and are a bit of a pain to handle. addr:street is much better supported. I don't recommend adding both, chances are good that your data will sooner or later be inconsistent. |
Author: lonvia see also #4810 |
Reporter: g.idema[at]zonnet.nl
[Submitted to the original trac issue database at 3.57pm, Wednesday, 10th October 2012]
When I search for "Reinier Roeststraat 6, Leusden" I get 2 results.
The first result is the one I'm looking for. The second is a different house with house number 6 in the nearby "Kees van Burgstedenstraat" street.
Strangely enough the second result is being reported as "Reinier Roeststraat 6" in stead of "Kees van Burgstedenstraat 6", even though it is in an associatedstreet relation with name "Kees van Burgstedenstraat".
The text was updated successfully, but these errors were encountered: