Tourism and travel

Provincial hotel registration GDC cluster.

Fragmented provincial evidence for registered hotels and licensed accommodation counts or lists. Useful as a registered-accommodation confidence cluster, not as a single national hotel-license API, live availability feed, room inventory source, or quality rating.

Free registration Government Data Catalog search cluster with province-level hotel-registration and licensed-accommodation CSV/XLSX datasets Free public catalog access where provincial resources remain published Annual / provincial release schedule Open source
Runtime role

Catalog only

Access class

Free registration

Access type

Government Data Catalog search cluster with province-level hotel-registration and licensed-accommodation CSV/XLSX datasets

Free status

Free public catalog access where provincial resources remain published

Cadence

Annual / provincial release schedule

Last verified

2026-05-11

Access class note

Publicly reachable, but account creation, an API key, or registration flow may be required.

Used in layers

page reference only

Useful fields

property or place name, lodging type, neighborhood or area, lat/lon, address, phone, website, star/category signals where available, brand/operator where available, room/rate policy only when authorized, cancellation notes, review/rating context, source ID

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

Turns accommodation into source-backed decisions about the right area to stay, whether the hotel type matches the trip, what transport or flood/noise/AQI friction exists around the base, and which source can actually prove map, legal, or commercial details.

Endpoint and API notes

Fragmented provincial evidence for registered hotels and licensed accommodation counts or lists. Useful as a registered-accommodation confidence cluster, not as a single national hotel-license API, live availability feed, room inventory source, or quality rating.

Open the source endpoint or documentation. Return to the Thailand data atlas.

Developer reference

Best endpoint

Use TAT and official tourism accommodation statistics for destination depth, DBD for operator identity, OSM and Google for map and place enrichment, and commercial partner feeds only when you need live room, rate, cancellation, or inventory fields.

Recommended refresh

Check weekly for change detection, but treat the official publication period as the real cadence.

Travel scoring role

Turns accommodation into source-backed decisions about the right area to stay, whether the hotel type matches the trip, what transport or flood/noise/AQI friction exists around the base, and which source can actually prove map, legal, or commercial details.

Comparable / backup source

TAT, MOTS accommodation statistics, OSM, Google Places, Booking partner data, Agoda context, Open DBD, and local destination pages with explicit source confidence.

Example request

# Source landing/download page; inspect linked resources before automation.
curl -L "https://gdcatalog.go.th/en/dataset/?tags=%E0%B9%82%E0%B8%A3%E0%B8%87%E0%B9%81%E0%B8%A3%E0%B8%A1"

Failure modes

  • There is no single public national Thailand hotel-inventory API.
  • Map and review sources do not prove legal operating status or licensing.
  • Legal-entity records do not prove each branch or room product.
  • Rates, cancellation rules, occupancy, and room availability are usually commercial or partner-only data.
  • Flood, AQI, traffic, and nightlife risk are area questions that room-level feeds often do not answer.
  • Free registration, keys, or rate limits can interrupt automated refresh.
  • Batch files can change schema, naming, encoding, or publication cadence.

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.