You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: kaldari [Submitted to the original trac issue database at 11.56am, Friday, 10th May 2013]
A month ago (April 10), I noticed that the Belize/Guatemala border was very wrong. Several towns that were unquestionably part of Belize were shown to be on the wrong side of the border and in Guatemala instead. I fixed the border to be accurate (using the actual physical features that define the border), and double-checked it against maps.google.com, www.bing.com/maps/, and a CIA map. This put the towns back in the right countries (at least in edit view). A month later, the border in the non-editing interface is still wrong in all but 3 of the 19 zoom levels. In addition, if you search for a town like Jalacte, it still reports that the town belongs to Guatemala. Can this problem be fixed?
P.S. - I have no idea what component this should belong to.
The text was updated successfully, but these errors were encountered:
Author: Ldp [Added to the original trac issue at 9.26pm, Friday, 10th May 2013]
I have asked for fresh renders in some zoom levels (8-19) around Jalacte. This seems to have moved the rendered border westward a bit, putting Jalacte visibly in Belize again.
The tiles showing an old, more easterly, placement of the border were from around Feb 7, although some were as recent as early April. So it seems that it was moved in the data not that long ago.
This can also explain why Nominatim hasn't picked this up yet, and still puts Jalacte squarely in Guatemala.
Author: lonvia [Added to the original trac issue at 9.55pm, Friday, 10th May 2013]
Looks like Nominatim isn't really able to pick up changes to country borders because of the search order in get_country_code(). It looks up the fallback geometries first which naturally do not change. Once it has picked up the wrong country from there, it will use the wrong partition and won't have any chance to calculate a decent address.
Reporter: kaldari
[Submitted to the original trac issue database at 11.56am, Friday, 10th May 2013]
A month ago (April 10), I noticed that the Belize/Guatemala border was very wrong. Several towns that were unquestionably part of Belize were shown to be on the wrong side of the border and in Guatemala instead. I fixed the border to be accurate (using the actual physical features that define the border), and double-checked it against maps.google.com, www.bing.com/maps/, and a CIA map. This put the towns back in the right countries (at least in edit view). A month later, the border in the non-editing interface is still wrong in all but 3 of the 19 zoom levels. In addition, if you search for a town like Jalacte, it still reports that the town belongs to Guatemala. Can this problem be fixed?
P.S. - I have no idea what component this should belong to.
The text was updated successfully, but these errors were encountered: