This feed has expired Service dates: 2023-12-01 - 2024-12-31

indebus - GTFS transit data for United States

Expired
TransLoc United States December 1, 2023 — December 31, 2024

About This Feed

indebus is the GTFS feed TransLoc publishes for United States: 6 routes, 234 stops, 1 transit agencies. BusMaps checks and corrects it every week and serves the result through the API and as GTFS files.

Active from December 1, 2023 to December 31, 2024; the schedule has ended. The files stay available for analysis.

Checked and corrected automatically. How we do it →

One API for this feed

The API behind this page serves the same 6 routes and 234 stops: stops near a point, departures, trips, timetables and the GTFS files. The requests below use the coordinates of this feed.

  • Stops within a radius of a coordinate.

    GET /v1/stopsInRadius?location=39.0799,-94.4071&radius=1000
  • Departures at the nearby stops, with real-time delays where the agency publishes them.

    GET /v1/nextDepartures?location=39.0799,-94.4071&radius=500&results=30
  • Itineraries between two points on this network.

    GET /v1/routes?origin=39.0799,-94.4071&destination=39.094,-94.3874
  • Directions, stop order and the schedule of one route.

    GET /v1/line?routeId={routeId}
  • GTFS files Free

    The corrected feed, the source feed, GeoJSON and the validation reports.

    GET /v1/getGtfsFeedsDownloads?feedName=indebus
  • Claude, ChatGPT or any MCP client asks this network questions in plain language.

    https://mcp.busmaps.com/mcp

Base URL https://capi.busmaps.com:8443. Send the key in the capi-key header. Route ids come from the responses above.

Per-feed pages: 6 routes, 234 stops, 1 agencies

Public pages merge every feed. Sign in to browse this feed on its own, which helps when you integrate or debug it.

Sign in →

GTFS files of this feed

Two builds: the copy BusMaps corrected and validated, and the original from TransLoc. The API returns either one for ?feedName=indebus. Documentation →

Enhanced & Validated Recommended

Updated 2026-08-21

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

ZIP GTFS Feed - Corrected & Enriched
0.04 MB
Available through API only The license for this work is not specified Content Hash: 6ce95e57fe3f4178
ZIP Validation Report
0.01 MB
Available through API only
0Errors
4Warnings
0Info
Top Issues
expired calendar2
feed expiration date7 days1
trip coverage not active for next7 days1
GeoJSON GeoJSON Data
0.01 MB
Available through API only

Original Source

Obtained 1979-12-31

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

ZIP GTFS Source Data
0.05 MB
Available through API only The license for this work is not specified Content Hash: 31c6eeb2594b2d6d
ZIP Validation Report
0.01 MB
Available through API only
0Errors
11Warnings
4Info
Top Issues
missing recommended field6
expired calendar2
feed expiration date7 days1

Frequently Asked Questions

What is GTFS data?

GTFS, the General Transit Feed Specification, is the open format transit agencies use to publish schedules, stops and route shapes. Trip planners, routing engines and analytics tools read it directly.

What is the difference between enhanced and source data?

The source feed is what the agency published. The enhanced feed is the same data after BusMaps fixed the errors and inconsistencies and checked it against the GTFS specification. Use the enhanced feed in production.

Can I use this data in my application?

That depends on the licence the publisher set; you find it next to the files above. Most GTFS feeds allow free use with attribution. Check the licence before you integrate.

How do I validate a GTFS feed?

Every feed here ships with a validation report of errors and warnings. For an independent check, run the MobilityData GTFS Validator. The enhanced feed has the critical issues resolved.

All data comes from public sources. If a file was posted in error, carries a wrong licence or lacks attribution, contact us and we will fix it.