Static GTFS feed Versions
Feed versions represent a specific static GTFS archive that was published at a particular point in time by a source feed.
Transitland calculates metadata about each feed version's contents, as well as importing the GTFS entities within the feed version. Metadata includes service levels over the duration of the feed, summaries of included CSV files, a convex hull geometry that contains all stops, etc.
Each feed version is accessed and referenced using the SHA1 checksum of the GTFS archive.
The static GTFS URL for each feed is checked approximately once per hour, and a new feed version is created any time new data is observed. New feed versions are given the SHA1 checksum value of the entire GTFS Zip archive.
Data is considered new if the total checksum of the individual GTFS CSV files, processed in alphabetical order, has not been observed previously. Checking for uniqueness in individual file content avoids the common situation where timestamps or other non-GTFS files inside the archive change but the GTFS CSV data itself has not been updated.
Each feed has at most one active feed version, selected as the best feed version for the current day. In most cases it will be the most recently fetched feed version, unless that feed version only contains service for dates in the future. Requests to other endpoints, such as map tiles, routes, stops, etc., will use data from this feed version unless another version is explicitly specified using the
Users may download static GTFS feed versions from the Transitland archives under the following conditions:
- The feed's license metadata cannot explicitly disallow redistribution.
- If the feed version is the most recent version, all users may download it from the REST API feed endpoint.
- If the feed version is a historic version (not the most recent version), users must be on a paid Transitland Professional plan, a paid Transitland Enterprise plan, or a complementary Hobbyist/Academic plan to download it using the REST API feed versions endpoint.