Openrailwaymap

openrailwaymap@openrailwaymap.org

1 participants
307 discussions

Train protection system naming inconsitencies
by 1993matiaslq＠gmail.com 26 Nov '23

26 Nov '23

Hello, I have started to improve the data on the Danish railway network. Despite some initial troubles and mistakes, I have begun to do some good progress. Unfortunately, I have reached an issue with train protection systems. It is defined that the Danish train protection system should be tagged as ZUB123 (the technical name), not ATC (the common name). What confuses me is that Sweden tags their system ATC (the common name) rather than Ebicab700 (the technical name). Why is there this inconsistency? And why has it not been resolved since the last discussion about it two years ago? Is there anything I can do to help the change, or is it a lost cause now? Also, where is the best place to talk about OpenRailwayMap? The OpenStreetMap Discord channel for OpenRailwayMap is not that active, mailing lists here seem dead, what else...? Thanks, Matias

6 13

Re: Train protection system naming inconsitencies
by Rolf Eike Beer 14 Oct '23

14 Oct '23

Am Dienstag, 3. Oktober 2023, 17:58:01 CEST schrieb Björn Mahrt: > Hello, > > > I just wanted to ask about the current state of the proposal in > https://wiki.openstreetmap.org/wiki/Proposal_talk:Railway:train_protection > . It very much seems that (as many additional train protection systems > are added to openrailwaymap) the issue is quite relevant and it would be > very helpful to be a step further. What do you think? How to push it a > bit more? > > Or differently asked: What is missing to step further? An agreement on the systems. Both the table on the actual proposal page as well as the discussion page is quite long and has many valid concerns about how things should be tagged. This starts with something simple like ETCS. I'm very much in favor if we strip this down to a second, simplified proposal that covers the "no" case (as that really helps cleaning up the quite messy database queries we already have) and maybe those that we can get a broad agreement on. This will likely include ETCS, and maybe the German systems as to my limited understanding they are a vendor independent standard across the country. Systems that are delivered by only a single vendor, and wher the same thing is sold under the same name with different configurations to differrent railway operators are… quite another mess. I think if we first want to reach consensus on them the basic proposal will never land. And then we could ship validator rules that just warn for any tag outside the agreed ones to avoid too much noise sneaking into the database. Greetings, Eike

1 0

Re: Train protection system naming inconsitencies
by Rolf Eike Beer 14 Oct '23

14 Oct '23

Am Mittwoch, 4. Oktober 2023, 09:41:19 CEST schrieb Matias Lq: > Unfortunately it doesn't seem like there is anyone who really decides > anything in OpenRailwayMap, so I don't expect the current state to change > at all... This is OpenStreetMap, there is noone (alone) to decide on anything. For the rendering Nakaner and I can pretty much do anything we want, because noone can stop us. We can also voice our concerns or ideas on how the tagging should be done, but we can always be overruled when a tagging proposal is voted on. This is also an important point on why someone should take part in that vote because even if there are no major objection, if there are simply not enough supporting votes the proposal would still fail. Greetings, Eike

1 0

OpenRailwayMap is not updated
by patrik.ekengren＠gmail.com 17 Jun '23

17 Jun '23

Two weeks ago, I changed the tagging of the Mälarbanan railway line in Sweden, from Branch to Main, according to another discussion here. After a day or so, Openrailwaymap was updated in the more detailed zoom levels. But if you zoom out, the line is still rendered with a yellow colour as a branch line. Is it expected to take this long to update, or has something stopped working? Regards Patrik

4 3

Rendering of lines under construction
by mdeen＠xs4all.nl 12 May '23

12 May '23

It looks like lines under construction are always rendered the same as normal lines (when they are rendered, from zoom 9). But when you get to zoom 10, in the legend there is a lighter line for lines disused/under construction. So it seems this is not used in the render style? I came across this because HS2 in the UK looks like it is already finished. Regards, Maarten

1 0

API version 2
by Michael Reichert 01 May '23

01 May '23

Hi, in the past weeks and months, I rewrote the API which is used by the OpenRailwayMap website to search stations by name or reference, and for mileage (that's broken in the current API). Main changes to the API are: - All queries are fast. - Searching stations by name makes use of the ranking used for map rendering. The ranking is based on route relations with stop or platform members at that station. - Disused, abandoned, razed, proposed stations and stations under construction (applies to halts, junctions etc. as well) are supported. - Search by name includes all languages. - Search by railway line and mileage works again. - Network length API removed because these queries are either slow or require pre-processing. Query examples: https://api.openrailwaymap.org/v2/facility?name=Karlsruhe to search for stations whose name contains the word "Karlsruhe" https://api.openrailwaymap.org/v2/facility?ref=RK to search by the reference code of the infrastructure operator (RK is the code for Karlsruhe Hbf). https://api.openrailwaymap.org/v2/facility?uic_ref=<UIC ref> to search by UIC reference code https://api.openrailwaymap.org/v2/facility?q=<string> to search by name, railway:ref and UIC number. Duplicates will be remove from the result list. https://api.openrailwaymap.org/v2/milestone?ref=2134&position=24.6 to search milestones near km 24.6 on railway tracks with ref=2134. Both endpoints support limit=<number> to change how many results are returned. Please feel free to point out any issues, you find. Bugs are tracked in the GitHub repository of the API at https://github.com/OpenRailwayMap/OpenRailwayMap-api Best regards Michael

1 0

missing updates
by Axel Zöllich 26 Mar '23

26 Mar '23

No signalling layer update has taken place for a long time. Maybe is another restart necessary?

4 6

Is the OpenRailwayMap project dead?
by conorfawcett＠gmail.com 06 Mar '23

06 Mar '23

There doesn't seem to have been any new development done in a very long time, there haven't been any blog posts since 2018, and this mailing list is completely inactive. Is there any hope for new features being added in the future?

2 1

Remove spam
by tomasmarklund75＠gmail.com 01 Mar '23

01 Mar '23

Could someone please remove these idiotic spam messages that keep appearing here? /Tomas

1 0

Betriebsstellenrelation
by Björn Mahrt 03 Jan '23

03 Jan '23

Moin, ich wurde gerade aufmerksam darauf gemacht, dass bei mir manchmal der type=* bei (Betriebsstellen-)Relationen fehlt: Wie wollen wir damit umgehen, dass type=public_transport laut wiki [1] nur "nahverkehrsbezogen" genutzt werden soll bzw. für den Ö(P?)NV? Ab wann gilt das? Sind schon Abzw. oder Bbf, die auch von ÖPN-Verkehr befahren werden dazugehörig? Und die eigentliche Frage: Was für ein type=* gilt für Gbf/Rbf's/Bft, die da definitiv nicht reinfallen? Und da die Frage eh schon offen ist: Ab wann ist der railway:traffic_mode passenger? Gilt das auch für Nutzung durch v.a. Leerreisezüge etc.? Viele Grüße Björn [1] https://wiki.openstreetmap.org/wiki/DE:OpenRailwayMap/Tagging#Betriebsstell…

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

Openrailwaymap