PS. once this is resolved we can add in that footbridge connecting Douglas with P2.

What's your source for changing P2 as shown in https://osmcha.mapbox.com/changesets/53663839 ?

If you look at the Mapillary imagery https://www.mapillary.com/app/?pKey=n_XySOWOiOvah91TDXfS_w&focus=photo&lat=-33.821719&lng=151.19080397220682&z=17&x=0.15626994051340276&y=0.5274092764743991&zoom=0.33670345817231884 you can see that the way it was mapped before this changeset matches the Mapillary photo (ie. the building doesn't go further south as per your change, but rather stays as a rectangle), but now it doesn't. I don't think it's been changed since the date of the photo as it was taken post construction.

It looks like you've added this twice, did you want to delete one of them?

Was your edit to way/188020579/history a typo?

Looks fine, good job! There's plenty more missing turn restriction in OSM that are just waiting to be added.

Getting closer... currently you have the members correct but spread across three relations for the left turn only each with a different member, but you need one relation with three members.

Try JOSM, it's much easier when working with relations and turn restrictions.

These are the 3:
relation/7713776
relation/7712221
relation/7707282

but it should only be one like
relation/7707084

https://ibb.co/hg20iG

There has been an influx of poor quality SEO entries where we don't hear back on changeset comments when things don't add up. Sorry you got caught up in this @Dynamic HVAC, but glad to see things have been worked out in the end. Thanks @tonyf1 for always being on the ball!

Is this rock pool, a swimming pool? leisure=swimming_pool can be used for man mad outdoor rock pools too.

If you're trying to get this to shop up on the map, it's probably best to pick either shop=butcher or shop=greengrocer, as this is the primary tag which is going to classify this feature.

Or if they occupy different spaces within the same building, place two nodes, one shop=butcher and the other shop=greengrocer, all within the building=retail.

No worries, try this guid https://www.mapbox.com/mapping/mapping-for-navigation/adding-turn-restrictions/. http://learnosm.org/en/ is also a good entry point for guides.

Yeah I had to split the way to add the turn restriction. Definitely try JOSM it's much better for relations. There you can fix up the southbound on Willarong relation. PS. you've duplicated the node so you'll need to fix that up in josm.

I don't have a strong opinion either way. Just chiming in with further facts from the ground to help guide what should be in OSM. Even if we did split the Blue Mountains out, You should be able to include both the Blue Mountains and Sydney in overpass together.

The left_turn_only relation is missing some members for from and to and the role for the via node, see relation/7707084. The relation needs 3 members, from via and to, but it only has one member the node and no role.

osm.wiki/Relation:restriction#Members

https://ibb.co/jvdJ0w

I find JOSM much easier to work with when doing relations/turn restrictions, as when you select the relation in ID you can't add members to it, you have to select the ways then add it to the relation. Maybe give JOSM a go?

For this one I've fixed it up in changeset/53525466, but it looks like you'll need to add one for when you head southbound towards the Kingsway too.

shop=supermarket

You can add shop=supermarket so it shows up as a supermarket.

Yes, please do map footpaths, they make pedestrian routing more accurate and informative.

There are two ways to map the footpath. Using sidewalk tags on the road and as a seperate way. You can have both in use at the same time.

See osm.wiki/Sidewalks#Sidewalk_as_separate_way

In particular by mapping as a separate way "This method allows for a more spatially accurate representation of the pedestrian environment. In addition, it allows a more straightforward use of barrier=*, tactile_paving=*, kerb=*, surface=*.".

The only thing I'd add is use footway=sidewalk to mark it as the footpath/sidewalk. This helps people distinguish footways through parks etc from the footpath/sidewalk.

No response from the mapper, so I've gone ahead and undeleted the footways while leaving the new sidewalk tags on the highways as both can coexist.

Partially reverted in changeset/53516154

Undeleted with JOSM:
way/524640907 way/532523005 way/524635444 way/524635443 way/524635442 way/524640908 way/524640159 way/524641618 way/524640906 way/524633279 way/524640161

Glad to help. Be sure to sign up to the talk-au mailing list https://lists.openstreetmap.org/listinfo/talk-au. I'm organising an OSM event for later this month (will post details on the mailing list) and it would be a good opportunity to learn more about mapping and OSM, see what others are up to, and share what you're interested in.

> Ok then I understand, and I can test the routing by using ORSM and it's routing correctly with only the Left Only Turn.

Maybe, maybe not. Since the routing only get's updated with new data ever several hours I think we can't know for sure if it's using the new turn restrictions, or if it's just avoid going that way since way/151022092 was oneway=yes before. (ps. it's fine to just delete oneway=yes, as the default is oneway=no. It doesn't hurt to leave oneway=no in there but it would be confusing if every road had it. But in this case where you wan't to signal to other mappers that it's not oneway then that's okay)

I don't know what the point of the no-u-turn there is, if it's not signposted then it's best to leave it to routing engines to apply sensible defaults. You would expect all routing engines to never tell you to take a u-turn in the way your no-u-turn relation is set up already. We want to avoid adding no u turn relations to practically every intersection as it just makes it harder to edit without any benefit as defaults can be applied anyway.

You don't need a turn restriction for this kind of thing.

That diagram isn't showing what turn restrictions are in affect, it's showing you what ways you can select for the current turn restriction you are adding. So even with just the only_left_turn it will prevent routing straight through.

You could use something like https://imgbb.com/ ?