no problem. done in changeset/52944761

https://www.mapillary.com/app/?lat=-33.771155303278704&lng=151.08031233063525&z=17&username%5B%5D=aharvey&signs=true&pKey=tV6yavMPhO16GMGJxU_DLA&focus=photo&menu=false&x=0.8206062351231989&y=0.13901422932967647&zoom=3

With relation/2521345 any reason why you've used except=psv? From the signage it should be except=bus?

@Daryl Radivokevic Unfortuantly the iD editor doesn't warn you when your changes affect a relation, so just try to watch out for how changes will affect relations too. When you go to save your changes in iD it will list what's changed and if it lists relations that you didn't intend to change you can double check.

Personally I find JOSM osm.wiki/JOSM easier for this as it warns that your changes will affect a relation.

Hmm I feel it's redundant as it's no different to most other intersections in OSM right? I don't think it makes sense to have a no-u-turn relation on every single intersection unless signposted.

https://www.mapillary.com/app/?focus=photo&pKey=xdaqerG1L6OL7HdYMRWNlg&lat=-33.76296111111111&lng=151.2066666666667&z=17&x=0.9393914297523406&y=0.48555368688611367&zoom=0

Sorry that's a bad example since I re-purposed your relation.

See any of these
relation/7010985
relation/7010988
relation/7010989

No uturn restrictions from and to the same way.

The whole section was added by you https://pewu.github.io/osm-history/#/way/49230851. I split the way so I could add a different trail_visibility to the section along the creek (which is vague and overgrown, but there is still a path, hence trail_visibility=horrible) to the part that seemingly goes straight up the cliff which I couldn't find.

Based on what you've said I'll remove that last section as after looking extensively around where it's marked on the map I couldn't find anything.

Thanks for proving the context here!

Sorry I should have been more clear. It's specifically this way way/530994011.

hi! Thanks for adding this.

The name key should only be used for a name, not a description or classification of what the feature is, so I've removed "Billabong". See osm.wiki/Good_practice#Don.27t_use_name_tag_to_describe_things

In OSM water=pond is more for mostly man made ponds in city parks, with ducks etc.water=stream_pool is a better tag for these natural pools formed along a creek or river, I think, so I've changed it over.

I tried but couldn't find the track you added from Erskine Creek to the parking lot at the top of Nepean Lookout Firetrail. I checked both ends with no success. It could be well overgrown by now. I'm tempted to remove, do you have any advice?

Any reason why way/271972464 is bicycle=designated? I couldn't find any signage or markings indicating that.

I don't understand relation/7010986, no u-turn from and to the same way? What's the purpose of this?

I don

I've reverted this changeset. In the iD or JOSM editor, if you change the background imagery to LPI Base Map you'll see the part near Captain Cook Bridge is labelled Cook Park. This lines up with what I saw in out of copyright historical maps of the area. It's just there is no signage... so I don't mind either way if the name is left there or not. But either way it's still a grassy area so should either be leisure=park or landuse=grass or something like that.

Done. I've removed the node, left the area. Marked it as surface=paving_stones. I know it's not all paving_stones, but it might be a good way to say mostly it is? I'd already added the bicycle_parking at node/5149716266. But please do add any further details from your survey.

Check out:
https://help.openstreetmap.org/questions/17501/when-mapping-polygons-surrounded-by-streets-should-they-share-nodes-or-be-traced-separately

And osm.wiki/Editing_Standards_and_Conventions#Areas_and_Ways_Sharing_Nodes
"...when the way is a highway, it usually is most accurate to include a gap, so that the area ends by the side of the road and does not share nodes with the road's way. This is because highway ways usually are traced along the center line of the road, and it is unlikely that the area being tagged actually extends to the center of the road."

I've found from experience areas snapped to the road make future editing more difficult as you need to consider both features, and ungluing is difficult, especially when trying to retain object histories.

Also it's not an accurate representation of reality. Anyone using OSM to say determine the area of that parking lot will get incorrect results if it extents out to the road center line.

I know it's tempting but it's well accepted to not map for the renderer osm.wiki/Good_practice#Don.27t_map_for_the_renderer

It's better for data consumers to post-process the data to extend areas which are close to the road, all the way to the road rather than having the source data in OSM do this.

That said, I think that on most maps I've seen, since the the width of the road as rendered on the map is usually wider than a the true width of the road even if the area isn't snapped it appears to extend to the road anyway, simply because of the width of the rendered road line.

is it an office where people work from? How about osm.wiki/Tag%3Aoffice%3Dassociation

If it provides services out of that location social_facility=* with social_facility:for=disabled ?

I'd use the full name in the name tag, and short_name for MDAA, but there is no clear agreement on the OSM wiki if short_name should be used for abreviations so I'll leave this up to you name=*.

The whole area is referred to as "Cook Park" all the way from up near Kyeemagh down to at least Sandringham.

The south part near Captain Cook Bridge I think is un-signposted so simply landuse=grass. If you've confirmed it's not part of Cook Park, then simply removing way/77083928 from the relation relation/1515434/history is the way to go, not actually deleting the way.

I surveyed way/75392223 a long time ago and it was signposted as "Peter Depena Reserve" part of "Cook Park", hence it was part of the Cook Park relation.

I'd like to revert this changeset to reinstate "Peter Depena Reserve" and then remove way/77083928/history from the Cook Park relation and change it to landuse=grass. Is that what your intention was? Did you want to do this, or would you like me to do the revert?

Perfect. Would be interested to see if it has a name sign posted, since it was mapped out with a name originally.