That’s great. Cheers

Dat is de inderdaad hoe het idee; hoe het formeel binnen OSM gaat. Carto is de (verreweg) meest-gebruikte renderer voor landuse=construction. Als je daar dingen in mist kan je daar een contribution voor schrijven op https://github.com/gravitystorm/openstreetmap-carto/issues. Bijvoorbeeld: render end dates van landuse=construction.

In de praktijk duurt het enorm lang om zo'n contribution door te voeren; met reviews en soms ook votes. Dat is eigenlijk gewoon de moeite niet waard. Daarom is het wat mij betreft verdedigbaar om onder bepaalde omstandigheden lokaal af te wijken van het gebruikelijke. Dé voorwaarde die ik daarvoor hanteer is: "kun je redelijkerwijze aannemen dat de afwijking geen nadelen heeft voor renderers die je misschien niet kent"? Mijn inschatting is dat er nergens ter wereld een renderer in brand staat als je een jaartal toevoegt aan een bouwplaatsnaam.

Tot zover theorie versus praktijk. Ik hoop dat het je overtuigt om iets coulanter te zijn.

Kunnen we hier niet iets minder strak mee om springen? Formeel gezien heb je gelijk, maar op allerlei kaarten is het erg gebruikelijk om het jaartal in dit soort context te noemen.

I simply based this on a European map. Local knowledge is always better. Do I understand correctly that there is no ETCS built/planned between Reading and Bristol?

Thanks!

Can you please state your source? The maxspeed is different than 2013 (https://youtu.be/twU763hHecc?t=185)

Thanks for the heads-up. It has been fixed in changeset/93469331

You indicate that the speed limit on the main line through Moers is 120 km/h. To me it seems that it should be 100 km/h, because I didn't find any evidence of 120 km/h in https://www.youtube.com/watch?v=uTl7VRd5qQM

What would you advise?

Oh sorry, I must have overlooked it. Thx

Hi Michael,
Thanks for the wms info. I don't see maxspeed information (likelf7 and lf6) on https://wms.michreichert.de/vzg-strecken-2017. Only lines and milestones. Am I using the wrong WMS service?
Best regards

Hi Nakaner,
Currently I'm trying to add maxspeed tags to St.Ingbert-Landau(Pfalz). I saw that you used DB data to do this partially, already. Is there any way I can access this dataset?
Best regards

I don't mind, if you don't mind. There's a broader discussion on this issue in the ORM mailing list at the moment. Still, I thought it would be better to ask you kindly.

According to the German definition, yes. I doubt that it is also a main line in the OSM definition: "Main line, mostly double tracked and electrified. Use this tag on railways with high maximum speed and dense traffic. Railway crossings are mostly elevated."
osm.wiki/OpenRailwayMap/Tagging#Tracks

Would you agree?

Why would Sigmaringen-Tübingen be a main line?

Hello,
The tag that was used doesn’t exist. I simply replaced it with one that does. For the maxspeed tag, it is sufficient that a track section was designed for a certain speed (check OSM in China for example). If the Swiss authorities make a decision on a new speed limit later, we should change the maxspeed tag at that time (but not before that) in my opinion.
Best regards

Fixed in changeset/92486590

Oh really? In that case it was a mistaken assumption. Thanks for pointing it out.

I can’t find “don’t tag maxspeed if maxspeed per direction is tagged” in the OpenRailwayMap tagging scheme. If it’s not rendered on ORM in that way, I could make an Issue and/or Pull Request on the ORM Github. Would you agree with that solution?

Why would it be contradicting?

Maxspeed tells something about the maximum allowable speed on the infrastructure. Maxspeed:backward and maxspeed:forward tell more specifically how this differs per direction; this is not an infrastructure issue, but an operations issue. Operations are not only influenced by technical properties of the track (like alignment) but also by safety margins that account for variations in train driver behavior.

Moreover, some OSM applications are not interested in the operational aspects. They only use the maxspeed tag. In cases where maxspeed:backward and maxspeed:forward are available, maxspeed should simply be tagged as the max(maxspeed:forward, maxspeed:backward).

Valid point. Thanks