Update your feed data
If you've set up your General Transit Feed Specification (GTFS) feed for automatic updates, it will update at the specified time if your feed data has changed. We recommend setting your feed to automatically update once per day. You can also request at any time that Google immediately fetch the latest version of your feed.
When a feed expires or schedules change, you must upload a new feed with extended service coverage and/or updated schedules. In the case of an upcoming feed expiration, we will send you multiple notifications. Please make sure that your notifications are configured properly in the Transit Partner Dashboard so you don’t miss this information.
When updating your feed data, there are a few rules you must follow in order to ensure that your feed continues to function properly:
New feed file: To change or update your feed, replace the old google_transit.zip with a new google_transit.zip.
Don’t change the name of the file - overwrite the existing file instead.
Ensure that the new feed has complete data as of the posting date.
- Coverage gaps: To guarantee a seamless transition, make sure that when you update your feed there is no gap between the service periods of the new feed and the old feed. For example, if the time period covered by the previous version of the feed ends with March 1, then the new updated version must not begin later than March 2.
- Merging feed versions: It’s no longer necessary to merge different versions of your feed to ensure seamless feed service, and we recommend that you avoid doing so.
Your new feed is usually live within 2-3 days.
To help ensure your new schedule is live on time, upload the new schedule a week prior to the start date.