Hello dknelson9876,
Thank you for reaching out. My name is Santoshi, and I'm a mapper with Lyft's OSM team.
I extended the road geometry based on a small amount of GPS tracks that crossed the intersection and relied on older background imagery. Unfortunately, I overlooked the edit history of the road ways. After reviewing the article you shared, I agree that the crossing has been indefinitely closed. I sincerely apologize for my edits and for any inconvenience they may have caused, I’ll take care when pushing future changesets up.
My teammate has now reverted the changes in the following changeset:
changeset/186902945#map=19/40.764820/-111.936562&layers=N
Thank you for your valuable contributions to OSM!
Santoshi

Hello dknelson9876,
Thank you for reaching out. My name is Santoshi, and I'm a mapper with Lyft's OSM team.
I extended the road geometry based on a small amount of GPS tracks that crossed the intersection and relied on older background imagery. Unfortunately, I overlooked the edit history of the road ways. After reviewing the article you shared, I agree that the crossing has been indefinitely closed. I sincerely apologize for my edits and for any inconvenience they may have caused, I’ll take care when pushing future changesets up.
My teammate has now reverted the changes in the following changeset:
changeset/186902945#map=19/40.764820/-111.936562&layers=N
Thank you for your valuable contributions to OSM!
Santoshi

Hi ljb_nj,
Thank you for reaching out. My name is Santoshi, and I am a mapper with Lyft's OSM team.
I mapped this way as a service road based on active Lyft track data and Bing imagery. Since I did not observe any private property or "No Trespassing" signage at the parking lot entrance or exit, I did not add an access=private tag. We typically apply that tag only when there is clear signage indicating restricted access.
Regarding the service=driveway tag, I chose not to use it because that tag is generally intended for ways that provide direct access to a residence, garage, house, business, or a small number of parking spaces. Although the parking area belongs to Seaview Dental, the size and layout of the lot suggest a large parking lot rather than a driveway in the conventional OSM sense. For that reason, I retained the existing service road classification without adding service=driveway.
I hope this clarifies the reasoning behind my edits.
Regards,
Santoshi

Hi silversurfer83,
My name is Santoshi, and I’m a mapper on the OSM team at Lyft. Thank you for your attention. Regarding my edits, I created the following ways (way/1472717033#map=19/41.771445/-71.353592&layers=P and way/1472717034) using Lyft-owned aerial and street-level imagery. Due to the presence of a physical divider, drivers can enter through the ways, and there is adequate space for vehicle movement.The attached images (https://drive.google.com/file/d/1Gd20lGfqYDQrbxk6Y_Xvfqa-Tk-fvzee/view?usp=sharing & https://drive.google.com/file/d/1wZoaYXD_3X-BzSfIwZv9mokdtPwQZBaT/view?usp=sharing) support this. I hope this explains the rationale behind my edits.

Regards,
Santoshi

Hi Baloo Uriza,
My name is Santoshi, and I’m a mapper on the OSM team at Lyft.
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,
Santoshi

Hi Allison P,

My name is Santoshi, and I am a mapper on the OSM team at Lyft. Thank you so much for paying attention & fixing my mistake! Agree with you that these roads are shared driveways.
Please accept my apologies & I’ll be more cautious when pushing changesets up.

Regards,
Santoshi

Hi,Roydon Olive!
My name is Santoshi, and I am a mapper on the OSM team at Lyft. Thank you for bringing this issue to my attention. I apologize for the mistake — you are correct that roads should not be mapped in this area. I reviewed the latest Lyft-owned street-level imagery as of 20/11/2025 https://drive.google.com/file/d/1cAgTE3BZfj8TH4sjcSdV04UXwaVex4ti/view?usp=sharing and it confirms that there is a temporary building and some construction equipment present. we do have some telemetry data in this area, but it is better to wait until the construction is completed before making any updates. https://drive.google.com/file/d/1m43hmKKRCtiFC9l6z-JOtYGKD99yqttv/view?usp=sharing
I have removed the roads in the following changeset: changeset/175060148#map=18/49.830373/-97.157623&layers=N Thank you again for your helpful comment.
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,
Santoshi