I think this could just be `ref=8822`.

This was the only instance of `highway_authority_ref`=* in NSW, but I understand that tag should be used for the TfNSW Road Numbers. In the dataset at https://opendata.transport.nsw.gov.au/data/dataset/nsw-state-roads-vertical-clearances there is a "Road Descriptions" sheet which includes all the Road Numbers of State managed roads in NSW and 8822 doesn't appear.

I was thinking if I need to do an import proposal to manually add those road numbers from that spreadsheet as `highway_authority_ref`=*...

Comments like "do not delete" aren't very helpful, I find it more helpful to other mappers to use the changeset comment to document why you made the changes, and if applicable referencing wiki guidance or documentation or another discussion elsewhere on the community channels.

> actually required for the entrance names to appear in https://transport.vic.gov.au/

The way features are mapped and tagged needs to accommodate a range of downstream data consumers, doing it a certain way just to make things easier for any single consumer might make it less useful for others.

@cs09736 is spot on here, regarding tagging for the renderer and verifiability. For your specific use case of the data, you could try to post-process the data to format the name as you need from other tags like entrance=* and ref=* on ways leading to a railway=subway_entrance.

> way/1430177324

"indoor pathway" could also be something you add into your application based on highway=footway + indoor=yes.

surface=*#Surface_for_footways_and_cycleways has an example of a segregated shared path, footway:surface=* + cycleway:surface=*

Hope it's okay I deleted the construction cycleway way/1377140432/history and replaced it with way/1459444640 with segregated=yes since the path is now open and doesn't have any physical separation between the foot and cycle parts, just paint (unless they are planning on adding physical separation later)

Good one Hugh. I was watching this to see who'd be first to update it, I really thought it was going to be ❤️‍🔥.

also for way/573748608 I think it's simpler to omit turn:lanes=*. Because in general the way within the intersection may be used by different vehicles coming from different directions and the turn:lanes usually only make sense leading up to the intersection for that reason.

If you think it should have turn:lanes, we might need to have a wider community discussion.

only one lane from Russel Av can turn right into Forest Way.

should way/288405561/history really have a turn:lanes tagged? given there's no markings once you enter the intersection and the way is used by both traffic going straight/right from Ferguson into the intersection, but also from Warringah Road eastbound turning into Starkey St, where there is only one lane turning.

there are no marked turn lanes on way/962492250 so I don't think it should have a turn:lanes=* tag at all. Even if it did, the turn lanes would stop at the northbound carriageway, not continue through to the southbound one.

Same for the lane count, I'm not sure if we should have a lane count here since there are no markings, but even if it did it would be lanes=1 since the forward and back share the same space.

grumble grumble... in my view this is excessive to split such small sections due to a small barrier in the middle and how they were mapped before was much simpler.

I don't think your changes to way/962492250 are correct, there's no marked lanes, if anything either turn shares the same space, so it's a bit like lanes=1, but I'm not sure it should be tagged.

turn:lanes, theres no marked turn lanes on this part, and you've got none:right coming for Forest Way to Russell Avenue?

"Authorised Vehicles Only" should be access=private, it allows deliveries and emergency services access.

access=no would mean no access by anyone, completely closed.

hi you have dragged the tree into the ocean node/13332744765/history

I can't find any signage or markings on the ground indicating way/470076706 is for bicycles, I would need to survey again though in case there is a sign at one of the entrances

It seems like these change continuously and you're endlessly updating the tags. If these values change so often do you need to have these updated in OSM?