Thanks! I'll have to revisit for another attempt. I would have suggested we add that to description=* which is used to provide additional information to the end map user, but it's limited to 255 characters.

I'd consider changing access=permissive to access=yes then. Per access=* "permissive" means it's private but the owner generally allows access, but that might change at any time. "yes" means it's public right of way.
I just added one of the foreshore bush tracks yesterday, but I'm sure there are more missing short tracks still to be mapped.

I tried to access Merlon Pathway, but couldn't find it without risking trespassing. It was very unclear where was private and where was public, and didn't look accessible. I guess I just needed to push on and if I found myself in someones house by accident then apologise. Have you physically surveyed this by walking through?

Have you seen StreetComplete https://github.com/streetcomplete/StreetComplete#readme helps survey details of these houses. And if you instead add them as generic building=yes then on the ground it will ask if it's detached, duplex, terrace, apartments etc.

A bubbler you could also use amenity=drinking_water
---

Published using OSMCha: https://osmcha.org/changesets/108006048

if the gate can still be opened by emergency services, national parks staff etc then better to set as motor_vehicle=private, motor_vehicle=no means there is no access even for those legally allowed.

You're really on the ball with these updates, nice work!

I don't think way/732339055 and similar should be tagged as leisure=park. A park leisure=park is an area of open space for recreational use. I can't go here to kick a ball around, sit around, or throw a picnic, so I don't think leisure=park should apply.

Hey you do realise many of these contact details were already tagged under the contact:* prefix?

oh interesting I didn't realise there was a track along the creek here connecting the other tracks. I'll have to check it out.

I've removed the overlapping beach sections here and split them into a few with different names.

hi it looks like you've added two overlapping beaches here so I've removed one so we have just the single beach. The south beach you've set the name as Mm could you please explain that?

It's good practice to try and modify existing objects rather than deleting and adding new ones to retain the history osm.wiki/Good_practice#Keep_the_history. In iD you can right click the node and select disconnect.

1. May I suggest trail_visibility=* it sounds like it might be bad or intermediate.

2. Per osm.wiki/Good_practice#Don.27t_use_name_tag_to_describe_things the name should be the proper name only, the one you entered can be added as a description tag. Or better yet, encode that information in tags. eg trailblazed=cairns trailblazed=*#Values

Hi please see the comment on changeset/107117225, the beach is already mapped. I have retained your area but used the JOSM replace geometry tool to retain the history from the original node and bring in the additional tags.

What's E473?

I'll change the surface to using a ; as value separator.

This looks like the name of the Harbour not the beach, if the beach doesn't have a name then it can be left blank.

I updated the name to the proper name "Chinamans Beach", Green Point is separately mapped as a headland.

Given Gerringong Harbour is the name of the Harbour not the beach, I'm not sure we should apply this name to the beach? If the surface is a mixture of sand and gravel, then surface=sand;gravel would be the best way to tag this as it's machine readable and the common practice for multiple surface values.

Hi this feature already exists at node/765088610 so I've removed the duplicate one you just added.

Does this facility analyze the samples or just collect them. Usually these customer facing facilities are just for sample collection so better tagged as healthcare=sample_collection