Catalog only
Religion, culture, and heritage
DOPA religious and important-place geospatial datasets.
Administrative and important-place datasets useful for province/district/subdistrict reconciliation, official place names, LAT/LONG, and ancient/religious-place context.
Public
JSON/XLS/geospatial resources where exposed through government catalogs
Free public/open catalog resources where published
Monthly or quarterly
2026-05-11
Public web, file, catalog, or documented endpoint access with no paid gate implied in the source profile.
page reference only
temple code, official Thai name, English/common name, aliases, religion, sect/nikaya, temple type, royal status, active/abandoned/ruin status, establishment date, wisungkhamsima, province, district, subdistrict, postal code, coordinates, heritage status, tourism category, opening hours, source IDs
High for official context; validate endpoint availability before automation.
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 temple planning into source-backed identity, heritage, visitor-friction, etiquette, weather/AQI, crowd, and nearby-route decisions instead of a loose list of famous places.
Endpoint and API notes
Administrative and important-place datasets useful for province/district/subdistrict reconciliation, official place names, LAT/LONG, and ancient/religious-place context.
Open the source endpoint or documentation. Return to the Thailand data atlas.
Developer reference
Use ONAB as the Buddhist wat identity spine, DRA for public religious-site fields, Fine Arts for ancient monuments and ruins, TAT/DASTA for tourist/community metadata, OSM for coordinates and polygons, and Wikidata/Commons for global IDs and images.
Check weekly for change detection, but treat the official publication period as the real cadence.
Turns temple planning into source-backed identity, heritage, visitor-friction, etiquette, weather/AQI, crowd, and nearby-route decisions instead of a loose list of famous places.
ONAB, DRA, Fine Arts Department, TAT, DASTA, Ministry of Culture, DOPA/GDC, OpenStreetMap/Overpass, Wikidata, Wikimedia Commons, and carefully licensed commercial POI enrichment for top temples only.
Example request
# Verify the documented temple endpoint before production use.
curl -L "https://gdcatalog.go.th/" -H "Accept: application/json"
Failure modes
- A legal Buddhist wat, abandoned wat, ancient ruin, shrine, church, mosque, and tourist attraction are not the same entity type.
- Thai temple names repeat often, so name-only matching is unsafe.
- Legal registries can lack coordinates, while map/POI sources can lack legal status.
- Tourist opening hours and reviews are usually commercial or social enrichment, not canonical public data.
- Royal, active, abandoned, and heritage classifications can conflict across sources.
- Batch files can change schema, naming, encoding, or publication cadence.
- Geospatial layers can be large, tiled, or projection-specific.
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.