No reaction.
Reverted.

Hi,

Way: 1061949919 does not appear to have any main tags. It does have a tag that I cannot understand .. building:levels+elevator, this appears to be only used by 'TfNSW Connected Journeys Data Team'.

Would you or mapsamillion78 or some other member of your team kindly respond to the above enquiry about the meaning of building:levels+elevator?

I wondered if you were questioning the tag...

Hi
What do you mean by the tag sport=beachvolleyball;q ... in particular 'q'?

Building=roof is usually elevated above 'ground level' by adding the tag layer=1, this keeps it above the platform. .

Hi,

building:levels=elevator is only used around Sydney. What does it mean?
See building:levels=*?uselang=en for the normal use of the tag building:levels ...

Hi,
The relation/14320066 now has no major tags .. so it is paved (surface=paved) and an area (area=yes) But what is it?

Next problem... the relation only has inners .. no outer way/s .. so where is the outer boundary for it?

See https://tools.geofabrik.de/osmi/?view=areas&lon=151.19098&lat=-33.88765&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

relation/14343725 looks to have the required outer for the above relation... and this relation is therefore not required. Just put these ways into the above relation.

Hi
The Lions Club does not usually operate a 'Mens Shed".

For how to tag a 'mens shed' please see osm.wiki/Australian_Tagging_Guidelines/Australian_features#Community_Groups
For how to tag the Lions Club see amenity=social_centre

Apologies .. this was my error, now fixed. My changes made gaps in quite a few train routes unfortunately. Taken me this long to fix them ..all the PTv2 ones at lest.

Hi
Partial reversion to restore 6 admin boundaries.

Hi,

Your leaving a few errors behind ...
See https://tools.geofabrik.de/osmi/?view=areas&lon=151.21312&lat=-32.66997&zoom=12&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

Would you mind fixing these? And do look at the warning messages you get before uploading.

level tag is for INDOOR use! It is not intended for outdoor use .. like on these rail lines and platforms that are outside.

"The level=* key indicates the floor level where a feature (such as an amenity or shop) is located in a building." In a building .. indside the building.

The other point is that the rail line and platforms are at 'ground level' .. so if they were inside a building they would be level=0

Putting the level tag everywhere is simply extra work for no benefit other than data bloat.

Navigation: The level key is not required. I chose to navigate as a pedestrian across the Sydney Harbour Bridge - no level tag there. Graphpopper works.. as does OSMand ... so level tags are not required.

I say again level tags are not required.

Hi,
You might find the DCS Imagery to have more resolution and better location accuracy than bing.

osm.wiki/Good_practice#One_feature,_one_OSM_element

Advantages ... if the feature moves it is easier to move the single node. The building may be operated by one firm while the library may be operated by another. There are probably other considerations two .. 'My' local library has other things in the same building but in other separate rooms so separate OSM entries is best there. I find shops can move around so a single node does well for them, even places like Subway move. Pub do stay put thankfully.

None of this is black or white .. there is a lot of grey.

Hi,
The OSM guide is "one feature=one OSM entry". The building is one feature, the Library is another feature. Some buildings have names while a feature within has another name. Some buildings contain more than one 'feature' .. think of a shopping mall.

The node with amenity=library will render by itself. See node/9557048958 So there are no 'penalties' for separating the building and library. A node with club=* will not render ... well not on the standard render, so I am think9ing about putting the ones I have changed/added back on to the buildings.

Note: I made some changes to the Canberra/Sydney route .. and am now fixing up the problems that created ... mutter mutter...

Hi,
Following your changes the Relation: Bankstown Line (9775430) a train route now has a gap See https://tools.geofabrik.de/osmi/?view=pubtrans_routes&lon=151.05959&lat=-33.90863&zoom=14&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 level value is 0 for 'ground level' and that would be the platforms and train line in this region. Connecting things would therefore be on level=0 ... That is the convention. More over the convention is that level=o does not need to be tagged explicitly as it is the default value.

Please read level=*

-----------------------------
For the layer tag read layer=*

Note drawing order is set by the render ... not the OSM tags. While most renders pay attention to the layer tag it is not what mappers should tag for., mappers should tag the layer for the vertical relationships between crossing or overlapping features.

Hi,

Why has the rail line been split?
Way: Main Western Line (1075696714)
Way: Main Western Line (193350054)

Note the split has effected some train routes .. they are now unordered and fail PTv2 requirements. These are now fixed.

The platform here is at 'ground level'. OSM convention is that 'ground level' is level=0.
The platform is not a building - so it does not require a level value and should be left without that tag. A feature without the level tag is taken as level=0. only when the platform & railway line are not at ground level should the level and layer tags be used.

I note you have a roof at layer=1 - above gorund ok .. but then level=-2 - below ground?

And the signal box at layer=-2 .. below ground and level=-2 .. below ground again?

The platforms are tag as level=-2 by you ... and that is not correct.

Please read level=*#Ground_floor_number

In particular the words "For typical street, waterway or railway crossings over bridges or tunnels, layer=* should be used instead. Roads or other ways passing through buildings should be marked with tunnel=building_passage; they should be only marked with level if there is a strong relation to the corresponding level of the building. "