Openrailwaymap

openrailwaymap@openrailwaymap.org

306 discussions

Yard vs service_station (and other yard questions)
by jbittner＠gmail.com 21 Aug '20

21 Aug '20

Hello everyone. I just got started mapping with OSM/ORM. I've added and cleaned up a few things and while I'm sure I've made some mistakes I've learned quite a bit. 1.) Is there an official convention for designating passenger train storage yards at the end of the line? I've noticed some users prefer to tag them as "service_station" and the guidelines weren't too clear. To me a "service station" should be an employees-only station where regular trains do stop, but only employees are allowed to board/exit (e.g. LIRR Hillside, NJT Meadowlands Maintenance Complex). I've been adding them as yards (they're also more visible zoomed out) but if someone had already had them as service_station but I left them alone. 2.) I've noticed that if someone tagged an "area" as a yard, it won't display in ORM. For a few of these, I've added a yard "point" so it could be seen on ORM. It seems "redundant" though. 3.) Should intermodal terminals ("ramps") be tagged as yards? Should we consider a new tag? Lastly, is there a guide for what renders in ORM and what doesn't? It might be helpful since sometimes I add something yet it takes a few days for ORM to update so it's hard to know in advance what will render. Things that I've realized won't render: funiculars and funicular stations (they're there but no highlighting), abandoned:railway=station (would be nice to see some of the historic stops and terminals, maybe rendered with a strikethrough without the blue text), railway=preserved (the entire Strasburg Railroad wasn't rendering and it's a freight shortline as well as a tourist line, I switched it to railway=rail, usage=branch, railway:preserved=yes which worked rather nicely), signal_boxes, signals, defect detectors (and we should add defect_detector:high_car yes/no as an allowed tag), tunnel names (but bridge areas seem to render; it would be nice to "tag" the Howard Street Tunnel especially since it's right under a light rail line), turntable "areas" (possibly even turntables themselves), switches, buffer stops Things I'm not totally sure will render: railway=workshop, railway=interlocking Things I know will render: railway=junction, railway=crossing, railway=site (can we consider a tag for "timetable stations" on freight railroads, even as a sub-tag?), railway=milestone (can we consider a railway:position:prefix for milestone prefixes, I don't think we should use things like railway:position=mi:CFP14.0) OK that's quite a lot for a first post from a new guy. Thanks for reading. My best to you, Jon

3 4

Guidance to port tagging scheme to local country
by João Ferreira 19 Jul '20

19 Jul '20

Hey everyone! Hope y’all are well. I’m João Ferreira, aka HedgiePT, a (noob) mapper from Portugal. I tasked myself with kickstarting the signal scheme for all Portuguese railways, and I have a few questions that weren’t answered by the Wiki: It seems like every signal requires its own name in this scheme. How does this apply to variations of, say, speed limits? Germany gives different names to 'sign' and 'light' forms. Is this a requirement? Also, our distant speed limit signals <=40 km/h have a yellow colour, versus white for >40 km/h. Are these different names as well? Or are the names just for cataloguing purposes and aren’t all that important for rendering? It seems that, despite all this, the same name applies to all different values of a speed limit. Is this true? What’s the best way to tag potential aspects of signals? Does each signal get it’s own aspect tags, or are the generic tags enough? Is ORM accepting new signals to display in its web app? Do any of my questions mean anything to the ORM renderer? :) Thanks in advance. P.S.: I tried asking around your IRC chat but it was pretty dead. P.P.S.: I also tried sending this via my own e-mail client and it seems the original message did not arrive, so I'm sending via the web form. If it turns out to be a duplicate, I'm sorry for the spam :)

2 1

openrailway.org Legend
by Eckhard M 07 Jul '20

07 Jul '20

Hi all, from my perspective it seems that the legend at openrailway.map is not up to date. The narrow gauge lines are in light green now but the legend shows a black dotted line. Even other types seem to be wrong. Also the localization is not working, the legend is in English all the time. Is this intended in that way? Best, Eckhard

2 1

Self organised session at SotM about Railway tagging in the US tomorrow
by Michael Reichert 03 Jul '20

03 Jul '20

