Boundary lines are imported from official data and are correct.
If they do not match features on the ground it suggests that they were traced without properly aligning imagery.
Cheers |Phil

Hi Phil from the Data Working Group here.
Please don't do this, the only logical conclusion is that the UK relation version number goes up exponentially.
I have removed this and amp planning to remove the others you have added.

Sorry about that, I should have gone back further.
Although the main issue was the lift gates.

Same dodgy mapping as at Stone

Due to your dodgy mapping OSMand was trying to sen me on a long diversion as you have rendered Aston by Stone Crossing un-routable by your addition of lift gates (tagging for the renderer?).
Please don't do that, level crossing barriers are mapped as and attribute to the level crossing. Please see railway=level%20crossing?uselang=en
Also the crossing tag you have added is for pedestrians to cross the road, not a railway crossing. This is a mistake I would expect from a beginner.
Cheers Phil

Hello
Describing a garage forecourt as a pedestrian highway is a little odd is it not?
There was nothing wron with the existing highway=service area=yes.
Cheers Phi

This is a PROW crossing, not a road.
I have restored it to the map.

There are no curent path orders for Whitchurch Rural.
This edit has removed a valid Restricted Byway. I am reverting these edits.
The crossing is clearly not intended for vehicles so will update from track to bridleway.

Still no response so reverted.
The level 6 authorities had been restored earlier.

Merely asking the source of these edits.

Google Maps, as you have linked above is absolutely not allowed as a source in OSM.
These edits will need to be reverted.

https://www.canadapost-postescanada.ca/cpc/en/support/kb/company-policies/terms-conditions/legal-terms-of-use-and-conditions says effectively that the site is for personal use so therefore does not include adding to OSM which is licensed to be used for any purpose.

Openstreetmap can only use opendat, or data we have specific permission to use.

The obvious gold standard is 'I went there and I saw it'. Just because something is on a website intended for personal use does not make it opendata.

"brand=Costcutter + amenity=post_office?"
Yes if you are mapping them as a single node. More correctly the shop should be mapped as an area with a post office node inside it.

"standalone counters"
The counter are separate. You do not wait to pay for a few beers behind someone collecting their pension.
The post office counter will have the expected security and away from the busy part of the shop to provide privacy.

https://www.anpost.com/Terms-of-Use particularly paragraph 3.

Did you obtain permission to reproduce that information as otherwise you are in breach of the terms of use for the website.

Hi
Have you really fixed this?
You have removed a shop tag but given no explanation of why. Did you go to Paris and stand outside?
Alos where did you magic the check_date from?
Cheers Phil

What is the source of this post partner edit?

Cheers Phil

Hello
Welcome to OSM.

We don't use post partner in the UK, post offices within small shops are considered post offices, you can do most of what you can in a larger post office so they really should be amenity=post_office.

They are standalone counters within the shop, usually with their own opening hours. It is more usual to map them as a node within the larger shop mapped as a way.

What triggered you to change this and others?

Cheers Phil

You also changed a Chinese Restaurant into a pub, way/248378684/history/4, I assume because Rapid told you too. Such changes require a mapper to put their brain in gear and carefully review each suggested change. This often requires local knowledge and other sources.
Where a business has a common surname this is even more important.
THe proliferation of you undiscussed automated edits has made review a very difficult task for the DWG and the local community.