2 ms·
Amusingly, OSM apps can suffer from similar problems, because the way things are done vary across the world, and the software tends to at least start by being d
by chrismorgan 6y ago
Amusingly, OSM apps can suffer from similar problems, because the way things are done vary across the world, and the software tends to at least start by being designed to work best with the way things are annotated in a particular area. I filed https://github.com/QwantResearch/qwantmaps/issues/65 https://github.com/QwantResearch/qwantmaps/issues/65 because Qwant Maps was resolving “Navarre” to the centre of a rather large administrative boundary by that name, so that it’s 20km away from the village node that it should be using instead.
(That particular issue is partly resolved by OSM data changes that have happened since: it’s still using the administrative boundary, which is the wrong thing for it to do, but seven months ago someone added an admin_center to that boundary so that Qwant Maps drops the pin on the right point rather than the centre of the boundary—though it still zooms to include the whole boundary, which is much wider than it should zoom.)