Cleaned up a bit of a tagging trainwreck here since a lot of those tags belong to the museum and the ship is not a building.
---

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

Please actually adjust the geometry to match the buildings; don't just blindly copy over from MapWithAI.
---

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

This is probably more likely ref=CR E0560.
---

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

E0560 sounds like the more likely name...probably should be ref=CR E0560 since it's presumably 56 miles south of the Kansas border and not 560.
---

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

Already tagged as a path. name removed. Width seems too small since it's about as wide as as a car. Contact the makers of the program that's giving bad directions since they shouldn't be trying to route cars down a path to start with.
---

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

Fixed it up for ya, since you tagged something not a bridge as a bridge, while missing the bridge itself. Also definitely not just 1 meter wide, 1 meter is about the distance from your belt to the floor standing.
---

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

lanes probably isn't worth tagging on this one if the lanes aren't delineated; probably should be "noname=yes" and "ref=CR 2976"
---

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

This one-way probably applies to the entire parking aisle through the Whataburger lot.
---
#REVIEWED_GOOD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/123344143

Oof, OK, I'll try to track down what happened. Super not a fan of Oklahoma's annexation rules that make for extraordinarily fiddly work. I'm trying to get it cleaned up around my area since it's *baaad* and not something that most people can do without having some idea how boundaries here work and looking at the public data...

When bringing in buildings from Map With AI, please adjust the footprints to actually match what's on the ground. If the data was already high quality, the whole dataset would have been mass imported long ago.

Just a heads up, it's not necessary nor desirable to duplicate ref=* information in name=*. osm.wiki/Names#Name_is_the_name_only

Please avoid using abbreviations in names.

Hi there! Please avoid using abbreviations in street names. Should be "Fish Creek Road", not "Rd."

When removing fixme=check lanes, it would be greatly appreciated if the lanes were actually checked and updated in detail, which is the goal of that.

Telegram has threads and replies, too.

I'm on the mailing lists, I'm afraid my only proprietary communicator slot's already taken by Telegram.

Eeh. Mappers here tended to go with the classic "trunk is expressway" route for a long time. Which I'm still personally a proponent of. It looks weird mostly because ODOT doesn't plan expressways or freeways so much as new ones get built or added on to when some dude who owns a paving company has a buddy in state congress with some pull...

Care to expand on that?

So, change secondary to primary for ? and then incorrectly tag lanes as one would for a one-way but not two-way highway? Trying to figure out what that accomplishes.
---

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

Yeah, this is outright wrong...there's plenty of spots where it goes to three lanes along these.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/118452055