City research brief

Kanchanaburi (กาญจนบุรี)

Kanchanaburi is modeled as: river/rail/history/nature base. Static copy should foreground traveler decisions and avoid live claims.

Quick call

river, rail, history, nature base

town, Sai Yok, Erawan distance makes base choice material

November–February unless the page-specific season window states otherwise.

first-class destination

These are the base choices that should replace generic one-size-fits-all city copy.

Best bases
Area	Best for	Watch outs	Transport logic	Walkability or spread	Caveat
Town / River Kwai Bridge	rail/history/food	not deep nature	rail/road	semi-compact	heat
Riverfront resorts	slow stays and families	needs transfers	road	spread	river/rain
Sai Yok / Nam Tok	nature and rail extension	far from town	rail/road	spread	rain-road risk

Use static season framing to narrow the trip shape, then let daily weather, AQI, ferries, and events stay live.

Season windows
Window	Guidance
Best	November–February
Acceptable with caveats	March–May heat, May–October rain-aware travel
High risk	town, Sai Yok, Erawan distance makes base choice material

Decision families: today; where-to-stay; route-check; food-route
Today signal: Do not hardcode; use TMD, Air4Thai/PCD, transport and event feeds where relevant.
Transport friction: Treat route timing, transfer spread and public transport schedules as live or semi-live.
AQI risk: Live-check via Air4Thai/PCD where station coverage exists; especially relevant in dry/smoke season.

Food angle: Support food-route only if official/local market/food sources are added.
Culture angle: Use official TAT/provincial/heritage sources; avoid attraction listicles.
Shopping / gold / gem angle: No primary static vertical unless separately listed.

These sources back the packet even when they are not all wired into live observations yet.

Source candidates
Source	Type	Why it matters	Supports
TAT Kanchanaburi	official	road/rail/accessibility and province identity	static copy