1ec5 left a comment (openstreetmap/openstreetmap-website#6758)
> In particular I wonder if any local communities maintain tags whose keys have
> non-latin characters. I'm no expert in any of the many tools that could
> answer this, so no idea.
I’m unaware of any tagging convention that explicitly calls for non-Latin
characters in keys, but some tagging schemes technically allow relatively
freeform names as subkeys, such as `payment:*=*` and `ref:*=*`. [This
report](https://taginfo.openstreetmap.org/reports/characters_in_keys#letters)
shows that non-ASCII keys are relatively rare, the most common being
[`agglomération=*`](https://taginfo.openstreetmap.org/keys/agglom%C3%A9ration)
(8,814 occurrences) and
[`railway:position:exact:京通`](https://taginfo.openstreetmap.org/keys/railway%3Aposition%3Aexact%3A%E4%BA%AC%E9%80%9A)
(120).
Formalizing a character set requirement would make the API more opinionated
about tagging schemes than it usually is. Mappers using QA tools have
historically been responsible for cleaning up exotic characters in keys. It’s
quite easy to introduce them using other mainstream editors. The only
difference here is that the text box is so accessible that a cat on the
keyboard could plausibly mess up a feature.
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/6758#issuecomment-3909231329
You are receiving this because you are subscribed to this thread.
Message ID:
<openstreetmap/openstreetmap-website/pull/6758/[email protected]>
_______________________________________________
rails-dev mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/rails-dev
