Ah I see you've done this now.

Technically the restriction=no_u_turn should only be used on signed no u turns, and not as an arbitrary way to place restrictions on the routing, but it is common practice it is widely used as the latter and seems mostly accepted to do this by the community.

So I would say in this case to prevent routers trying to u-turn from Ellerton Drive back onto Ellerton Drive where the dual carriageway merges into single it is acceptable to use a no_u_turn relation here, even though it may not be an intersection and even though there is no signage.

hi I'm not sure what you mean by "open plan" but for the 5 units you've mapped if they are sharing a common wall, but next to each other and not on top what you have for the outlines is good, but for the tags I would use building=house + house=terraced per house=*

It looks like the unit number 4 is repeated in your mapping though.

no reply so I'll revert this.

The overtaking=no is good, but the restriction=no_u_turn restriction=no_u_turn needs to go on a relation object which has to/from/via members, and not on the way.

In JOSM add a new relation, set the tags type=relation + relation=no_u_turn then add the two ways as to/from members and the intersection node which connects both as a via member.

Thanks. I've added a few extra tags to mark the brand and tag it as a bottle return machine.

name is for proper names not descriptions per osm.wiki/Good_practice#Don't_use_name_tag_to_describe_things

See diet:vegetarian=* and diet:vegan=*

cuisine=* should be for french, german, japanese etc, not the diet types.

hi shanewh, given you're brand new to OSM, I suggest taking some time to learn about how OSM works, learn from other experienced mappers in the area, and take in feedback.

In this case fortera is correct that if the bike lane exists it should be mapped. If you don't like narrow bike lanes perhaps you could work on tagging the widths of each bike lane so people can make maps highlighting those that are wide and those that aren't? Then routing engines can favour wide ones and avoid narrow ones.

Agreed with fortera here. a top level access=no strongly implies it's in general not accessible to anyone, it's always best to try and tag specific modes and omit the top level access tag.

So it sounds like foot=yes + bicycle=no + horse=no.

hi shanewh, I can see you're brand new to OSM, I suggest reading some wiki pages like osm.wiki/Good_practice

In this case, it's easy, just tag the bike lane width per cycleway=*#Supplementary_details then data consumers like maps and routers can factor that in. You can even then make your own map style using OSM data that ignores bike lanes less than a width you choose, then others can make other map styles showing bike lanes even if they might be narrow.

Seems unlikely there would be a house ware shop here, can you provide anything to support your claim? Also the building added should only cover the building footprint, not the whole lot, is that something you can fix?

I added a landuse=brownfield to indicate what's there now, but I'm just going of Esri World Imagery, nut sure if construction has started?

Sorry I just found out "On 1 July 2023, MMP was officially formed through
the amalgamation of three previous cemetery
operators and Crown land managers: Northern
Cemeteries, Rookwood General Cemeteries and
Southern Metropolitan Cemeteries."
So that answers the Northern Cemeteries piece, but not sure about the Council?

From what I can see the operator is Metropolitan Memorial Parks https://www.metropolitanmemorialparks.com.au/locations/field-of-mars-cemetery

Given you added both Northern Cemeteries and Ryde City Council I wanted to check with you if you had any extra local knowledge?

Thanks for adding this, it looks more like a shared driveway rather than a residential road/street, what do you think? I'm also not sure about including the name Ryan Place, if it is a shared driveway we won't normally apply the street name of the adjoining street to the driveway.

If you check the history at https://pewu.github.io/osm-history/#/node/11013942187 you can see the node was originally correctly placed, but then subsequently (likely accidentally) moved. Therefore I've restored the node back to v1 which was placed correctly.

In this case the name appears on the DCS NSW Basemap which is an allowed sourced and available out of the box in iD as a background layer, since the name is there we can keep the name you've added.

hi the Georges River website and spatial portal contained copyrighted data and content, and they are not able to be used for mapping in OSM. You can rely on local knowledge and from physical signage, but please don't copy across copyrighted council information.

looks good, you could consider adding segregated=*