Industrial site screening with Thailand geographic data

Compare candidate factory sites using terrain, mapped waterways, place context and historical flood evidence before commissioning site surveys.

How can a factory shortlist sites before a detailed survey?

Use the same geographic evidence checklist for every candidate site: district terrain, mapped waterways, historical flood observations and nearby mapped places. This makes missing evidence visible before engineers conduct drainage, utility and access surveys.

Review workflow

  1. Supply your own candidate-site polygons or coordinates; the public catalog is not a registry of licensed factories.
  2. Compare district elevation summaries and mapped waterways, noting that neither gives finished-floor height or drainage capacity.
  3. Check available historical flood extents and inspect mapped access context; obtain actual truck-access and utility constraints from the site operator.
  4. Build a survey shortlist based on documented evidence and unknowns, then commission parcel surveys and engineering review.

What to produce

A site comparison matrix with regional terrain context, observed flood overlap, mapped waterways and questions for engineering inspection.

Available evidence and its limits
DatasetCoverage and cadenceSources and licencesLimitations
Terrain

Beta

Thailand district summaries

Static historical elevation model

Historical or versioned data; no real-time freshness claim

Copernicus DEM GLO-30 via Mapterhorn
Copernicus WorldDEM-30 Licence (commercial use permitted)

District-level elevation summaries sampled from Copernicus DEM GLO-30. They are regional context, not parcel or building elevation and not a flood-probability model.
Waterways

Beta

Mapped OpenStreetMap coverage in Thailand

Versioned releases; no fixed public cadence

Historical or versioned data; no real-time freshness claim

© OpenStreetMap contributors
ODbL 1.0

Rivers and streams derived from OpenStreetMap. Hydrography completeness varies by area and is not a flood-risk model.
Flood history

Beta

Published UNOSAT observation extents in Thailand

Fixed historical archive

Historical or versioned data; no real-time freshness claim

UNOSAT / United Nations Satellite Centre (Thailand flood extents)
CC BY-SA (UNOSAT; verified in HDX catalog)

A fixed archive of historical satellite flood-extent observations (UNOSAT). It is not a real-time flood map, and absence of an extent is not evidence that an area stayed dry.
Place search

Stable

Thailand

Versioned releases; no fixed public cadence

Historical or versioned data; no real-time freshness claim

© OpenStreetMap contributors
ODbL 1.0

Places derive from OpenStreetMap and vary in completeness by area. Treat names as display data and join on stable ids.

Questions this data cannot answer

Live factory registers, industrial-estate occupancy, utility capacity, environmental permits and parcel elevations are not available in this catalog. Mapped places may be incomplete and cannot verify an operating factory.

Try a bounded data request

Read-only, no key required, limited to 100 features in the stated viewport. An empty response can indicate missing coverage. Read the response timestamps, sources and status before use.

curl --fail-with-body 'https://api.mapscale.io/v1/public/atlas/layers/terrain?bbox=101%2C12.6%2C101.5%2C13.1&limit=100'

Terrain →

Foundation API documentation →

Relevant geographic context

Inspect source-backed public examples

Use these references to inspect source identity, timestamps and limits. They do not establish coverage for every location in your project.

Prepare a pilot with your team

For a site-comparison pilot, provide candidate locations, truck-access questions and the source dates you need. Agree one matrix that exposes missing evidence consistently; verify estate identity and operator claims separately.

Scope a data pilot with MapScale →

Workflow documentation by MapScale, using the linked dataset contracts for sources and limitations. Report source discrepancies through our contact channel. Your team remains responsible for domain review and approval.