Decision driving
Transport
Namtang GTFS.
Best open Thailand multimodal public-transport spine for agencies, routes, stops, trips, stop_times, shapes, frequencies, fares, and some interchange logic across bus and rail systems. No public GTFS-Realtime endpoint was verified.
Public
GTFS ZIP download and related static transit resources
Free public; attribution required where license applies
Static feed; monitor every 6-24 hours
2026-05-11
Public web, file, catalog, or documented endpoint access with no paid gate implied in the source profile.
source health, observation ingest, signal compute, decision compute
agency_id, route_id, route_short_name, route_long_name, route_type, stop_id, stop_name, stop_lat, stop_lon, trip_id, service_id, shape_id, stop_sequence, arrival_time, departure_time, frequency, fare attributes, feed version
Medium-high for discovery and context; operational reliability depends on endpoint stability.
Runtime truth
Decision driving
Yes
route, station, airport, pier, destination, terminal, bus_terminal
transport_structure_score
where_to_go_today, where_to_stay, route_check, ferry_check, food_route
Feeds active observations and signals that currently influence traveler-facing decisions.
How this helps travel recommendations
Turns public-transport structure into traveler-facing route confidence: which stations, piers, stops, and interchanges actually exist in the public network spine, how much rail or bus support a base has, and where route or ferry planning still needs a stronger backup layer.
Endpoint and API notes
Best open Thailand multimodal public-transport spine for agencies, routes, stops, trips, stop_times, shapes, frequencies, fares, and some interchange logic across bus and rail systems. No public GTFS-Realtime endpoint was verified.
Open the source endpoint or documentation. Return to the Thailand data atlas.
Developer reference
Use the public GTFS ZIP as the structural transit spine. Normalize agencies, routes, stops, trips, stop_times, shapes, frequencies, and fares, then join it to official airport, pier, rail, and terminal sources instead of pretending GTFS alone proves live departures or disruption status.
Refresh weekly or when the catalog metadata changes; many agency catalogs update irregularly.
Turns public-transport structure into traveler-facing route confidence: which stations, piers, stops, and interchanges actually exist in the public network spine, how much rail or bus support a base has, and where route or ferry planning still needs a stronger backup layer.
Transitland GTFS archive, Namtang stop and pier downloads, MOT terminal datasets, SRT/BTS/MRTA public pages, OSM transit mapping, and route or destination pages that explain where static network support still needs a live backup.
Example request
# Source landing or publication page; inspect linked documents or resources before automation.
curl -L "https://namtang-api.otp.go.th/download/namtang-gtfs.zip"Failure modes
- The GTFS ZIP is a structural network feed, not a public GTFS-Realtime or live disruption API.
- Stop, route, and trip structure can lag ground truth when agencies update service faster than the published static feed.
- GTFS can prove station, stop, and interchange structure without proving same-minute departures, headways, or cancellations.
- Entity joins still need airport, pier, rail, and terminal sources because GTFS alone does not explain every transfer burden.
Last checked and source confidence
Last checked: 2026-05-11.
Source confidence: Treat this profile as strongest for the exact role named above. It is weaker when the source is stretched into live availability, legal proof, or traveler-fit decisions it does not directly prove.