How to interpret Thailand historical flood extents

A published satellite extent records an observed event footprint. An overlap is evidence for that observation; no overlap cannot establish that a location has never flooded. The MapScale archive is historical and fixed, not a forecast.

Procedure

  1. Fix the asset coordinates and retain the positional uncertainty.
  2. Retrieve a bounded archive view and inspect its dates, sources and truncation before spatial comparison.
  3. Record each event overlap separately and commission additional records when a financial decision needs a complete history.

Interpretation checks

Input or conditionHow to interpret it
OverlapObserved footprint intersects the location for a named event.
No overlapNo matching extent in the returned archive; not a dry-history certificate.
Truncated responseContinue the returned cursor before treating the request as complete.

Illustrative working example

Code illustrates a review procedure, not an observed result. Replace illustrative inputs with verified records; missing values deliberately remain unknown.

review = {"historical_overlap": None, "event_date": None}
# None = not yet evaluated, never evidence of zero flood risk.
# Record observation date and extent before assigning overlap.

Bounded API request

Read-only public request, limited to 100 features. Check HTTP status, freshness and pagination before interpreting the result. Foundation layers use their dedicated APIs; this is not a bulk database export.

curl --fail 'https://api.mapscale.io/v1/public/atlas/layers/flood-history?bbox=98.75%2C18.5%2C99.25%2C19&limit=100'

Useful output and decision limits

An event-by-event overlap register with observation dates and missing-history notes. It is not an actuarial probability, depth estimate or insurance quote.

Datasets, coverage and source contracts

Related customer workflows