Well, we can see in the LPI Aerial:
a). A horse here -36.38543, 149.89142
b) a trailer to transport two horses here -36.38496, 149.89167 (Bing has two trailers there)
c) a stream flowing through the meadow way/772369871
d) a footprint structure on the grass typical for meadows where horses are living (bad grass around the stable and near gates and water places) and
e) a big difference in grass texture to areas nearby which are clearly lawns.

Free and non-free sources offer information about the fence, its surroundings and other trivia. And I used them all.

The copyrighted book about "The Easter Bunny and the Rabbit Fence" is one of them, see https://books.google.de/books?id=PMz3CJdd-e0C. This made me feel bad. My work might still be incomplete because the mapped fence does not run through Goombi as described in the book. A dilemma.

I hope it is OK for the DWG that all (even copyrighted and technically copyprotected) sources can be used to form a personal idea how such a fence needs to be built and maintained and might look like. For example this non-free https://www.facebook.com/DDMRB/posts/1949264168460782 leads to Karara. As a search result for "rabbit fence" in JOSM/Nominatim I found two roads way/333041274 (plus way/765928303) which gave an idea where the fence might be.

The rabbit fence is accompanied by two maintenance tracks (I got this idea from several photos from Facebook). It has also thither meshes than cattle or sheep fences. Therefore it looks darker. And a lot of its corners and gate posts are stabilized with metal frames, see here https://www.mapillary.com/app/?focus=photo&pKey=TbHwfNUCAJMdLDqCqcnkvQ. These features makes the rabbit fence distinguishable from other fences in the aerials.

Wikipedia has a list of the eight councils financing the fence. Screening the aerials in south wester direction of the villages of these LGAs and their predecessors brought me a big step further.

Three sections of the fence have already been mapped by others, see way/738488848, way/658389012 and way/658389016.

Using the hopefully free image https://www.mapillary.com/app/?focus=photo&pKey=ce_D9g3dadKv6KeF78wP9A and the next one gave the idea how the construction looks when the rabbit barrier needs to cross a road. This was a big help for finding this node node/7205852660 near Chinchilla.

Some "educated guesses" were made. For example the node node/7205852638 and its neighbours were mapped to the idea that the fence would no run through the sewage handling area.

Another guess was that the fence line goes up further North at this node node/7205864196. At first the fence going westwards looked better. And I did a few nodes on that route. But then the misses came: No grids, no gates and no maintenance tracks aside. So I guessed that this structure way/771871452 needs to be a cattle grid
to keep on going.

The final guess to be described here is that this part way/771871458 was only formerly the rabbit fence. It is not in use any more because the coal mine expanded. Bing shows nothing on the new route, but the newer Esri images do show the fence.

To conclude: While still having some guesses I was convinced that the data taken from allowed sources is good enough to be seen as "reliable" and therefore I uploaded.

1) Please let me know if the statement above is not enough to answer the first question.

2) For the guesses I made one factor was which councils pay for the fence. This information comes from the DDMRB. I consider this information as free.

In future someone might notice this gate node/7209079924. It has an URL tagged to an article which describes it and shows it. No data from that article was uploaded to OSM, only the URL directing to it. Please feel free to give some thoughts about this.

It seems that you have moved this toilet node/3709202664 accidentally 750 meters away.
Please check your edit.

>Source of the path 'Sculpture Walkway'.

You can see the bridge over the drain in the LPI aerial.

'Cobargo Apex Park' is the common name for that area. It is local knowledge.

The boundary is clearly visible in the LPI aerials.

Nobody uses 'Cobargo Town Park'. A web search for this term gives zero results. Seems that the LPI map guys are the only ones using it.

The sculpture walkway has it's name from the sculptures it is leading to. This is local knowledge in Cobargo. Formerly it was called Riverside Walk too.

You can see the handrail in both sources attributed in the changeset comment. No need for writing them down again here.

The residential area was last edited ten months ago. You edited the wood ten days ago. So you are responsible.

