This feed has expired Service dates: 2020-12-31 - 2021-12-31

trailways-nyt - GTFS transit data for United States

Expired
North-Country-Express-Transit United States December 31, 2020 — December 31, 2021

About This Feed

The trailways-nyt GTFS feed by North-Country-Express-Transit provides structured public transit data for United States, covering 8 routes, 28 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.

This feed was active from December 31, 2020 to December 31, 2021 and is no longer current. It remains available for historical analysis and research.

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

Transit map showing trailways-nyt routes and stops in United States
Explore 8 routes, 28 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=trailways-nyt 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.12 MB
Available through API only This work is licensed under Custom_license. Content Hash: 735c0153c022b180
ZIP Validation Report
0.01 MB
Available through API only
0Errors
20Warnings
0Info
Top Issues
expired calendar6
fast travel between consecutive stops4
stop too far from shape4
GeoJSON GeoJSON Data
0.01 MB
Available through API only

Original Source

Obtained 2021-09-13

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

ZIP GTFS Source Data
0.24 MB
Available through API only License: Custom_license Content Hash: 0929d7a0f21d13f1
ZIP Validation Report
0.03 MB
Available through API only
5Errors
649Warnings
0Info
Top Issues
trip distance exceeds shape distance5
equal shape distance same coordinates546
mixed case recommended field44

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
trailways-nyp 4 (14.29%)
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.