Religion, culture, and heritage

OpenStreetMap Thailand temple POIs.

Geospatial enrichment for amenity=place_of_worship, religion=buddhist, building=temple, historic=ruins, tourism=attraction, names, aliases, opening_hours, website, accessibility, polygons, and nearby access.

Public OSM/Overpass API and OSM extracts Free open data under ODbL attribution/share-alike terms Weekly for national index; daily or weekly for high-tourism areas Open source

Runtime role

Catalog only

Access class

Public

Access type

OSM/Overpass API and OSM extracts

Free status

Free open data under ODbL attribution/share-alike terms

Cadence

Weekly for national index; daily or weekly for high-tourism areas

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

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

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 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

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

Developer reference

Best endpoint

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.

Recommended refresh

Refresh daily, or more often only when the source publishes explicit current-status fields.

Travel scoring role

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.

Comparable / backup source

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://overpass-turbo.eu/" -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.
Dashboard markup or public-page layout can change without notice.
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.