I have been working on the bus and subway routes in Seoul lately, but there are still many discrepancies and missing tags. So I thought I might try to do some planning instead of always improvising, une fois n’est pas coutume. And I’ll practice my English, too, and learn more about Markdown.
The references:
The rules :
-
Work on subway lines 1 to 9. Whether other lines should be dealt the same way might be discussed later.
-
Every existing
railway=stationnode that corresponds to a subway station should also be tagged aspublic_transport=station,subway=yesand (if it’s only for lines 1 to 9)station=subway. Reciprocally, anypublic_transport=stationshould be tagged the same way if it corresponds to a subway station. -
Existing nodes should not be moved unless really necessary (i.e. do not apply the “This node should not be part of a railway track” rule for an existing
railway=stationnode, unless I am ready to really map apublic_transport=stop_arearelation for that station). -
Only one
railway=stationnode should exist for every subway station, unless it is used for very different networks (lines 1 to 9 will be considered as one single network, I may let severalrailway=stationnodes if they exist in multi-network stations such as 서울역, but I’m not sure about that). -
Every existing
public_transport=stop_positionnode in the subway network should be tagged assubway=yesand be located on arailway=railorrailway=subwayway. It should not be tagged asrailway=stationorstation=subway. -
All the
public_transport=stationnodes that belong to the same line should be members, with no role, of the relation(s) associated with that line. These relations may follow the new Public transport proposal (i.e one relation for each direction or branch) or not.

