Hi Artem, Thank you for the reply. 

The oneway tag here has been reverted back and forth four to five times now. I see that lyft has had to come back to fix it more than once. I think there may be automated QA tools that are flagging it and causing drive by contributors to change it back to oneway.

I will solicit additional feedback from community on proposed change to ensure it is the optimal approach and best way to map this intersection. I’ll also see if I can confirm my suspicion about QA tool and if this needs to be raised with the maintainer of said tool. 

If the proposed solution changes and it appears that it might benefit from further solicitation of input from Lyft, I’ll follow up with another comment on this changeset.

Best regards. :)