Hi
way/1222365541 is wrong.
See
https://tools.geofabrik.de/osmi/?view=areas&lon=149.12122&lat=-35.24394&zoom=19&baselayer=Geofabrik%20Standard&overlays=duplicate_node%2Csingle_node_in_way%2Cduplicate_segment%2Cway_in_multiple_rings%2Cintersection%2Cintersecting_segments%2Cring_not_closed%2Ctouching_rings%2Crole_should_be_inner%2Crole_should_be_outer%2Cinner_with_same_tags%2Cways%2Cduplicate_node%2Csingle_node_in_way%2Cduplicate_segment%2Cway_in_multiple_rings%2Cintersection%2Cintersecting_segments%2Cring_not_closed%2Ctouching_rings%2Crole_should_be_inner%2Crole_should_be_outer%2Cinner_with_same_tags%2Cways
Where a feature has a hole inside it a multi polygonrelation should be used .. see
osm.wiki/Relation:multipolygon

However, looking at the imagery some of the 'building' looks like a covered walk way and could be better mapped as a highway=footway, covered=yes.

Hi,
Construction relation/16622825 deleted as the outer ways shared segments. Retagged ways with 'landuse=construction' - this is simpler and easier to edit in future.

Deleted relation...

Hi,
Ritches IGA relation is wrong. Multipolygon outer ways cannot share segments.
See https://tools.geofabrik.de/osmi/?view=areas&lon=144.96378&lat=-35.52714&zoom=19&baselayer=Geofabrik%20Standard&overlays=duplicate_node%2Csingle_node_in_way%2Cduplicate_segment%2Cway_in_multiple_rings%2Cintersection%2Cintersecting_segments%2Cring_not_closed%2Ctouching_rings%2Crole_should_be_inner%2Crole_should_be_outer%2Cinner_with_same_tags%2Cways%2Cduplicate_node%2Csingle_node_in_way%2Cduplicate_segment%2Cway_in_multiple_rings%2Cintersection%2Cintersecting_segments%2Cring_not_closed%2Ctouching_rings%2Crole_should_be_inner%2Crole_should_be_outer%2Cinner_with_same_tags%2Cways

I would simply map the outside of the whole thing .. no need to divide it up into two bits.

The same error has been made in two other relations - See https://tools.geofabrik.de/osmi/?view=areas&lon=144.95456&lat=-35.53222&zoom=16&baselayer=Geofabrik%20Standard&overlays=duplicate_node%2Csingle_node_in_way%2Cduplicate_segment%2Cway_in_multiple_rings%2Cintersection%2Cintersecting_segments%2Cring_not_closed%2Ctouching_rings%2Crole_should_be_inner%2Crole_should_be_outer%2Cinner_with_same_tags%2Cways%2Cduplicate_node%2Csingle_node_in_way%2Cduplicate_segment%2Cway_in_multiple_rings%2Cintersection%2Cintersecting_segments%2Cring_not_closed%2Ctouching_rings%2Crole_should_be_inner%2Crole_should_be_outer%2Cinner_with_same_tags%2Cways

What is the purpose of the relation? To group things together that carry the same street name?... but his relation only has streets .. not addresses in it. It also contains parts of a roundabout ..
The addresses along the street already contain the street information ..

The relation looks to me to be redundant as all the information, and more, is already in the data base.

Hi
There is an error on way/822372606 addr:street=cton Drive ? A fair way from Action Drive...

reverted

Hi
The import has Ramsay Road, yet OSM has the road named Ramsay Street...

There are a number of similar discrepancies. I am inclined to trust the road names as they are displayed on maps. What say you?

Hi,
Here there is addr:street=Turubul Crescent ... but the road is named Turubul Court ... which is it?

Hi
Here is Ospray Lane while addr:street has Osprey Lane..

Which is it?

I'm a JOSM user. I can search and download for anything with the tag name=Macarthur Avenue. Similarly I can search and download any addr:street=Macarthur. I don't know if Id has the same capablity?

Yep, really frustrating. I started years ago adding just road names where OSM was missing them. In Vic. & NSW we now have gov. data for both road names and house numbers... so much quicker.

The same problem with all caps exists on the DCS Base Map for NSW too.
I am not local so cannot do anything that way. Street signs too mostly all caps so they too are usually of no help.
The lower case entry dates from some 14 years ago. That is a long time for the capitalization to be corrected. I leave it to you, but make any change to both the addresses and road name. If it is wrong I expect someone will pick it up from the displayed road name.

Hi,
way/1180947989 - addr:interpolation has both even and odd addr numbers .. that does not work for either even or odd values in addr:interpolation...

Hummm .. Can I leave you to look at this for correction?

The name on the road is "Macarthur Avenue" Note the capitalization should be the same on the addr:street value so they are an exact match. I assume the road name is correct as that is what is displayed on most maps.

Hi,

There is a problem with building way/1216150277.
See https://tools.geofabrik.de/osmi/?view=areas&lon=138.65942&lat=-34.90813&zoom=19&baselayer=Geofabrik%20Standard&overlays=duplicate_node%2Csingle_node_in_way%2Cduplicate_segment%2Cway_in_multiple_rings%2Cintersection%2Cintersecting_segments%2Cring_not_closed%2Ctouching_rings%2Crole_should_be_inner%2Crole_should_be_outer%2Cinner_with_same_tags%2Cways%2Cduplicate_node%2Csingle_node_in_way%2Cduplicate_segment%2Cway_in_multiple_rings%2Cintersection%2Cintersecting_segments%2Cring_not_closed%2Ctouching_rings%2Crole_should_be_inner%2Crole_should_be_outer%2Cinner_with_same_tags%2Cways

PS thanks for adding addr:street here. The rendering generates ~2.7 Mb of error messages .. some of them get fixed when addr:street is present.

I have picked up some of my own.

I think I have all of them now.

The NSW ones look to be correct already.

Reverted

Reverted.

Name corrected using DCS Base Map... Use what OSM has available .. not copyright stuff.

Reverted