5. https://osmlab.github.io/osm-deep-history/#/way/1244811645 I had tagged as a service way. It's quite wide with a gate, and the connection with the driveway to me it's designed for emergency/service/maintenance vehicles to access. Therefore I think it's still best tagged as highway=service + motor_vehicle=private + foot=yes.

I've made further changes to address 2, 3, and 4. But apart from that, good work on the other improvements.

hi, welcome back to OSM. Some good changes here, but I also have a few comments:

1. The Northern Beaches Council Aerial Imagery is copyright, "The contents of this website are copyright and may not be reproduced in any form without the prior consent of Northern Beaches Council." as such the imagery cannot be used at all, as a reference to map from, or to trace features from. What in particular did you derive from the council images, as we'll want to remove/redo with imagery sources we can use.
2. Where possible it's good practice to keep the history of objects osm.wiki/Good_practice#Keep_the_history. For example https://osmlab.github.io/osm-deep-history/#/node/11671234344 had a long history of 10 edits, people improving the data over time but then you've replaced it with a new object https://osmlab.github.io/osm-deep-history/#/node/12415070400 which makes it harder for people to identify the history of the object which can be useful for mappers to understand how/why/when different tags were added. I'll restore the original node here to retain the history.
3. From what I can see the playground entrance was deleted here https://osmlab.github.io/osm-deep-history/#/node/10104608514 and now missing. I'll re-introduce this node.
4. According to natural=* natural=scrub is "Uncultivated land covered with shrubs, bushes or stunted trees." while there are shrubs and bushes in the understory, there are more substantial trees and think natural=wood would be more appropriate.

I found node/12419076028 as one feature imported with addr:flats10. Could we move this discussion to the community forum or a GitLab issue at https://gitlab.com/alantgeo/vicmap2osm/-/blob/master/README.md or the import page talk, osm.wiki/Talk:Import/Catalogue/Vicmap_Address

I raised this question at osm.wiki/Talk:Key:addr:flats#Exceeding_255_characters previously. Is there anything you can point me to that indicates the :2 :3 etc. key suffix is in use already for overflowing tag values?

On another note, thinking about this more, perhaps there is a different syntax we can come up with that represents these long addr:flats values in less characters?

I missed your comment Graeme. I just updated them to match the months listed on the website, exact dates would be better if you know that flaming heart?

Looks good @Tewuzij

I disagree @mcliquid, for a change like this, its better to keep it together as all the changes are related, as it makes it easier to review, comment on, etc.

please take care to not remove the branch information from the name eg. https://osmlab.github.io/osm-deep-history/#/way/444590133

In my view it should be
branch=Chatswood Interchange
brand=McDonalds
name=McDonalds Chatswood Interchange

footway=sidewalk should only be used on footpaths where they run along side a road, many of these here are walkways to access the buildings, no alongside a road and therefore shouldn't be footway=sidewalk.

good suggestion, I've mapped the area as brownfield, but this is from some drone imagery from August 2024. I'm not sure if construction has started yet.

I've cleaned up a few of these and this one. It does appear Hannah you're working with the best intentions to improve the tagging, but the way you've made these changes has introduced data issues due to the duplication of the ways. In JOSM what you'll need to do is add a node to the existing way (shortcut key is A), then press escape to stop it from continuing it as a way. You can now swap back to select mode (shortcut key is S), and select the node you added on the way, then under Tools > Split way. You'll now have split the way and can set different tags for the different segments. I believe this is what you've been trying to do .

I've never come across this kind of mapping before, so I was surprised that the wiki suggests this. I would think the way being tagged crossing=traffic_signals, and splitting the crossing way so that only the kerb to kerb section is crossing would be sufficient.

I agree with Kurisu here, the commercial landuse can be useful for some data consumers to show residential/retail/commercial/industrial landuse. Given no response in 2 years I've reinstated it in changeset/158436901

Either way I think a change of this scale is worth discussion first, especially when there may be different opinions within the community.

I'm fine with a revert, followed by a discussion, best to do that on talk-au or https://community.openstreetmap.org/ not here.

> this data is free to use for non-commercial research purposes with the correct credit.

OpenStreetMap does not fit that criteria.

> community consensus

I'm talking about the OpenStreetMap community, this was discussed at https://discord.com/channels/413070382636072960/926020366927790130/1292754771077365801 and the community consensus there is that OSM's standard on the ground rule should apply here, which is "Wattle Glen".

> community consensus

I'm talking about the OpenStreetMap community, this was discussed at https://discord.com/channels/413070382636072960/926020366927790130/1292754771077365801 and the community consensus there is that OSM's standard on the ground rule should apply here, which is "Wattle Glen".

This has swapped back and forth 12 times so far https://osmlab.github.io/osm-deep-history/#/node/892863645 please take into account the community consensus and best practice guidance. Per name=* it's clear to me that the common and on the ground usage is "Wattle Glen" with "Wattleglen" as the official_name=*.

Sorry for the late reply. You can have overlapping ways which share nodes (that helps with the topology and keeps it neat and tidy). That would be simpler here, you can also reuse a way as relation inner. eg. car park as a way, and re-use that as a wood relation inner. I think shared nodes between different ways rather than creating relations is easier to manage, but does come down to editing style.

Yeah absolutely. I was going to do that, but as a first draft found it easier to just sketch out the rough location first. Improvements welcome.

This changeset has been reverted in changeset/157035383