Context

Dataset GTFS - EMTU

What is GTFS?

GTFS - General Transit Feed Specification It is a specification that defines a format for exchanging static transport information.

https://gtfs.org

Files GFFS EMTU

EMTU GTFS files could be obtained in EMTU website

agency.txt

Transit agencies with service represented in this dataset.

calendar.txt

Service dates specified using a weekly schedule with start and end dates, this file is required unless all dates of service are defined in calendar_dates.txt.

fare_attributes.txt

Fare information for a transit agency's routes.

fare_rules.txt

Rules to apply fares for itineraries.

frequencies.txt

Headway (time between trips) for headway-based service or compressed representation of fixed-schedule service.

routes.txt

Transit routes. A route is a group of trips that are displayed to riders as a single service.

shapes.txt

Rules for mapping vehicle travel paths sometimes referred to as route alignments.

stop_times.txt

Times that a vehicle arrives at and departs from stops for each trip.

stops.txt

Stops where vehicles pick up or drop off riders also defines stations and station entrances.

trips.txt

Trips for each route. A trip is a sequence of two or more stops that occur during a specific time period.

ГТФС (енгл. General Transit Feed Specification) представља општу, глобално прихваћену спецификацију формата података о јавном превозу који обухвата податке о линијама, редовима вожње, локацијама стајалишта, трасама, ценама аутобуских карата и сл. Овај формат омогућава превозницима и градским службама да објаве податке у интероператибилном формату који се може лако искористити и имплементирати у различитим апликацијама.

ГТФС представља зип фајл који се састоји се од следећих фајлова у txt формату: _-agency.txt -stops.txt -routes.txt -trips.txt -stop_times.txt -calendar.txt -calendar_dates.txt -fare_attributes.txt -fare_rules.txt -shapes.txt -frequencies.txt -transfers.txt -pathways.txt -levels.txt -feed_info.txt_

Овај ресурс је објавила Градска агенција за саобраћај Града Крагујевца.

https://www.kgbus.rs/wp-content/uploads/2019/10/google-transit.png" alt="ГТФС Крагујевац" title="овде унесите наслов слике">

As of Report Year (RY) 2023, FTA requires that reporters with fixed route modes create and maintain a public domain general transit feed specification (GTFS) dataset that reflects their fixed route service. This specification allows for the mapping and other geospatial data visualization and analyses of key transit elements such as stops, routes, and trips. At least one GTFS weblink is provided by the transit agency for each fixed route bus mode and type of service. These include all Rail modes as well as Bus, Bus Rapid Transit, Commuter Bus, Ferryboat and Trolleybus.

GTFS requires that an overarching compressed file contain, at a minimum, seven underlying text files: (a) Agency; (b) Stops; (c) Routes; (d) Trips; (e) Stop Times; (f) Calendar or Calendar Dates.txt; and (g) Feed Info.txt. An eighth file, Shapes.txt, is an optional file. FTA collects and publishes these links for further analysis using related GTFS files. FTA is not responsible for managing the websites that host these files, and users with questions regarding the GTFS data are encouraged to contact the transit agency.

In many cases, publicly hosted weblinks could not be provided (i.e., due to constraints within the transit agency), but the agency was able to produce a zip file of the required GTFS data. Demand Response, Vanpool, and other non-fixed route modes are excluded. The column "Alternate Format" indicates that the agency provided FTA a weblink in an alternate format with some justification for doing so. The file "Waived" indicates that no GTFS files were produced and FTA granted the agency a waiver from the requirement in Report Year 2024.

Note: if the Validated Date is earlier than the Modified Date for a specific row, then the weblink has not yet been reviewed. If you encounter issues with a weblink that has been validated, please contact NTDHelp@dot.gov, as this may indicate an error with the host website.

If you have any other questions about this table, please contact the NTD Help Desk at NTDHelp@dot.gov.

The National Transit Map - Routes 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 Routes dataset shows transit routes, which is a group of trips that are displayed to riders as a single service. To display the route alignment and trips for each route, this dataset combines the following GTFS files: routes.txt, trips.txt, and shapes.txt. The GTFS Schedule documentation is available at, https://gtfs.org/schedule/. To improve the spatial accuracy of the NTM Routes, the Bureau of Transportation Statistics (BTS) adjusts transit routes 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/1529048

NOTE: As weblinks are updated continually by transit agencies, some links submitted in Report Year 2023 may no longer work. The most up-to-date weblinks dataset is refreshed on a monthly basis: https://data.transportation.gov/Public-Transit/General-Transit-Feed-Specification-Weblinks/2u7n-ub22/about_data

