enjoythai.land

Geospatial and satellite

OpenStreetMap Thailand.

Roads, buildings, POIs, land use, and map features.

Public OSM API/bulk via mirrors Free public under ODbL Continuous Open source
Runtime role

Catalog only

Access class

Public

Access type

OSM API/bulk via mirrors

Free status

Free public under ODbL

Cadence

Continuous

Last verified

2026-05-11

Access class note

Public web, file, catalog, or documented endpoint access with no paid gate implied in the source profile.

Used in layers

page reference only

Useful fields

route, station, stop, airport, operator, schedule, delay/incident, traffic count, accident count, timestamp

Reliability rating

Medium-high for discovery and context; operational reliability depends on endpoint stability.

Runtime truth

Runtime role

Catalog only

Production ready

Not yet

Entity scope

No runtime entity scope yet.

Observation scope

No live observation ingestion yet.

Decision scope

Not wired into active decisions yet.

Runtime note

Profiled in the atlas and public pages, but not yet connected to live graph computation.

How this helps travel recommendations

Estimates how hard a destination is to reach, whether a short pivot is realistic, and which transport leg can break the itinerary.

Developer reference

Best endpoint

Separate static network data from live incidents and schedules; do not treat route geometry as current service availability.

Recommended refresh

Refresh every 15-60 minutes, with caching and backoff when the upstream fails.

Travel scoring role

Estimates how hard a destination is to reach, whether a short pivot is realistic, and which transport leg can break the itinerary.

Comparable / backup source

MOT, DLT, SRT, DOH, CAAT, AOT, ThaiRSC, OSM, official operators, and local advisories.

Example request

# Verify the documented transport endpoint before production use.
curl -L "https://www.openstreetmap.org/" -H "Accept: application/json"

Failure modes

  • Schedules and service status can be stale.
  • Dashboards may not expose clean APIs.
  • Route data often lacks real availability or disruption context.

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.