[Talk-ko] Fwd: MapRoulette Challenge: Korean junctions

[Lukas Sommer]

I think it would also be useful to mention that complex junctions
(that have more than only one central joining node) should be tagged
with junction=yes on an area instead of a node.

2017-03-20 14:38 GMT, 느림보 <nrimbo at gmail.com>:
> I joined MapRoulette today and found a challenge whose name is Korean
> junctions.
>
> Description of the project is below:
>
>> *Junctions and their names are very important in Korea and Japan, because
>> people will reference those (instead of the street names) to describe a
>> route or location. A junction with a name will be rendered in Mapnik, but
>> unfortunately many junctions have been imported as single points close to
>> the actual junction.*
>>
>
> It suggests two fixed one is related to point and the other is naming rule.
>
>> Help fix junctions mapped as points in Korea.
>>
>>    1. Junctions need to be the joining node of several ways, not a point.
>>    2. In ID, you can just move the node to the actual intersection.
>>
>> Make sure the naming is correct.
>>
>> Example: OLD (wrong): name:사동삼거리 (Sadongsamgeori)
>>
>> NEW: name:사동삼거리, name:ko_rm:Sadongsamgeori name:ko:사동삼거리
>>
> I have some concerns related to the challenge.
>
> Many Korean junctions were imported using mp2osm, however I looks like
> there was no crosscheck after the importment. When I joined OSM community,
> I modified some junctions in my local area (Gunpo, Anyang, and Uiwang), and
> I found many POIs indicate un-named junction. (I justified it using street
> sign on the road.) -- 17 of 58 POIs were classified to the case and I
> deleted them.
>
> Second, naming rule. Discussion on the naming rule is on-going. It is going
> to have a consensus on some cases. Korean name into name / name:ko tag.
> English name into name:en tag. However discussion on other topics are
> on-going.
>
> name:ko_rm is also on discussion -- some topics are
> 1) It is transliteration of name tag. Should we manage this tag manually?
> 2) Where should we write down Romanizeed form of untranslatable name?
>     For example. "name:en : Seoul." Is it OK to write down some romanized
> form into name:en?
>
>
> From above description, I suggest following things
> 1) Add task to check existance of the named junction.
>
> You can find name of a junction top of road sign or near the junction
> eg) http://pds.joins.com/news/component/htmlphoto_mmdata/201402/
> 04/htm_2014020411231837003790.jpg (청담사거리)
> <http://pds.joins.com/news/component/htmlphoto_mmdata/201402/04/htm_2014020411231837003790.jpg>
>
> 2) Do not require to add name:ko_rm tag. Instead replace its severity to
> optional.
>
> I think it would be better to encourage to add English name of juctions.
> Some of road signs displays English name, in other cases it can be easily
> translatable except one arguable thing.
> There may be dis-agreements on translation of '삼거리 (3-way junction:
> junction)' or '사거리 (4-way juction: intersection)' or '오거리 (5-way junction:
> crossroads)' as description on http://wiki.openstreetmap.org/
> wiki/Korea_Naming_Convention because offical english words for 삼거리, 사거리,
> 오거리 are junction and only "junction"s are shown on road sign.
>
> Nrimbo.
>


-- 
Lukas Sommer