Hi, railway tagging in the US has been a large topic on the OpenRailwayMap mailing list (and partially on Talk-us) for the last couple of weeks. I think that there is still some need for further discussions and would like to invite all those who are interested in it to join a self organised session via Jitsi at the virtual State of the Map conference tomorrow at 20:00 UTC (= 22:00 CEST, 16:00 Eastern, 13:00 Pacific) Time in your time zone: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Railway+tagging+i… Jitsi room: https://jitsi.geofabrik.de/railway-tagging-us Please use Chromium or Chrome, avoid Firefox please. Best regards Michael

2 1

Draisine tracks
by Eckhard M 03 Jul '20

03 Jul '20

Dear all, what is the right way to tag routes where is draisine traffic only. Just wondering why https://www.openstreetmap.org/way/33651736 is not shown in ORM. Best, Eckhard

4 5

Bogenweichen
by Björn Mahrt 28 Jun '20

28 Jun '20

Moin, ich stolpere immer wieder über Bogenweichen, von denen im bisherigen Taggingschema nur die symmetrischen Außenbogenweichen berücksichtigt werden (railway:switch=wye). Ich würde gerne das Tagging dafür durch folgendes erweitern: 1.) railway:switch=wye eigentlich für alle Außenbogenweichen, da der genaue Radius eh nicht ermittelbar sein wird (und optisch geht es halt eh beides nach außen) 2.) railway:switch=inner_curved oder curved für Innenbogenweichen, die bisher bei den einfachen Weichen mit drinstanden. Natürlich gibt es das Problem, dass eigentlich alle railway:switch=default überprüft werden müssten, ob sie nicht Innenbogenweichen sind, aber schadet wohl auch nicht. Die Definition muss ja nicht sofort geändert werden, es wäre ja lediglich eine genauere Spezifikation. Gibt es da irgendwelche Meinungen oder Bedenken? Sonst würd ich das (demnächst) mal mit auf die ORM-Tagging-Seite übernehmen. Viele Grüße Björn

3 2

Tagging permanently earthed OCL
by garry.keenor＠gmail.com 28 Jun '20

28 Jun '20

In the UK we have a number of locations which are permanently wired with overhead line, but the wires are permanently earthed. This is typically done where the OCL is out of use in depots (for safety), to pass OCL through a very low bridge where electrical clearances cannot be provided, or at the limit of an electrified line. Has this been dealt with before? I would propose the following approach: electrified=contact_line voltage=0 frequency=<unset>

1 0

Tagging dual electrified tracks
by garry.keenor＠gmail.com 28 Jun '20

28 Jun '20

One of the issues that we've faced in improving the electrification tagging in the UK is dual electrified tracks. At some locations in the UK - and I believe in most countries - different electrification systems meet and overlap, with an overhead contact system and a ground-level contact system co-existing on a single track for a short distance. We have around 10 of these locations in the UK, some with multiple tracks. There is currently no guidance given to taggers on how to treat these tracks AFAIK. Has anyone already looked at this? We were thinking to use the standard OSM key=<value1;value2> syntax to identify these tracks. As an example, a single track provided with both 25kV 50Hz AC overhead line and 750V DC third rail would be tagged as follows: electrified=contact_line;rail voltage=25000;750 frequency=50;0 Thoughts welcome!

2 2

Tagging proposed railways as electrified
by garry.keenor＠gmail.com 28 Jun '20

28 Jun '20

Hello all again. I have a query about acceptable convention for tagging a proposed railway, i.e. one that is tagged railway=proposed If the electrification system that this new railway will adopt is known, it is normal/acceptable to add electrification tags? The obvious example here in the UK is HS2, which is going to be 25kV 50Hz AC overhead line as a matter of public record. Should we tag that as electrified=contact_line/voltage=25000/frequency=50?

2 2

hello, an introduction
by garry.keenor＠gmail.com 24 Jun '20

24 Jun '20

Hello! I'm a railway electrification engineer working in the UK, and a small group of us are planning to produce an electrification-focused map of the UK rail network using OSM data. We are aware of your ongoing project, and it is clear from chat on your github that you have plans to add an electrification view at some point. I wanted to introduce us and let you know that we exist; and to let you know that we are not intending to compete with your much bigger project, but rather produce something fairly quickly to inform the ongoing debate about decarbonisation and further electrification in the UK. We are also thinking about how we represent a couple of electrification features that we have in the UK that the existing tag scheme does not support, and wondered if we could collaborate on that aspect. Garry Keenor

6 16

← Newer
1
...
5
6
7
8
9
10
11
...
31
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

Openrailwaymap