Hi carciofo,
My name is Shubham, and I’m Santosh’s teammate on the OpenStreetMap team at Lyft.

Thank you for reaching out and bringing this issue to our attention. After reviewing the edits again, we agree that this was a mistake on our side. We sincerely apologize for any inconvenience caused by our changes and will take extra care with future edits to avoid similar issues.
The issue has now been corrected by one of my teammates in this changeset: changeset/190761787. The correction was made using Lyft tracks, which show vehicle activity from the past two weeks. I've attached the supporting evidence of the active Lyft tracks below for reference- https://drive.google.com/file/d/1RDMsLXRUVSwjoo6EYC2lSxW411nJffcu/view?usp=sharing

Regards,
Shubham

Hello hoserab,
My name is Shubham and I’m Lalit’s teammate. We are mappers on the OSM team at Lyft.
Thank you for identifying this issue and removing the incorrect turn restriction. After reviewing the fleetview imagery again, I completely agree with you that the restriction was actually a "right turn only" restriction rather than a "no right turn" restriction. I also agree that mapping a right-turn-only restriction would not add any practical value since Macleod Trail is a one-way road.
I sincerely apologize for the mistake and my teammate will be more careful when reviewing and submitting future changesets. Thank you for helping maintain the accuracy and consistency of OpenStreetMap.

Regards,
Shubham

