# Nonthaburi (นนทบุรี)

Nonthaburi is modeled as: Ko Kret / river day-trip / Bangkok-adjacent stay. Static copy should foreground traveler decisions and avoid live claims.

- Province: Nonthaburi
- Recommended page status: support node only
- Merge recommendation: Keep under Bangkok metro
- Data confidence: high

## Quick call

- Best for: Ko Kret, river day-trip, Bangkok-adjacent stay
- Avoid if: indistinct from Bangkok for most travelers
- Best months: November–February unless the page-specific season window states otherwise.

## Best bases

| Area | Best for | Watch outs | Transport logic | Walkability or spread | Caveat |
| --- | --- | --- | --- | --- | --- |
| Nonthaburi core / main access area | specific-purpose support trips | not a broad standalone base | road/transit-dependent | spread unless local core is defined | rain/AQI/traffic should be live checked |

## Season windows

- Best: November–February
- Acceptable with caveats: March–May heat, May–October rain-aware travel
- High risk: indistinct from Bangkok for most travelers

## Nearby pivots and route role

- Nearby pivots: 
- Route roles: Ko Kret / river day-trip / Bangkok-adjacent stay
- Arrival modes: road/bus/van, rail/airport/ferry where relevant

## Keep static

- page status
- merge/split logic
- seasonal caveats
- base-area logic

## Do not hardcode

- daily weather
- AQI
- transport schedules
- event dates
- prices

## 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: 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.

## Source candidates

| Source | Type | Why it matters | Supports |
| --- | --- | --- | --- |
| TAT Nonthaburi | official | Bangkok-adjacent/river identity | static copy |

## Product links

- Nonthaburi is in the research package, but it does not yet have a dedicated live traveler page in the current public product.

## 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/
