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. |
|---|
What to confirm before booking
Some lodging details are stable, while availability, prices, policies, and property rules can change. Confirm the changeable details before booking.
What to confirm before booking
| Rule | How to use it |
|---|
| Stable planning context. | 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 |
|---|
| Confirm before booking. | 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 booking check. | 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. |
|---|
| Useful planning checks. | How to use it: town/river/Sai Yok/Erawan base chooser / rail/park/weather check |
|---|
Named-stay source notes
These stay examples help compare areas and trip styles. Confirm current details with each property before booking.
U Inchantree Kanchanaburi
Source type: official hotel
Why it is here: town/bridge base anchor
Review themes to verify live: bridge view, river terrace, boutique rooms, town accessibility
Primary source Review or catalog signal
The FloatHouse River Kwai
Source type: official hotel
Why it is here: river nature base / route-friction warning
Review themes to verify live: floating villas, river swimming, boat/road logistics
Primary source Review or catalog signal
River Kwai Jungle Rafts
Source type: official hotel
Why it is here: niche high-friction stay card
Review themes to verify live: floating bamboo lodge, no electricity concept, Mon/local cultural context, boat-only access
Primary source Review or catalog signal
Hintok River Camp @ Hellfire Pass
Source type: official hotel
Why it is here: route-specific base card
Review themes to verify live: glamping tents, natural pool, Hellfire Pass route
Primary source Review or catalog signal
Airbnb / vacation rental / serviced-apartment pattern
Source type: booking-platform listing; verify directly with the property
Why it is here: confirm property status, booking terms, and building rules directly
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.