The one member residential relation is not a replacement for the residential relation that was altered to the point of making no contribution (no outer way as it has been deleted) as it does not cover the area south of Stringybark Reserve

One member relations should be removed with the tags simply moved to what was the outer way of the relation. If the one member relation has no outer way then it makes no sense.

The sign a the top is legal access=no ... While people might break the law OSM should not encourage it???

Bus stops out of sequence and without roles removed from relation.

Out of sequence bus stops without roles removed from relation/3766951. Ways have been re-sequenced.

Hi,
I think you have tried to make a hole in a tree area. What you have made is a 'self crossing way, or a 'dplicate segment'. See https://tools.geofabrik.de/osmi/?view=areas&lon=148.05925&lat=-42.14655&zoom=17&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

To fix it - make a new way for the hole. Enter the new way into the relation with the role 'inner'. See osm.wiki/Relation:multipolygon#Multipolygon_created_by_only_one_polygon

I did not say it was 'your work'.

What do you think of the 'taxilane' tag? It does distinguish between one control area and another control area...

relation/3766951 has stop in wrong order. I have removed the stop from the relation.

We map and tag in OSM. The renders draw the way they want to, they can exclude some things etc. We map and tag according to the 'rules' what the renders do is up to them ...

The 'green areas' are used by pedestrians, so they are part of the pedestrian are as are the roof area - people walk under than for shade..

If you object to way something is drawn - take it up with the renders.

See
node/10178481999
amongst others.

Thank you for moving some of the 'gates' inside the terminal buildings.

also see for more on taxiway taxilanes...
osm.wiki/Proposal:Taxilane

I have raised the 'parking_position' being used as a way on the tagging list. Lets see what the tagging experts think? I note there has been on proposal on the 'parking_possition'.

That is a rendering issue.
The example you gave looks to be correctly rendered. The 'edge' of a park does not appear to be drawn - just the 'fill' .. see way/388948281.

A 'national park' is tagged as a boundary and is drawn as a line around the outside - no fill. See relation/6110851

??? Eh? No motor vehicle parking spaces were changed to areoways. Your changes may be well intentioned but.. think about it!

The intention was to change ways with areoway=parking_position to areoways=apron. A parking position should be a stationary spot? Not the way to the stationary spot.

aeroway=parking_position – Where the plane parks

The presentness areoway=gate are wrong - those should be inside the terminal where passengers go before they enter the plane. These 'gates' are the plane parking positions!

Think.

node/11572336916 deleted.

This appears to be a duplication of existing Node: Stand F, Epping Station, Beecroft Rd (1170757338)

The bus stops added to route 549 are;

Not in sequential order

Have no relationship role

A 'platform' is beside the road/rail track...
A 'stop position' is on the road/rail track...

See public_transport=*#Stop_position

"on the way" meaning on the road/tail line...

'platform' where passengers wait - not on the road/train line..

Hi,
When you add a bus stop - such as node 11563923368 it should be tagged highway=bus_stop (for rendering) and for PTv2 public_transport=platform, bus=yes. Not doing this throws errors.

PTv2 requires;
'stops' to be before the train tracks
and
'stops' to be in sequence.

You should fix this simple error so you know what to do for next time.

When you make a multipolygon relation the members do not have to be new blank ways - you can use existing ways no matter what tags they use;
An existing building can be used as an inner in the relation
A lake could be used as an inner .. or even an outer.
and many other things.. they can all be used in the relation ...

This reduces your work load AND reduces data bloat in OSM.

3 year and still have crossing buildings...

The path Way: 1089492851... it cross the rail way line ... mist be either under ground or on a bridge... It also crosses a retaining wall...

Bus route 199 is not compliant with PTv2 - reset to PTv1