Hello ChaireMobiliteKaligraphy,
Thank you for the correction and for bringing this to my attention. I'm Ankit, a mapper on the OSM team at Lyft. My changes were based on the available background imagery and ground truth images. Based on the evidence, I believed the physical obstruction began a little further ahead, so I updated the geometry to better match the actual road layout. After reviewing your correction, I realized that my edits unintentionally impacted the placement tags.
I sincerely apologize for this oversight and truly appreciate you taking the time to fix it. Your feedback is very helpful, and I'll be more mindful of similar situations in future changesets. Thanks again!
Ankit

Hello deneben,
Thank you for reaching out, and thank you for your contributions to OSM. My name is Ankit, and I am a mapper on the OSM team at Lyft.
Regarding my edits, I originally added a square-shaped road based on ESRI World Imagery (https://drive.google.com/file/d/1g02fVxOfWk6Za_9-x29-62X_d4HrQAZ1/view?usp=sharing). However, the imagery was outdated, and several parked vehicles in the center of the area led me to incorrectly interpret it as a square parking lot. After reviewing more recent imagery, I could not identify any structured parking spaces or any painted lines as you said.
I sincerely apologize for this oversight and for any confusion or inconvenience my edits may have caused.
Now I have updated the geometry in this changeset (changeset/184042639) and retained a single way leading to a parking aisle, as active vehicle movement in the area was confirmed through Lyft GPS tracks (https://drive.google.com/file/d/1q3yqTTMmJfxNLy9PMgR07Tch1NDz5dX3/view?usp=sharing).
Regards,
Ankit

Hello Pizza TreeIsland,
My name is Ankit, and I work as a mapper on Lyft’s OSM team. Thank you for highlighting this! I have aligned the roads with the roof structure based on the OSM wiki guidance, which states that ways passing through covered areas may share nodes with the building boundary at entry and exit points.
Reference: OSM Wiki – Key:covered(covered=*#:~:text=Ways%20passing%20through,blind%20arcades.)

I hope this helps explain the reasoning behind my edits.This has been fixed once more in the following changeset: changeset/182365331

Best regards,
Ankit

Hello Pizza TreeIsland,
My name is Ankit, and I work as a mapper on Lyft’s OSM team. Thank you for highlighting this! I have aligned the roads with the roof structure based on the OSM wiki guidance, which states that ways passing through covered areas may share nodes with the building boundary at entry and exit points.
Reference: OSM Wiki – Key:covered(covered=*#:~:text=Ways%20passing%20through,blind%20arcades.)

I hope this helps explain the reasoning behind my edits.This has been fixed once more in the following changeset: changeset/182365331

Best regards,
Ankit

Hi jm428,

My name is Ankit & I am a mapper on the OSM team at Lyft. Thank you for letting me know about the duplicate entries and for removing them. I was in the process of adding a way when a technical glitch on our side caused it to be captured three times in separate changesets. I sincerely apologize for the oversight and will be more careful with my future mapping changesets.

Regards,
Ankit

Hi Baloo Uriza,

My name is Ankit, and I’m a mapper in the OSM team at Lyft. Regarding my edits, I realigned the roads using Lyft-owned aerial imagery from July 2025 and Lyft-owned telemetry data (https://drive.google.com/file/d/1pdK6J7KO84f81WJGiiDlGu9j8BdGPBMr/view?usp=sharing) collected one week ago.
With the Lyft owned street-level imagery (https://drive.google.com/file/d/1lztsTaUsUWgpYTZgCL5BSzgaNxxtazqz/view?usp=sharing) from January 15, 2026 now available on both sides, right now I’ve added the street names and made other necessary changes in the following changeset: (way/14926273).
I hope this clarifies my edits. The screenshots will be available for a month. Please let me know if you are unable to view them within this timeframe – I could generate them once again.

Regards,
Ankit

Hi Roydon Olive,
My name is Ankit, and I’m a mapper in the OSM team at Lyft. Thank you so much for paying attention to this. I apologized for removing half of the proposed road. Definitely it shouldn’t be removed from there, as it could be mapped in the future.
I have corrected my mistake & restored half of the proposed road in this changeset (way/1244266677#map=17/49.818901/-97.075328&layers=N). I apologize for any inconvenience these edits may have caused. I’ll be more cautious when pushing changesets up. Thank you so much for your contribution.
Happy mapping!!

Best Regards,
Ankit