Hi,
Way is part of relation/2816025 .. both are tagged for pedestrians... i.e. duplication. I have removed the duplication.

Relation 15518947 deleted...
Not so certain that this is water .. look at the mapbox imagery.

I have deleted the relation. Make a new relation?

Deleted relation. Bye.

Removed relations...

Thinking about this more.. On your property put up 'Private Property' signs. And then remove traces of the path. Once that is done you could separate your section of the path and mark it abandoned:highway=path. Don't re-tag it until you have removed those path traces or you'll have people re-entering it. If you want to keep the path then your out of luck.

Sorry. This has come up many times before - including private roads that people use as a short cut.. See osm.wiki/Why_we_won%27t_delete_roads_on_private_property

I have restored the Todd Rv back to a simple way.

I have removed the name 'Junction Waterhole' from the node/10311202231 - the name is attached to a way (better) and has additional tags to tell OSM what the name is applied to - water.

Don't worry about making errors at this stage. Keep mapping, your getting the detail that 'we' armchair mappers don't have. Use the OSM wiki to get information e.g. osm.wiki/Names

Hi,
The Todd River .. why do you want that as a relation??? It only has one member ... so why make the way into a relation?

Hi,
I have restored the path and marked it access=private. It is better to contact the previous mapper and get their ideas on this kind of thing - particularly when it is recent. See changeset/130144565

Another hint ... the tree area and the residential area .. those can cross one another, one being a land cover the other being a land use.

Keep mapping, your local and can 'see' more than armchair mappers using imagery.

Hi,
I have tagged this as access=private as it goes through private property. A new mapper deleted it because it goes through private property... So ... is it public or private?

Hi,

"Pole 13 Camp" looks to be a group of buildings froming a 'campus'. See tourism=hotel#As_a_campus for a better way to map them.
The track named "Fire Trail" well that is not a 'name' but a 'description' ... see osm.wiki/Names#Name_is_the_name_only
A similar comment for 'Ranger Station' see amenity=ranger_station

Keep mapping!

Hi,
Sixmaps is not usable in OSM due to copyright. Use the DCS Base Map, this is authorized for use in OSM.

The cricket is evident in present OSM accessible imagery. Previous mappers have entered it into OSM.

It maybe better to tag is as "was:leisure=pitch was:sport=cricket" to stop others from re-entering the data.

Hi,
Regarding the beach. The OSM coastline stops at the hi tide mark ... but the beach goes further out to sea. So I map further than the OSM coast line..
See way/4042219
The same with rocks etc.

I have restored the National Park Boundary .. so it is now unbroken and does not cross itself.

The coast line should, I think, be a separate entity thus it can be altered using upto date imagery but leaving the government boundaries alone.

What do you think?

Changeset has nothing to do with National Park nor coastline.

Hi,
These relations named 'Loop 1', 'Loop 2', 'Loop 3' ... what are they??? Are there any web pages on them?

The OSM coast line is not the National Park boundary.

"The natural=coastline tag is used to mark the mean high water springs line along the coastline at the edge of the sea. "

See natural=coastline

The National Park boundary is created by the government .. it could be anything... such as the low water mark... but it is unlikely to be the OSM coast line. The original source of the entered National Park boundary comes from the Government! Leave it alone!
See changeset/72634280

The National Park boundary look like it is the low water mark .. as far as I can see. Do you have other information?

To restore the National Park boundary the following changesets may have been partially or fully reverted..
134119333, 134118581, 134118130, 134118022, 134101476, 134118022, 134108831, 134108066, 134107612, 134106999, 134106626, 134106019, 134104024, 134102957, 134102241

Please use changeset comments that reflect the actual changes...