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
Someone in the Korean OSM community just pointed out that these tiles are using romanised Japanese versions of Korean city names rather than the name:en field. Aside from being incorrect, this is rather offensive, so you might want to fix your underlying data source for this.
The cities below are a sample identified in the Korean OSM group, but are not exhaustive. I quick glance shows it's a pretty widespread issue.
Outch, that's bad. Also what's going on with the different font for cities with an breve character in it. Hwawŏn and Naesŏ? The breve is only used in the McCune–Reischauer romanization which is not any more in use since 2000 (But still the official romanization in North Korea). We seem to have a map of Korea here with place names from the period of Japanese Imperial occupation and romanized in North Korean style. Truly unique!
Someone in the Korean OSM community just pointed out that these tiles are using romanised Japanese versions of Korean city names rather than the name:en field. Aside from being incorrect, this is rather offensive, so you might want to fix your underlying data source for this.
Or the name:ko-Latn field which is more appropriate in most cases. We cleaned this up not too long ago. There shouldn't be a reason to use third party names sources anyway, and in particular not when there is just an OSM attribution and the imperial names are taken from another source while OSM will be blamed for it.
Someone in the Korean OSM community just pointed out that these tiles are using romanised Japanese versions of Korean city names rather than the
name:en
field. Aside from being incorrect, this is rather offensive, so you might want to fix your underlying data source for this.The cities below are a sample identified in the Korean OSM group, but are not exhaustive. I quick glance shows it's a pretty widespread issue.
URL: maps.stamen.com/terrain/#8/35.729/-233.124
The text was updated successfully, but these errors were encountered: