fullington-us - GTFS transit data for United States

Active
Transport-Usa United States 1 de julio de 2021 — 31 de diciembre de 2027

About This Feed

The fullington-us GTFS feed by Transport-Usa provides structured public transit data for United States, covering 17 routes, 61 stops, and 1 transit agencies. Formatted according to the General Transit Feed Specification (GTFS), this dataset is ready for transit apps, routing engines, and urban planning tools.

Valid from 1 de julio de 2021 to 31 de diciembre de 2027. Suitable for production use in transit applications, GTFS editors, and GTFS-RT integrations.

Data is automatically validated and corrected. View our quality pipeline →

Transit map showing fullington-us routes and stops in United States
Explore 17 routes, 61 stops, and 1 agencies

Browse routes, stops, and agencies from this feed. Public pages show merged data from all feeds. Sign in for per-feed details useful for GTFS integration and debugging.

Sign in to access →

Download this feed through the BusMaps API

Enhanced GTFS, source GTFS, GeoJSON, and validation reports are available through the API.

Use ?feedName=fullington-us to request this feed. View API documentation.

Enhanced & Validated Recommended

Updated 2026-08-01

Cleaned, corrected, and validated against GTFS specifications. View corrections.

ZIP GTFS Feed - Corrected & Enriched
0.7 MB
Available through API only The license for this work is not specified Content Hash: dfb32c80bc21411d
ZIP Validation Report
0.01 MB
Available through API only
0Errors
49Warnings
0Info
Top Issues
fast travel between consecutive stops24
stop too far from shape12
fast travel between far stops10
GeoJSON GeoJSON Data
0.01 MB
Available through API only

Original Source

Obtained 2022-06-02

Unmodified GTFS data from official sources. May contain errors or inconsistencies.

ZIP GTFS Source Data
1.79 MB
Available through API only The license for this work is not specified Content Hash: ff132b9a9a6c40ff
ZIP Validation Report
0.05 MB
Available through API only
6Errors
2,689Warnings
19Info
Top Issues
trip distance exceeds shape distance6
equal shape distance same coordinates2,266
missing timepoint value183

Use This Feed from AI Agents

This feed is also served through the BusMaps MCP server: point Claude, ChatGPT, Gemini or any MCP client at https://mcp.busmaps.com/mcp and your agent can plan routes, read departures, and query this network in plain language.

About the MCP server →

Overlapping Feeds

Feeds that share stops or routes with this dataset.

Feed Stops Overlap Routes Overlap
merged-gtfs-feed 4 (23.53%)
fullington-trailways 2 (11.76%)
trailways-nyp 3 (4.92%)
Integra salidas en tiempo real en tu aplicación Acceso gratuito a la API →

Frequently Asked Questions

What is GTFS data?

General Transit Feed Specification (GTFS) is an open data format for public transit schedules and geographic information. Created by Google and TriMet, it enables transit agencies to publish interoperable data for applications, trip planners, and mobility analytics tools.

What is the difference between enhanced and source data?

Source data is the original GTFS feed obtained from the transit agency or official provider. The enhanced version has been processed to fix errors, remove inconsistencies, and ensure compliance with GTFS specifications. We recommend the enhanced version for production applications.

Can I use this data in my application?

Data usage depends on the license specified by the original provider. Check the license information in the download section. Many GTFS feeds use open data licenses that allow free use with attribution. Always verify the license terms before integration.

How do I validate a GTFS feed?

Each feed includes a validation report documenting errors and warnings. You can also use the MobilityData GTFS Validator for independent validation. Enhanced feeds have already been processed to resolve the most critical validation issues.

All data on this site comes from publicly available sources. If a file was posted in error, has an incorrect license, or lacks correct source attribution, please contact us and we will correct it.