Reverted. Do not destroy data in OSM.

Reverted. Do not destroy data in OSM

Reverted. Do not destroy information in OSM.

Car park entrance + exit oneways reinstated, do not delete data from OSM.

Reverted. Do not destroy information in OSM.

Reverted. Do not destroy information in OSM

Vandalism reverted. Your edits are monitored.

Please note that the Maxar imagery is not well aligned in this area. In general the imagery needs aligning to existing mapped features, not the other way around.

Marc, Thanks for your support. Sorry, didn't see your 'wait 2 days' message in time. Actually the user is (in my opinion) entirely ill-equipped to fix, understand or even determine what he has done, and the last thing we need is for him to try to fix anything. I successfully reverted BCNorwich's 8 fix changesets in reverse order (and reapplied one unrelated fix contained within one), then reverted the big bad one, and reapplied 3 valuable changes, one of which (a typo correction) was good, the other two of which were badly implemented anyway. I added a detailed, robust but hopefully appropriate comment at the changeset changeset/76544078
The best we can hope for is for him to give up editing, although there are a bunch of new roads in the area that need names adding etc if we could trust him... Regards, Clive

This changeset has been reverted for the following reasons:
- you have again realigned existing well-mapped ways to unaligned Maxar imagery, an issue you have previously been made aware of, including moving a way to run into a mapped building which is clearly and obviously bad mapping.
- added ways crossing without a connecting node, or added highway=crossing tag where there is no special crossing of any kind. Ways that cross (on the same level) need a common node, but don't need highway=crossing just for the sake of it eg at footway crossing a service road or track.
- added a kink to, and slightly laterally displaced, a railway line
- created ways that nearly connect but are actually separate, useless for routing
- created duplicate ways by deleting/merging nodes without the necessary care, and also by adding new way starting from wrong node
- created a likely false connection to a road junction which is (historically and in imagery at least) not available - due to quality of this and previous edits, it cannot be trusted that this change is real, have to assume not (West exit of Back Northgate)
- deleted a well mapped way and added a new one (with bad alignment) thus loosing both history and accuracy
- moved a well mapped road and junction to connect to a (Naptan imported) bus stop node, then moved that node
- moved a well mapped footway to run diagonally through the centre of buildings shown on the imagery
- moved a node that has address as well as shop tags from one location to another in the town, rather than marking the original shop as vacant (or as appropriate - actually still operating according to Boots' website) and updating the new location details as appropriate
- adding duplicate POI, again - you really should know by now that buildings as well as nodes can carry shop/amenity information
- removed a fixme regarding a missing road name without adding a name

Also note for consideration:
- changeset, as usual, covers a wide area of the town with many different changes which will have to be accepted or reverted as a whole, changesets that are smaller in geographical area and subject would be better reviewed and accepted (or not)
- changeset comment "I have added paths , roads and traffic lights" isn't too bad but does not entirely describe changes made - simpler, more focussed changesets are easier to describe too.
- started moving traffic lights back from stop line to junction points having previously moved them the other way
- started re-adding cycleways, having previously added them, then later changed them to foot only (after which they were removed as ordinary sidewalks adding no value). Consequently it is hard to know whether to trust the cycleway as real (ie. signed)
- (re)added traffic_signals:direction tag on lights at stop lines on oneway ways which is completely unnecessary, and very wrong on lights at the junction.
- a fixme for maxspeed check was removed/resolved with speed changed to 20 mph. But 3 adjacent roads were not changed from 30 although one other had the fixme removed. This remains utterly unconvincing, in the absence of reliable evidence these ways have been set back to 30 mph with fixmes removed.
- re-added mapped footways which are merely sidewalks: foot only, separated from road only by kerb - adding no value - they are the same route and way as the road. There are places where this has been done, with care and precision, but creating poorly aligned and badly connected ways makes the map worse not better (complexity, routing, appearance etc)
- added footways on the edge or, or through, areas without considering the relative position eg inside a construction site
- generally well below acceptable standard of editing

The following changes (only) have been reapplied:
- added a cycleway on the south side of De Lacy Way, connecting (not stopping short of) Skinner Lane
- adding the missing traffic light from the quarry exit to De Lacy Way, fixed the direction tags on adjacent stop lights
- applied name typo correction on post office in WH Smith's

Pontefract and the surroundings are fairly well mapped with ways well aligned. If you are ever tempted to move a way or feature, you MUST consider first that the imagery may be out of alignment. In general you will not need to move ANY of the ways in Pontefract unless there is new construction work to realign them. But the Maxar imagery is very badly aligned in this area (worse than elsewhere) -
Always compare the existing mapped features to the imagery first - in Pontefract the mapped features are correct and the (Maxar) imagery is wrong!

As many as possible of your many previous errors have been fixed at the cost of many hours (actually days) of action by other members of the OSM community. In contrast the total amount of positive contribution to OSM of your edits has not been great. This cannot continue.
Due to the repeated very bad quality of your edits, any future edits will be closely monitored and reverted if not up to standard.

Hi Bernard,
Thanks for your reply and ongoing efforts on this, the history and your new comment on changeset/72585822 noted. Yes, stumbled across this editor due to seeing the same name in a couple of really truly awful edits, got curious about what else they'd done and ended up spending several days editing Pontefract and nearby!

I'll have a look at what's easiest for this, might still be easier for me to carefully revert your 8 relevant changesets (no bad reflection on your good edits obviously) then his in reverse order, noting that one of yours 76576248 ended up with another geographically separated change which I'll re-apply if I go down this route. At some point I'll also add a message to the (re)offending changeset/76544078, will try again for education but don't hold much hope. Thought my message on changeset/75031501 would at least stop the misalignment of good ways, but no such luck. Regards Clive

Hi BCNorwich,
Having gone through every single one of LukeTheEditor' edits a few weeks ago and fixed many many terrible errors and misalignments (due to using Maxar without alignment), and got the town back into a nice state, I was minded to revert the whole of changeset/76544078 and reapply the one or two useful changes (couple of speed limit fixmes resolved, nearly nothing else actually useful? He's still moving well placed ways to unaligned Maxar, changing his mind on traffic light mapping at junctions and creating dubious connections, adding footways when its just a sidewalk, creating duplicate ways, deleting and readding ways rather than moving, dragging a node with address details across the town, creating potentially duplicate POIs... Any ideas how to handle this? Cebderby (Clive)

You need to understand that the imagery, especially Maxar is not necessarily well aligned. Suggest you change the background to OS OpenData StreetView and find some mapped features (eg road junctions, buildings) that seem well matched to that. Then change the imagery to Bing and note that the same features are almost exactly aligned here too. Now change back to Maxar and see the offset. Scroll right to the bottom of the backgrounds tab and open the 'adjust' section, and drag in the box until the Maxar imagery lines up for some features you have found to be good in OS OpenData StreetView and/or Bing. Now (for this location and session anyway) you should be able to use Maxar imagery if you need to see latest changes. Any time you have felt the need to shift existing features you may have been moving them to the wrong place. Hope this helps. Clive

Your use of 'primary' in the changeset description is confusing and different to others' use of the word. A roads are primary (or trunk), do you mean the road is NON-trunk - and in the convention used by the OSM community in the UK. And you have removed junction=roundabout.

Has the mini-roundabout that was previously mapped and is shown on imagery been replaced by a roundabout with a central island?

Your actions and changeset comment do not seem to match. The road was primary (see history, was changed from trunk in 2018). You also deleted some junction=roundabout tags, modified the geometry of some junctions and removed some dual carriageway sections.

I see you've not added names for any of these roads or removed the construction=residential tags, or changed the limits of the construction or residential areas - did you survey the site to see what is actually in occupation, or just change them all arbitrarily?

I assume it was an unintended error to delete way/77156922 (residential tower Blok 7 in Sint-Maartensdal, Leuven) in this changeset.
I have undeleted it.

Are you sure the main road route should be _link and the linking routes primary? And can't you go from the B road to the primary without going via a _link?

D'oh! thanks. Looks like I dropped a node to remove kink in the old roman road line and managed to shorten the 2 halves of B road, fixed now.