Thank you very, very much, JJJWegdam!

Hallo JJJWegdam,

maxspeed=160 ist widersprüchlich zu maxspeed:backward=140 (maxspeed:forward=160).

Minimum diese beiden Linien:
way/804388391
way/804611578

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).

I have tagged those two ways about two months ago. maxspeed (without backward/forward) should not be used in these case since speeds will then not be rendered in OpenRailwayMap.

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?

Yes, that sounds perfect.