The General Transit Feed Specification (GTFS) is an Open Standard used to distribute relevant information about transit systems to riders. It allows public transit agencies to publish their transit data in a format that can be consumed by a wide variety of software applications.GTFS Schedule is a feed specification that defines a common format for static public transportation information. It is composed of a collection of simple files, mostly text files (.txt) that are contained in a single ZIP file.Each file describes a particular aspect of transit information such as stops, routes, trips, etc. At its most basic form, a GTFS Schedule dataset is composed of 7 files: agency.txt, routes.txt, trips.txt, stops.txt, stop_times.txt, calendar.txt and calendar_dates.txt.Along with this basic set of files, additional (optional) files can also be grouped to provide information of other service elements, such as fares, translations, transfers, in-station pathways, etc. Currently there are more than 15 optional files that extend the basic elements of GTFS, including locations.geojson which introduced a new format besides text files (.txt) which can be used to represent geographical areas.The source of truth for all GTFS Schedule files is the official GTFS Schedule Reference, which provides detailed information on the requirements for all information elements in each file that composes a GTFS Schedule dataset.

This item is a reference to the .zip file hosted on the city's website at: https://www.detroitmi.gov/Portals/0/docs/deptoftransportation/pdfs/ddot_gtfs.zip . Click that link or the "Open" link at top right to download the GTFS .zip file.You can find more information about GTFS here: https://developers.google.com/transit/gtfs/

The General Transit Feed Specification (GTFS) defines an open standard format for exchanging public transportation schedule, geographic and fare information. GTFS “feeds” let public transit agencies publish data in a format that can be consumed and utilized in applications in an interoperable way.Iowa DOT has taken this data and turned it into a more usable format.http://gtfs.org/

