the-woodlands-township - GTFS transit data for United States

Active
Transport-Usa United States 1 de marzo de 2025 — 31 de diciembre de 2027

About This Feed

the-woodlands-township is the GTFS feed Transport-Usa publishes for United States: 33 routes, 79 stops, 1 transit agencies. BusMaps provides the original source through the API. Corrected and validated builds are not available in the API and require the data request form.

Valid from 1 de marzo de 2025 to 31 de diciembre de 2027.

Checked and corrected automatically. How we do it →

One API for this feed

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

  • Stops within a radius of a coordinate.

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

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

    GET /v1/routes?origin=29.8797,-95.4427&destination=29.9602,-95.42
  • Directions, stop order and the schedule of one route.

    GET /v1/line?routeId={routeId}
  • The original source feed, source validation report, and provider links. Processed data is not returned.

    GET /v1/getGtfsFeedsDownloads?feedName=the-woodlands-township
  • 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: 33 routes, 79 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.

Entrar →

GTFS Data Products

Request enhanced data access

The API provides source files only. Submit the data request form to discuss enhanced or custom data, coverage, and delivery terms.

Open the data request form →

Enhanced & Validated Recommended

Updated 2026-08-22

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

ZIP GTFS Feed - Corrected & Enriched
0.17 MB
Access: Submit the data request form The license for this work is not specified Content Hash: f9edc90827018ef4
ZIP Validation Report
0.01 MB
0 Errors
5 Warnings
0 Info
Top Issues
route short name too long 5
GeoJSON GeoJSON Data
0.01 MB

Original Source

Obtained 2025-10-08

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

ZIP GTFS Source Data
0.28 MB
Available through API The license for this work is not specified Content Hash: 50db0e55be854423
ZIP Validation Report
0.01 MB
Available through API
0 Errors
55 Warnings
11 Info
Top Issues
mixed case recommended field 27
stop without stop time 13
trip distance exceeds shape distance below threshold 9

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?

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. API plans include source data only. Enhanced data requires a separate request through the data request form. Request access through the form →

Can I use this data in my application?

Source-data use depends on the licence set by the publisher; check it before integration. Enhanced and custom data is supplied under terms agreed for your coverage, delivery, and intended use.

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, we will fix it.

Contact us →