My preference is usually to avoid mapping a path on a beach since there is usually no actual path there, just the beach and really you can walk anywhere on the beach. I understand for routing it makes it easier and if there is a well signposted route which traverses the beach it might make sense to map it as a path, but otherwise I'd be tempted not to.

That's okay, mistakes happen. One way to prevent this is always keep the original way and just tweak it's nodes, or in JOSM there is an approach to replace geometry while retaining the original way object osm.wiki/Keep_the_history

I've partially reverted this changeset in order to restore the history of https://osmlab.github.io/osm-deep-history/#/way/648268968 and reinstate the tags which were deleted.

I've re-instated the original building in https://osmcha.org/changesets/85121532/ in order to keep the history per osm.wiki/Good_practice#Keep_the_history please next time re-use the existing way so we can retain the history.

Hi I can't make sense of these changes, I've reverted it out of caution. What was your intention here?

I've reinstated the buildings now, but still working through the aliment issue.

It's good practice to keep the history of objects osm.wiki/Good_practice#Keep_the_history
Deleting and then re-adding looses that history and in this case also lost the information about the type of building. Further when something was added by a ground survey you should be extra careful about removing something since aerial imagery isn't that great compared to a ground survey

Also https://pewu.github.io/osm-history/#/way/760475673 was deleted here, but you can see at https://www.mapillary.com/map/im/fyzmT-7t_Rqc0qN6Mr8Qqw it quite clearly a driveway, just all the fire trucks were out fighting fires. I'll restore the driveway.

I'll fix this but also wanted to point out here that https://pewu.github.io/osm-history/#/way/760475671 was deleted only to be re-added again https://pewu.github.io/osm-history/#/way/802774744. I'll fix this by reinstating the original building tagged as a shed, but curious about what happen in the process which caused this?

> offset started up there

It's a good idea to re-check your offset as here it was quite a bit off from the GPS traces.

> Oh this is for a HOTOSM project by the way.

Yep I saw that, any idea who organised it?

> Wait I also noticed you unmapped all of the buildings I mapped. Do I really have to redo this again?

I reverted the whole changeset to reinstate the path and revert the road shift, I noticed a few other changesets which shifted the roads too which I'm working through reverting but it's quite hard when there are ongoing edits in this area. I can try to reinstate the buildings you had mapped.

Hi I've re-classified a few of these roads as driveways or forest/agricultural tracks. What source did you use for these roads, a few of them are very unclear based on the imagery.

hi I've reverted this change since it shifted the alignment of roads, which put them quite off compared to the GPS Traces Layer. I also restored the deleted path. If imagery is not aligned you can manually set an offset using the GPS traces layer as a reference.

https://osmlab.github.io/osm-deep-history/#/way/143812389 I believe freqency=0 indicated it was dc, did you mean to remove that tag?

The section at https://www.mapillary.com/map/im/OGNWdJkgd0Pk3viFIxjHnA only looks like shared lane heading west, heading east it's one of those doorzone cyclelanes. I've updated the tag, but if this has changed since my mapillary capture just shout out.

I've reverted this changeset since the other changesets by this user appear to be fabricated and/or spam and so don't think we should be trusting this change. Indeed the OpenStreetCam imagery here does not confirm any Telstra office, telephone exchange or mobile tower and so likely this was also fabricated.

This changeset has been reverted by changeset/84587904 as suspected fabricated and/or spam.

This changeset has been reverted by changeset/84587904 as suspected fabricated and/or spam.

This changeset has been reverted by changeset/84587904 as suspected fabricated and/or spam.

This changeset has been reverted by changeset/84587904 as suspected fabricated and/or spam.

This changeset has been reverted by changeset/84587904 as suspected fabricated and/or spam.