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

FYI addr:flats is to list out the unit numbers at the address, not a total count of units. building:flats is for the count of units in the building. Per the wiki.

This looks good to me.

Hi welcome to OSM, the scrub area you added was already existing at way/788214827 and the railway area isn't scrub so I've reverted this changeset. What were you trying to do with this change? Maybe I can help?

addr:unit is used to represent a single unit, this apartment block would contain multiple units probably with a number, so addr:unit is not the right place for the building number. You could just use name on the building like you have or addr:housename on the building.
You can use addr:flats to list individual unit numbers in the building.

addr=*

Unless you know it's wrong you should retain the prior tags like building:levels and building=residential
---

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

In the Vicmap Address data, all the addresses at Melbourne Park south of the train line have 3004 however your boundary here follows the Yarra. However when I check some venues in that area online their websites still list as 3000 postcode, so based on this I think we should ignore Vicmap and leave the boundaries as you've enter them.

On second look, I've left the node which has an address and just removed the tags for shop=mall and name since these are already mapped. If the address here is for the whole shopping centre then add it to the existing Westfield outline, otherwise if the address is just for this location here it can remain.