Line 4, Sunset/Alvarado stop, showing crossed out times in Transit App

[matikin9]

Reported via this tweet, which shows crossed out times for Line 4 at Sunset / Alvarado, westbound towards Santa Monica, in the Transit App. No alert appears. This took place on at 4:45pm on 5/3/23.

Swiftly shows stop closures in effect at Sunset / Alvarado and Sunset / Rosemont, ending at 2pm.

IBI has two open alerts related to “Alvarado”: #12339 and #12350.

Looks like they both cover the same service adjustment but they have slightly different info:

• Effective period of 9am-4pm vs 9:30am-4pm
• Affected stops of Sunset/Alvarado (westbound) vs Sunset/Alvarado (westbound) and Sunset/Rosemont (eastbound)
• Effect period of 5/1-5/5 vs 5/3-5/5

None of that matches the service adjustment info in Swiftly which starts 4/27 and ends 5/4, starts at 9am and ends at 2pm.

12339 is a Stop Move alert with only Sunset / Alvarado (westbound) selected as an affected stop.

12350 is a Stop Move alert with Sunset / Alvarado (westbound) and for some reason Sunset / Rosemont (eastbound) selected as affected stops.

[matikin9]

This incident is a combination of a few things:

1. We can't set recurring time periods for service adjustments within Swiftly. It only allows the selection of a start date/time and an end date/time.
2. We're not associating the correct stops with the alert in IBI.

The result is that Transit App shows the correct information of an upcoming alert impacting the stop (shown in a grayed out box), but the times listed are shown as crossed out because the Swiflty data shows all service canceled at the stop for the entire period.