Hello Udarian,
Thanks a lot for reaching out. My name is Shubham and I’m Akshay’s teammate. We are mappers on the OSM team at Lyft.. The edits were made using Lyft’s aerial imagery (https://drive.google.com/file/d/1a12JvSce905x2X-nZA-82Jx8cqD31MzQ/view?usp=sharing) from Mar 2026 (https://drive.google.com/file/d/168ss5Mkhal-GWTIC37xmyP1bWYMMLG_s/view?usp=sharing), which is more recent than the available ESRI imagery. Based on this imagery, updated the roads and ensured the vertex density was accurate. I also identified some missing footways, which have now been corrected in this following changeset: way/1442910312
I hope this explains the reasoning behind the edits. If you have more recent data or local knowledge about the territory, please feel free to update or amend the changes accordingly.

Happy mapping!
Shubham

Hi Flap Slimy Outward,
My name is Shubham and I’m Ankit’s teammate. We are mappers on the OSM team at Lyft. Thank you for letting me know about the duplicate entries. I was in the process of adding a way when a technical glitch on our side caused it to be captured multiple times in separate changesets. I’ve removed the duplicate entries in this changeset (changeset/182047056#map=19/35.968297/-114.857954&layers=N)
I sincerely apologize for the oversight and will be more careful with my future mapping changesets.

Regards,
Shubham

Hi DFW-backyard7,
My name is Shubham and I’m Surander’s teammate. We are mappers on the OSM team at Lyft. Thanks a lot for bringing this to my attention and reverting the edits. I had added the service roads based on older aerial imagery and didn’t cross-check with the latest updates.You’re absolutely right—the area is still under construction, which I confirmed using Lyft’s street-level imagery (https://drive.google.com/file/d/1Ko2o569QDdvJaxQCyvEKPHwz7Q0JheOZ/view?usp=sharing) from April 2026.
Sorry for the oversight and any trouble caused, and thank you for your help in improving OSM!

Best Regards,
Shubham

Hi DFW-Backyard7,
My name is Shubham and I’m Surander’s teammate. We are mappers on the OSM team at Lyft. Many thanks for reviewing & reverting the edits. The service road on parking lots was added based on Bing imagery, which I now realize was outdated, and I missed signs of construction. After verifying with Lyft’s street-level imagery (https://drive.google.com/file/d/1mhQu4_0ft4ftqu1BSc3rX6NUHIsdBAml/view?usp=sharing) from April 2026, I agree the area is still under construction.
I apologize for the oversight and any inconvenience caused. I’ll be more careful with upcoming changesets.

Happy Mapping!!
Regards,
Shubham

Hi Spaghetti Monster,
Hi, I’m Shubham, Abhishek’s teammate on the OSM team at Lyft. Thank you for your feedback. Regarding my edits - I chose to add an implicit turn restriction instead of splitting the way into two, since the physical separation was short. And based on Osmwiki - the implicit key is typically used when a restriction arises not from explicit signage but from physical constraints that make a maneuver impractical, often inferred from road layout or driving norms.
However, I agree with you too that mapping it as a dual carriageway would have been more accurate. Apologies for the oversight and any issues caused.

Happy Mapping!
Regards,
Shubham

Hi Baloo Uriza,
Hi, I’m Shubham, Santoshi’s teammate on the OSM team at Lyft. Sorry for the delayed response & thank you very much for your insight and feedback. Regarding the edits, I added the roads based on the available evidence. After adding them, a warning appeared stating that “Bus route MetroLink Tulsa looks like a common feature with non-standard tags,” and I mistakenly clicked on “upgrade the tags” instead of ignoring the issue.
I sincerely apologize for this oversight & thank you so much for your time, feedback, and contributions to OpenStreetMap.

Happy Mapping!
Best regards,
Shubham

Hi ElliottPlack,
My name is Shubham, and I’m Amit’s teammate. We are mappers on the OSM team at Lyft. Thank you very much for your feedback. Based on Lyft-owned aerial imagery from November 2025 (linked here: https://drive.google.com/file/d/1DiRJPUjhOy1DAyHJkPVwDLK0isg5sfU-/view?usp=sharing), which we used for our edits, there is no circularized surface at the end of Villabrook Way. In line with the OSM wiki guidance (highway=turning_circle), I therefore did not add a turning circle tag to the node. But I understand that the functionality may be exactly the same as for typical turning circles.
I hope this clarifies my edits, and thank you for your contribution to OSM.

Happy Mapping!
Thanks,
Shubham

Hi justinsenemy,

My name is Shubham and I’m Ravinder’s teammate. We are mappers on the OSM team at Lyft.
Thank you for sharing your insights. Regarding my edits, they were made based on older aerial imagery, and at the time I did not observe any closures or active construction.
& yes,you are correct that construction work is currently ongoing. Please accept my apologies, and feel free to modify or revert our changes if needed.
Sorry for any inconvenience caused. I will be more cautious when submitting changesets in the future.

Regards,
Shubham

Hi, Udarian
My name is Shubham and I’m Ravinder’s teammate. We are mappers on the OSM team at Lyft.
Thank you for your feedback. Regarding my edits: I classified the way as residential because it appeared to be located at the front of the buildings. According to the OSM Wiki (service=alley), an alley (or alleyway) is typically a narrow highway=service road situated between properties, primarily used for accessing rear entrances, back gardens, fire exits, or storage areas. Since these roads are usually located at the back and this particular one seems to be in front, I chose residential. Unfortunately, I don’t have any street level imagery to confirm it. If you have street level sources or alternative sources, please feel free to amend our changes if necessary.
I apologize for that and for any inconvenience these edits may have caused.

Happy Mapping!

Best Regards,
Shubham

Hi, Udarian
My name is Shubham and I’m a mapper in the OSM team at Lyft. About my edits: The recent road I added is supported by Lyft-owned aerial imagery (https://drive.google.com/file/d/1N_bsXbrxEU537l_SPqjFZwZ8-S-u2OX3/view?usp=sharing) from May 2025 and Lyft-owned street-level imagery https://drive.google.com/file/d/1gp8xw_pw22oh0_e3ny3B_CzW7HlydLS9/view?usp=sharing) from December 2024. Both clearly depict an access point between the DoubleTree Hotel and the adjacent mall. If you have more recent or alternative sources, please feel free to amend our changes if necessary.
Happy Mapping!!

Best Regards,
Shubham

Hi, Sharp gift!
My name is Shubham and I’m mapper in the OSM team at Lyft.
I didn’t notice the ponds earlier—sorry for that. Corrected the issue: changeset/170603588. According to Lyft-owned aerial imagery from March 2025, these ponds no longer exist.

Best regards,
Shubham