Public transit routes in San Diego County managed by the San Diego County Metropolitan Transit System (MTS) and the North County Transit District (NCTD). Bus, commuter and light rail, and trolley routes managed and developed from the General Transit Feed Specification (GTFS) data available from the transitland feed registry (formerly from GTFS Data Exchange). Routes are developed from the GTFS data available through the transitland feed registry (https://transit.land/feed-registry/), formerly from the GTFS Data Exchange. GTFS data is provided to the exchange by the transit agencies and processed by SanGIS to create a consolidated GIS layer containing routes from both systems. SanGIS uses a publicly available ESRI ArcToolbox tool to create the GIS data layer. The toolbox can be found at http://www.arcgis.com/home/item.html?id=14189102b795412a85bc5e1e09a0bafa. This data set is created using the ROUTES.txt and SHAPES.txt GTFS data files.Routes layers for MTS and NCTD are created separately and combined into a single layer using ArcGIS tools.

RTA Transit Stops refers to the geographical information about the stops of public transit systems operated by the Greater Cleveland Regional Transportation Authority (RTA) with data collected by GTFS. This data is representative of the location of transit stops along with information such as the route name(s), number of routes serves, as well as transit frequency (calculated by weekday AM and PM rush averages). This data can be used to analyze transit accessibility, travel time, and service coverage, and can also be combined with other data sources, such as demographic information, to support land use and transportation planning. The data can be displayed as line features on a map, with different symbols and colors used to distinguish different types of routes and level of transit frequency.GTFS (General Transit Feed Specification) transit data refers to a set of digital files that describe a public transit system's routes, stops, and schedules. When used in a Geographic Information System (GIS), GTFS data can be displayed as map layers that show the locations and connections of a transit system's stops, as well as the routes and schedules of its vehicles. These layers can be used to analyze transit accessibility, travel time, and service coverage, and can also be combined with other data sources to support land use and transportation planning.Data Sources:Mobility Database, GCRTA, GTFSESRI ArcGIS Pro Transit Analysis Tools (Used for mapping and modeling GTFS data)Current Vintage: 2023Update Frequency: Annually

Transit stops, routes and schedules in the standardized General Transit Feed Specification (GTFS) format for use by app developers. Updated quarterly if required.

Public transit stops in San Diego County serviced by the San Diego County Metropolitan Transit System (MTS) and the North County Transit District (NCTD). Bus, commuter and light rail, and trolley stops developed from the General Transit Feed Specification (GTFS) downloaded from https://www.sdmts.com/google_transit_files/google_transit.zip and http://www.gonctd.com/google_transit.zip.GTFS data is provided to the exchange by the transit agencies and processed by SanGIS to create a consolidated GIS layer containing stops for both MTS and NCTD systems. SanGIS uses built-in ArcGIS tools to develop the stops from the STOPS.txt data file.Stops layers for MTS and NCTD are created separately and combined into a single layer using ArcGIS tools.

Defines a common format for public transportation and associated geographic information. The feed is composed of a series of text files that each models a particular aspect of transit information: stops, routes, trips, and other schedule data. It also includes the shape of the lines of the routes.

This dataset describes the public transport networks of 27 cities across the world in multiple easy-to-use data formats. These data formats include network edge lists, temporal network event lists, SQLite databases, GeoJSON files, and General Transit Feed Specification (GTFS) compatible ZIP-files.

The original source data for creating these networks has been published by public transport agencies according to the GTFS data format. To produce the network data extracts for each city, the original data have been curated for errors, filtered spatially and temporally and augmented with walking distances between public transport stops using data from OpenStreetMap.

Cities included in this data set: Adelaide, Antofagasta, Athens, Belfast, Berlin, Bordeaux, Brisbane, Canberra, Detroit, Dublin, Grenoble, Helsinki, Kuopio, Lisbon, Luxembourg, Melbourne, Nantes, Palermo, Paris, Prague, Rennes, Rome, Sydney, Toulouse, Turku, Venice, and Winnipeg.

More detailed documentation of the data will be added once the accompanying data descriptor manuscript has been finalised.

Data has been obtained from the GTFS or General Transit Feed Specification. Data has been updated based on available GTFS as of May 2023.Bus stops downloaded as General Transit Feed Specification (GTFS) files. Transit operators in this data include, Yolo County Transit District, Sacramento Regional Transit District, Roseville Transit, City of Elk Grove, Folsom Stage Line, City of Davis' Unitrans, Placer County, El Dorado County, Yuba Sutter Transit, Tahoe Area Regional Transit, and Amtrak. Operators may change bus stops availability at any time, so stop locations may change. To check for more current information by jurisdiction, go to the individual transit website or https://sacregion511.org/#/. For more information about GTFS files https://gtfs.org/.Date operators transit stops updated within this data:El Dorado Transit 10/3/2022National Railroad Passenger Corporation 10/5/2021Placer County Transit 5/1/2023Sacramento Regional Transit District 3/1/2023SacRT Elk Grove Transit 4/18/2023SacRT Roseville Transit 6/7/2022SacRT South County Transit 11/22/2021Tahoe Area Regional Transit 5/3/2023Unitrans City of Davis 11/14/2022Yolo County Transportation District 1/24/2023Yuba-Sutter Transit 11/21/2022Field Info:Operator: is the transit operatorstop_name: is the name of the transit stopGTFS: The long name of the transit operatordate: the as-of date from the GTFS data or the date last updatedSACOG provides data as a public service. These data are provided "as-is." While every effort has been made to ensure the accuracy or correctness of these data, SACOG makes no warranty, expressed or implied, as to its accuracy or correctness and expressly disclaims liability for the accuracy thereof. In no event shall SACOG become liable to users of these data, or any other party, for any loss or damages, consequential or otherwise, including but not limited to time, money, or goodwill, arising from the use, operation or modification of the data. In using these data, users further agree to indemnify, defend, and hold harmless SACOG for any and all liability of any nature arising out of or resulting from the lack of accuracy or correctness of the data, or the use of the data. Users will not distribute these data to other potential users. Instead, they will refer those users to SACOG for an independent dataset and documentation. To assist SACOG in the maintenance of the data, users should provide SACOG's GIS staff information concerning errors or discrepancies found in using the data.

GTFS (General Transit Feed Specification) data is a standardized format for public transportation schedules and associated geographic information. It enables public transit agencies to publish their data in a format that can be easily used by developers to create applications that provide transit information to the public. For Somerset County, GTFS data can be utilized to improve the accessibility and usability of public transit information.Using GTFS data, riders can access real-time information on routes, schedules, and stops via apps and websites, improving their travel experience. Transit authorities can analyze service efficiency, identify gaps in service, and optimize routes and schedules based on passenger usage patterns. GTFS data can be integrated with other transportation data, such as bike-sharing systems, to offer comprehensive multimodal transport solutions.GTFS data comprises multiple text files collected in a ZIP archive. These files describe:Agency: Information about the transit agency.Routes: Details about the transit routes.Trips: Specific trips for each route.Stop Times: Timing information for each stop along the trips.Stops: Geographic locations of the stops.Calendar: Days of service for the routes.Calendar Dates: Exceptions for the regular service days.Shapes: Geographical shapes of the routes. **NOTE (07/17/2025): New feed is available. To view the current available routes, please reference PassioGo: Somerset County Transportation | Passio GO!

This layer shows all Montgomery County Ride On bus routes including all variations. The information was retrieved from January 2016 MCRO GTFS files. The GTFS file was converted to ArcGIS format by CMRT. This is a MD iMAP hosted service. Find more information on https://imap.maryland.gov.Feature Service Layer Link: https://mdgeodata.md.gov/imap/rest/services/Transportation/MD_LocalTransit/FeatureServer/

The National Transit Map - Stops dataset was compiled on September 02, 2025 from the Bureau of Transportation Statistics (BTS) and is part of the U.S. Department of Transportation (USDOT)/Bureau of Transportation Statistics (BTS) National Transportation Atlas Database (NTAD). The National Transit Map (NTM) is a nationwide catalog of fixed-guideway and fixed-route transit service in America. It is compiled using General Transit Feed Specification (GTFS) Schedule data. The NTM Stops dataset shows stops where vehicles pick up or drop off riders. This dataset uses the GTFS stops.txt file. The GTFS schedule format and structure documentation is available at, https://gtfs.org/schedule/. To improve the spatial accuracy of the NTM Stops, the Bureau of Transportation Statistics (BTS) adjusts transit stops using context from the submitted GTFS source data and/or from other publicly available information about the transit service. A data dictionary, or other source of attribute information, is accessible at https://doi.org/10.21949/1529049

This file contains the travel times between origin and destination pairs on a single line.

It includes all heavy rail and light rail rapid transit lines. These travel times are calculated from the departure time at the from_stop to the arrival time at the to_stop. Due to track circuit or other data issues, data is not guaranteed to be complete for any origin-destination pair or date.

Data Dictionary

Each row represents a unique service_date-trip_id-from_stop_id-to_stop_id unit for rail service.

field name

type

description

source

example

service_date

date

equivalent to GTFS-RT start_date value in Trip Descriptor as date instead of string

GTFS-RT

2024-01-01

route_id

string

equivalent to GTFS-RT route_id value in Trip Descriptor

GTFS-RT

Orange

trip_id

string

equivalent to GTFS-RT trip_id value in Trip Descriptor

GTFS-RT

62248746

direction_id

int

equivalent to GTFS-RT direction_id value in Trip Descriptor

GTFS-RT

0

direction

string

equivalent to GTFS direction value from directions.txt for route_id-direction_id pair

GTFS

East

from_parent_station

string

stop_name of the parent_station associated with the stop_id from stops.txt for origin stop.

GTFS

place-amory

from_stop_id

string

equivalent to GTFS-RT stop_id value in VehiclePosition for origin stop.

GTFS-RT

170141

from_stop_name

string

equivalent to GTFS stop_name from stops.txt for destination stop_id.

GTFS

Amory Street

to_parent_station

string

stop_name of the parent_station associated with the stop_id from stops.txt for destination stop.

GTFS

place-babck

to_stop_id

string

equivalent to GTFS-RT stop_id value in VehiclePosition for destination stop.

GTFS-RT

70560

to_stop_name

string

equivalent to GTFS stop_name from stops.txt for origin stop_id.

GTFS

Babcock Street

from_stop_departure_datetime

datetime

earliest "IN_TRANSIT_TO" OR "INCOMING_AT" status timestamp from origin stop (previous stop) from GTFS-RT VehiclePosition as an Eastern datetime.

GTFS-RT

11/1/2023 5:24:51 AM

from_stop_departure_sec

int

from_stop_departure_datetime as seconds after midnight

LAMP Calculated

84912

to_stop_arrival_datetime

datetime

earliest "STOPPED_AT" status timestamp for destination stop from GTFS-RT VehiclePosition or last arrival timestamp from GTFS-RT StopTimeUpdate if VehiclePosition value is not available as an Eastern datetime.

GTFS-RT

11/1/2023 5:25:34 AM

to_stop_arrival_sec

int

to_stop_arrival_datetime as seconds after midnight

LAMP Calculated

84992

travel_time_sec

int

seconds the vehicle spent traveling between origin stop and destination stop on trip.

Calculated for Open Data Portal

80

Changes to the data

Rapid Transit Travel Time data is now sourced from Lightweight Application for Measuring Performance (LAMP). To learn more about LAMP, please visit LAMP website.

The data changed as follows:

Trip_id field is added.

Direction field is added.

From_parent_station field is added.

From_stop_name field is added.

To_parent_station field is added.

To_stop_name field is added.

From_stop_departure_datetime field is added.

To_stop_arrival_datetime field is added.

Start_time_sec is now from_stop_departure_sec.

End_time_sec is now to_stop_arrival_sec.

MassDOT/MBTA shall not be held liable for any errors in this data. This includes errors of omission, commission, errors concerning the content of the data, and relative and positional accuracy of the data. This data cannot be construed to be a legal document. Primary sources from which this data was compiled must be consulted for verification of information contained in this data.

The Intercity Bus Atlas - Routes dataset uses source data from April 08, 2025 and was created on April 08, 2025 from the Bureau of Transportation Statistics (BTS) and is part of the U.S. Department of Transportation (USDOT)/Bureau of Transportation Statistics (BTS) National Transportation Atlas Database (NTAD). The Intercity Bus Atlas (ICBA) initiative collects, compiles, maps, publishes, and archives scheduled intercity bus service data provided by North American bus service providers. ICBA data--collected as periodic historic snapshots of available intercity bus services--is intended for federal, state, local, and tribal transportation decision makers, metropolitan planning organizations, transportation-related associations, private sector actors (including the freight community), and the public to better understand the density, frequency, accessibility, and reachability provided by the intercity bus industry's services. The stop, route, and schedule data provided by the ICBA reveal the local, interregional, and international connectivity, service densities, frequencies, and travel patterns enabled by the intercity bus component of the United States' myriad transportation facilities and services as well as how these services co-exist with other modes of passenger travel. The underlying source data of the ICBA are supplied by participating North American bus service providers, who publish their schedule information compliant the General Transit Feed Specification (GTFS). This GTFS standard allows intercity bus providers to publish operational information on their stops, routes, trips, schedules, fares, and transfers in a way that is maximally interoperable with applications that consume, process, and visualize the data for riders and others interested in learning more about their services. The ICBA, however, relies only on data provided via GTFS' schedule component; while there is a second GTFS component for real-time bus location data, it is not currently utilized or required for the ICBA. More information on GTFS is available at https://gtfs.org/schedule/. In turn, the Bureau of Transportations Statistics collects GTFS schedule data from provider websites and compiles them into a single geospatially enabled database. As of December 2023, this database contains two feature layers, each representing a different component of providers networks: stops and routes. The ICBA Routes dataset shows the alignment of each intercity bus route (i.e., a group of trips displayed to riders as a single service) along the national road network; it combines information from the GTFS "routes.txt", "trips.txt", and "shapes.txt" files. A data dictionary, or other source of attribute information, is accessible at https://doi.org/10.21949/1529305

This layer displays all of Allegany County Transit's bus stops. ACT's system is a flag bus route system so not all of the stops have physical posts. Stops were retrieved from GTFS file. This is a MD iMAP hosted service. Find more information on https://imap.maryland.gov. Feature Service Layer Link: https://geodata.md.gov/imap/rest/services/Transportation/MD_LocalTransit/FeatureServer/0

This dataset helps to investigate the Spatial Accessibility to HIV Testing, Treatment, and Prevention Services in Illinois and Chicago, USA. The main components are: population data, healthcare data, GTFS feeds, and road network data. The core components are: 1) GTFS which contains GTFS (General Transit Feed Specification) data which is provided by Chicago Transit Authority (CTA) from Google's GTFS feeds. Documentation defines the format and structure of the files that comprise a GTFS dataset: https://developers.google.com/transit/gtfs/reference?csw=1. 2) HealthCare contains shapefiles describing HIV healthcare providers in Chicago and Illinois respectively. The services come from Locator.HIV.gov. 3) PopData contains population data for Chicago and Illinois respectively. Data come from The American Community Survey and AIDSVu. AIDSVu (https://map.aidsvu.org/map) provides data on PLWH in Chicago at the census tract level for the year 2017 and in the State of Illinois at the county level for the year 2016. The American Community Survey (ACS) provided the number of people aged 15 to 64 at the census tract level for the year 2017 and at the county level for the year 2016. The ACS provides annually updated information on demographic and socio economic characteristics of people and housing in the U.S. 4) RoadNetwork contains the road networks for Chicago and Illinois respectively from OpenStreetMap using the Python osmnx package. The abstract for our paper is: Accomplishing the goals outlined in “Ending the HIV (Human Immunodeficiency Virus) Epidemic: A Plan for America Initiative” will require properly estimating and increasing access to HIV testing, treatment, and prevention services. In this research, a computational spatial method for estimating access was applied to measure distance to services from all points of a city or state while considering the size of the population in need for services as well as both driving and public transportation. Specifically, this study employed the enhanced two-step floating catchment area (E2SFCA) method to measure spatial accessibility to HIV testing, treatment (i.e., Ryan White HIV/AIDS program), and prevention (i.e., Pre-Exposure Prophylaxis [PrEP]) services. The method considered the spatial location of MSM (Men Who have Sex with Men), PLWH (People Living with HIV), and the general adult population 15-64 depending on what HIV services the U.S. Centers for Disease Control (CDC) recommends for each group. The study delineated service- and population-specific accessibility maps, demonstrating the method’s utility by analyzing data corresponding to the city of Chicago and the state of Illinois. Findings indicated health disparities in the south and the northwest of Chicago and particular areas in Illinois, as well as unique health disparities for public transportation compared to driving. The methodology details and computer code are shared for use in research and public policy.

