Current and active Rider Alerts are published in an XML/RSS feed which can be accessed directly of through a feed reader, at: https://sanjoaquinrtd.com/rideralerts/RTDrideralerts.xml
Downloading RTD’s GTFS Feed
The most current version of RTD’s GTFS Feed can accessed here by downloading (see below) or via the address: https://sanjoaquinrtd.comRTD-GTFS/RTD-GTFS.zip
The General Transit Feed Specification is an open format that Google created to allow transit agencies to easily provide schedule data to Google Transit. However, Google encourages its use for other applications, and it’s available under a Creative Commons Attribution-ShareAlike (free) license.
Publicly available GTFS feeds
A number of transit agencies and operators have already published their schedule data in GTFS format for developers to use. GTFS Data Exchangeis a great resource showing which agencies have feeds available for use.
This section defines terms that are used throughout this document pertaining specifically to GTFS.
The field column must be included in your feed, and a value must be provided for each record. Some required fields permit an empty string as a value. To enter an empty string, just omit any text between the commas for that field. Note that 0 is interpreted as “a string of value 0″, and is not an empty string. Please see the field definition for details.
The field column may be omitted from your feed. If you choose to include an optional column, each record in your feed must have a value for that column. You may include an empty string as a value for records that do not have values for the column. Some optional fields permit an empty string as a value. To enter an empty string, just omit any text between the commas for that field. Note that 0 is interpreted as “a string of value 0″, and is not an empty string.
The field contains a value that maps to a single distinct entity within the column. For example, if a route is assigned the ID 1A, then no other route may use that route ID. However, you may assign the ID 1A to a location because locations are a different type of entity than routes.