Hi,
relation/5333614 - swimming pool ... that looks to be 2 pools - one for sport - marked lanes. The other for ? wading? depth might be a good indicator here. I have made this into 2 separate ways - both pools but one sport .. and left the other.
The 'other' looks to have a circular roof .. a sun shade?

Three things;
1) HGV/caravan .. this in present OSM terms should be done using the access tags .. IIRC you have hgv=yes .. but nothing banning other things .. so should add access=no to ban everything else. I'd be tempted put this on the road/parking? This should then work for GPS navigation maps.

2) the above does not work for a paper map. Maybe there needs to be a 'label' in OSM for this? That could be used to indicate the function 'label=truck parking only' for instance?

3) rest area OSM documentation is poor. I use the service area documentation to get more detail - so I would leave the parking area tagging .. but put the rest area as a single node near the parking area with the toilets=yes/no etc on that. As a single node as I don't know the area that it occupies.

This source does not give you;
fee
toilet
drinking water
hgv

information.

You have also used the name to give a function. As some of these areas have a name (LPI Base Map) there is a problem here.

Another problem .. are these parking areas? that is what the renders are picking up on. OSM says something about one feature = one element.

relation 6760414 residential .. shares a segment. I have removed the shared segment, combined the two remaining ways - thus making a simple single way .. and now deleted the relation!
Try to keep things simple?

Still not closed .. deleting.

Error - duplicated node in way/491460496 - building.

Is it id that makes these errors so easy to do? Or is it something you are doing?
I'm a JOSM user so i don't know.
These 'errors' appear on OSMinspector so you can find and fix your 'own' 'errors'
http://tools.geofabrik.de/osmi/?view=areas&lon=140.04&lat=-32.8&zoom=7.

Did you real mean to add 4 ways to the admin boundary for relationship 6246037 - suburb of Macgregor?

Quite some time ago I sent Jeffery a message on one of his changesets about adding fictitious bicycle infrastructure. Apparently he wants to indicate a bicycle route .. I did inform him of how to do that.
He has not made any recent edits.

Imagery can be used to add surfaces, structures.
Parks may not be easily detected from imagery unless you have additional information

The LPI Base Map has additional information .. particular regarding legal boundaries, parks etc.

Welcome to OSM.
You moved node/3985397985 by over 100 meters, this has removed a section of the LCR National park.

I have moved it back and disconnected it from the 'wood'.

Will need some time to check your removal of node/3993045108.

This relation/polygon 7170268 (beach) is not closed.

Removed crossover and connection to roundabout.

Don't know that this is an official 'park'.

Removed duplicate segment from relationship 7166553 wood. This shares boundaries with the Jilliby State conservation Area .. why? I would remove the tagging of wood on the conservation area as the wood would not stop at its boundaries ...

Relationship 7165413 residential has touching rings ... if you look at the LPI Base map you can remove the touching.

Your way/487677999 grassland crosses it self. It should b+e corrected.
See http://tools.geofabrik.de/osmi/?view=highways&lon=151.04&lat=-33.8&zoom=11

way/475592320 crosses over itself. So it does not render well ... OSM inspector calls it a 'self intersection'.

Errr ...
Removed a node from relation/6987348 - parking .. node is on a street outside the parking area. This now looks reasonable.

Way: 475189238 - parking ... looks bad. Please take a look at it. I have removed some nodes from it .. one of them the same one as the above parking relation.

HI,
way/487105547 - residential has a shared segment where you go to/from a section of Harrison Reserve.
Shared segments are not good in OSM.. some renders get confused by them.
It is not necessary to exclude other landuses inside residential areas ... one of the few less picky things in OSM.
See http://tools.geofabrik.de/osmi/?view=highways&lon=151.04&lat=-33.8&zoom=11 for the error report. I'll leave you to figure out what to do.

A better way of mapping inner voids is to make a relation. Using a single way can confuse renders as two sections of the way occupy the same space. Made into relation/7160595

way/330452626 - residential ...
is
2 areas that you have joined together by a line of 0 width.
This confuses renders ....
It should be drawn as 2 separate ways.
I have split it .. and made a new way/486873385 to solve this problem. Where ever you make a line of 0 width .. it should not be part of an area.