Data provided by Metropolitan Atlanta Rapid Transit Authority (MARTA) General Transit Feed Specification (GTFS) at https://www.itsmarta.com/app-developer-resources.aspxCity of Sandy Springs translates the stops, shapes, routes and trip files in FME with FME Workbench. The Stops and Routes are published to ArcGIS online. General Transit Feed SpecificationThe MARTA GTFS feed is updated approximately four times per year, which is about how often MARTA service changes. It will be published to the same URL with each new update.

This polyline data layer contains the bus routes for the Regional Transit Authorities of Massachusetts, except for the MBTA. Attributes included the RTA the route belongs to, the route name, to and from destination, and a link to information about the route (if applicable). The data was obtained from the GTFS feeds on the MassDOT Developers page which were processed into KML files using the python GTFS toolkit. All data is in WGS84. The RTAs included are listed below.Regional Transportation AuthoritiesBrockton Area Transit (BAT)Berkshire Regional Transportation Authority (BRTA)Cape Ann Transportation Authority (CATA)Cape Cod Transportation Authority (CCRTA)Franklin Regional Transportation Authority (FRTA)Greater Attleboro Taunton Regional Transit Authority (GATRA)Lowell Regional Transit Authority (LRTA)Montachusett Area Regional Transit (MART)Merrimack Valley Regional Transit Authority (MVRTA)MetroWest Regional Transit Authority (MWRTA)Nantucket Regional Transit Authority (NRTA)Pioneer Valley Regional Transit Authority (PVRTA)Southeastern Regional Transit Authority (SRTA)Vineyard Regional Transit Authority (VRTA)Worcester Regional Transit Authority (WRTA)

This point layer was created from the GTFS data feeds from the Washington D.C. Metropolitan Area Transportation Authority (WMATA) to represent the new WMATA bus transit stops for the Better Bus Network Redesign(BBNR). Points in this layer represent individual bus stops; they were generalized from the GTFS format where stops depicted individual services. On June 29, 2025, WMATA implemented a brand new Metrobus Network – known as Better Bus. Each point in this layer represents a bus stop served by the routes, with the stop sequence field indicating the order of stops based on the route's travel direction. This feature class was generated using a relational query on the trip_id, shape_id fields from the trip.txt and stop_times.txt files from the GTFS. The unique identifier for each stop is designated by the REG_ID (Regional ID), a field created by WMATA to assign a recognizable number to each stop, ensuring that every stop has a distinct ID. Learn more about GTFS feeds at wmata.com/about/developers.The District Department of Transportation (DDOT) has added DC attribution for Roadway Blocks and Roadway Subblocks. Use BLOCKKEY, SUBBLOCKKEY, and ROUTEID to relate back to DC government data. Learn more about DDOT's roadway centerline data at opendata.dc.gov/pages/roadway-centerlines.