Bullfighting... ??? I don't believe it. At what looks like a residential address...

Hi

There are now gaps in the relations for train routes ...
Relation: Brisbane XPT (8406942)
Relation: North West Xplorer 223 (12418296)

Perhaps you could keep an eye on https://tools.geofabrik.de/osmi/?view=pubtrans_routes&lon=151.58109&lat=-33.22853&zoom=9&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 ?

------------
The link for the TfNSW TOC Manual is still pending a file upload... see osm.wiki/Australian_Data_Sources#New_South_Wales

Bing can have offset errors ... use DCS Imagery and Base Map for better accuracy

Bing can have offset errors. Suggest you refer to DCS Imagery and Base Map for better accuracy of the locations

Hi
The warning 'close node vertices' in this instance indicates 2 nodes exist where one node should be used. I have merged these to fix the issue.

Most buildings have square corners ... these are hard to draw exactly right... When the way is selected a press of the 'q' key will square them up .. makes the corners square and looks better.

From osm.wiki/Relation:multipolygon

"multipolygon are used to represent areas (polygons), typically complex areas with holes inside, or consisting of multiple disjoint areas"

The relation/14440396 is not correct. Further it is not the way to map buildings consistng of multiple parts ...

See osm.wiki/Relation:multipolygon "multipolygon are used to represent areas (polygons), typically complex areas with holes inside, or consisting of multiple disjoint areas" .. this relation shares segments .. so it is not "disjointed"

See building:part=* "Areas with the tag building:part=* allow you to differentiate a building into parts that differ from each other in terms of some building attributes or the building function. "

Part revert to restore relation/10406083

The DCS Base Map gives the names to some of these buildings .. and those named would be, for the most part, homesteads

Hi,
Welcome to OSM.

The way/981879114 is not quite right ...
building=yes means all of it is a building
sport=shooting_range .. umm the range part can be dropped.

I'd tag the area as a sports centre ... see leisure=sports_centre

Does the club control the whole facility? If so leave the club tag and name tag on this outer way. If not then I'd map one of the buildings and put the club tags on that...

The OSM wiki can be very helpfull, there is a search field on t he top right of the wiki pages..

Hi,

The individual residential areas are not named 'Town Of Yandina' ... Some times a node would be used to signify the town center (post office/town hall) with place=town ... or if an administration district then a administration boundary would be used..

layer=0 is the default value. The JOSM validator will automatically removes these ... and I click the button to do that every time I finish. So don't waste your time putting them in.

See osm.wiki/Relation:multipolygon

In particular "consisting of multiple disjoint areas" ... the areas here are joined.

No worries.. many people get those multipoygon relations wrong ... some with much more experience.

HI
relation/14444280 has problems with duplicate_segments. The ways that are in the relation have no tags.

I think it is better to have the amenity=fast_food on a single node. Then the ways can be tagged as;
a retail building
two off building=roof, layer=1
There is no need for a relation.

Please read osm.wiki/Relation:multipolygon ... in particular "Relations of type multipolygon are used to represent areas (polygons), typically complex areas with holes inside,

or consisting of multiple disjoint areas." Note the "disjointed" - 14444280 is joined.

Error
relation/14440560 - problem duplicate_segment.

Hi,
Welcome to OSM.

Some problems with this entry.

Multipolygon relations outer ways cannot cross one another.

What is being mapped is a multipart building.... these are mapped using the 'building:part' tag ... see building:part=* Note! The building:part=* areas should always be within a separate building=* area representing the entire building.

The layer=* tag is used to describe vertical relationships between crossing or overlapping elements, e.g. a bridge over a street. So layer=-2 is not appropriate here. See layer=*

Great! Well done.

Arr The Train Operating Conditions (TOC) are copyright... they cannot be used in OSM unless you have a waiver... it is not listed on osm.wiki/Australian_Data_Sources#New_South_Wales. If you have a waiver then it should be listed.

Hi,

What is the 'TOC Manual'? Is it copyright?

Your changes are breaking route relations ... for example relation/9806974 has a gap created by you .