yakima2 - GTFS transit data for United States

Active
Yakima-Transit United States 8 de mayo de 2019 — 31 de diciembre de 2027

About This Feed

The yakima2 GTFS feed by Yakima-Transit provides structured public transit data for United States, covering 23 routes, 605 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 8 de mayo de 2019 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 yakima2 routes and stops in United States
Explore 23 routes, 605 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=yakima2 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.11 MB
Available through API only The license for this work is not specified Content Hash: b49a7839a4a2db4d
ZIP Validation Report
0.01 MB
Available through API only
6Errors
11Warnings
0Info
Top Issues
stop time with arrival before previous departure time6
duplicate route name11
GeoJSON GeoJSON Data
0.02 MB
Available through API only

Original Source

Obtained 2021-06-30

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

ZIP GTFS Source Data
0.1 MB
Available through API only The license for this work is not specified Content Hash: 4bdef5b16da67f20
ZIP Validation Report
0.06 MB
Available through API only
20Errors
2,067Warnings
29Info
Top Issues
stop time with arrival before previous departure time20
stop too far from shape1,361
mixed case recommended field587

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
yakima 557 (92.07%) 14 (60.87%)
c26-yakimatransit 9 (39.13%)
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.