In JOSM, you could have just copy and pasted the existing object.
---

Published using OSMCha: https://osmcha.mapbox.com/changesets/65674767

permissive is "private but generally accessible", potentially a weird flex here.
---

Published using OSMCha: https://osmcha.mapbox.com/changesets/65648165

access=permit isn't a likely to be identified value, access=private would be more likely to be accurately handled.
---

Published using OSMCha: https://osmcha.mapbox.com/changesets/65648024

This changeset has been reverted fully or in part by changeset/65658098 where the changeset comment is: Removing SEO spam.

Check abbreviations (please avoid them) and spelling.
---

Published using OSMCha: https://osmcha.mapbox.com/changesets/65594416

Good start, please avoid abbreviations and combinations seperated by /. I'd have gone with "Eagle Nest Campground" as the name and "Fort Cobb State Park" as the operator.
---

Published using OSMCha: https://osmcha.mapbox.com/changesets/65594317

Looks like you can see the bridge footing just south of the gantry, only a couple feet north of the original node positio..
---

Published using OSMCha: https://osmcha.mapbox.com/changesets/65591653

I honestly could go either way on this, on one hand it is somewhat well established to use a / in this case. On the other hand, aeroway refs are the only thing that does it this way. Even ref:forward/backward=single_value would make more sense.

On the runways, ref=* has both runway numbers seperated by a /.

This changeset has been reverted fully or in part by changeset/65532876 where the changeset comment is: Rolling back inaccurate ramp geometry.

This changeset has been reverted fully or in part by changeset/65532866 where the changeset comment is: Rolling back inaccurate ramp geometry.

This changeset has been reverted fully or in part by changeset/65532852 where the changeset comment is: Rolling back inaccurate ramp geometry.

This changeset has been reverted fully or in part by changeset/65532823 where the changeset comment is: Rolling back inaccurate ramp geometry.

This changeset has been reverted fully or in part by changeset/65532807 where the changeset comment is: Rolling back inaccurate ramp geometry.

This changeset has been reverted fully or in part by changeset/65532784 where the changeset comment is: Rolling back inaccurate ramp geometry.

I'm not sure why that got edited in the first place, if the split isn't at the tip of the theoretical gore, then route guidance assumes you have made the transition way too soon and announces the next instruction before you've completed the exit move and indicated distance to the ramp won't be accurate in most routers. placement=transition along the ramp from the start to the bullnose is typical to indicate that the ramp is in transition from the main road.

This changeset has been reverted fully or in part by changeset/65532715 where the changeset comment is: Rolling back inaccurate ramp geometry.

This changeset has been reverted fully or in part by changeset/65532697 where the changeset comment is: Rolling back inaccurate ramp geometry.

Possibly redundant. The payment:pikepass=* and payment:cash/coins/whatever=* tags provide hints on what payments are accepted.
---

Published using OSMCha: https://osmcha.mapbox.com/changesets/65512557

This changeset has been reverted fully or in part by changeset/65532623 where the changeset comment is: Rolling back inaccurate ramp geometry.