Catalog only
Geospatial and satellite
Google Earth Engine public catalog.
Satellite and geoscience datasets filterable to Thailand.
Commercial
Earth Engine API
Free for eligible noncommercial/research use
Varies; many datasets update daily
2026-05-11
Usually needs payment, partner approval, or a commercial agreement before production use.
page reference only
layer name, geometry type, CRS/projection, bounding box, feature attributes, resolution/scale, update date
Medium-high for discovery and context; operational reliability depends on endpoint stability.
Runtime truth
Catalog only
Not yet
No runtime entity scope yet.
No live observation ingestion yet.
Not wired into active decisions yet.
Profiled in the atlas and public pages, but not yet connected to live graph computation.
How this helps travel recommendations
Improves map context, nearby pivots, route geography, protected-area context, coast exposure, and destination coverage.
Endpoint and API notes
Satellite and geoscience datasets filterable to Thailand.
Open the source endpoint or documentation. Return to the Thailand data atlas.
Developer reference
Use OGC services, GeoJSON, SHP, STAC, PBF, or documented feature layers; record CRS, geometry type, and update date.
Refresh daily, or more often only when the source publishes explicit current-status fields.
Improves map context, nearby pivots, route geography, protected-area context, coast exposure, and destination coverage.
OpenStreetMap, Geofabrik, GISTDA, HDX, WorldPop, Protected Planet, Open Development Thailand, and official boundary layers.
Example request
# Verify the documented geospatial endpoint before production use.
curl -L "https://developers.google.com/earth-engine/datasets" -H "Accept: application/json"
Failure modes
- Large layers can be slow or tiled.
- CRS/projection mismatches can break maps.
- Feature names and boundaries can vary across sources.
- 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.