Hello,
Please contact the DWG by email at data@openstreetmap.org with a subject line of "[Ticket#2023050810000254] changeset/164364458" so that we can add you to the ongoing discussion about this.
Best Regards,
Andy Townsend, on behalf of OSM's Data Working Group

Despite those maps being "© Crown Copyright and database right 2024" I believe that I've seen similar data released under OGL (and hence licence-compatible).
I'm a bit confused by what I see at both "Natural England - Open Access maps" and "CROW Section 4 Conclusive Maps" linked from there - locally to me only some of what I thought was "common land" is listed as such, but there's extra sections of "access land" that I wasn't expecting!
Nothing listed in the Woolton area though.

Not sure what the letting policy is; I'm guessing it's relatively short term and therefore would benefit from some sort of tourism tag; I local might want to add that.

To contact the DWG about this edit, please email data@openstreetmap.org with a subject line of "[Ticket#2025032810000494] Clifton Lane".
Note that "primary" was backed up by both OS OpenData StreetView (from 2016) and also last year's OS OpenMap Local, both of which are licence-compatible with OSM.
Apparently some listed speed limit was also wrong, but as https://overpass-turbo.eu/s/21kx shows no current speed limit there, I've left as is.

Editing CanVec-inspired relations is always a challenge - I mean, just look at relation/1100815 :)
It looks like iD didn't flag anything up here (which is not entirely a surprise).
One thing that you may be able to do immediately after the edit is to check affected relations with JOSM's validator - I wrote @SomeoneElse/diary/406398 a few days ago in another context, but it should work here too.
There's also the more general check that was mentioned above - https://tools.geofabrik.de/osmi/?view=areas&lon=-63.76396&lat=44.62007&zoom=13&baselayer=Geofabrik%20Standard&opacity=0.95&overlays=duplicate_node%2Csingle_node_in_way%2Cduplicate_segment%2Cway_in_multiple_rings%2Cintersection%2Cintersecting_segments%2Cring_not_closed%2Ctouching_rings%2Crole_should_be_inner%2Crole_should_be_outer%2Cinner_with_same_tags%2Cways%2Cduplicate_node%2Csingle_node_in_way%2Cduplicate_segment%2Cway_in_multiple_rings%2Cintersection%2Cintersecting_segments%2Cring_not_closed%2Ctouching_rings%2Crole_should_be_inner%2Crole_should_be_outer%2Cinner_with_same_tags%2Cways . That won't show issues immediately but it will check everything, and is also useful to do.
As for the best way to make CanVec relations "editable by humans", that's probably a question for https://community.openstreetmap.org/c/communities/ca/95 . Where I've encountered similar things (not in Canada) I've tried to isolate bite-sized pieces of natural=wood from the monster relation and attack it that way.
That will also allow you to update OSM to match changes since CanVec was imported at osm.org/#map=20/44.6587018/-63.8351248 , that's 14 years ago. A glance at the underlying imagery suggests that it's all either more or fewer trees, and there isn't a great correlation between "natural=wood" in OSM and "lots of trees in imagery" - there's some, but not much.
Best Regards,
Andy

Thanks for fixing this. For info, there is still an issue with some of the other relations here. Since at least 4 people are fixing things, I've posted in the Irish forum at https://community.openstreetmap.org/t/coastline-and-relation-breakage-in-killiney-south-of-dublin/128102 suggesting that people work together there.
I mention this not in any expectation of you fixing anything else, just purely for interest :)

For completeness, there is still an issue here. Since at least 4 people are fixing things, I've posted in the Irish forum at https://community.openstreetmap.org/t/coastline-and-relation-breakage-in-killiney-south-of-dublin/128102 suggesting that people work together there.

For completeness, there is still an issue here. Since at least 4 people are fixing things, I've posted in the Irish forum at https://community.openstreetmap.org/t/coastline-and-relation-breakage-in-killiney-south-of-dublin/128102 suggesting that people work together there.

I think that the merge of the ways to make way/323221895/history makde a couple of townlands invalid polygons; I split it again in changeset/164282607 .
To be clear it might not have been this changeset; this was just the most recent one that edited the road :)

I'm not familiar with this area - I'm hoping that you were!
I'm always puzzled by "what is officially a common and what isn't". In some case it's obviously signed as such on the ground (and you might have get some bylaws posted - one near me has that). Part of another one near me seems to be used as farmland currently - but maybe that was never part of, but only adjacent to, the "common" part? I'm not sure how you'd tell...

Hello,
What was "invalid" that led to the change here? The comment just says "Fixed an invalid way." which does not really explain anything.
Best Regards,
Andy

Just wondered - how do you check that this isn't dedicated as a common?

Hello MPFG,
It'd be great if the changeset comment here was a bit more descriptive, such as "added buildings to a suspiciously empty area in the east of Glasgow"
Best Regards,
Andy

The "one vs four" problem was caused indirectly by the mapping of the former units as "buildings" (possibly by me!). This isn't really correct; there's actually really only one building on each side, and the interior partitions can be moved and removed easily.

@NTMountainRanger the problem with "just deleting" things like this is that it will not have the effect that you want it to have. If someone sees a "missing path" from old imagery, they might just add it back.
Your colleagues in England and Wales have worked extensively with OSM (including at least one joint session in Clumber Park in Nottinghamshire, if I remember correctly) - perhaps it's worth chatting with them?
An example of the sort of fix that would work can be seen at way/1086252957/history and changeset/135290950 , over Dropping Crag near Scafell Pike in the English Lake District. "AWMapper" in that conversation is one of your English colleagues.
Best Regards,
Andy

Hello,
It looks like this change might have introduced a gap into a couple of townlands - see relation/4204334#map=19/54.816293/-6.130655 and relation/4161726#map=19/54.816293/-6.130655 . Are you able to fill it in or would you like help with that?
Best Regards,
Andy

Near Yarm, from survey 27/3/2025

Hello,
It looks like this changeset introduced a gap in the "Anglesey National Landscape" relation (10676742). I fixed that in changeset/164158424 . If you do find yourself modifying ways that are part of a relation you can check them by following @SomeoneElse/diary/406398 , but in a case like this you'll need to notice that the ways you edited were actually part of a relation, since neither you nor I changed the relation itself, just the geometry of the ways that make it up.
As ever, and questions - please don't hesitate to ask!
Best Regards,
Andy

Just for info - a bit of a curate's egg, this one: it looks like this changeset fixed one (part of a number affected by a different change by someone else last week) and broke two:

11a12
> -15480473 | Killiney DED 1971
126d126
< -13061512 | Killiney ED 1901
169d168
< -12498334 | Dalkey ED
1132c1131
< (1129 rows)
---
> (1128 rows)

Relations 13061512 12498334 still fail in Josm's validator.

I was in contact with the person who made the original change at the weekend, and they said they'd try and have a go at fixing things this week.

Of course, it could be argued that perhaps the best place for "historic electoral districts from 1901" might be OHM rather than OSM, but I couldn't possibly comment on that :)

Hello Wamia Zaman and welcome to OpenStreetMap!
One thing that'd be really helpful would be if you would use descriptive changeset comments that explain to other mappers what you're changing.
"#hotosm-project-16289 #OSM_Guatemala #Quetzaltenango #Kaart" is just a bunch of gibberish hashtags that don't actually mean anything, but something like "added some buildings in Guatemala based on (whatever) and (whatever)" would.

Best Regards,
Andy