C'mon, buddy, that note is disputable and capricious at best. Let's have a little decorum instead of flag planting, eh?

It was actually already there before but under the boundary=protected_area protect_class=24 scheme, which it was suggested that I update. I literally woke up to that ruling this morning. I suspect Oklahoma is now much smaller with three exclaves (the Pawnee triangle near Tulsa, the southwest corner and Fort Sill's c1890 boundary), but not entirely sure yet.

Seems like we've been going back and forth on this for about a decade but looks like aboriginal_lands is more or less winning out. Changed it.

Can't use Google Maps for this, that violates both OSM and Google's licenses.

Likewise, looks like the motorways themselves were moved without any regard to the placement, lanes or turn lanes tagging...took quite a bit of work to straighten that out.

I'm curious where you're getting Crossroads of America, Crosstown Expressway and Tinker Diagonal from... those freeways were renamed years ago and have signs up, and ODOT commonly refers to that interchange as Dallas Junction.

Yeah, nationally, in the US, trunk is expressway. It's really hard to argue that 33 is more than a secondary on either end of this expressway, or that this isn't an expressway.

highway=trunk is for surface expressways (ie, freeways that are not grade seperated) and single-carriageway freeways (one road, no intersections).

South Walnut Avenue works better than S. Walnut Ave. because computers have a hard time expanding abbreviations but can easily create abbreviations if desired.
---

Published using OSMCha: https://osmcha.org/changesets/86472516

No abbreviations in names and addresses, please.
---

Published using OSMCha: https://osmcha.org/changesets/86472542

Easily done. Instead of mapping it as a single golf course, map both golf courses separately and then add both to a single site relation. osm.wiki/Relation:site

This is the object that your golf course name should be on. way/769791424

From there, it's easy for anything to infer that if it's within that polygon, it belongs to that entity.

right, but they're inside the boundaries of the golf course in both cases, correct? Problem solved already.

Name the golf course the proper name, not the holes. Tags apply specifically to the object you're tagging.

Nice fix, good job.
---
#REVIEWED_GOOD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/86191581

Let's work on that geometry and actually mapping the whole parking lot if you're going to map a parking lot.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/86192212

Unless the name of every one of these holes is literally "silverhorn", then this is an inappropriate use of the name=* tag. See osm.wiki/Names
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/86199355

If holes don't have names, then don't add name=*.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/86087807

It's both a pond and a water hazard.
---

Published using OSMCha: https://osmcha.org/changesets/86091970

Odd choice of geometry for the middle driveway, but otherwise, very nicely done.
---

Published using OSMCha: https://osmcha.org/changesets/86112134