Saturday, May 7, 2022

Feed expiration - Transit Partners Help [gg-transitpartners-en]

Feed expiration

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

Determine when a feed expires

The feed end date is based on the feed_end_date field in feed_info.txt. If the feed_end_date is not populated, but is close to its expiration date, we try to deduce the end date This helps prevent loss of coverage when certain services are no longer valid, in case the feed has inconsistent service end dates in calendar.txt.

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. This will cause a gap in coverage for that extra period. We may also reject the feed in this case, based on how big the loss or whether the previous version had coverage.

Extending auto-feed expiration date

When a feed expires, Google automatically extends the services, based on the assumption most schedules continue the same as before. Services that end at least a week earlier than the feed_end_date, or on the deduced end date if the feed_end_date is not present, aren't extended.

How to control auto extension

To control the automatic extension, define a feed_start_date and feed_end_date in the feed_info.txt file.

In some cases, like a seasonal service, the deduced majority end date may not correctly reflect how long the feed is valid. Services can end before the latest service end date and should not be automatically extended. If you have a seasonal service but don't want auto extension, we recommend you make your feed_end_date greater than 1 week after the service_end_date.

Important: If you encounter unexpected routing results because of an automatic extension, contact us.

Example

Example of a feed with 5 winter-only routes and 1 route that operates year round

routes.txt:

route_id,route_short_name,route_long_name,route_desc,route_type,route_color

1,,Winter Route,,3,

2,,Winter Route,,3,

3,,Winter Route,,3,

4,,Winter Route,,3,

5,,Winter Route,,3,

a,,Regular Route,,3,

calendar.txt:

service_id,monday,tuesday,wednesday,thursday,friday,saturday,sunday,start_date,end_date

1,1,1,1,1,1,1,1,20201001,20210430

1,1,1,1,1,1,1,1,20201101,20210331

2,1,1,1,1,1,1,1,20201101,20210331

3,1,1,1,1,1,1,1,20201101,20210331

4,1,1,1,1,1,1,1,20201101,20210331

5,1,1,1,1,1,1,1,20201101,20210331

This table summarizes the various start and end dates for this feed: 

Latest start_date in calendar.txt 20201001
Latest end_date in calendar.txt 20210430
Deduced start date 20201101
Deduced end date 20210331
Feed_start_date in feed_info.txt 20201001
Feed_end_date in feed_info.txt 20210430

With the above configuration, Google shows that the winter routes (1, 2, 3, 4, 5) won't operate after 2021-03-31. Without the feed_end_date, the deduced end date of 2021-03-31 is used and the winter routes are extended indefinitely. 

No comments:

Post a Comment

Search This Blog

Use a List view in an Access app [MS]

Use a List view in an Access app Access for Microsoft 365 Access 2021 ...