Thank you for your help!

Hi WilliamHarrison,
My name is Melaniya, and I'm a mapper on the OSM team at Lyft.

Could you verify the accuracy of the turn restriction relation/19258814 (relation/19258814)? It appears that after the removal of a slip road, way/1434966835 (way/1434966835) is inaccessible due to this turn restriction. On Mapillary (https://www.mapillary.com/app/?pKey=24388736367474565&focus=photo&lat=41.3809222&lng=2.1418528&z=17) from August 2025, this turn isn’t prohibited. If the information is outdated, could you please update it?

Best regards,
Melaniya

Hi MacLondon,
My name is Melaniya, and I'm a mapper on the OSM team at Lyft.

In your changeset, you marked way/315269000 (way/315269000) as was:highway, which was the only way for buses and taxis to get to way/1434966835 (way/1434966835) due to this turn restriction relation/19258814 (relation/19258814).

Could you please verify if this turn restriction relation/19258814 is up-to-date? On Mapillary (https://www.mapillary.com/app/?pKey=24388736367474565&focus=photo&lat=41.3809222&lng=2.1418528&z=17&x=0.50385334802273&y=0.47767490716932154&zoom=0) from August 2025, the turn from way/129216259 to way/1434966835 isn’t prohibited.

Best regards,
Melaniya

Hi Dannmer,

My name is Melaniya, and I'm a mapper on the OSM team at Lyft. Thank you for your feedback. The road way/123622065 (way/123622065 ) is no longer under construction, according to our ground truth imagery from April 14th at 30.41875, -84.35093 (https://drive.google.com/file/d/14S_NwAzUbOmwaiZtOXFxtRJDypPeqL29/view?usp=sharing) and telemetry data from last week (https://drive.google.com/file/d/1OFWYGudQg6hN5p_7DGjcntTA2CjDPfe2/view?usp=sharing ). Since our last edits (changeset changeset/163182305#map=14/30.41306/-84.34617&layers=N ), traffic has shifted from way/123622072 to way/123622065, so I updated the construction tags accordingly. However, I mistakenly forgot to remove the construction tag. I apologize for this. Thank you for pointing out this oversight. I have corrected it in the next changeset: changeset/170109530 .

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.

Best regards,
Melaniya

Hi Udar,

My name is Melaniya, and I'm a mapper on the OSM team at Lyft. Thank you for your feedback. Currently, we don't have up-to-date street-level imagery for this bridge, which made it challenging to determine the correct geometry, so I refrained from adding new roads there. However, upon revisiting the website, I found evidence that these roads will indeed be present, and we have active telemetry on them. Thank you for pointing this out. Your edits are correct, and I have now corrected the lanes tags based on Nearmap imagery https://drive.google.com/file/d/1iEsmuZkTU_Wz-r1xyHyzBDCFUne3njoF/view?usp=sharing , https://drive.google.com/file/d/1_87exSia883Z4D83jDSFyFmz3uEUHrNV/view?usp=sharing
and the website https://okeechobeeprojectmap.com/. You can view the changes in this changeset: changeset/170109322

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.

Best,
Melaniya

Hi Baloo Uriza,

My name is Melaniya, and I'm a mapper on the OSM team at Lyft. Thank you for your feedback. At the time of my initial edits, there was no up-to-date street-level imagery available to accurately modify the turn:lanes tags. Given the changes in the road's geometry, the existing turn:lanes tag was no longer applicable, so I removed it. With the availability of new street-level imagery:

https://drive.google.com/file/d/1PGX9xFpaCoKYI6ETSR5F4Se3UqsB818O/view?usp=sharing
https://drive.google.com/file/d/1jwsZT8rNA6NGK5iFinpN4qn2xRsC2Wl4/view?usp=sharing

I have now corrected the lanes tag: changeset/169726062

Best,
Melaniya

Hi Udar,

My name is Melaniya, and I'm a mapper on the OSM team at Lyft. Thank you for bringing this to my attention. I apologize for the oversight regarding the road's geometry. I had initially planned to correct this in the next changeset, but I didn't mention it in my previous comment. The geometry has now been corrected: changeset/169667075

Best regards,
Melaniya