Is this two lanes the whole way? Or are exit and turn lanes missing?
---

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

Seems like some of these aren't really name so much as a description...
---

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

Not bad. Not great, either. I cleaned it up a bit more based on bing imagery and local knowledge to better reflect what appears to be on the ground. I'll probably survey it at some point after I get a truck again.
---

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

Looks like you messed up the ramps at Lewis in this edit...use change:lanes=* and turn:lanes=* instead of mapping lane restrictions as seperate ways.

Looks like a sidewak leading from a driveway into a building.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/82325080

Please provide informative changeset comments and limit your area geographically.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/82311758

Not sure where you're getting a rounded corner out of a T intersection.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/82298552

This driveway, which is obviously a truck scale, goes through the truck scale wall??
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/82284884

For purposes of mapping in OSM, the gore location is the start of the neutral zone, not the start of the channelizing line. For the channelizing line, that's what the change:lanes=* tagging is for.

placement=transition
osm.wiki/Proposed_features/change

OK, apparently we're not on the same page here. Is it just the layer=* tags that are wrong or is there something else?

yes, I understand that. I'm starting to wonder if you know what splitting a way is? It takes one way, and creates two ways, so you can have different tags on different sections of road to describe what's going on...

Splits? Splitting a way leaves one way with the history and creates a new way. There's multiple changes in lane count, speed limit, advised speed, and more that would have necessitated splits.

It wasn't deleted and redrawn, it may have crept in from a join and retag since I'm not usually looking for or expecting layer=1, 0 or -1 in places where the layer=* tag isn't necessary because the implicit values for bridge=yes, tunnel=yes or an absence of both are sufficient.

The theoretical gore is where I placed the end of the transition on I 405. Sorry, can't use Google as a citation for map data, not only are they usually wrong, they're also copyrighted and using it would be a copyright violation.

The theoretical gore does NOT start at the end of the solid line as you're suggesting. The solid line is why the segment has a change:lanes=no|not_left|yes|... tag. If Tesla isn't able to handle that, then the problem isn't that it's not mapped accurately, it's that Tesla is not correctly interpreting the data.

OK, that's not where the ramp should start. The ramp should start where the painted gore starts. That's handled by the change:lanes tag. See way/781574733

Adding turn lanes for direction confirmation arrows on offramps aren't useful, it's the actual function of the lanes that is.

Please keep an eye out for placement tags, which provide a hint where the line needs to go. This edit resulted in lanes on the ramp being shifted about half a lane right of where they're actually located.

Please keep an eye out for lane and placement tags, as this will affect where the line itself needs to be placed. You moved all the lanes on this ramp out of alignment to the right.

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

name is not ref, don't use refs in the name tag. You also added embankment tags where they don't apply, and extended turn lanes past their exits. This edit makes very little sense.