Weather, environment, and disasters

NASA FIRMS.

MODIS/VIIRS fire and thermal anomaly data filterable to Thailand.

Free registration API, CSV, WMS Free public; API key may be required Near real time Open source
Runtime role

Catalog only

Access class

Free registration

Access type

API, CSV, WMS

Free status

Free public; API key may be required

Cadence

Near real time

Last verified

2026-05-11

Access class note

Publicly reachable, but account creation, an API key, or registration flow may be required.

Used in layers

page reference only

Useful fields

hazard type, severity/status, affected area, geometry/layer, timestamp, warning text, sensor/source, update time

Reliability rating

High for official context; validate endpoint availability before automation.

Runtime truth

Runtime role

Catalog only

Production ready

Not yet

Entity scope

No runtime entity scope yet.

Observation scope

No live observation ingestion yet.

Decision scope

Not wired into active decisions yet.

Runtime note

Profiled in the atlas and public pages, but not yet connected to live graph computation.

How this helps travel recommendations

Adds flood, fire, drought, earthquake, tsunami, hotspot, and disaster context when a route, coast, road, or outdoor plan could become unsafe or unrealistic.

Developer reference

Best endpoint

Use official disaster feeds, hazard APIs, WMS/WFS layers, or event feeds; keep geometry and severity separate from the text summary.

Recommended refresh

Refresh every 15-60 minutes, with caching and backoff when the upstream fails.

Travel scoring role

Adds flood, fire, drought, earthquake, tsunami, hotspot, and disaster context when a route, coast, road, or outdoor plan could become unsafe or unrealistic.

Comparable / backup source

GISTDA, DDPM, GDACS, NASA FIRMS, USGS, TMD earthquake feeds, Thaiwater, and local authority announcements.

Example request

# Verify the documented disaster endpoint before production use.
curl -L "https://firms.modaps.eosdis.nasa.gov/" -H "Accept: application/json"

Failure modes

  • Hazard layers can be geospatial, tiled, or projection-specific.
  • Event feeds may lag official local announcements.
  • Dashboard-only layers may change markup or token behavior.
  • Free registration, keys, or rate limits can interrupt automated refresh.
  • Batch files can change schema, naming, encoding, or publication cadence.
  • Geospatial layers can be large, tiled, or projection-specific.

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.