Fully aware of that, it's also an extremely long and twisted boundary to try to sort out and it's been mostly broken since import.

Please don't move onramps downstream of where they actually come together and exits upstream. The junction node should be next to the end of the painted split on the pavement.

Which Tulsa (city or county)?

I would expect both are pretty bad right now, and I've been trying to get it sorted but boundaries in Oklahoma are quite complex. I've been untangling boundaries as I map other things in the area because it's really the only way to not go insane at this point.

Looked up Heavener's municipal code (which actually had a pretty decent description of their local speed limits) and updated based off that and a better understanding of who controls which roads than I had 5 years ago. Not my highest quality work, I had about 20 minutes over breakfast before leaving to go to work.

Inside an incorporated city, it's probably safe to remove the default speed limit, though as the code is written, that would be the case if the town doesn't have something lower within the county.

Is there a specific town you have in mind?

Anyrate, sorry for the goof, thanks for the catch.

OK, looks like it was a clean copy and transform missing the relation, so this *should* be fixed in changeset/128060909

My confusion was definitely the buried lede, copying US 81 to the southwest was definitely not my intention.

You're right, I didn't see it until you pointed out the Lake Ellsworth giveaway. I'm fairly certain this goof was limited to just the pasted version, but I'm doublechecking.

Double white solid lines would mean no lane changes...and even then there's change:lanes=*...

Also seems a lot of junctions got moved to be too early on the exits and too late on the entrances, the junction should be next to the tip of the painted gore on the road.

Or, rather, outward from the median on both sides, since I see the westbound side got moved too.

Please be mindful of moving geometry when placement tags are in play, this shifted the entire highway over by two lanes to the south.

Might consider squaring up the corners...JOSM makes short work of this but I'm pretty sure there's a way in iD as well.
---

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

Turn lanes should be tagged on the way they're belonging to and not as a separate way. You'll probably need JOSM instead of iD to do this effectively.
---

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

Proprietary sources are generally prohibited due to licensing; please provide specifics.
---

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

Was this meant to add a kilometers-long culvert?
---

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

Kinda seeing the Durant Bypass as more of an aspirational motorway given that a decent chunk of it's still single carriageway. Thinking maybe highway=trunk, expressway=yes is probably better on the dual carriageway, no?
---
#REVIEWED_GOOD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/127906863

US 81 is mostly what I was working on in this changeset, this particular one getting details around Enid (lanes in particular) updated.

Might I ask why this is drawing hostility now after I've been working on lanes for basically a decade at this point?

Good thing to do in general for sidewalks along roads since it helps out blind people using navigation apps.
---
#REVIEWED_GOOD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/127074169

I updated the tags on this to match tagging a little more typical of the rest of the map based on the information available.
---

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