Tourism and travel

DNP Tourism Datasets.

Department of National Parks tourism, attraction, fee, and visitor datasets useful for park-access context, seasonal closure notes, and conservation-area planning. Treat as park and attraction support data unless a stable daily operational closure feed is verified.

Public Public catalog resources, CSV, and API-style downloads where exposed Free public where open Monthly or periodic depending on park, attraction, fee, and visitor dataset Open source
Runtime role

Decision driving

Access class

Public

Access type

Public catalog resources, CSV, and API-style downloads where exposed

Free status

Free public where open

Cadence

Monthly or periodic depending on park, attraction, fee, and visitor dataset

Last verified

2026-05-11

Access class note

Public web, file, catalog, or documented endpoint access with no paid gate implied in the source profile.

Used in layers

source health, observation ingest, signal compute, decision compute

Useful fields

destination, attraction, accommodation, route, event, arrival count, survey period, source agency, update date

Reliability rating

Medium: useful public signal, but extraction can depend on dashboard or agency publishing patterns.

Runtime truth

Runtime role

Decision driving

Production ready

Yes

Entity scope

destination, attraction, hotel_area, route, venue_zone

Observation scope

park_access_context_score

Decision scope

where_to_go_today, route_check

Runtime note

Feeds active observations and signals that currently influence traveler-facing decisions.

How this helps travel recommendations

Helps estimate attraction depth, accommodation base, seasonality, demand pressure, events, and whether a destination has enough support for a traveler type.

Endpoint and API notes

Department of National Parks tourism, attraction, fee, and visitor datasets useful for park-access context, seasonal closure notes, and conservation-area planning. Treat as park and attraction support data unless a stable daily operational closure feed is verified.

Open the source endpoint or documentation. Return to the Thailand data atlas.

Developer reference

Best endpoint

Use official tourism APIs/catalog data for attractions, hotels, routes, events, and statistics; treat slow statistics as context, not live demand.

Recommended refresh

Check weekly for change detection, but treat the official publication period as the real cadence.

Travel scoring role

Helps estimate attraction depth, accommodation base, seasonality, demand pressure, events, and whether a destination has enough support for a traveler type.

Comparable / backup source

TAT, AOT, CAAT, OSM POIs, tourism statistics, events calendars, and destination editorial notes.

Example request

# Source landing or publication page; inspect linked documents or resources before automation.
curl -L "https://data.go.th/th/organization/dnp"

Failure modes

  • Tourism stats can lag.
  • Attraction lists can be incomplete or marketing-oriented.
  • Events and opening status may change faster than catalogs.
  • Batch files can change schema, naming, encoding, or publication cadence.

Last checked and source confidence

Last checked: 2026-05-11.

Source confidence: Treat this profile as strongest for the exact role named above. It is weaker when the source is stretched into live availability, legal proof, or traveler-fit decisions it does not directly prove.