Note I have made the route contiguous.

motor_vehicle=permit implies permit is ordinarily granted ... I think you mean motor_vehicle=private?

Humm...
These carry access tags of foot=yes and no for the rest of the tagged access ... would it not be better to tag access=no and let the foot=yes remain?

Hi,
Do you check these routes meet the OSM requirements?
The relation/4513980 has the ways in the reverse order...
OSM Inspector shows quite a few of these ferry routs are incorrect...
https://tools.geofabrik.de/osmi/?view=pubtrans_routes&lon=151.23079&lat=-33.84752&zoom=13&baselayer=Geofabrik%20Standard&overlays=ptv2_routes_valid%2Cptv2_routes_invalid%2Cptv2_error_ways%2Cptv2_error_nodes%2Cptv2_routes_valid%2Cptv2_routes_invalid%2Cptv2_error_ways%2Cptv2_error_nodes

There, rendered on default map. Some of the enclosed features may not be there any more ... sculptures relocated?

Hi
The relation type=building does not render???
I'm trying this: the outer way as a multipolygon relation - there are at lest 2 holes in it according to Esri so this is 'legal'? That should get the outer to render.. I have left the building relation alone other than setting the outline to the multipolygon relation... see how that goes?

Hi,
The warning you got on uploading this is real and would have been best fixed before upload. The multipolygon relation does not have a closed outer.

In fact this does not need to be a relation at all... a simple closed way would do the job. I would suggest you delete it and remap it as a closed way.

Relation deleted.
Bye.

This made the train route relation Alamein Line: Flinders Street => Alamein (via City Loop) (11592518) only have one member - the changeset has deleted the rest.

Not interested in it?

Shall I delete it?

HI,
relation/19777606 (post depot) has been deleted, the tags have been placed on the landuse=commercial.
A multiploygon relation outer ways cannot be inside other member outer ways ...

The 2 ways that make up relation/19785222 (scrub) .. well the simple solution is to remove the relation and place the tag on both ways... Technically not as nice as a relation with a hole in it but it will work and it is simpler.

A one member multipolygon relation is data bloat .. tags transferred to simple way and relation deleted...

Hi,
Problem: relation/2204423 (wetland is no longer closed ... needs ways along the coast?

Hi,
Some issues in this area some from this changeset.
In OSMInspector relation/5948947 (residential) the outer way is broken.
The one member relation (residential) doe not have the backyards going to the water front, yet the DCS Base Map shows their ownership of those area and imagery shows they do use that area as residential.
relation/1319504 (Lake Macquarie) has a broken outer way ..

Way Way: 845012863 (fence) crosses 2 roads but only one has a gate.

HI,
The relation/19410911 (building=train_station) does not from continuous outer way. In fact the existing members have no other use? would suggest that the building could be represented by a single simple way?

-------- Note
The tag identifiable_factor:age has only 4 uses in OSM world wide. It is not documented in the OSM wiki suggesting that it isa of no use?

Hi,
On node/12311157759 you have tagged 'fixme=ref' ... what does that mean? There is no ref tag on the object.. so what fix is requested?

? Looks like you might be correct.. must be somewhat confusing
Been putting 686 back into sequential order...

There is only ONE bus route 695! Not 6 of them.

The relation for the main south railway line looks to be obsolete. Before people added a second track it 'worked; but people have added a second tract and not added it to the relation ... or made a second relation with down and up as appropriate.
This needs a tidy up ... as does most of the rail system here.
Busses are not much better .. number of errors with ways missing or not in sequence.