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: jacques[at]famille-lys.com [Submitted to the original trac issue database at 4.07am, Thursday, 3rd March 2011]
When searching for Maubeuge, the two first results are wrong, as they place this city in Belgium instead of France, although the postal code is correct. The third result returns a small hamlet or locality bearing the same name and located in an other French region.
This error (Belgium instead of France) is also encountered for several other cities or towns in the administrative area of Maubeuge. (test 'Hautmont'...)
The text was updated successfully, but these errors were encountered:
Author: twain [Added to the original trac issue at 10.57pm, Sunday, 27th March 2011]
This is related to the fact that France uses a non-standard way of defining its borders using relations of relations. Until that is resolved (or osm2pgsql is extended to support this data format) this can't be fixed.
Reporter: jacques[at]famille-lys.com
[Submitted to the original trac issue database at 4.07am, Thursday, 3rd March 2011]
When searching for Maubeuge, the two first results are wrong, as they place this city in Belgium instead of France, although the postal code is correct. The third result returns a small hamlet or locality bearing the same name and located in an other French region.
This error (Belgium instead of France) is also encountered for several other cities or towns in the administrative area of Maubeuge. (test 'Hautmont'...)
The text was updated successfully, but these errors were encountered: