Skip to content

Latest commit

 

History

History
108 lines (101 loc) · 5.97 KB

README.md

File metadata and controls

108 lines (101 loc) · 5.97 KB

GRD-TRT-BUF-4I: Extract Microservice

Dependencies

  • OS: Ubuntu 20.04 LTS (Focal Fossa)
  • Language: Python 3.8
  • Web App: Flask 2.3.1
  • WSGI: Gunicorn (Latest)
  • Reverse Proxy: Nginx (Latest)

Requirements

GTFS Realtime API Keys:

  • New York, NY (MTA)
  • Washington DC (WMATA)
  • Los Angeles, CA & Miami, FL (Swiftly)
  • San Francisco, CA (MTC)
  • San Diego, CA (MTS)
  • Portland, OR (TriMet)
  • Phoenix, AZ (Valley Metro)
  • Montreal, QC (STM)
  • Vancouver, BC (TransLink)
  • Stockholm, Sweden (Trafiklab)
  • Dublin, Ireland (NTA)
  • Sydney, Australia (NSW)
  • Auckland, New Zealand (AT)
  • Christchurch, New Zealand (ECan)
  • Delhi, India (DTC)

Getting Started

  1. Obtain the required GTFS Realtime API Keys from the list in the Requirements section. The supporting links can be found below in the Support section.

  2. Using the .env.example file in the ./ext service folder, rename it to .env and create an environment variable for each API key as follows. This is a strict naming convention.

export API_KEY_NYC=
export API_KEY_DCA=
export API_KEY_LBM=  ## la and miami same key
export API_KEY_SFO=
export API_KEY_SAN=
export API_KEY_PDX=
export API_KEY_PHX=
export API_KEY_YUL=
export API_KEY_YVR=
export API_KEY_ARN=
export API_KEY_DUB_A=  ## requires toggling 
export API_KEY_DUB_B=  ## between two keys
export API_KEY_SYD=
export API_KEY_AKL=
export API_KEY_CHC=
export API_KEY_DEL=
  1. Build and execute the Docker container using the following command:
docker-compose up --build -d extract

Support