As of Report Year (RY) 2023, FTA requires that reporters with fixed route modes create and maintain a public domain general transit feed specification (GTFS) dataset that reflects their fixed route service. This specification allows for the mapping and other geospatial data visualization and analyses of key transit elements such as stops, routes, and trips. At least one GTFS weblink is provided by the transit agency for each fixed route bus mode and type of service. These include all Rail modes as well as Bus, Bus Rapid Transit, Commuter Bus, Ferryboat and Trolleybus.

GTFS requires that an overarching compressed file contain, at a minimum, seven underlying text files: (a) Agency; (b) Stops; (c) Routes; (d) Trips; (e) Stop Times; (f) Calendar or Calendar Dates.txt; and (g) Feed Info.txt. An eighth file, Shapes.txt, is an optional file. FTA collects and publishes these links for further analysis using related GTFS files. FTA is not responsible for managing the websites that host these files, and users with questions regarding the GTFS data are encouraged to contact the transit agency.

In many cases, publicly hosted weblinks could not be provided (i.e., due to constraints within the transit agency), but the agency was able to produce a zip file of the required GTFS data. Demand Response, Vanpool, and other non-fixed route modes are excluded. The column "Alternate Format" indicates that the agency provided FTA a weblink in an alternate format with some justification for doing so. The file "Waived" indicates that no GTFS files were produced and FTA granted the agency a waiver from the requirement in Report Year 2023.

NTD Data Tables organize and summarize data from the 2023 National Transit Database in a manner that is more useful for quick reference and summary analysis. This dataset is based on the 2023 General Transit Feed Specification database file.

If you have any other questions about this table, please contact the NTD Help Desk at NTDHelp@dot.gov.

The GTFS Schedule dataset contains static timetable information of public transport services in Victoria. The modes included are:

* All metropolitan and regional trains
* All metropolitan and regional buses (including coach)
* All metropolitan trams

It is published in a standardised data format according to the GTFS specification.




Release Notes

DTPs GTFS Release Notes (.docx)

DTPs GTFS Release Notes (.pdf)




Additional Notes

GTFS Schedule now includes additional features. These include:

Transfers

* Introduction of transfers.txt to complement existing Block Transfers information

Wheelchair Access

* New attribute of 'wheelchair\_accessible' was added to trips.txt
* New attribute of 'wheelchair\_boarding' was added to stops.txt to identify wheelchair accessible stops and platforms

Pathways

* Introduction of pathways.txt for more detailed path links into stations ('pathway\_id', 'from\_stop\_id', 'to\_stop\_id', 'pathway\_mode', 'is\_bidirectional', 'traversal\_time')
* Addition of new records in stops.txt to support more detailed path links inside stations

Levels

* New attribute of 'level\_id' was added to stops.txt
* Introduction of levels.txt to use in conjunction with pathways.txt ('level\_id', 'level\_index', 'level\_name')

Platform Numbers

* New records were added to stops.txt to include the name and location of all 'Metro Train' platforms. In accordance with the GTFS Specification, parent stop records of train stations have also been created.

Bus Replacement Stops

* New records were added to stops.txt to include the name and location of all 'Metro Train' Bus Replacement stops. Note their 'platform\_code' has been designated as 'R\-Bus'.

Bus Replacement trips

* Additional bus replacement trips information has been incorporated into the consolidated train routes in trips.txt and shapes.txt. Note \- 'route\_id' and 'trip\_id' structure has changed from previous GTFS.zip files as part of DTP's backend system improvements.

Tram ID improvements

* 'route\_id' and 'trip\_id' are updated to include business identifiers to improve matching to GTFS Realtime data feeds

Tram Headsign changes

* 'trip\_headsign' in trips.txt is updated to show improved end of trip destination text.




Folder Structure

The GTFS.zip file is currently structured with folder of Public Transport mode operational branches as per this list.

1 (Regional Train)

2 (Metropolitan Train)

3 (Metropolitan Tram)

4 Myki Bus (Metro Bus and Regional Town Bus)

5 (Regional Coach)

6 (Regional Bus)

10 (Interstate)

11 (SkyBus)




Data Currency

This information is updated on a weekly or as needed basis. There may be periods where publication is delayed due to scheduled maintenance or unforeseen circumstances.




Valid Time Period

The data contains a rolling 30 days of data from the date of export. Some route information may not be complete for this entire period due to service information not yet being made available. As this information becomes available to DTP, it will be made available in subsequent data publications.



Geographic Accuracy

The path information provided is generated based on a mix of automatic algorithm and manual pathing. There may be inaccuracies with the paths and hence the paths may not always match on road operations.

