Hi justinsenemy,
My name is Santosh & I am a mapper on the OSM team at Lyft. Thank you so much for paying attention & correcting the mistake. I added some roads according to the old background & didn’t notice any closure & construction work there. Now, I agree with you that some kind of construction work is still ongoing.
Please accept my apologies for that & I’ll be more cautious in future.
Thank you for going forward and fixing my mistake.

Happy Mapping!
Regards,
Santosh

Hi ChaireMobiliteKaligrafy,

My name is Santosh & I am the mapper on the OSM team at Lyft.
Thank you very much for noticing the issue and correcting it. Regarding my edits: I removed the segment because there was no physical separation and converted it from dual to single carriageway, but I missed fixing the connection with restrictions. I completely agree with your correction. Please accept my apologies.
I apologize for any inconvenience my changes may have caused and will be more careful with future edits. Thanks again for taking the time to fix this.

Happy Mapping!
Regards,
Santosh

My name is Santosh and I’m a mapper in the OSM team at Lyft. I apologize for not considering the placement tag in this revision. Thank you for your timely correction. I appreciate your commitment to ensuring the accuracy of the map, and understand the reasons behind reversing our changes.
We take the OSM rules very seriously and collaborate with data providers strictly under legal terms, ensuring that we have all necessary licenses. In this case Nearmap provides us a license for imagery usage for OSM mapping purposes. You can read more about Lyft-owned data here: https://github.com/Test-DCT/OSM-LYFT-DCT/blob/1beae15649f43e0bef043fc0ef3950d7cbfdc867/osmtrainingmaterialsfeatures/Lyft-owned%20sources%20(ex.%20proprietary%20sources).md

Best regards,
Santosh

My name is Santosh and I’m a mapper in the OSM team at Lyft.
Many thanks for letting me know about the issue on turn:lanes added.
According to our approach we refer to the green signboard closest to the junction. The green sign board is visible in below street-level imagery which is freshest: https://drive.google.com/file/d/1XgpxsNTSnUf14Keejiium5ersr25xSAO/view. If there is a directional arrow indicating an exit, we use that to assign the turn as slight_right.
I will be grateful if you provide your thoughts on these edits.

Kindly let me know if you're unable to access the imagery link, and I will resend it.

Best regards,
Santosh

My name is Santosh, and I’m a mapper in the OSM team at Lyft.
Thank you for your message, and for catching this error! The lanes tags shouldn’t be modified here. I apologized for this mistake. I have reverted my edits in the changeset:changeset/172305783
I will exercise greater diligence when submitting changesets.

Best regards,
Santosh

Hi Buy_osmand!

My name is Santosh and I’m a mapper in the OSM team at Lyft.

Thank you very much for bringing this to our attention. I apologize for the conflicting information. We will take measures to prevent such situations in the future

Best regards, Santosh

Hi,ChaireMobiliteKaligrafy

My name is Santosh and I’m a mapper in the OSM team at Lyft.

Indeed, according to our data, this bypass is no longer in place. I apologize for overlooking the fact that this was a temporary bypass. We aim to implement long-term changes on the map (exceeding three months). However, it is not always possible to accurately determine the anticipated timeline for these changes. Thank you for promptly updating the transitions. We appreciate your contribution to OSM.

Best regards, Santosh

Hi mf8s003j,

My name is Santosh, and I'm a mapper on the OSM team at Lyft. Thank you for your comment.
Sorry for such a delayed response, there was some issue with comment notice on our side.
My edit was based on street-level data from February 2025, which shows a left-turn restriction sign present before the median.
https://drive.google.com/file/d/1GU3Bp83pa1iTX2VOBmu15BETGYeUEtb2/view?usp=sharing
If you have any more up-to-date information regarding this restriction, please feel free to update it accordingly.

Best regards,
Santosh

Hi keithonearth,

My name is Santosh, and I'm a mapper on the OSM team at Lyft. Thank you for your comment.
Sorry for such a delayed reaction, there was some issue with comment notice on our side.
We are grateful for the on ground confirmation of our edits. Happy mapping!

Best regards,
Santosh

Hi Baloo Uriza,

My name is Santosh, and I'm a mapper on the OSM team at Lyft. Thank you for your comment.
Our edit was based on recent street-level data from August 2024, which shows a U-turn sign present before the intersection.
https://drive.google.com/file/d/1SuOdgRZVzlSZacVucwBkK4o7a-E4cYs1/view?usp=sharing
If you have any more up-to-date information regarding this restriction, please feel free to update it accordingly.

Best regards,
Santosh

Hi, Baloo Uriza,

My name is Santosh, and I'm a mapper on the OSM team at Lyft. Thank you for your comment.
I'm not sure why you removed the edits of the lanes and turn lanes tags. This contradicts the rules outlined in the wiki regarding indication. According to the wiki (turn=*#:~:text=the%20first%20indication%20via%20road%20markings%2C%20signposts%20or%20similar%20indications), a split should occur where the lane count or turn:lanes conditions change. My edits were based on this approach, and the lanes and turn:lanes were edited appropriately.
Also, in navigation, turn:lanes guidance is used for particular destinations independently. If a driver from the main road wants to reach the parking through way/740160600, they receive lane guidance like - left|left|through|through|through|right, where the rightmost lane will be highlighted. Meantime if the driver decides to go to North Rockwell Avenue, they also receive the same guidance. So, in both cases, the driver receives correct lane guidance. However, according to your edits, the driver who wants to turn into the driveway sees incorrect lanes and turn lanes suggestions because the value 'left|none|none|none' is not relevant.

Could you please explain why you didn't follow the wiki guidelines and reverted the edits?

Best regards, Santosh

Hi, Baloo Uriza,

My name is Santosh, and I’m a mapper on the OSM team at Lyft. Thank you very much for bringing the unnecessary restriction to our attention and for removing the relation. We have informed our entire team about this case to prevent such mapping in the future. I apologize for any inconvenience caused by the edit.

Best regards, Santosh

Hi, ElliottPlack
My name is Santosh and I’m a mapper in the OSM team at Lyft.

In this changeset, I have added roads based on Lyft-owned satellite imagery (https://drive.google.com/file/d/1fwogtnBmIG1qD1HCAZnmgZ3IV57XY82-/view?usp=sharing) as part of the Missing Roads initiative (https://github.com/Test-DCT/OSM-LYFT-DCT/issues/27). It seems that the construction landuse (way/1310633877/history) can be removed here. I have done it and rectified the building within this changeset (https://osmcha.org/changesets/159791967). Please feel free to reach out if you have any further questions.

Best regards!