Authority order
Use this order when a destination looks tempting but the real risk lives in the base, hotel type, or booking layer.
Authority order
| Rank | Source layer |
|---|
| 1. | Source layer: Hotel area fit comes first: pick the right neighborhood or beach before comparing room prices. |
|---|
| 2. | Source layer: Official tourism-accommodation statistics and TAT context explain whether the destination has enough room depth, seasonality, and guest pressure for the trip style. |
|---|
| 3. | Source layer: OSM and Google hotel POIs help map real areas, walkability, nearby food, and transport friction. |
|---|
| 4. | Source layer: DBD hotel-operator records validate legal-entity context, not live room inventory or star quality. |
|---|
| 5. | Source layer: Booking and Agoda partner layers are for live rates, policies, reviews, and bookability only when authorized. |
|---|
Matching rules
Accommodation confidence gets worse when hotel POIs, legal operators, booking layers, and rental platforms are flattened into one generic claim.
Matching rules
| Rule | Meaning |
|---|
| 1. | Meaning: Same place ID or OSM ID is exact only within that source layer. |
|---|
| 2. | Meaning: Same hotel name plus same address plus nearby coordinates is a strong physical-property match. |
|---|
| 3. | Meaning: DBD company identity proves a legal operator, not every property, building, or room class. |
|---|
| 4. | Meaning: Tourism accommodation statistics describe destination depth and occupancy, not live room availability. |
|---|
| 5. | Meaning: Cancellation terms, room inventory, and guest reviews belong to commercial booking layers, not public registry layers. |
|---|
Static versus live treatment
The lodging package is strict about what can be written statically and what must stay live.
Static versus live treatment
| Rule | How to use it |
|---|
| Safe to publish statically. | How to use it: base-area role / route role / official hotel identity/source URL / approximate area / stable history/opening notes only when sourced / caveats / stay-guide priority |
|---|
| Must stay live. | How to use it: room availability / nightly price / user rating score / individual review count / Airbnb listing legality / condo/building rules / host license / cancellation policy / ferry/weather/event disruption / exact shuttle/transfer times |
|---|
| Rental policy. | How to use it: Do not static-publish individual Airbnb or vacation-rental listings. Use city-level patterns and require live checks for legality, host status, building rules, and cancellation terms. |
|---|
| Suggested widgets. | How to use it: old-town/gem-market/coast base chooser / gem-buying live checklist |
|---|
Named-stay source notes
These are the package-backed stay anchors and the source roles behind them.
Baan Luang Rajamaitri Historic Inn
Source type: official hotel
Why it is here: heritage old-town stay card
Review themes to verify live: historic house, riverfront, community-led old-town stay
Primary source
Chaanburi Boutique Resort
Source type: commercial-catalog-only
Why it is here: Chanthaburi car-base resort card
Review themes to verify live: colonial/Shino-Portuguese styling, pool, family-friendly resort feel
Primary source Review or catalog signal
Kasemsarn Hotel
Source type: official hotel
Why it is here: city-center practical stay
Review themes to verify live: central city base, practical access to old town and gem area
Primary source
Rimnaam Klangchan Hotel
Source type: official hotel
Why it is here: river hotel fallback
Review themes to verify live: river views, pool, city access
Primary source
Airbnb / vacation rental / serviced-apartment pattern
Source type: commercial-catalog-only / generated platform search
Why it is here: future accommodation live-signal / legal-caveat widget
Review themes to verify live: review counts, host status, building rules and cancellation terms are unstable
Primary source Review or catalog signal
Package and source files
Use the rendered stay guide first. Drop to the package layer only when you need the row-level lodging research, rental-policy note, or raw archive.
Source notes, if you want them
Use TAT and tourism-accommodation statistics for destination depth and occupancy context, OSM and Google for mapped stays and hotel-area discovery, DBD for legal operator identity, and commercial booking APIs only when you need live rates, cancellation terms, reviews, and room availability.