As of Report Year (RY) 2023, FTA requires that reporters with fixed route modes create and maintain a public domain general transit feed specification (GTFS) dataset that reflects their fixed route service. This specification allows for the mapping and other geospatial data visualization and analyses of key transit elements such as stops, routes, and trips. At least one GTFS weblink is provided by the transit agency for each fixed route bus mode and type of service. These include all Rail modes as well as Bus, Bus Rapid Transit, Commuter Bus, Ferryboat and Trolleybus. GTFS requires that an overarching compressed file contain, at a minimum, seven underlying text files: (a) Agency; (b) Stops; (c) Routes; (d) Trips; (e) Stop Times; (f) Calendar or Calendar Dates.txt; and (g) Feed Info.txt. An eighth file, Shapes.txt, is an optional file. FTA collects and publishes these links for further analysis using related GTFS files. FTA is not responsible for managing the websites that host these files, and users with questions regarding the GTFS data are encouraged to contact the transit agency. In many cases, publicly hosted weblinks could not be provided (i.e., due to constraints within the transit agency), but the agency was able to produce a zip file of the required GTFS data. Demand Response, Vanpool, and other non-fixed route modes are excluded. The column "Alternate Format" indicates that the agency provided FTA a weblink in an alternate format with some justification for doing so. The file "Waived" indicates that no GTFS files were produced and FTA granted the agency a waiver from the requirement in Report Year 2023. NTD Data Tables organize and summarize data from the 2023 National Transit Database in a manner that is more useful for quick reference and summary analysis. This dataset is based on the 2023 General Transit Feed Specification database file. If you have any other questions about this table, please contact the NTD Help Desk at NTDHelp@dot.gov.

This web map integrates two powerful datasets to explore the intersection of public transit access and vehicle availability across the United States. The first layer features the National Transit Map – Routes, by the Bureau of Transportation Statistics (BTS). This nationwide dataset illustrates fixed-guideway and fixed-route public transit services and is built from General Transit Feed Specification (GTFS) Schedule data. It merges information from routes.txt, trips.txt, and shapes.txt files to display detailed route alignments and associated trip data. To enhance spatial accuracy, BTS refines route geometries using source data and other public information. The National Transit Map is part of the U.S. Department of Transportation’s National Transportation Atlas Database (NTAD) and provides a consistent, national view of transit systems.

This file contains the data of bus lines 1-34 (without lines 7 and 22) operated by Stadtwerke Münster and N80 — N85. The data is available in GTFS format. The GTFS (General Transit Feed Specification) format is a digital exchange format for public passenger timetables. This also includes geographical information, such as the locations of stops. The file contains the following information: Agency.txt: includes the transport undertakings whose lines are included calendard_dates.txt: includes various traffic days, such as holidays. routes.txt: contains all lines shapes.txt: contains the line paths for map representations stop_times.txt: includes all arrival and departure times at the stops stops.txt: contains the location of all stops trips.txt: includes all journeys The exact explanation of the content can be found at https://developers.google.com/transit/gtfs/reference/. Please refer to the General Terms and Conditions of Use for the GTFS data of Stadtwerke Münster at this link.

Las formas describen la ruta física que realiza un vehículo y vienen definidas en el archivo shapes.txt (formato GTFS). Las formas se asocian con viajes individuales y se componen de una secuencia de puntos. El trazado ordenado de los puntos proporciona la ruta del vehículo. No es necesario que los puntos coincidan con las ubicaciones de las paradas. Para más información sobre el formato GTFS consultar: https://developers.google.com/transit/gtfs/reference?hl=es#term-definitions

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.

The National Transit Map - Routes dataset was compiled on March 19, 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 Routes dataset shows transit routes, which is a group of trips that are displayed to riders as a single service. To display the route alignment and trips for each route, this dataset combines the following GTFS files: routes.txt, trips.txt, and shapes.txt. The GTFS Schedule documentation is available at, https://gtfs.org/schedule/. To improve the spatial accuracy of the NTM Routes, the Bureau of Transportation Statistics (BTS) adjusts transit routes 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/1529048

The public transport network of the Community of Communes of Briançonnais, called Altigo, has been active since 1 November 2022. However, several structuring steps will take place during 2023 to achieve a full deployment of the Community transport network by 1 September 2023. Thus, GTFS data will be required to evolve regularly and will be updated as the Altigo network evolves.

The GTFS comprises the following files: - agency.txt => identifies the transmission network; - stops.txt => lists all network breakpoints; - routes.txt => lists all the lines in the network; - trips.txt => lists all the races in the network; - stop_times.txt => lists, for each race, all the stopping points served and the time of passage; - calendar.txt => lists the entire calendar of the network (dates of operation of the lines); - calendar_dates.txt => lists exceptional operating days (example: the Thursday of the ascent which functions as a Sunday); - shapes.txt => lists the routes;