GTFS Realtime REST API endpoints are developed and maintained by the following transit agencies. This is where to obtain the GTFS Realtime API Keys.

  1. New York, NY (MTA): http://bt.mta.info/wiki/Developers/GTFSRt
  2. Philadelphia, PA (SEPTA): https://www3.septa.org/#/
  3. Washington, DC (WMATA): https://developer.wmata.com/docs/services/gtfs/operations/5cdc52139e0b4de98fdfd54a?
  4. Boston, MA (MBTA): https://www.mbta.com/developers/gtfs-realtime
  5. Pittsburgh, PA (PRT): https://www.rideprt.org/business-center/developer-resources/
  6. Los Angeles, CA (Metro): https://developer.metro.net/api/
  7. San Francisco Bay Area, CA (MTC): https://511.org/open-data/transit
  8. San Diego, CA (MTS): https://www.sdmts.com/business-center/app-developers/real-time-data
  9. Seattle, WA (King County Metro): https://kingcounty.gov/en/dept/metro/rider-tools/mobile-and-web-apps
  10. Sacramento, CA (SacRT): https://www.sacrt.com/schedules/gtfs.aspx
  11. Portland, OR (TriMet): https://developer.trimet.org/GTFS.shtml
  12. Atlanta, GA (MARTA): https://www.itsmarta.com/app-developer-resources.aspx
  13. Miami, FL (MDT): https://www.miamidade.gov/global/transportation/open-data-feeds.page
  14. Tampa, FL (HART): https://github.com/CUTR-at-USF/HART-GTFS-realtimeGenerator
  15. Louisville, KY (TARC): https://www.ridetarc.org/developers/
  16. Nashville, TN (Nashville MTA): https://www.wegotransit.com/contact-us/data-request-submission/
  17. Minneapolis-St. Paul, MN (Metro Transit): https://svc.metrotransit.org/
  18. St. Louis, MO (Metro Transit): https://www.metrostlouis.org/developer-resources/
  19. Madison, WI (Metro Transit): https://www.cityofmadison.com/metro/business/information-for-developers
  20. Columbus, OH (COTA): https://www.cota.com/data/
  21. Des Moines, IA (DART): https://www.ridedart.com/developer-resources
  22. Denver, CO (RTD): https://www.rtd-denver.com/open-records/open-spatial-information/real-time-feeds
  23. Phoenix, AZ (Valley Metro): https://www.phoenixopendata.com/dataset/general-transit-feed-specification
  24. San Antonio, TX (VIA Metro): https://www.viainfo.net/developers-resources/
  25. Austin, TX (CapMetro): https://data.texas.gov/Transportation/CapMetro-Vehicle-Positions-PB-File/eiei-9rpf/about_data
  26. Billings, MT (MET): https://www.billingsmt.gov/3042/MET
  27. Montreal, QC (STM): https://www.stm.info/en/about/developers
  28. York Region, ON (YRT): https://www.yrt.ca/en/about-us/open-data.aspx
  29. Hamilton, ON (HSR): https://open.hamilton.ca/documents/6eeccf172c824c2db0484aea54ed7fe4/about
  30. Halifax, NS (Halifax Transit): https://data-hrm.hub.arcgis.com/pages/open-data-downloads
  31. Thunder Bay, ON (Thunder Bay Transit): https://www.thunderbay.ca/en/city-services/developers---open-data.aspx
  32. Vancouver, BC (TransLink): https://www.translink.ca/about-us/doing-business-with-translink/app-developer-resources/gtfs/gtfs-realtime
  33. Calgary, AB (Calgary Transit): https://data.calgary.ca/Transportation-Transit/Calgary-Transit-Realtime-Trip-Updates-GTFS-RT/gs4m-mdc2/data
  34. Edmonton, AB (ETS): https://data.edmonton.ca/Transit/Real-Time-Vehicle-Position-GTFS-PB-File-/uyt2-vrrn/about_data
  35. Saskatoon, SK (Saskatoon Transit): https://transit.saskatoon.ca/about-us/open-data-saskatoon-transit
  36. Amsterdamn, Netherlands (OVapi): https://gtfs.ovapi.nl/nl/
  37. Stockholm, Sweden (SL): https://www.trafiklab.se/api/trafiklab-apis/gtfs-regional/realtime-specification/
  38. Helsinki, Finland (HSL): https://hsldevcom.github.io/gtfs_rt/
  39. Dublin, Ireland (National Transport Authority): https://developer.nationaltransport.ie/apis
  40. Rome, Italy (ATAC): https://romamobilita.it/it/tecnologie
  41. Warsaw, Poland (Miasto Stołeczne Warszawa): https://mkuran.pl/gtfs/
  42. Krakow, Poland (ZTP Krakow): https://gtfs.ztp.krakow.pl/
  43. Gdansk, Poland (ZTM Gdańsk): https://ckan.multimediagdansk.pl/dataset/tristar/resource/976e1fd1-73d9-4237-b6ba-3c06004d1105?inner_span=True
  44. Prague, Czech Republic (PID): https://pid.cz/o-systemu/opendata/
  45. New South Wales, Australia (Transport for NSW): https://opendata.transport.nsw.gov.au/dataset/public-transport-realtime-vehicle-positions-v2
  46. Queensland, Australia (Translink): https://translink.com.au/about-translink/open-data/gtfs-rt
  47. Adelaide, Australia (Adelaide Metro): https://gtfs.adelaidemetro.com.au/
  48. Auckland, New Zealand (AT): https://dev-portal.at.govt.nz/realtime-api
  49. Christchurch, New Zealand (ECan): https://apidevelopers.metroinfo.co.nz/api-details#api=gtfs-realtime-service&operation=vehicle-positions
  50. Delhi, India (DTC): https://otd.delhi.gov.in/documentation/