Best use for travel intelligence
For travel decisions, temple data separates legal Buddhist wat identity from shrines, ancient ruins, royal temples, tourist attractions, and mapped POIs so visitors get the right page, etiquette, opening, and route context.
Official / agency sources
7 of 14 sources look official or agency-backed.
API/feed candidates
11 sources expose API, feed, CKAN/DataStore, JSON, XML, or similar machine-readable access.
Near-real-time signals
1 sources have live, hourly, event-driven, warning, or frequent update language.
Developer note
Use ONAB as the wat identity spine, DRA for religious-site fields, Fine Arts for ancient monuments, TAT/DASTA for tourist/community metadata, OSM for coordinates, and Wikidata/Commons for IDs and media.
Last checked and source confidence
Last checked: 2026-05-11.
Source confidence: This cluster is strongest when several sources describe the same traveler problem from different angles: official context, machine-readable feeds, and slower fallback documentation.