API to expose alerts with effective dates in the future #2351
We have alerts in our GTFSrt feed with effective dates happening in the future. In fact, we have a includeFuture=true param (ala http://trimet.org/transweb/ws/V1/FeedSpecAlerts/includeFuture/true) that exposes all alerts current and upcoming service alerts. We'd like to (continue to) show those alerts in our trip itineraries, and not have them filtered by the OTP API. But the 1.0.0 API is filtering out any alert with an effective date happening in the future. NOTE: the behavior of the 0.10.x code we're currently using was to show any and all alerts, regardless of effective date.
Thus we're requesting some config parameter that will stop the API from filtering on effective date.
One idea: a config parameter with a numerical value representing minutes to look ahead when filtering the alerts that come back via an itinerary (say 'alertsEffectiveDateOffset':29999). The alert offset will then only filter those alert effective dates that happen beyond system-time + offset.
The text was updated successfully, but these errors were encountered: