port-authority - GTFS transit data for United States

Active
Port-Authority United States June 28, 2026 — October 24, 2026

About This Feed

The port-authority GTFS feed by Port-Authority provides structured public transit data for United States, covering 98 routes, 6,345 stops, and 1 transit agencies. Formatted according to the General Transit Feed Specification (GTFS), this dataset is ready for transit apps, routing engines, urban planning tools, and AI agents / LLM applications.

Valid from June 28, 2026 to October 24, 2026. 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 port-authority routes and stops in United States
Explore 98 routes, 6,345 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=port-authority 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
13.02 MB
Available through API only This work is licensed under Custom_license. Content Hash: cb596d89cc5301a6
ZIP Validation Report
0.02 MB
Available through API only
397Errors
12Warnings
1Info
Top Issues
block trips with overlapping stop times397
mixed case recommended field11
expired calendar1
GeoJSON GeoJSON Data
0.18 MB
Available through API only

Original Source

Obtained 2026-06-28

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

ZIP GTFS Source Data
21.47 MB
Available through API only License: Custom_license Content Hash: 9f13314d2fa1a196
ZIP Validation Report
0.04 MB
Available through API only
0Errors
24,333Warnings
18,350Info
Top Issues
mixed case recommended field24,290
unused shape29
route color contrast7

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
mon-valley 2 (0.03%)
wcta-rideralerts-com-westmoreland-county-transit-a 2 (0.03%)
Build real-time departures into your app Free API Access →

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.