fiction reverted

No response. Incorrect change reverted, limit was correctly mapped.

osm.wiki/IT:Good_changeset_comments

osm.wiki/IT:Good_changeset_comments

What is your source for this "update"?

Wrongly blocked left turns from side roads (both sides) onto main; corrected

As well as moving a node in Gibraltar causing a large changeset, one of the turn restrictions added was wrong, blocking E-bound routing along 210 road; corrected.

osm.wiki/IT:Good_changeset_comments

Please be careful when moving the map while editing. 5 nodes were dragged out of position. All is repaired.
[Google translate:]
Bitte seien Sie vorsichtig, wenn Sie die Karte während der Bearbeitung verschieben. 5 Knoten wurden aus der Position gezogen. Alles ist repariert.

https://overpass-api.de/achavi/?changeset=143276893

Reverted - fiction

The paragraph you pick from the OSM definition of highway=bridleway relates to Germany. The England/UK section has:
Occasionally, ways that are not physically bridleways are designated as public bridleways, such as when a right to travel by foot and by horse passes along an otherwise private way (often, a farm track). In these cases the physical feature should have whatever highway=* tag is the best fit for the physical reality, with the right of way indicated by designation=public_bridleway as above.

Please read highway=bridleway
I think it's unambiguous.

Also highway=track
which is a well defined long established OSM highway type, not to be avoided when correct (this and other changeset(s)) for ways with farm / tractor / four-wheel drive usage typically where ordinary road cars wouldn't be expected to routinely go.

Vehicles cannot pass along an OSM highway=bridleway. This way has (private) vehicles on it, therefore it is a vehicle way (such as a track) carrying a designation=bridleway. This is how OSM is.

reverted

Thanks. Had done some sliced buildings before and plenty of other (not-so-)simple 3d buildings in OSM. No purpose made tools for making OSM 3d buildings, but I used a 3d CAD program 'OpenSCAD' (which uses a 'programmed geometry' approach rather than a more conventional drawing tool) to make an ideal (not achievable in OSM) model matching to photos and ground survey (for near-ground details and height estimates for these eg the loading area and pods relative to the riverside ground, plus did my own measurement of the outer diameter by standing under it and noting ground positions). Then I played with slicing the wheel and A-frame in OpenSCAD until I had a reasonable accuracy vs complexity compromise, and wrote out coords (x,y,z metres) for all the slice corner points. (Did some geometry roughly by hand in JOSM and saved the resulting file to see the format etc.) Imported all the calculated coords into a spreadsheet to rotate it to match the riverbank angle and convert to lat,long & z height and output as near as I could to a JOSM text file with node and way ids etc etc. Some search and replace with a text editor to finish off, if I remember correctly, then loaded to JOSM to review with Kendzi3d-dev plugin, and repeat until satisfied. Did some manual adjustment of the 'roof' slope angles for the lowest part of the wheel I think. Then lots of checking in JOSM then finally uploaded wheel, A frame+axle and all the ground fixed stuff. It's a monster, and slicing a triangular section wheel is a bit of a nightmare, but it worked.

Welcome to OSM and thanks for highlighting this change. The turn restrictions you added weren't quite right (should be 1 way 'from', 1 point 'via' and 1 way 'to' in each turn restriction separately. I've added these and the 4 way lights, dropped the no right turn out of Church Hill and very roughly marked the parts of the main roads which are likely now 20mph according to the notices about the changes that I can see. Also improved some alignments locally. Have a look and see if it seems ok, you can probably improve which roads are 20mph if you want. (Routers will take a bit of time to pick up the changes so won't change which turns are allowed for a few days)
Cebderby (Clive)

Damage and addition of grossly misplaced office node reverted.
See https://overpass-api.de/achavi/?changeset=142924563
for visibility of the damage and the tags you added for reference.
If there is a verifiable (ie. visible external signage) and visitable business office at the address you used, it might be appropriate to add a node at that correct location.

A quick search suggests this is long planned and permanent, it gets a mention here:
https://www.glanllyn-newport.co.uk/wp-content/uploads/2022/11/newsletter-spring-2022.pdf
which includes the text (as of 1+ year ago):
"we are bringing
forward plans to close the junction between Bloomery
Circle and Baldwin Drive to vehicles and make this area into
a cul-de-sac as intended in the overall masterplan for Glan
Llyn. The road will still be open for pedestrians, cyclists and
emergency vehicles"
(which also suggests the main road is/will be "Baldwin Drive", which looks like could be set as tertiary).
This also seems to correspond with the overall site plan photographed here:
https://www.geograph.org.uk/photo/2794612

I can only repeat what I said before: these ways *are* the A516. They do not have their OSM trunk status because of the connections to the A38, but because the green-signed A516 runs here on its way to the the A50 junction at Hilton. It is just a free-flow merge of 2 nearly equal status A roads. The only part of the A516 that does not carry its own ref is where the carriageway is shared with the main run of the A38 (and following the A516 route actually has its own continuous nearside lane both ways for the short distance until it divides again). By this logic, how much of the continuation of the A516 would be _link? - to the Mickleover S turns/roundabout?

There are also highway type changes hidden in these changesets, not described in the changeset comments, typically favouring 'unclassified' over previously set residential and tertiary choices.