Mini-roundabouts (traversable centre, road marking per TSRGD diagram 1003.4) are tagged as nodes rather than as circular ways as routing software needs to be able to differentiate between them. I realise that it is tempting to re-map them so that they look better on the map, but it is incorrect and unhelpful to data consumers. Reverted.

Unfortunately adding in incorrect access=yes tag to the Luton Dunstable Busway could have adverse effects on other data consumers. Reverted in changeset/154376239

Mini-roundabouts (traversable centre, road marking per TSRGD diagram 1003.4) are tagged as nodes rather than as circular ways as routing software needs to be able to differentiate between them. I realise that it is tempting to re-map them so that they look better on the map, but it is incorrect and unhelpful to data consumers. Reverted.

Mini-roundabouts (traversable centre, road marking per TSRGD diagram 1003.4) are tagged as nodes rather than as circular ways as routing software needs to be able to differentiate between them. I realise that it is tempting to re-map them so that they look better on the map, but it is incorrect and unhelpful to data consumers. Reverted.

The whole point of the Luton Dunstable Busway is that general traffic is excluded, so access=yes would rather defeat the point. Reverted.

Reverted and repaired. A section of road with clear "BUSES ONLY" road markings cannot be access=yes,.

The tagging you probably wanted here is access=customers. A petrol station forecourt with motor_vehicles=no seems unlikely. Reverted.

Thanks for adding the bridges. Original access tagging of motor_vehicle=permit reinstated in changeset/154360323

Reverted and updated. It is correct now.

No, it was mapping for the renderer. Reverted in changeset/154344167

Temporary restrictions should be implemented with conditional restrictions, particularly as you may not be in a position to revert this. I have reverted it and added a fixme for a local mapper to check changeset/154343962

I don't know why you fel that deleting a parking aisle here would help the busmiles router snap journeys to roads. Reverted in changeset/154343747

There was no legitimate reason to delete the access road to the school car park. Reverted in changeset/154343591

Reverted. Adding motor_vehicle=no to a school car park's access road was unhelpful. The correct tag would probably be access=private (no and private are not synonyms, although they are often used as if they were).

Thanks for reverting this. I'm trying to exterminate the rest of the damaging edits by @MKBE_

They've made some edits which are probably harmless geometry changes like minor realignments, so it'll take a while.

This may give you an idea of the quality of their editing https://resultmaps.neis-one.org/osm-discussions-info?uid=21272584

Current mood re their edits: https://www.youtube.com/watch?v=aCbfMkh940Q

Now reverted in changeset/154343220

@MKBE_ maybe you shouldn't have made so many damaging, unverifiable and incorrect edits? They're easy to spot with QA software, so even if you create a less obvious sock puppet than @MKBE_2, you'll still waste the time of a lot of real human beings (not bots) who care about the integrity and accuracy of OSM data for ALL of its data consumers.

Deleting almost all the tags, including the name, from roads would have no useful effects on the routing algorithms used by busmiles. It is highly detrimental to other OSM data consumers. Reverted in changeset/154342422

Deleting all this information doesn't help routing for the busmiles snap to roads feature.

Reverted.

Erasing the name, surface, speed limit and street lighting information from Corporation Street would have had no influence on the router used for the busmiles snap to highway feature. I would have had adverse effects for all other OSM data consumers.

Reverted in changeset/154341209