Korea Naming Convention
In Korea the following naming convention has been adopted. See Ko:Map Features#표기법 For the original Hangeul reference.
For any named feature it is recommended to include the name in Hangeul. If the feature has an English name, you may add it as well. It is not necessary or advised to add transliterations as they may be done by a renderer of the data with better accuracy. If you still want to add romanisations they should follow the Revised Romanization of Korean for South Korea, and the McCune–Reischauer romanisation for North Korea. If you don't know all of this information, don't worry.
|name=한국어||This is the 'general' name of the object. Usually this will be in Korean (using Hangeul) only.|
|name:ko=한국어||The Korean name of the object, in Korean (using Hangeul). Usually this will be identical to the name. This redundancy was necessary to facilitate the transition to the current naming scheme, but may be phased out.|
If you don't know the Korean Romanisation, leave this tag empty.
|name:en=English||The English name of the object if known. In the English name, do not include any number transliteration (mostly found on street signs) e.g. "7(chil)" should simply be "7". The reason for this is because it is not used on all signs, so we should be consistent and omit it. If this field is identical to ko_rm it should be omitted, because romanised Hangeul is not English!|
If you can't type Hangeul, or don't know the Korean (or English) then simply omit it. Someone will hopefully come along later and add it. Alternatively, ask for help on the talk-ko mailing list.
For the English information, please use the English that is printed on the sign (if present). Don't simply put romanised Korean in the field for English. That it is written in Latin characters doesn't make it English. Consider adding additional names as name=* variations.
Common Korean expressions
In 2009 a number of roads and POIs were imported into OSM. Some of the translations for the English part of the names can be improved. They are mapped as individual points or in the case of bridges as a pair of points. They need to be made a node on a line. In the case of junctions the node needs to be placed where the roads actually intersect and the tag junction=yes needs to be added. In the case of a bridge, the line must be split in segments and for the bridge segment the bridge=yes tag needs to be added. Here are some common ones with suggested improvements:
|Hangeul||Romanised Korean||English||Usage tips|
|-분기점||-bungijeom||JC||Junction between two motorways|
|-삼거리||-samgeori||Junction||T-junction, 3-way junction|
|-사거리||-sageori||Intersection||This is basically the same thing|
|-교||-gyo||Bridge||Drop the ~gyo, so Namhagyo becomes Namha Bridge. See Bridges in Korea|
|-산||-san||Mountain||Drop the ~san, so Hallasan becomes Halla Mountain.|
|-사||-sa||Temple||Drop the ~sa, so Heinsa becomes Hein Temple.|
|-강||-gang||River||Drop the ~gang, so Hangang becomes Han River.|