why are there bbq's at the station exit?

the full length can be left, but the way can be split and tagged with access=private if there's no public access at all...

way/1448328912

I think if it's natural woodlands over a larger area but the nature of the trees there is that they are sparse then it's fine, but in a metro park or in this case a cemetery where there are graves underneath I think a natural=wood area like this is incorrect and mapping for the renderer, and it should be done via natural=tree nodes for each tree.

note/4971581 says there's no barrier where you added one, but no photo, so might need another survey....

I've removed the duplicate road, and split the original way where you describe the 50 limit change and set that for the town section. Feel free to take a look and improve if needed.

you've already set the speed limit on way/462198936 which is where it needs to be set.
way/1447829950 created a duplicate road

I've finished restoring the original highway ways here to retain the history osm.wiki/Good_practice#Keep_the_history and restore the lost tags (like maxspeed etc).

Bing imagery isn't aligned here, please check the GPS traces layer for alignment.

Bing imagery here has an offset, which needs to be accounted for if mapping against it, this can be checked via the GPS traces layer. Furthermore I believe service=alley was correct per service=alley

due to this I've reverted this changeset.

...also chiming in. It looks like you're trying to split roads into dual carriageways (two oneways) where they are physically split but in OSM they were previously mapped as a single two way, but in doing so many of the existing tags were lost and in some instances the original ways were deleted in place of new ways which looses the history. Is best to retain the existing ways for the history.

Furthermore enabling the GPS traces here it seems that Bing imagery has an offset and ESRI imagery is better aligned, but the ways have been mapped to match Bing.

Because of the lost way history I'll revert the problematic changes, we can continue to work on improvements from there.

how do you know the building height and building levels from aerial imagery?

In the iD editor there is a "Driveway" preset which should be used for driveways, the tags should be highway=service + service=driveway.

hi and welcome to OSM. The building outline should follow the building footprint instead of the property boundary. You can take a look at how other buildings nearby have been mapped to check.

I'm not sure the reason to remove historic=memorial here? I've reverted the changeset to restore it for now.

not sure what was wrong with this, but I've reverted this changeset in changeset/174187322 based on the reasons given in the changeset description

I've reverted this changeset since it appears to be related to a temporary event and per osm.wiki/Good_practice#Don't_map_temporary_events_and_temporary_features we don't map these kinds of temporary events in OSM.

the boundary=national_park tag is discouraged in Australia per the guidelines at osm.wiki/Australian_Tagging_Guidelines/Land_and_boundaries

We generally use boundary=protected_area in combination with protection_title=National Park to indicate the designation along with the protect_class tag.

it's good practice to keep the history as you edit features osm.wiki/Good_practice#Keep_the_history

this means instead of deleting something just to re-add it, it's best to adjust what's already there. this will depend on the situation, but in this case it would be better practice to try and fix the existing buildings.

It's also possible in JOSM to find the affected dragged nodes, look at their coordinates history and right click over the Latitude/Longitude text and choose "Restore".

Sometimes this can be easier than a selective revert where you do want to keep most of the other changes.

that's not pyramidal, it's hipped roof:shape=*