Now that I'm in front of an editor that visualizes lanes correctly (JOSM does this), I was able to fix it correctly.

Is South still the prefix?
---

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

Be sure to make sure you're not affecting lane tagging when changing ways like this.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/164321942

Restriction already implied by access=no on crossover.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/164461563

Turn restriction already implied by access=no on crossover.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/164492939

Turn restriction already implied by access=no on crossover.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/164492939

I'd also appreciate a more reasonable answer than the same template you've used as three other people now. Human intelligence is required here.

OK, now go back and look at your edit, and explain to me which lane is closed and which lane is a turn lane. I'm not sure if you don't know what a lane is or if you didn't care at all how geometry works, because you got all of it wrong.

In this case, it's not inconsistent with the wiki. The turn lanes apply to the ends of the way, if there's a split where the lanes don't apply for that direction, then turn:lanes is removed from the way where those no longer apply. There needs to be an intersection at the end of the way for the turn:lanes tag to be relevant or consumed correctly by existing software.

Thanks for the suggestion, we've tried that and it doesn't work. I recommend you at least use an editor that visualizes the changes you're making, trying to edit lanes in id is really only for GIS professionals and Lyft's skill level is more "first time editor that never learns".

Available street level imagery shows no such restriction, though it is older. Could you please provide the updated imagery?
---

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

This is a free turn back to the street so people inadvertently turning into the driveway or rejected at the gate aren't stuck at the gate.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/165397716

Not a necessary relation, the crossover is already tagged access=no.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/166200809

Turn lanes should be tagged for the node at the head of the way, there's no where to turn left at the end of the transition segment.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/166570935

There was no part of this changeset that's even close to being reflected on the ground. Please stop lane tagging, Lyft clearly has no comprehension on lanes.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/166593182

This appears to be some kind of barrier, not a gap.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/167482352

The way you have tagged this indicates that there's a right-turn-only lane into a driveway.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/167822286

The way you have tagged this indicates that there's a right-turn-only lane into a driveway.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/167822286

But what changed? Just the boundary?
---

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

What was this edit supposed to accomplish? It's not clear based off the changeset comment or what changed.
---

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