How to combine location evidence without inventing a risk score

Keep geographic identity, historical events, terrain summaries and place references as separate evidence records. They differ in scale, time and meaning. A transparent decision matrix preserves those differences instead of presenting an unsupported combined risk number.

Procedure

  1. Verify one location and record coordinate uncertainty and district identifier.
  2. For every layer retain source, licence, spatial scale, observation period and coverage status.
  3. List findings and missing dependencies separately, then send material decisions to the responsible reviewer.

Interpretation checks

Input or conditionHow to interpret it
Administrative identityWhich reference geography contains the location.
Historical footprintWhat was observed for particular archive events.
Terrain and placesRegional elevation and mapped context, with different scales.

Illustrative working example

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

evidence = [
    {"layer": "terrain", "scale": "district", "observed_at": None},
    {"layer": "flood-history", "scale": "event-extent", "observed_at": None}
]
# Preserve each evidence record; do not average unlike measures.

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/terrain?bbox=100.3%2C14.1%2C100.8%2C14.6&limit=100'

Useful output and decision limits

An auditable evidence matrix for site review, insurance research or property due diligence. It is not a validated risk model or a substitute for professional review.

Datasets, coverage and source contracts

Place search

Coverage
Thailand
Publication cadence
Versioned releases; no fixed public cadence
Freshness policy
Historical or versioned data; no real-time freshness claim
Dataset limits
Places derive from OpenStreetMap and vary in completeness by area. Treat names as display data and join on stable ids.

Related customer workflows