The tracks have been provided with a maxspeed:source tag to prevent the issue that you describe.

My general opinion: having an estimate is better than having nothing (as long as it is clear that it's an estimate).

Sounds great! I’ll have a look. Cheers

Many thanks for your clear clarification. As far as I can see, the phenomenon you describe is a so called Operating Site. That's a location that serves as checkpoint for timetables (like EuroTunnel North Portal).

In OpenStreetMap, this should be tagged as railway=site. This allows it to be found and rendered on websites like OpenRailwayMap.

If you appreciate it, I can look in to your TIPLOC nodes and provide them with the correct tags.

You can also do it yourself if you prefer that. Feel free to have a look at the following link for more information:
osm.wiki/OpenRailwayMap/Tagging#Other_Operating_Sites

What kind of object is this node referring to? You tagged it as railway=yes. It is at the postion of a switch. You named it to be a signal.

The UK has a very complex railway network, with a lot of railway lines with peculiar usage=* tags. It is the only country I know of where I see the usage=freight combination. Other railway lines don’t have a usage tag at all. Some local commuter railways up to a dead end bear the usage=main tag. And so on.

It seemed like usage=* tags on railways in the UK are in dire need for improvement, so I searched for information about the usage both inside and outside the OSM community. I hope that I searched well, but didn’t find any solid information on how usage-distinction is done in the UK.

For this reason I started basing the usage tags on the sources as stated in the changeset source. More specifically: the west part of the Fife Circle Line doesn’t feature any long-distance traffic, so I perceived it as a local line and tagged it as usage=branch.

Hello,
Thanks for the heads-up. The 80 kmh / 60 mph is indeed a mistake; I'll fix it.
I do wonder though, how to tag links between NR and the CTRL (domestic and international network). These tracks have physical speed limit signs both in mph and kmph. I was unsure about this and thus "invented" the maxspeed:mph key. Would you advise mph, kmph or (in some way) both on these tracks?

Good evening, for all sections I try to use the best quality videos. If you know a better video for the section, could you perhaps provide me with the YouTube link? I'll use it to improve the tags. Thank you in advance.
Best regards,
Jeroen

Ok, that's a very clear answer. Thanks

What is the source of the track speed limit? Can it be used for other Belarusian tracks in OSM that don’t have this information yet?

Якая крыніца абмежавання хуткасці дарожкі? Ці можна яго выкарыстоўваць для іншых беларускіх трэкаў у OSM, якія яшчэ не маюць гэтай інфармацыі?

Where did you find the information about the speed limit? I'm looking for a source which I can use to map more railways with maxspeed.

(Где вы нашли максимальную скорость?)

Good evening,

When looking strictly at the wiki, you definitely have a point. However, I would like to emphasize the goal of this changeset (and some others). As far as I know, the goal is to get to a map layer (OpenRailwayMap maxspeed, or others) that displays speed limitations around the world as correctly as possible.

This would be undoable if data can only be added when we are 100% certain that the data is as local as possible, that it is currently valid, etc. Even infrastructure operators themselves often don’t have that specific data.

For this reason I apply the principle that I add data when it benefits the goal; in this case, an indication of the line speed is better than no info at all. Information per section would be better, but it simply is not always available. Adding line speeds can therefore be a good intermediate step, before better data becomes available.

Would you agree with this reasoning?

Thanks for the heads-up. This is indeed a mistake. I’ll repair it

Repairing it right away

To adress "In this CS you marked entire lines that still exist as razed. That's why I reverted it.":

Even then, I am certainly available and willing to repair mistakes. This is not possible if the changeset is reverted without notice

This revert has been reverted:
changeset/77641554

Note to the author of 77636565:
please refer to
osm.wiki/Revert_scripts#Act_responsibly.21
and provide room for discussion before reverting a changeset

Revert reverted 🤷‍♂️
changeset/77641554

Note to the author of 77636565:
please refer to
osm.wiki/Revert_scripts#Act_responsibly.21
and provide room for discussion before reverting a changeset

This revert was done without providing any possibility to discuss the original changeset.

Apparently it is now common practise that we revert an entire changeset if not all changes are mentioned in the changeset description. Even more so that such a revert happens without any room for discussion.

Island is om aan te geven dat het een polder is. Aangezien er geen goeie tag is voor polder, heb ik bedacht dat een polder eigenlijk niks anders is dan een kunstmatig eiland in een meer. Vaak is de omtrek van het meer nog te zien in de vorm van de ringvaart.

Graag gedaan. Wijzigingenset is overigens onderdeel van detaillering Betuweroute.

Ik was me niet helemaal bewust van het verschil tussen deze tags. Bedankt voor de uitleg.