Removing hov=designated isn't correct, as this leaves just access=no as the access tag, which means nobody can use that road. access=no, hov=designated means only carpools can use that road.

This changeset has been reverted fully or in part by changeset/82221199 where the changeset comment is: See previous note.

Thanks for the update on it not being an exit number, however, extending the ramp long past its split and erasing lane guidance is not the way to go around this. If your autopilot is failing to get this right when the map is matching ground truth, you need to contact your manfuacturer and report a bug. See also: osm.wiki/Tagging_for_the_renderer

I agree the wording is a little odd on the challenge, however, aeroway=helipad is literally just the helipad.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/82190473

Yeah, pretty sure a helicopter landing there would punch straight through the roof. Map the helipad where it is.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/82190473

Might check against the GPX traces in the area to line up the background to known roads. I think Bing and Maxar are closer last time I was mapping in that part of Oklahoma.

Not wholly sure where you're getting a Y where it looks to be more of a T.
---

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

This geometry feels especially wonky.
---

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

Doing pretty good, but might want to doublecheck your imagery alignment, I feel like everything's shifted northwest a few meters.
---

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

Pools should be mapped as pools, not natural bodies of water.
---

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

This changeset has been reverted fully or in part by changeset/82184305 where the changeset comment is: Still under construction.

What gives? Have you recently been on this road? It's still very much under construction and OklaDOT is still asking people to avoid it.

This changeset has been reverted fully or in part by changeset/82113662 where the changeset comment is: Problem exists with Tesla not OSM, reverting Tesla-specific edit that doesn't reflect ground truth.

Yeah, looking at it now, it looks like the mapping is now bugged. If that fixed your Tesla, the map should still be fixed to match reality and you need to work with Tesla to fix a bug on their side.

I might also recommend doublechecking with Tesla on this one before going for that, there's no reason it shouldn't be able to handle the way it's mapped now.

OK, I doublechecked it against Mapillary imagery from January to confirm and updated based on what I saw.

Also looking at this more and working knowledge of how interstates work, I'm thinking 605 departs from 405, not 22, and the ramps between 22 and 605 are just ramps?

Yeah, I think we were trying to solve the same problem. If you open in Id and have the background set to Bing, does that imagery match what you're seeing on the ground? I honestly only go through that interchange maybe once or twice every ten years myself since I moved away.

Basically, I'm trying to work out how the south end of the HOV ramps end because it's causing problems for navigation systems if it's starting earlier than exists in reality.

Also looks like you were trying to mitigate a lane change restriction by extending the ramp... there's change:lanes for that, which is what I had going on there.

Also is the ramp for the HOV lanes on the left just west of 23 really starting much farther south as you put it now, compared to where it's located on the Bing imagery where I put it?