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

What do you mean by "the incormation provided and pictures"?
---

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

Heh, I love this...just watching for misspelled "Seattle" instances?
---
#REVIEWED_GOOD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/85634220

Looks like you replaced the name=* value with the operator=* value.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/85393531

That median was recently removed.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/85385705

Are you copying names out of Bing?
---

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

Where are you getting the idea that there's a ford there?
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/85348221

This changeset has been reverted fully or in part by changeset/85353077 where the changeset comment is: Reverting; driveway got changed to a residential road and a ford that doesn't exist was added.

Broadway Extension also steps down to a trunk before turning into a street at Comfort Drive. Little dodgy if it steps down at Kilpatrick or Memorial. Portland/Lake Hefner's more of a four-way boulevard to 164th last I drove it, but aware that they're planning on giving it the surface expressway treatment to Waterloo about 10 km north.

Trunk and Motorway are special cases, where trunks are analogous to expressways, where there can be a mix of ramps and surface intersections, and motorways are freeways, where they're grade separated in all but the most exceptional circumstances.

Analogous situations would be WA 500 between Fourth Plain and Interstate 5 (which also should be trunk) and literally almost all of US 75 in Oklahoma (save for the stretch between 86th Street North and OK 117 generously)

North of Kilpatrick, Lake Hefner Parkwa should be an expressway thanks to the at-grade intersections. Where OK 74 goes down to a single roadway with at grade intersections, it should be a primary at the absolute highest and a secondary at lowest.

I, and the FHWA, disagree that freeways can terminate at an at-grade intersection. The turnpike is the last major junction the expressway starts.

Really the only difference between an expressway and a freeway is if there's an at-grade crossing as an integral part of the experience. The difference between say, Lake Heffner Parkway and the Sand Springs Expressway is that the Diamond Head Junction is a one-off dozens, if not hundreds, of kilometers either way. Lake Hefner Parkway has a mix of ramps and intersections north of it's last major intersection at the Kilpatrick Turnpike.