Feed expiration

If your feed is going to expire soon, we will send you email notifications so that you can upload a new feed with extended service coverage. To ensure that you receive these emails, access the Transit Partner Dashboard and configure your notifications.

Determine when a feed expires

In order to determine how long a feed is valid and when it expires, instead of considering the latest end_date defined the in calendar.txt file, we calculate the latest date the majority of trips are valid. If a feed has inconsistent service end dates, this prevents loss of coverage when certain services are no longer valid.

The majority of services in this feed expire within 60 days. Feeds must include the current date along with dates in the near future to avoid gaps in service for feed consumers.

In some cases like a seasonal service, the majority end date may not reflect correctly how long the feed is valid. Services can end before the latest service end date and should not be extended automatically. To control the automatic extension, define a feed_start_date and feed_end_date in the feed_info.txt file. The feed_end_date will replace the end date of the majority of trips to determine the feed's validity.

Don't define a feed_end_date later than the end of valid service information defined in the calendar.txt file unless there are no services available between these dates. The same applies if your feed_start_date is earlier than the start of valid service information as defined in the calendar.txt file.

Extending feed expiration date

When a feed has expired, Google automatically extends the services, assuming most schedules continue following the same pattern. Services that end much earlier than the majority end date are not extended. 

If you encounter unexpected routing results that may be caused by automatic extension, please contact us.


The following example shows a feed with 5 winter-only routes and 1 route that operates the whole year.

Latest start_date in calendar.txt 20151001
Latest end_date in calendar.txt 20160430
Computed majority start date 20151101
Computed majority end date 20160331
Feed_start_date in feed_info.txt 20151001
Feed_end_date in feed_info.txt 20160430

With the above configuration, Google shows that the winter routes will not operate after 2016-03-31. Without the feed_end_date setting, the winter routes would have been extended to operate until 2016-04-30.

Was this helpful?
How can we improve it?