I wonder what is happening to this bus stop?

If it's disused then it shouldn't be part of the route relations anymore.

The data could be wrong, but bustimes still shows timetabled services for that stop: https://bustimes.org/stops/250020050

I'm finally getting round to fixing up some more bus route validation errors.

If you are removing the public_transport:stop_position from nodes, then these nodes also need to be removed from the public_transport route relations. They are often included with role:stop.

I don't necessarily agree that the stop_position nodes are unnecessary. and they are part of the PTv2 tagging schema. However I do see the point that in most cases they are next to the platform.

Version 31 now looking like the correct route again. Thanks for spotting this

Probably a bug in relatify. I'll see if I can revert the change

There are a large number of validation errors today on Edinburgh bus routes which I suspect may be due to some of your changes. For example:

{"relationID":946200,"name":"Bus 5: Hunters Tryst =\u003e The Jewel","validationErrors":["ways are incorrectly ordered - way/482837515","ways are incorrectly ordered - way/482837515","ways are incorrectly ordered - way/66111779"]}

Editing bus routes using the iD editor is generally a bad idea because it's not been programmed to understand them. I'd recommend something like josm instead.

Geofabrik OSM Inspector

https://tools.geofabrik.de/osmi/?view=pubtrans_routes&lon=-3.27824&lat=55.94504&zoom=13&baselayer=Geofabrik%20Standard&overlays=ptv2_routes_valid%2Cptv2_routes_invalid%2Cptv2_error_ways%2Cptv2_error_nodes%2Cptv2_routes_valid%2Cptv2_routes_invalid%2Cptv2_error_ways%2Cptv2_error_nodes

The E1 route is now failing validation due to stops appearing after the ways. Is this something you are able to fix?

Thanks for your edit. Bus route relations 2805560 and 11087987 are now failing validation with the message: ways are incorrectly ordered. Is this something you are able to fix?