You can find more information on the [Altigo] website (https://www.monaltigo.fr/)

Update 20/07/2023

Position of stops and lines of all public transport datasets available on the platform transport.data.gouv.fr.

This dataset is a fusion of GeoJSON generated from GTFS files and published in community resources on data.gouv.fr.

GeoJSON is an extract of the position of the transport stops as well as the layout of the lines, when these are available in the GTFS (via the file shapes.txt). GeoJSONs are generated with the https://gitlab.com/CodeursEnLiberte/gtfs-to-GeoJSON/ tool.

Merged files are updated regularly automatically (with this script, contributions are welcome), and published in several formats to simplify reuse:

— a GeoJSON, zipped;

— one GeoJSON per line, zipped. Each line is a GeoJSON with geometry. This file may be easier to use due to the size of the GeoJSON file;

— a file GeoPackage.

Note: These files are a simple aggregation of GeoJSON available on transport.data.gouv.fr. There will therefore be duplicates in the positions of stops/trace lines since some (notably the major Parisian stations) are present in several data sets.

The Total-Text dataset contains the text of various shapes, including horizontal, multi-orientational, and curved.

This spatial dataset includes the train lines generated from the shape.txt file in the Sydney Trains GTFS static bundle. \r \r Spatial route datasets included in the following formats and will be updated on a monthly basis:\r \r -\tcsv\r -\tgeojson\r -\tjson\r -\tkml\r -\tshapefile\r

A complete list of live websites using the tsparticles-shape-text technology, compiled through global website indexing conducted by WebTechSurvey.

This dataset was created for detecting many shape types of different colors with different alphanumeric characters on them for the SUAS 2023 Competition.

13 shapes: Circle, Semi-Circle, Quarter-Circle, Triangle, Square, Rectangle, Pentagon, Hexagon, Heptagon, Octagon, Star, Cross, Trapezoid.

10 colors: Black, White, Gray, Blue, Red, Orange, Yellow, Green, Purple, Brown.

36 Alphanumeric characters: all capital letters and all numbers.

3 examples of each combination is available for more variation. Variations of tones of text and shape colors and text rotation selection 0 or 90 degrees on rectangles has been implemented.

The images are full size as to allow for simple bounding box creation when they get copied into a background image for shape detection. The images are transparent for realism when copied into the background image.

The dataset was created with Luxor, a julia package.

In real-world scenarios, a major limitation for shape-matching datasets is represented by having all the meshes of the same subject share their connectivity across different poses. Specifically, similar connectivities could provide a significant bias for shape-matching algorithms, simplifying the matching process and potentially leading to correspondences based on recurring triangle patterns rather than geometric correspondences between mesh parts. As a consequence, the resulting correspondence may be meaningless, and the evaluation of the algorithm may be misled.
To overcome this limitation, we introduce TACO, a new dataset where meshes representing the same subject in different poses do not share the same connectivity, and we compute new ground truth correspondences between shapes. We extensively evaluate our dataset to ensure that ground truth isometries are properly preserved. We also use our dataset to validate state-of-the-art shape-matching algorithms, verifying a degradation in performance when the connectivity gets altered.

Dataset structure

• offs: a directory containing all the triangular meshes in the dataset in OFF file format
• pairs.txt: a list of all the 420 possible pairs of shapes in the dataset
• gt_matches: a directory containing all the ground truth correspondences listed in `pairs.txt` and stored in MAT file format

Подаци о свим градским линијама, редовима вожњи, локацијама стајалишта, трасама, ценама карата итд. у јавном саобраћају Града Ниша, укључујући и GTFS формат.

Овај сет података садржи 3 ресурса:

GTFS (engl. General Transit Feed Specification) представља општу, глобално прихваћену спецификацију формата података о јавном превозу који обухвата податке о линијама, редовима вожње, локацијама стајалишта, трасама, ценама аутобуских карата и сл. Овај формат омогућава превозницима и градским службама да објаве податке у интероператибилном формату који се може лако искористити и имплементирати у различитим апликацијама. Сам ГТФС представља зип фајл који се састоји се од следећих фајлова у тxт формату: ● agency.txt ● stops.txt ● routes.txt ● trips.txt ● stop_times.txt ● calendar.txt ● calendar_dates.txt ● fare_attributes.txt ● fare_rules.txt ● shapes.txt ● frequencies.txt ● transfers.txt ● pathways.txt ● levels.txt ● feed_info.txt

Атрибути за стајалишта јавног превоза: ИД стајалишта, "Назив стајалишта", "Смер", "Линије", "Зона"

Атрибути за трасе јавног превоза: ИД руте, "Назив трасе", "ИД превозника", "Назив превозника", "УРЛ адреса превозника", "Контакт телефон превозника"