Difference between revisions of "Publicly-accessible public transportation data"
Jump to navigation
Jump to search
| (4 intermediate revisions by the same user not shown) | |||
| Line 74: | Line 74: | ||
| [http://www.takeets.com/ Edmonton Transit Service (ETS)] || Edmonton, AB || https://data.edmonton.ca/browse?category=Transit&utf8=%E2%9C%93 || [http://www.edmonton.ca/transportation/Web-version2.1-OpenDataAgreement.pdf Terms of Use] | | [http://www.takeets.com/ Edmonton Transit Service (ETS)] || Edmonton, AB || https://data.edmonton.ca/browse?category=Transit&utf8=%E2%9C%93 || [http://www.edmonton.ca/transportation/Web-version2.1-OpenDataAgreement.pdf Terms of Use] | ||
|- | |- | ||
| − | | [http://www.metro.net/ Los Angeles County Metro] || Los Angeles, CA || | + | | [http://www.metro.net/ Los Angeles County Metro] || Los Angeles, CA || https://developer.metro.net/gtfs-schedule-data/ || [http://developer.metro.net/policies/terms/ Terms and Conditions] |
|- | |- | ||
| [http://www.septa.org/ SEPTA] || Philadelphia, PA || http://www3.septa.org/developer/index.php || | | [http://www.septa.org/ SEPTA] || Philadelphia, PA || http://www3.septa.org/developer/index.php || | ||
| Line 152: | Line 152: | ||
| [http://www.taketrax.com/ Tehama Area Rural eXpress (TRAX)] || Tehama County, CA. Including Susanville Indian Rancheria Public Transportation Program between Redding, Red Bluff, and Susanville. || http://data.trilliumtransit.com/gtfs/tehama-ca-us/ || | | [http://www.taketrax.com/ Tehama Area Rural eXpress (TRAX)] || Tehama County, CA. Including Susanville Indian Rancheria Public Transportation Program between Redding, Red Bluff, and Susanville. || http://data.trilliumtransit.com/gtfs/tehama-ca-us/ || | ||
|- | |- | ||
| − | | [http://www.duluthtransit.com/ Duluth Transit] || Duluth, MN || | + | | [http://www.duluthtransit.com/ Duluth Transit] || Duluth, MN || https://www.duluthtransit.com/home/doing-business/developer-resources/ || |
|- | |- | ||
| [http://www.metlink.org.nz/google-transit-feed/ Metlink] || Wellington (New Zealand) || http://www.metlink.org.nz/customer-services/general-transit-feed-specification/ || | | [http://www.metlink.org.nz/google-transit-feed/ Metlink] || Wellington (New Zealand) || http://www.metlink.org.nz/customer-services/general-transit-feed-specification/ || | ||
| Line 824: | Line 824: | ||
|[https://www.mauicounty.gov/ Maui County] || Maui, HI || https://www.mauicounty.gov/Search?searchPhrase=google_transit.zip&pageNumber=1&perPage=10&departmentId=-1 || | |[https://www.mauicounty.gov/ Maui County] || Maui, HI || https://www.mauicounty.gov/Search?searchPhrase=google_transit.zip&pageNumber=1&perPage=10&departmentId=-1 || | ||
|- | |- | ||
| − | |[https://www.barcelonanord.cat/en/home | + | |[https://www.barcelonanord.cat/en/home/ Barcelona Nord] || Barcelona (Spain) || https://opendata-ajuntament.barcelona.cat/data/dataset/c46503e3-cec6-4032-894d-1063b7a365ee/resource/1c92542e-0346-4df5-9824-d7753ab02e33/download || |
| + | |- | ||
| + | |[https://go.parkcity.org Park City Transit] || Park City, UT || https://go.parkcity.org/infopoint/google_transit.zip || | ||
| + | |- | ||
| + | |[http://atd.lv ATD] || Latvia || https://data.gov.lv/dati/eng/dataset/atd-gtfs/resource/b0a020e4-1ee6-4e1a-9a94-63b1f8defd6d || | ||
|} | |} | ||
| Line 913: | Line 917: | ||
|- | |- | ||
|[https://amarillo.gov Amarillo City Transit] || Amarillo, TX || https://code.amarillo.gov/gtfs/gtfs.zip || GTFS Transit data || || | |[https://amarillo.gov Amarillo City Transit] || Amarillo, TX || https://code.amarillo.gov/gtfs/gtfs.zip || GTFS Transit data || || | ||
| + | |- | ||
| + | |[https://amarillo.gov Duluth Transit Authority] || Duluth, MN || https://www.duluthtransit.com/home/doing-business/developer-resources/ || jsone, Real-Time Data in GTFS-realtime Format || || | ||
|- | |- | ||
|} | |} | ||
Revision as of 18:27, 22 November 2019
Introduction
Spearheaded by a small group of transit agencies in the United States, public transportation operators started publishing their transportation network and schedule data in electronic form, accessible to the public through the Internet for bulk download in a Zip archive. The data format used in the publications is GTFS, which was incubated for this purpose. GTFS has become an industry standard for publishing transportation network and schedule data, as more and more agencies and operators followed the example that the initial group had set. The audience for the published data consists of software developers and web services such as Google, who use the data to provide content to their apps and web services. The following two lists contain references to the published data. The first list contains references to schedule and network data published in GTFS. The second list contains references to data feeds that are published in formats other than GTFS. It also includes references to dynamic data that contains next bus and train departure data and transit vehicle locations in "real time". Both lists include references to applicable terms and conditions or data licensing requirements as stated by the data publishers.
Resource for Multi-Agency Consolidated GTFS Feeds
As of September 2016, the U.S. Department of Transportation has published a National Transit Map with map-based views and access to raw GTFS data.
List of publicly-accessible public transportation data feeds: static data in the GTFS format
tThis is a list of references to public transportation data feeds that contain static data, and that are published by transit agencies and transit operators in the GTFS format. The feeds contain data about scheduled times, stop locations, route information and optionally fare information and route shape details over a scheduling period, which is defined in the feed. For the GTFS format specification, see the General Transit Feed Specification document. This list was originally maintained at Public Feeds wiki page on Google Transit Data Feed Google Code project
List of publicly-accessible public transportation data feeds: dynamic data and others
This is a list of references to static public transportation data published by transit agencies and transit operators in formats other than GTFS. It also includes dynamic data feeds in GTFS-realtime
| Agency | Area | Feed Location | Type | Format | Notes |
|---|---|---|---|---|---|
| TriMet | Portland, OR | http://developer.trimet.org/ws_docs/ | Real time departure predictions and vehicle locations | REST/XML | Registration for API key required |
| TriMet | Portland, OR | http://developer.trimet.org/GTFS.shtml | GTFS-realtime | GTFS-realtime | Terms of Use |
| BART | San Francisco Bay Area | http://api.bart.gov/docs/overview/index.aspx | Real time departure predictions, route and schedule information | REST/XML | Developer page |
| BART | San Francisco Bay Area | http://www.bart.gov/schedules/developers/gtfs-realtime.aspx | BART GTFS-Real Time | GTFS-realtime | Developer page |
| King County METRO | Seattle, WA | http://www.its.washington.edu/its_ws.html | Real time departure predictions | REST/XML | |
| L.A. Metro | Los Angeles, CA | [3] | Trip planner API, Real time departure predictions (buses) | REST/XML | Trip planner: Registration for API key required |
| Transport for NSW | New South Wales and Sydney (Australia) | https://tdx.131500.com.au | Network and schedule data | File set TransXChange | Registration required |
| CTA Bus | Chicago, IL | http://www.ctabustracker.com/bustime/APIDocument.jsp | Real time departure predictions and bus locations | REST/XML | Registration for API key required |
| SFMTA | San Francisco, CA | http://www.sfmta.com/cms/asite/nextmunidata.htm | Real time departure predictions and vehicle locations | REST/XML | |
| ytv | Helsinki Metro (Finland) | http://developer.reittiopas.fi/pages/en/home.php | Trip planner API | REST/XML | Registration required, non-commercial use (test and development) |
| Traveline NextBuses | England, Wales and Scotland | Scheduled and some real time departure predictions | REST/XML | Registration required, commercial license | |
| Traveline NextBuses | England, Wales and Scotland | Scheduled and some real time departure predictions | REST/XML | Registration required, commercial license | |
| MBTA/EOT | Boston, MA | http://www.eot.state.ma.us/developers | Real time departure predictions and bus locations | REST/XML | Bus, Subway and Commuter Rail |
| MBTA/EOT | Boston, MA | http://www.eot.state.ma.us/developers | Real-Time Data in GTFS-realtime Format | GTFS-realtime | License |
| WMATA | Washington, D.C. | http://developer.wmata.com/ | Real time departure predictions for Metro Rail and Bus | REST/XML | Registration for API key required |
| AC Transit | Alameda and Contra Costa Counties, CA | http://www.actransit.org/rider-info/nextbus-xml-data/ | Real time departure predictions and bus locations | REST/XML | 110 out of 175 routes |
| London Datastore | London (UK) | http://www.tfl.gov.uk/businessandpartners/syndication/16492.aspx | Various datasets and real time feeds | ||
| Toronto Transit Commission | Toronto, ON | NextBus Webservices | Real time departure predictions | REST/XML | |
| Various Universities | US | NextBus Webservices | Real time departure predictions | REST/XML | |
| DC Circulator, Charm City Circulator, US | Maryland, Virginia | NextBus Webservices | Real time departure predictions | REST/XML | |
| Portland Streetcar | Portland, OR | NextBus Webservices | Real time departure predictions | REST/XML | |
| MTA | New York, NY | [4] | Bus locations route B63 | REST/XML | |
| Triangle Transit | Chapel Hill, NC | NextBus Webservices | Real time departure predictions | REST/XML | |
| Dutch Railways (NS) | The Netherlands | [5] | Trip planning, station list, live departures, prices and service disruptions | REST/XML | |
| CUMTD | Champaign-Urbana, IL | [6] | Real time departure predictions | REST/XML | Terms of Use |
| MTC | San Francisco Bay Area, CA | [7] | Real time departure predictions | REST/XML | Terms and Conditions |
| CTA Customer Alerts | Chicago, IL | http://www.transitchicago.com/developers/alerts.aspx | Real time service messages | REST/XML | |
| CTA Train Tracker | Chicago, IL | http://www.transitchicago.com/developers/traintracker.aspx | Real time departure predictions | REST/XML | Registration for API key required |
| OTS | Oahu, HI | http://hea.thebus.org/api_info.asp | Real time departure predictions | REST/XML | Registration for API key required |
| PSTA | Pinellas County, FL | http://psta.net/developers/ridepsta_API.php | Real time departure predictions | REST/XML | Registration for API key required |
| MARTA | Atlanta, GA | http://www.itsmarta.com/marta-developer-resources.aspx | Real time departure predictions | REST/Json | |
| MTA | New York, NY | http://datamine.mta.info/ | Subway real-time data feeds (Beta) | GTFS-realtime | |
| UTA | Salt Lake City, UT | http://developer.rideuta.com/DeveloperResources/DataInstructions.aspx | Next bus and train times | REST/XML/SIRI | |
| OpenData.ch | Switzerland | http://transport.opendata.ch/ | Public timetable data | REST/JSON | |
| OC Transpo | Ottawa, ON | http://www.octranspo1.com/developers | Real time departure predictions | REST/XML | |
| Victorian Government | Victoria (Australia) | https://www.data.vic.gov.au/raw_data/ptv-timetable-api/6056 | Timetable API | REST/JSON | Documentation at http://stevage.github.io/PTV-API-doc/ |
| Transit Authority of River City | Louisville, KY | http://gtfsrealtime.ridetarc.org/ | Real-Time Data in GTFS-realtime Format | GTFS-realtime | |
| Metro Transit | Madison, WI | http://transitdata.cityofmadison.com/ | Real-Time Data in GTFS-realtime Format | GTFS-realtime | Terms of Use |
| CTTransit | Hartford, CT | http://www.cttransit.com/about/developers/realtimedata | Real-Time Data in GTFS-realtime Format | GTFS-realtime | |
| Amarillo City Transit | Amarillo, TX | https://code.amarillo.gov/gtfs/gtfs.zip | GTFS Transit data | ||
| Duluth Transit Authority | Duluth, MN | https://www.duluthtransit.com/home/doing-business/developer-resources/ | jsone, Real-Time Data in GTFS-realtime Format |