Temple or religious-site page
Use as heat-exposed heritage-route stop; pair with old-city bike/tuk-tuk route logic.
Site call
Historical island / riverside
opening hours, ticket price, ceremony access, review rating/count
Before you book
This temple page is not claiming a page-specific current score. Use it as the static guide, then check Today, route, and comparison pages before paying for anything hard to change.
These fields keep a temple or religious-site page from flattening legal identity, heritage status, and tourist route role into one vague attraction card.
| Field | Value |
|---|---|
| Thai name | วัดใหญ่ชัยมงคล |
| Site type | historical temple ruin / active temple |
| Religion context | Buddhist / Thai temple |
| City | Ayutthaya |
| Province | Phra Nakhon Si Ayutthaya |
| Area | Ayutthaya Historical Park / old city area |
| Recommended public role | Anchor / popular |
Use this page as a route decision surface, not as a claim that every operational detail can be hardcoded.
| Layer | Guidance |
|---|---|
| Traveler decision use | Use as heat-exposed heritage-route stop; pair with old-city bike/tuk-tuk route logic. |
| Base-area relationship | Historical island / riverside |
| Access logic | Use as a route/base-area stop; exact hours, ticketing, closures and ceremony restrictions should be live-checked. |
| Etiquette and behavior | Temple etiquette: covered shoulders/knees, remove shoes where posted, avoid intrusive photography during worship, verify rules on active ceremony days. |
| Weather or AQI caveat | Open-air ruins amplify heat and rain; river/lowland flood risk should be a live signal. |
| Crowd or event pressure | Treat review counts, festival dates, ceremonies and long-weekend crowding as live signals. |
| Nearby food or market link | river prawn / old-city market route |
Temple pages can publish stable identity and route fit. They should not pretend that current hours, ticketing, or crowding are stable facts.
| Rule | How to handle it |
|---|---|
| Safe to keep static | identity / route role / approximate area/base relationship / long-run etiquette caveats |
| Must stay live | opening hours / ticket price / ceremony access / review rating/count / crowd level / exact traffic / daily weather/AQI |
| Review policy | live-review candidate; do not store static rating/count |
| Uncertainty | First-pass temple intelligence layer; validate exact address/coordinates/hours before publishing high-confidence widgets. |
These are the actual source roles behind the page. If they disagree, the contradiction should stay visible instead of being flattened away.
| Source | Type | Evidence level | Source note |
|---|---|---|---|
| Ayutthaya Historical Park | official | official individual or heritage-site source | Candidate for entity-seeds.json religious/culture route nodes; pair with today/weather/AQI and route-check widgets where city risk warrants. |
Use ONAB as the canonical 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.
# enjoythai.land Temple / Religious-site Static Policy Access date for source pass: 2026-05-15 ## Scope This package covers **temple and religious-heritage sites that are materially useful for traveler decisions** across the 31 requested city/town nodes. It is not a claim to enumerate every legally registered wat, shrine, mosque, church, meditation center, or monastery in each province. Thailand has too many local temples for that to be useful in a static destination layer. ## Static-safe fields