# Bangkok (กรุงเทพมหานคร)

Bangkok is modeled as: arrival hub, stay-area choice, food, gold/shopping, rail/air pivot. Static copy should foreground traveler decisions and avoid live claims.

- Province: Bangkok
- Recommended page status: first-class destination
- Merge recommendation: Do not merge; use metro provinces as related nodes
- Data confidence: high

## Quick call

- Best for: arrival hub, stay-area choice, food, gold, shopping
- Avoid if: AQI, heat, rain flooding, event crowding are live signals
- Best months: November–February

## Best bases

| Area | Best for | Watch outs | Transport logic | Walkability or spread | Caveat |
| --- | --- | --- | --- | --- | --- |
| Sukhumvit / Asok–Phrom Phong | rail access, hotel depth | traffic and generic mall-hotel feel | BTS/MRT | linear/compact rail corridor | rain/AQI |
| Silom / Sathorn | business, river access, BTS/MRT | office traffic | BTS/MRT/river | compact corridors | rain/AQI |
| Riverside / Old City | heritage, temples, river hotels | weaker late-night rail | boat/road/MRT mix | spread | river/rain sensitivity |

## Season windows

- Best: November–February
- Acceptable with caveats: March–May heat; May–October rain if transit-flexible
- High risk: bad-air episodes; heavy rain/flood advisories; major festival/event dates

## Nearby pivots and route role

- Nearby pivots: Nonthaburi, Samut Prakan, Ayutthaya, Kanchanaburi, Pattaya
- Route roles: primary air gateway, rail hub, bus/van hub, gold-buying live-price node
- Arrival modes: Suvarnabhumi Airport, Don Mueang Airport, SRT rail, intercity bus/van, river boat

## Keep static

- base-area logic
- route role
- seasonal risk bands
- gold-price source identity

## Do not hardcode

- AQI
- daily rain
- event crowding
- gold price
- train/bus schedules

## Static decision signals

- today signal: Do not hardcode; use TMD, Air4Thai/PCD, transport and event feeds where relevant.
- weather risk: Use seasonal static framing only; daily weather is a future live signal.
- aqi risk: Live-check via Air4Thai/PCD where station coverage exists; especially relevant in dry/smoke season.
- transport friction: Treat route timing, transfer spread and public transport schedules as live or semi-live.
- food signal: Use as static food-route positioning only when supported by official/local source candidates.
- crowd level: Do not hardcode current crowding; express event/weekend sensitivity as static risk.
- comfort penalties: heat, rain, AQI where relevant, event/crowd pressure, route spread

## Specialist angles

- Food angle: High-confidence food-route city; build neighborhood route widgets rather than attraction copy.
- Culture angle: Old-city, river, museum and temple routes; event calendar should be live.
- Shopping / gold / gem angle: Gold-buying check should be live-price/shop-trust using Gold Traders Association pricing and static Yaowarat context.

## Source candidates

| Source | Type | Why it matters | Supports |
| --- | --- | --- | --- |
| TAT Bangkok | official | official destination identity | static copy |
| Visit Bangkok | official | city tourism/event surface | future signal |
| Suvarnabhumi Airport | official | airport route evidence | route-check |

## Product links

- [Open current traveler page](https://enjoythai.land/where-to-go/bangkok/)
- [Open food guide](https://enjoythai.land/food/bangkok-food-guide/)
- [Open stay guide](https://enjoythai.land/accommodation/bangkok/)

## Raw package links

- https://enjoythai.land/research/cities/files/city_research_packets.json
- https://enjoythai.land/research/cities/files/city_strategy_matrix.csv
- https://enjoythai.land/research/cities/files/source_appendix.csv
- https://enjoythai.land/research/cities/