Proposed features/Multiple Tracks
|Number of tracks which are represented by this way|
|Used on these elements|
|Status: in use|
|Tools for this tag|
|Proposal status:||Abandoned (inactive)|
|Tagging:||tracks=single, double, left, right|
|Definition:||For multiple railroad tracks|
|Rendered as:||Renders multiple tracks next to each other|
|Nowadays each railway track is typically mapped as a separate way. Consider using fixme=* where multiple tracks are mapped as one|
Often double railway-tracks are only inserted to the database as single way. This key should tell the amount of tracks.
tracks=single or =1
tracks=double or =2
tracks=3, 4, ...
tracks=right or =left
This key is not widely used yet (as of 2009-03-23), there are some tests in Vienna .
Usage in Europe (as of 23-07-2009): tracks=... 2 (2090), 1 (972), 4 (234), 8 (8), 5 (8), 3 (5), single (4), grade3 (3), left (2), stairs (1), multiple (1), 25 (1), 6 (1), right (1), 7 (1)
Usage in Australia-Oceania (as of 23-07-2009): tracks 2 (41), 4 (4), 8 (2), 3 (2), 1 (1)
- Due to changes in Query-to-map this Template does not work anymore. You can use Template:Osm-query2. Please replace or delete this use of Osm-query template.
There could be problems on the connection between single- and double-tracks. Maybe a Key 'switch' can be introduced to specify how to handle them.
- If you switch from modelling multiple-tracks-on-one-way to one-way-per-track prior to the split, then you make it a lot cleaner for the renderer to handle. They can deal with making that transition look clean, given that track separation is a near-standard 3m, then you can send the separate lines off in different directions (eg a tram terminous loop).--RichardMann 13:58, 19 June 2009 (UTC)
This key is supported by the following renderers: