AddingJunctionsAndSidingsToOsm

= Introduction =

In this project we're working on adding extra metadata - junctions, sidings and other non-station location data - to OpenStreetMap (openstreetmap.org).

The AddingJunctionsAndSidingsProgress page shows what we've done so far.

= Aims =


 * To add nodes for junctions and sidings to OpenStreetMap
 * To add TIPLOC and STANOX codes to existing locations where the data is available

= Instructions = ''TODO. Develop instructions''

Most likely the tag ref:tiploc will be used as it has been used once already and is the most self explanatory.

= Involved =


 * Peter Hicks (talk) (OSM edits)
 * Mark Steward
 * Shaun McDonald (talk)
 * Harry Wood (talk)
 * Chris Northwood (talk) (OSM edits)

= Tasks =

Process
Develop process ideas e.g. : Assign one person to each route from the Sectional Appendix

Agreeing and documenting tags in OpenStreetMap
Agree with the OpenStreetMap people which tags to use when documenting TIPLOC and STANOXes. The process of agreeing OSM tags is a fun and fluid (and you may find it alarmingly informal!). User:Harry Wood and User:Shaun McDonald are long-time OSMers who can help with this. Some sub-tasks:
 * Look at existing tagging - DONE (there isn't much, but ref:stanox has been used and seems to make sense)
 * Proceed with adding in a small amount of data first of all, to establish example tagging (map first, ask questions later)  -  DONE
 * Clearly lay out on this page (above) instructions for finding source data, adding it to OSM, and how the tagging should work
 * Develop a couple of other examples and check that other people can follow the same instructions, but then slow down for the next steps:
 * On the OpenStreetMap wiki document the tags being used e.g. Key:ref:stanox. Label them as "proposed" and link to this project page for details
 * email for wider discussion. Maybe talk-transit and talk-GB with details of the tagging approach, and the proposed project here. See what the community thinks of it.
 * ....Receive ten different answers. Decide which answers to ignore :-)
 * Possibly link the the proposed tag docs from the more widely followed 'Railways' page, and/or Public transport, but note that these docs are international. We probably wouldn't expect these ref tags to be mentioned on 'Map Features' (there's quite a lot of tags on there, but not all tags)

= Questions =


 * Where a junction spans multiple lines, where does the junction node go?
 * Show the junction as being an area? Shaun McDonald (talk) 15:34, 5 November 2012 (UTC)
 * We could create a relation for the nodes involved in the junction and then add the tag to that relation? --Chris Northwood (talk) 14:11, 7 November 2012 (UTC)
 * Relations with all the points are a workable solution. Shaun McDonald (talk) 15:33, 9 November 2012 (UTC)
 * Where there is more than one TIPLOC at a station - e.g. Clapham Junction which has three - where should the nodes go? Should a closed way be created instead?
 * I would recommend a closed way, though I'm not sure about what other tags should go on there. I'm thinking that trying it in with a relation with the full station outline would prove useful. Shaun McDonald (talk) 15:34, 5 November 2012 (UTC)
 * If the station already exists, then we should add the TIPLOC to the station node or closed way that already exists? (can you have multiple tags with the same name on a node, or perhaps TIPLOC could be comma-separated?) --Chris Northwood (talk) 14:11, 7 November 2012 (UTC)
 * The keys on each node/way/relation have to be unique. In some cases people use a semicolon to add two values to the same key, however this is best avoided. Shaun McDonald (talk) 15:33, 9 November 2012 (UTC)
 * Should we also add platform data?
 * Yes, many stations already have the platforms mapped out in OSM. Shaun McDonald (talk) 15:34, 5 November 2012 (UTC)

= Rules =


 * If a station has more than one TIPLOC (e.g. Watford Junction which has WATFDJ and WATFJDC), but there is only a single 'station', do not attach the TIPLOC
 * Why? --Chris Northwood (talk) 14:11, 7 November 2012 (UTC)
 * If you are unsure of the correct TIPLOC, CRS code or STANOX, leave it blank and make a note so that somebody else can investigate