Catalog only
Transport
OpenStreetMap Thailand bus stops and route relations.
Crowdsourced highway=bus_stop, amenity=bus_station, public_transport platforms/stations, route=bus relations, route_master=bus, operator, network, ref, and stop facility hints.
Public
OSM/Overpass API and OSM extracts
Free open data under ODbL attribution/share-alike terms
Daily or weekly; minutely diffs possible
2026-05-11
Public web, file, catalog, or documented endpoint access with no paid gate implied in the source profile.
page reference only
agency, route_id, stop_id, stop name, station type, lat/lon, trip_id, stop_times, route shape, fare, operator, terminal owner, timetable, service days, source license
Medium-high for discovery and context; operational reliability depends on endpoint stability.
Runtime truth
Catalog only
Not yet
No runtime entity scope yet.
No live observation ingestion yet.
Not wired into active decisions yet.
Profiled in the atlas and public pages, but not yet connected to live graph computation.
How this helps travel recommendations
Turns bus travel from vague advice into station, route, timetable, terminal, and confidence logic for Bangkok pivots, intercity routes, and lower-cost overland itineraries.
Endpoint and API notes
Crowdsourced highway=bus_stop, amenity=bus_station, public_transport platforms/stations, route=bus relations, route_master=bus, operator, network, ref, and stop facility hints.
Open the source endpoint or documentation. Return to the Thailand data atlas.
Developer reference
Use Namtang GTFS as the route/stop spine, MOT passenger bus terminals as the official terminal master, BKS timetable/facility resources for intercity context, and OSM/Transitland as validation layers.
Refresh every 15-60 minutes, with caching and backoff when the upstream fails.
Turns bus travel from vague advice into station, route, timetable, terminal, and confidence logic for Bangkok pivots, intercity routes, and lower-cost overland itineraries.
MOT, DLT, Namtang/OTP, Transport Co./BKS, BMTA, Thai Smile Bus, OpenStreetMap/Overpass, Transitland, Mobility Database, and official operator pages.
Example request
# Verify the documented bus endpoint before production use.
curl -L "https://overpass-turbo.eu/" -H "Accept: application/json"Failure modes
- Static GTFS does not mean realtime vehicle positions.
- App-visible realtime is not automatically a public ingest API.
- Station coordinates and X/Y labels need validation.
- Intercity timetable pages can be brittle without documented JSON APIs.
- Commercial booking inventory usually requires partner access.
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.