Hi dknelson9876

My name is Oscar, and I'm a mapper in the OSM team at Lyft.
Thanks for catching that! Based on our ground truth imagery, aerial views, and telemetry, you're right:
North End (WB Herriman Rose Blvd): Left turns onto Towne Commons Drive are permitted. While our street-level Ground Truth imagery is from March 1, 2026 (so we can't visually confirm if construction signs/barriers are still up), our aerial photos and telemetry from two weeks ago show vehicles actively turning left here. Based on this recent traffic activity, I decided to open this link on the map.
(https://drive.google.com/file/d/1saarr2q2x-sfAS78tPwcRtOglWczHis1/view?usp=sharing)(https://drive.google.com/file/d/1hk0qpbqlQMKuwpZ92bD6hs5ATi-Od1gV/view?usp=sharing)
South End (EB 13400 S): a turn lane link exists from EB 13400 S onto Towne Commons Dr. However, since the latest data shows it isn't open yet, I've left it disconnected for now until traffic is officially using it. (https://drive.google.com/file/d/1-wiX_iBKdXRjDzkT33srNMSXNqOQieiF/view?usp=sharing)(https://drive.google.com/file/d/1SZeYljM18S2rEhC52uTd97d-gxOm2sAR/view?usp=sharing)

Best regards,
Oscar

Hi Udar,
Thanks a lot for confirming this and for sharing the link to the 2026 Miami-Dade imagery! That custom layer is super helpful to have right in iD.
Best regards and happy mapping,
Oscar

Hi devemporer,

My name is Oscar Medinilla, and I'm a mapper in the OSM team at Lyft.
Thanks for checking on this edit. You're right that standard Esri imagery doesn't match—it hasn't caught up with the recent construction/realignment here yet. We verified the shift on the ground using our updated internal imagery (from Feb 2026), ground-level photos (from Aug 2026), and aggregate telemetry data. Below I attached links to the aerial view, street level and telemetry matching.
(https://drive.google.com/file/d/10gq6arAe7FSvgiG4LYggSNPnkxB16JfK/view?usp=sharing)
(https://drive.google.com/file/d/1cLVL-3rWg7qiIFTe5nN4SRkjoSOC-WiV/view?usp=sharing)
(https://drive.google.com/file/d/12YEjjRR_ljuE4gCKll79J0pjpOvPEurg/view?usp=sharing)

Best regards Oscar

Hi in2itivity,

Thank you for bringing this to our attention, I apologize for any inconvenience my edits could have caused, and appreciate your edits to correct this. I made these edits based on available street level imagery from April 2025, so thank you for more up to date validation.

Best regards, Oscar Medinilla

Hi Baloo Uriza,

Our team’s objective is to maintain consistency with the documented OSM wiki guidelines and the consensus reached in previous community discussions.
As mentioned, we only apply specific turn values when we have verifiable evidence to support them, and we treat the placement tag as optional rather than mandatory, in line with current wiki standards. We will continue to follow these guidelines to ensure data integrity across our edits.

Best regards, Oscar Medinilla

Hi Baloo Uriza!

My name is Oscar Medinilla, and I'm a mapper in the OSM team at Lyft. As we mentioned in the forum discussion, we don't tag any specific turn key value if we don't have corresponding evidence for it. We proceed to follow the wiki guidelines if another approach is not approved and documented. (https://community.openstreetmap.org/t/consensus-regarding-lane-and-turn-lane-tagging-guidelines/133364)
Based on the wiki, the ‘placement’ tag is not mandatory when working with lanes and turn:lanes, so we don't add it as a new tag in our edits. However, we adjust the key if the geometry changes somehow influence the current key value.
Hope the comments above is clarifying my edits.

Best regards,
Oscar Medinilla

Unfortunately as for now these images that I shared are the only evidence that I have regarding possible construction, so I can hardly identify the geometry, extension and nature of it.

Best regards,
Oscar Medinilla

Following the OSM Wiki guidelines (highway=construction), we add any kind of construction tags only where we have confirmation from official sources that construction or repair works will be ongoing for more than 1 month. In this case, we didn't find any confirmation of that, so we will proceed with the edits mentioned in our previous response and add motor_vehicle=private to the missing segments based on the Lyft street level images. However, if you have any additional information about construction or believe that construction tags will be necessary in this case, you can add them on your own.

Best regards,
Oscar Medinilla

Hi, ChaireMobiliteKaligrafy!

My name is Oscar Medinilla, and I'm a mapper in the OSM team at Lyft. I appreciate your message and bringing this to my attention.

I have used Lyft-owned street-level imagery highlighted below as evidence to add the motor_vehicle=private tag to road way/169851110:
- 45.453284113666186, -73.74502748250961 Date: 2026-01-16 (https://drive.google.com/file/d/1CqYGQTgN5C1I0lr3aJs0uvS19Ui-75T7/view?usp=sharing)
- 45.45365971570624, -73.74480921775103 Date: 2025-12-14 (https://drive.google.com/file/d/1XmQIeaCya3l1DzvoywdqcbmZpWrwSW0s/view?usp=sharing)

Additionally, I used Lyft-owned telemetry, which does not show active passes on this road during the last two weeks (green color indicates the southeast direction) (https://drive.google.com/file/d/1fyztoNzuPBVFO3cz2G_6u9ELCq5eyyAH/view?usp=sharing).

However, I've reviewed the street-level imagery again to build a logical sequence. While the original edit only covered part of the road, the signage at 45.45436, -73.7454 clearly impacts the merging link and the subsequent ways:
Date: 2026-01-25 (https://drive.google.com/file/d/1r3gN3cpNA381iTB3YY_GSCBqy5xIJb-6/view?usp=sharing)

Since imagery from late 2025 through January 2026 and telemetry activity confirm these signs are actual, I plan to add the restriction to the entire impacted area for map accuracy. If you have any concerns regarding this or more up-to-date evidence, please share it with me

Best regards,
Oscar Medinilla

Hi, atticquilt!
My name is Oscar Medinilla and I’m a mapper in the OSM team at Lyft.
You are right, I apologize for any inconvenience caused by my edits. I really appreciate your help by bringing this mistake to our attention. Thank you for correcting my mistake, and I will be more attentive in the future.

Best regards, Oscar Medinilla

Hi, user_5359!
My name is Oscar Medinilla and I’m a mapper in the OSM team at Lyft.
You are right, I apologize for any inconvenience caused by my edits. I really appreciate your help by bringing this mistake to our attention.
I removed the non exist pond in this changeset (changeset/174967691)

Best regards, Oscar Medinilla