MapshareVic is copyright and not approved for use in OSM?
See

https://www.delwp.vic.gov.au/copyright
osm.wiki/Australian_data_catalogue

Please cease using this data.

I have deleted Fryers Range State Forest way/992153454. and restored the relation for Fryers Range State Forest that was effected by a past changeset.

The way tagged here as Fryers Range State Forest (992153454, v7) looks to overlap the Fryers Range Nature Conservation Reserve...

Are not 'State Forests' operated to produce timber? As such they are not 'parks' nor 'nature conservation' areas. Those are secondary rolls... OSM should map the primary roll ..

You should fix this.

No need for apologies...

I too suffer from missing emails amongst the number that come daily. Really need to set up some filtering. And weed out the older messages too.

Err...
Why have you deleted the outer ways for relation/1013829 oh .. and the name 'Fryers Ridge State Forest'???

Deleted.
Area is not entirely scrub, nor does it stop within the rectangular area.

Hi,
Welcome to OSM.

Adding things that have no tags ... well the software will not be able to tell what they are.

See
way/984863508
way/984863509#map=19/-33.66255/151.14136

The relation/13263246 for Bilinga Beach has several problems:

Shared segments in outer ways - see https://tools.geofabrik.de/osmi/?view=areas&lon=153.50362&lat=-28.15080&zoom=18

More than one object is tagged: landcover and natural - either one or the other.
The name .. one of the ways is tagged with another name... so which is it?

---------------
Suggest .. delete the relation. The tags on the ways are ok.. if the name Tugan is correct for the beach northern part.

Note:
The relation above generates errors on a QA tool. You should fix this.

Most data sources are copyright and cannot be used for OSM.
See osm.wiki/Australian_data_catalogue for ok sources - green ones .. others may have been applied for but waiting for responses.

There is a mailing list for ozies see https://lists.openstreetmap.org/listinfo/talk-au.

Map cluter is a rendering (map drawing) thing... us mapperrs simply enter data into the data base .. complaints about how it gets rendered/drawn .. well adding or removing data so that one render (among many) is called 'mapping for the render' and is not a good practice.

Ok.
Umm I thought Way: 980158223 was tagged as a building, but I see now it is tagged as disabled parking spaces. You have fixed this too so .. all good as far as I see (which is not far).

Hi,
Welcome to OSM
I have partially reverted this and a previous changeset of yours to restore the tree area relation/2514023.
Note relations are tricky. Take care, but keep mapping.

Hi,
Parking relation/13273938 has errors.
First the inner touches the outer .. that is not allowed.
Second the building in not present in the source imagery - Bing. And it does not look to be present in other imagery.

Next: parking_space relation/13273937 ... Please read amenity=parking_space.
Then correct the tagging on this relation, and then think about both ways with the role outer - yet one is inside the other.

Hi,

Mulitipolygon relations outer ways cannot share segments. See https://tools.geofabrik.de/osmi/?view=areas&lon=151.20936&lat=-33.91583&zoom=18
The height tag should not be used for multiple heights.

I think what your trying to do is distinguish between the 2 building parts - all part of one building but at differing heights. Please see building:part=*

I think the relation should be deleted and then the base of the building mapped with the tags for the name and the maximum height. Then the smaller part of the building mapped with the reduced height, it will get its name from the base.

Hi,
Welcome to OSM.

The Wianamatta Regional Park boundary was broken - leaving a gap. And it did not follow the DCS Base Map - you cannot rely on imagery here.

Fixed. (I hope - we'll see tomorrow when the QA tools run tonight.)
While your changeset comments are good .. the "imagery used" statement is not so good. You can edit it - don't stick to what the computer generates if it does not indicate the truth.

Hi,
There is no gate in this fence...

Hi
Building=stadium would have an open area in the middle for the sport. Use the OSM wiki - see building=stadium

I have changed this to building=sports_hall. See osm.wiki/Buildings

Hi,

Building parts do not require a multipolygon relation. In fact the relation generates errors.

See https://tools.geofabrik.de/osmi/?view=areas&lon=147.18157&lat=-9.43986&zoom=18

Please cease adding relations to building:past - it is not required.

Hi,
relation/13254274 has shared segments - see https://tools.geofabrik.de/osmi/?view=areas&lon=151.10590&lat=-34.05149&zoom=18

Note A relation is not required for this building... there is no difference in the tagging. So a simple single way around the outside will do the job.

You should fix this so you learn how. First make a simple way around the outside - tag building=yes then delete the old relation and the 3 old ways.

Problems? Leave a message here - changeset/111582956