area=yes is not required for multiplygon members.

Reverted owing to probable copyright issue.

Reverted owing to probable copyright issue.

Reverted owing to probable copyright issue.

Reverted owing to probable copyright issue.

As per my previous post - relation is not needed ...

Deleted relation and ways .. start again.

Hi,
The beaches that you are making do not need to be relations...

For example the relation made here 13939050 has 2 member ways both with roles 'outer'. Both these ways can be tagged as beaches ... and not need a relation.
The tag 'area=yes' is not required.. there are automatic tools that will delete them .. don't waste your time adding that tag.

Name tag for names only .. not descriptions..

See osm.wiki/Names#Name_is_the_name_only

Paths connect to the bridges! They don't stop some meters before them..

The 'roads' on the bridges' are of the same type as the 'roads' they connect to....

access=no?

Looks to be a new residential development ... access=private?

Hi,

What is the source of this information?
1) The name of 'Apew Park'?
2) the geometry of 'Apex Park'?

As the school is already mapped there is no need to tag the buildings as amenity=school.
The OSM guide is 'one feature' (school) 'one OSM entry'.

Hi,
Multipolygon relations outer ways cannot share segments. See https://tools.geofabrik.de/osmi/?view=areas&lon=150.74970&lat=-33.75020&zoom=17

As both ways used in the relation have no tags .. simply place the relevant tags on those ways and remove the relation. Much simpler.

Hi
I don't see vicmap - AERIAL_VG2020 in osm.wiki/Australian_data_catalogue#Victoria
Can you explain how this source meets OSM copyright requirements?

If the tree area are enclosed by the heath then yes they should be inner in a heath relation.
If the tree area touches the heath area outer boundary then the heath area does not enclose the tree area - the heath boundary should go, possibly the long way, around the tree area.
This comes down to a 'rule' - multipolygon relations outer ways should not share segments with other members (or the same relation).

Practice?
For instance you have grassland - Way: 1037499472 .. that should be a relation with inners for the tree and heath areas. Relying on the order a render draws them may not work for all renders. This area could be incorporated with the relationship you made here.

Changes made. I note that the grass areas in the prison have not been mapped.

Hi,
The relation/13899526 only has outters - no inners. So the tags can be placed on the outers and the relation removed. Always better to use the simplest solution.

Humm looking at it again .. there is at least one water feature that should be made an inner .. so it is needed .. but not for every area.

opps...

Hi,

This new Relation: San Remo Coastal Reserve (9278066) missed the preexisting Way: San Remo Coast Reserve (376043009) which is still present.

Note the relation has been changed by mappers adding landcovers... so the park relation my not be accurate any more.
I have re-closed the relation following a mapper editing paths...