Hi,
Welcome to OSM.

I have deleted the building=retail relation as it did not form a closed area and the building/s are already mapped.

Advice?
I would not include the front roofed area as part of the building - I'd just map to the shop front.
And there is an OSM guide - one feature = one OSM entry. So having bouth building and shop on the one feature goes against that. Some disagree with this. What I do is map the building footprint (area) and then use a node for the shop.Makes it easier if the shop moves as the node can then be simply moved to the new location.

Enjoy!

Hi
TC building corrected and simplified to a simple way.

Hi,
Welcome to OSM.

There is an error in relation/13105685 - parking. The 2 outer ways share a segment - this is an error.

My best solution would be to delete the shared segment and combine the 2 outer ways in to one way. Then just tag the single way for parking and then delete the relation. Much simpler data wise.

Hi
relation/13077729 - church ... has one member only .. with the role 'inner' .. where is the outer?

Hi,

Roles of coastline in Bass Straight corrected from inner to outer.

No response .. deleting.

Hi
Relation13070654 - grass only has one member.. so it does not need to be a relation?

Unless you want the sole member to be an inner of the surrounding grass? In which case the surrounding grass should be pat of this relation - with the role 'outer' ...

You have failed to respond to past attempts to have you correct your own errors and this changeset has yet more errors ... I wonder if you are getting the messages.. or you simply don't want to communicate?

Hi,
The lake Vincent relation is faulty - does not close. This has been deleted and the older simpler closed way has been restored and detailed.

The 'name' of "Historic Alignment (1943)" appears to be a description and not a name? In some places this looks not to exist? Possibly this should be tagged 'disused:highway=track description=Historic Alignment (1943)' ??? And ... what is the source of this information - the description cannot come from Bing?

Still needs fixing...

The role 'inner' is for things inside the 'outer' ... you have them reversed.

Oh, and the inner and outer rings touch.

Hi
relation/13092193 has no properties... other than type=multipolygon...

Hi there,
I have only restored the park boundary.. done nothing to tracks nor bridges.

'Inaccessible' could apply to anything, park, river ... please be a little more informative with your changeset comments?

Bridge? Which bridge? The bicycle path one looks like there is no fence across any end, nor the M3 bridges?
Possibly you mean there is a fence along side the M3 to prevent people from going across it? If so .. just map the fence .. barrier=fence. Where a path/road ends and there is no way to go further .. tag the last node with noexit=yes and that should be all you need to confirm that there is no way to go further.

Hope that helps. I don't think you meant to touch the park boundary at all.

Hi,

Adding a track to a public transport version2 when it is not inserted in order brakes the route. Either take the trouble to insert it in the order from one way to the next ... or simply leave it out until you can?

Relation: Train Indian Pacific (2033217) has the ways removed now.

The master route should not have individual ways... they should go into the route relations - not the master route relation.

Ok?

Hi,

Just caught that you added individual ways to a route master... they should go into the route relations - not the master route.

Hi,

Welcome to OSM.

I don't understand your changeset comment 'inaccessible'??? What are you trying to do here?

node/6246408121 has been moved back to where it was as this caused problems the the Yarra Bend Park boundary.

Hi,
Welcome to OSM.

The tag area=yes is not required on most things.

Hi,
The bing imagery does not appear to show much water if any in these ways you have added. I have deleted them.

The relation again is for an area of trees, not water.. changed back to trees.

Oh dear ... Way: 244950975 is part of administration boundaries.

Note another mapper changed it to a path, not you. But further changes have broken the administration boundaries.

The path has been removed and the original admin boundary restored.

Please don't use the admin boundary as the path.

HI,
This imagery looks to be displaced 10 meters to the west.

Why not use the DCS NSW Imagery???