Test?
If you want to 'test' there is a sandbox 'development server', use it - see osm.wiki/Sandbox_for_editing

The name tag is for real names only. See osm.wiki/Names#Name_is_the_name_only

Suggest you do more reading on the OSM wiki.

The building numbers support it all being one road - no duplications that I can see on a casual look.
Humm ... I think alt_name may have to do. If the road signage gets changed ??? I used to drive along here some moons ago to get to and from work, only knew it as Mowbray Rd. .

Possibly a site relation with that name with each feature are a member? Or a landuse=recreation_ground with that name? More than one way to skin a cat.

Forgot Imagery source = bing

The playground is best left as a separate entry. Leisure=playground:pitch does not 'make sense' in OSM terms. The OSM guide is 'one feature = one OSM entry'.

I have attempted to detail the area. There may be toilets and a bubbler here that are not mapped.

Hi,
The DCS base map divides 'Mowbray Road' into 'Mowbray Road West' and 'Mowbray Road', the addresses along the road agree with the west naming.
Ok to sufix the name with West as appropriate?

Part reverted to restore Meryla State Forest boundary.

I have partially reverted this changeset to restore the bus route.

Hi,
This has broken the bus route Singleton to Maitland ...

Sections of hwy are not tagged oneway as I would think they would be with the new section open...

There may be other problems here too... oh .. looking at the warnings there are other problems here ...

disconnected hwy 4 off , impossible one way 5 off...

Hi,

Welcome to OSM!

Some hints?
relation/16309539 - multipolygon (shop) makes no sense.

First a multipolygon relation must make a closed area.

Next the tag shop=yes does not convey much information.
I have deleted this.

relation/16309540 'Centre Pharmacy' ... That does not need to be a relation. I have made it a simple way. The 'name' looks to be a 'description' rather than a name? See osm.wiki/Names#Name_is_the_name_only

And finally ... buildings don't go inside buildings... The shopping center is the outside of the building, the others are contained within the single building. The OSM guide is 'one feature = one OSM entry' .. note the word guide.. it is broken from time to time.

Hi,
Is this another 'gated community'???

These keep cropping up .. I expect the QA tools think these are 'locational' rather than 'postal'...

I have placed a few in order .. but deleted many as I cannot be bothered to correct all of them.

A)
oneway=yes with maxspeed:forward or maxspeed:backward .. that is not logical

B)
maxspeed:forward equals maxspeed:backward, just use maxspeed instead.

There maybe more of these logical types of errors..

There are warning messages about these max speed tags.

As these are unable to be checked I will delete them.

Hi,
The OSM guide is "one feature = one OSM entry"

The Intercontinental Hotel had 2 entries - one as a node the other as a relation. I have removed the node entry while placing the additional tags on the relation.

Hi,
I have altered this.

Relation outer ways cannot touch .. so a relation does not work here.

The church building now has the tags that were on the relation - service times syntax corrected.
The other building simply tagged building=yes.

Think that should do?

HI,

The bus stops are in the wrong order for relation16246834 Strathfield Connector Blue route (Cave Rd - Wallis Ave).

Hi,

addr:street should have the same capitalization as the associated highway, in this case "Guinea Street" not "Guinea street"

Hi
relation/16248772 has a number of issues:
tagged as both sand and grass??? Chose one, Looks like grass to me, so landuse=grass and remove the sand and other grass taggs.

The outer way crosses and inner... that is an error see https://tools.geofabrik.de/osmi/?view=areas&lon=152.00120&lat=-32.73891&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