[openstreetmap/openstreetmap-website] Add OpenMapTiles vector map (PR #4042)
Minh Nguyễn
notifications at github.com
Fri Jul 21 09:41:00 UTC 2023
> > so an English-speaking user will see the OSM area’s tag value, not the Wikidata item’s label.
>
> This fallback doesn't work well for places that only have a `name` tag. In Germany, OMT seems to be using mainly names from wikidata when I look at the map with a German locale. The reason of course being that we don't tag `name:de` when there is only a `name` tag present and no translations.
[This wiki page](https://wiki.openstreetmap.org/wiki/Special:PermanentLink/2559647#Repeating_name_with_language_specific_tag) discusses the issue in more detail. If the feature’s name is translated or transliterated into another language, then it is valid and expected to pair `name` with `name:de`. [This can come as a shock](https://lists.openstreetmap.org/pipermail/tagging/2022-March/thread.html#64124) to mappers who focus on monolingual regions and normally think of their language as the “obvious” one. To be sure, not everything named should have a `name:*`. An individual shop’s name typically does not have a reasonable translation, so `name:de` would serve very little purpose.
There is a gray area when it comes to features that do have translations but none of them is [locally attested or locally relevant](https://wiki.openstreetmap.org/wiki/Names#Language-specific_names). Data consumers face a catch-22 between, on the one hand, the principle that only locally attested names should be tagged in `name:*` and, on the other hand, the opinion that they should prefer `name` over any translations in Wikidata if there’s no `name:*`. Perhaps it isn’t a bad thing to expose mappers to this reality (optionally, as the Standard layer is still the default).
Again, an OpenMapTiles-based layer can address your feedback in at least two ways:
* Include both `name:de` and `name` in each label when the two differ (at the cost of some extra clutter and a stylistic departure from osm-carto)
* Disable the Wikidata fallback (which would require changes on MapTiler’s backend to avoid impacting their other customers)
> The issue is rather obvious with railway stations, e.g. https://osm.openmaptiles.org/#map=14/52.5229/13.4028&layers=V, even when using an English locale.
I assume you’re referring to the redundant “Station” suffix everywhere. This is the legacy of Wikidata bootstrapping its labels from Wikipedia (where the suffix is necessary for technical reasons that don’t apply to Wikidata). The issue can be comprehensively fixed in a matter of hours, as [I once did](https://community.openstreetmap.org/t/is-there-support-for-removing-all-name-tags-on-objects-with-a-wikidata-qid-present/8374/8) for place names in one language in many countries. Nevertheless, it highlights the fact that Wikidata is still a work in progress, just like OSM. If this project wants to hold a featured layer’s external data sources to a higher standard than OSM, then that is indeed this project’s prerogative.
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/4042#issuecomment-1645304893
You are receiving this because you are subscribed to this thread.
Message ID: <openstreetmap/openstreetmap-website/pull/4042/c1645304893 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20230721/8fbcf0a2/attachment-0001.htm>
More information about the rails-dev
mailing list