Hi,
In Austrlai we associate an address with a building, not the entrance way. In the case of Node: 12008941940 this appears to be the entrance to a vehicle garage, not the residence.

The address for Node: 12008889339 is incorrect, see the DCS Base Map!

The buildings appear to be offset and not well recognized. Use the DCS Imagery for better resolution and location accuracy. Observe the vehicle driveways to see which are garages?

2 month later?
See changeset/148866385 .. the mapper did not respond, the listed source did not support the entry.
Is this now residential, not planned nor under construction>?

Reverted.

A source for admin boundaries that is easy to use is the DCS Base Map.

Please don't damage a boundary such that it is not useable, fix it yes but damage no.

Where the address should be is 'contentious' within OSM. Some think it should be where the post goes - a 'letter box'...
However it should only be on one feature, that is the OSM guide.

See osm.wiki/Addresses

The role 'address' in a relation .. will probably be flagged as an error in the QA tools.. so those will need to be looked at.

Hi
Welcome to OSM
Concerning relation/17722831 -farmland;
If this has an address then the address tags should be on the relation, not on a node as a member of the relation.
As the address is within a building I have left that there - deliveries would then be directed to that building. I have removed the address node from the relation, but added the farmyards as inners in the relation.

The address node in the relation raised a flag in QA tools that I use, hence my interest here. Keep mapping!

Ok,
I have attempted to detail this library...

The building base is way/1292752686 - this carries the tags for the library. It should have the highest level tagged on it.. I think arr yes .. building:part=*

I think I have it right, please check it!
Other than the base library way above the 2 other ways are ;
way/205303849
way/159946355

Hi,
The complete line is not operational, the bit that is non operational should be tagged as under construction...

Nearmap is not compatable with OSM licence conditions
See osm.wiki/NearMap_PhotoMaps

Reverted.

Nearmap is not compatable with OSM licence conditions
See osm.wiki/NearMap_PhotoMaps

Reverted.

Nearmap is not compatable with OSM licence conditions
See osm.wiki/NearMap_PhotoMaps

Reverted.

Nearmap is not compatable with OSM licence conditions
See osm.wiki/NearMap_PhotoMaps

Reverted.

Nearmap is not compatable with OSM licence conditions
See osm.wiki/NearMap_PhotoMaps

Reverted.

Nearmap is not compatable with OSM licence conditions
See osm.wiki/NearMap_PhotoMaps

Reverted.

Nearmap is not compatable with OSM licence conditions
See osm.wiki/NearMap_PhotoMaps

Reverted.

Nearmap is not compatable with OSM licence conditions
See osm.wiki/NearMap_PhotoMaps

Reverted.
Past edits using nearmap are about to be reverted too. Future changesets too...

Nearmap is not compatable with OSM licence conditions
See osm.wiki/NearMap_PhotoMaps

Reverted.

Me too with the time gap. I've done a tree area in WA that is wrong - imagery shows the old fire damage so I've map that .. need to change it to a more realistic area as trees have regrown... been a week or 2..

Hi,
How about this?
When you enter a new bus route, untill it complies, or as near as you can get it, with public transport version 2 you leave the tag for public transport version 2 out of it? That way the QA tools won't pick it up and it won't annoy me...

No worries! And no need to apologise.

No need to apologise!

Thanks for fixing it. Been past it a few times never bothered to map it. Not going to this years Vivid either .. went last year and it was jam packed. I'll go next year, might have improved pedestrian traffic by them..