Hi jleedev,
My name is Ravinder & I am a mapper on the OSM team at Lyft. Many thanks for letting me know about the official data of the construction project & reverting the edits. To explain my changes: according to Lyft-owned street-level imagery (https://drive.google.com/file/d/1KRfLLpN2otsJLEDXUVcOULqJadwGcVuo/view?usp=sharing) from 20th January 2026, I didn’t see any closures, and Exit 73 appeared open to general traffic. Based on that, I adjusted the junction node to its actual location. The intention behind these edits was to improve traffic safety.
I acknowledge that construction ways (way/1467627714#map=17/40.613601/-80.095620&layers=P & way/1467627715) should not be removed from the database till the completion. I apologize for any inconvenience these edits may have caused & I’ll be more cautious with future changesets.

Happy Mapping!
Regards,
Ravinder

Hi keithonearth,
My name is Ravinder and I'm a mapper on the OSM team at Lyft. Thanks for fixing the 8th and Quebec re-routing — much appreciated. Regarding my edits, they were made based on Lyft-owned aerial imagery and telemetry data but now I see that these sources are outdated for this location & Lyft-owned street level evidence is showing some kind of construction work. I agree that local knowledge is often more reliable in such cases. I sincerely apologize for any inconvenience caused, and I’ll be more cautious going forward.
I’ll also make sure to share this with the rest of the team.

Thank you for your contribution to the OSM.

Regards,
Ravinder

Hi salisburymistake,
My name is Ravinder and I'm a mapper on the OSM team at Lyft. Thank you so much for correcting the mistake & reverting the edits. Regarding my edits: I updated the way (way/1463713727) based on Lyft-owned telemetry data and aerial imagery. Unfortunately, the imagery I referenced was outdated (March 2025), and I did not review the note in the OSM history beforehand.
I sincerely apologize for any inconvenience this may have caused. I will be more diligent with future changesets.
Thank you for your contribution.

Regards,
Ravinder

Hi ratrun,
My name is Ravinder, and I’m a mapper on the OSM team at Lyft. Thank you very much for your feedback. While adding ways in this area, I didn’t notice the existing construction ways, as construction features were disabled at the time. As a result, I mapped the ways over them.
Now I’ve corrected this in the following changeset: changeset/177549402#map=19/51.040615/-113.847357&layers=N.
I sincerely apologize for any inconvenience these edits may have caused, and I’ll be more careful when submitting future changesets.

Thank you for your contribution to OSM!

Regards,
Ravinder

Hi draconic_mapper,
My name is Ravinder and I am the mapper on the OSM team at Lyft. I appreciate your insights. It appears that the section of Rue Jeanne-Mance west of the barrier remains inaccessible but according to Lyft track data (https://drive.google.com/file/d/1pdK6J7KO84f81WJGiiDlGu9j8BdGPBMr/view?usp=sharing) and Lyft-owned street level imagery (https://drive.google.com/file/d/1fCKpunBhNCP8dTj0Y_dFTUBPqIiBSiSN/view?usp=sharing) from September 19, 2025, show a “straight only” sign that actually functions as a one-way indicator. This observation is verified through way (way/794905835#map=19/45.508169/-73.567404&layers=N) and images (https://drive.google.com/file/d/1VeTJp9h6xPDFbc6WGbCw3Vwtpzk8AXjl/view?usp=sharing) from October 29, 2025. Collectively, this confirms the area’s one-way designation, which seems to allow access only sometimes to authorized vehicles west of the barrier.

Please let me know if you have any additional questions. Thank you for your contribution.

The screenshot will be available for a month, please let me know if you are unable to view them within this time frame - I could generate them once again.

Happy Mapping!

Best Regards,
Ravinder

Hi JuanElDemografo !
I am not entirely sure if I understood your question. In this changeset. I have added a way through the building because as per bing imagery we clearly see the arrow, which passes through the building and having physical barrier too, near location 30.21439, -93.25054. Could you please clarify what exactly needs to be corrected here?
Best regards, Ravinder

Hi, Stretch Longfellow!
My name is Ravinder, and I’m a mapper in the OSM team at Lyft.

I left one road (https://pewu.github.io/osm-history/#/way/660070833) with the driveway tag because it was already mapped as a driveway. I added the other roads without the driveway tag as according to background imagery & Mapillary imagery (https://www.mapillary.com/app/?pKey=2955600471281836&focus=photo&lat=40.847459473418&lng=-96.738368359494&z=17&x=0.7860515793724374&y=0.5180032806745453&zoom=1.2949640287769784), building (way/198253092) is related to logistics, so I don’t think that driveway should be there. The driveway was later removed by Easy_pete (https://osmcha.org/changesets/169263153). I notice that you have already added driveway tags across the entire area. While this does not align with our mapping policy, we understand that there are different approaches within OSM. I would appreciate it if you could share your thoughts on this matter. Anyway, thank you for your contribution to OSM!

Best regards, Ravinder

Hi, j0hn33y!
My name is Ravinder, and I’m a mapper in the OSM team at Lyft. I sincerely apologize for overlooking your comment on my edits. Thank you for promptly removing the roads that I mistakenly added to the demolished area and for supporting your correction with an article. I appreciate your contribution to OSM.

Best regards, Ravinder

Hi, Mashin!
My name is Ravinder, and I’m a mapper in the OSM team at Lyft. I sincerely apologize for overlooking your comment on my edits. I appreciate your commitment to ensuring the accuracy of the map and understand the reasons behind reversing our changes. At the same time we utilize Lyft-owned sources, which are often more up-to-date than what is available in OSM. You can read more about this here: https://github.com/Test-DCT/OSM-LYFT-DCT/blob/1beae15649f43e0bef043fc0ef3950d7cbfdc867/osmtrainingmaterialsfeatures/Lyft-owned%20sources%20(ex.%20proprietary%20sources).md.
Regarding this case, Lyft-owned aerial imagery from April 2025 (https://drive.google.com/file/d/1ZNXXg03SQS8tdbYeffaoAcM64IhELIaq/view?usp=drive_link), along with telemetry data from the past week https://drive.google.com/file/d/1igzHsB7Fs9voTaJQQkMUhN10GCr8yatW/view?usp=drive_link, indicates that the motorway link should be removed.
I hope you won't mind if I reinstate my edits.

Best regards, Ravinder

Hi, MikeN!
My name is Ravinder, and I’m a mapper in the OSM team at Lyft. I apologize for adding new roads over the existing construction roads, and would like to assure you that I am taking steps to prevent similar mistakes from happening in the future.
Thank you very much for bringing it to my attention and correcting my edits.

Best regards, Ravinder