The overlap occurs were both areas touch each other, see osm.org/#map=19/-30.36203/153.07300

Turns out that way/771395490 is no swamp on the LPI maps but another wetland without trees, see https://maps.six.nsw.gov.au/arcgis/rest/services/public/NSW_Base_Map/MapServer/tile/17/77855/121074

Because of it's saline input and the written description by the government I decided on saltmarsh for this treeless, often water-filled part.

The other one further up northwest is a reedbed. All other wetty areas are swamp because trees grow there. The part between the beach and the swamp is scrub because of it's low growing bushes.

Please do not stick to much to the LPI maps but trust your eyes and interpret the aerials.

Hi, let's check this in detail:

As of today, both of the LPI NSW Base map and LPI NSW Topographic map shown in JOSM present a swamp in that area.

So I added the 'LPI approved swamp', (way/771395490) a wood on the right hand side of the Moor Creek and some trails. Especially the 'Swamp Trail' from https://www.environment.nsw.gov.au/topics/parks-reserves-and-protected-areas/park-management/documents/khappinghat-nature-reserve and the text on page 9 of the 2019 plan which reads "Forested wetlands surrounding Khappinghat Creek and its tributaries include swamp sclerophyll forests dominated by swamp mahogany (E. robusta), swamp oak (Casuarina glauca), red mahogany (E. resinifera) and the paperbark trees Melaleuca nodosa, M. sieberi
and broad-leaved paperbark (M. quinquenervia). The saltmarsh complexes adjacent to Khappinghat Creek include areas of sedges, rushes and tussock grasslands dominated by bare twig-rush (Baumea juncea), sea rush (Juncus kraussii), common reed (Phragmites australis), samphire (Sarcocornia quinqueflora subsp. quinqueflora) and marine couch (Sporobolus virginicus). These wetland and forested wetland areas include Freshwater ..." makes me feel that swamp is not too bad.

The next paragraph deals with "shrubland, dry wallum sand heath and wet heath communities." which may also fit.

Please feel free to check the current mapping after the changes I made with changeset/80810033

On this matter I would be happy to hear your opinion again.

Surely you damaged the parks mapping. It was based on the On the Ground Rule, see osm.wiki/Good_practice#Map_what.27s_on_the_ground. As this page says, the local legislation should NOT be considered if not bound to reality.

If you do not have enough knowledge to accept a fence around a park as boundary of this park, then this is your issue.

While reverting your tagging I did you a favour and created a copy of your data with the parks 'legal boundaries' in changeset/80797958.

By moving node/7107923227 to the "legal" you neglected :
1. The sidewalk along the Bermagui Road
2. The footpath from that sidewalk to the western side of the Princess Hwy (below bridge),
3. The fence at the borders of the park and
4. The small stream at the eastern border of the park.

All mentioned facts above are clearly visible on the LPI NSW aerial.

Please repair the damages you made.

Now the natural=wood area you changed overlaps the residential area (way/371875703)
Please correct this.

With this edit a duplicate landuse tagging was created on the swamp 691952756 already tagged in May 2019.

Please correct your work.

With this edit you left the eastern half of the bushland formed by way/519186155 as wood.
Please complete your work and delete it.

After this edit the relation still has the error of duplicate landuse mapping made in #51195671
Please correct this.

With this edit a landuse=forest and a natural=wood was placed on the same part of the Jinjera Hill – By the same mapper who mapped the other forest two week earlier :-)
Please check your work before uploading and delete the double tagged parts.

After this edit your forest relation lays over an area mapped as residential, see way/538632435
Please correct your work.

This edit placed natural=wood relation/10668996 above the landuse=cemetry tagged since 2013, see way/233587980.
Please correct it.

This edit placed landuse=forest (nodes 7185664758, 7185665181, 7185665487, 7185666222 and more) on top of an area where landuse=residential was mapped since January 2016 (north of the nodes node/3964005596 and 3964005594)

Please correct your work.

This issue is closed now.