Earth SAT Data
Home › Technical Guides › Cloud Delivery & APIs
Cloud Delivery & APIs

GIS and REST API Integration: STAC, WMTS, and Webhook Pipelines

Wire unified satellite catalogs into ArcGIS Pro, QGIS, and production apps with REST search, webhook order events, and COG streaming.

Connecting REST Search, Ordering, and Webhook Events

Earth SAT Data BUILD exposes an OpenAPI 3.1 REST API across 700+ sensors using three core endpoints: `GET /v1/search` to query geometry, date, resolution, and clouds; `POST /v1/orders` for fixed-price archive or tasking purchases; and `GET /v1/deliveries` for signed COG links.

Rather than polling endlessly, services register HTTPS webhooks that receive signed delivery events the moment scenes pass QA.

  • Filter `/v1/search` by bbox, ISO-8601 dates, max GSD, and cloud percentage.
  • Pass idempotency keys on `POST /v1/orders` to prevent duplicate billing.
  • Verify webhook HMAC signatures and test workflows against a sandbox.

OGC Streaming Standards: WMS, WMTS, and Direct COG

In ArcGIS Pro and QGIS, OGC WMTS and WMS deliver fast cached 8-bit RGB pyramids for visual basemaps, whereas direct COG streaming via GDAL `/vsicurl/` preserves raw 16-bit multi-band values for spectral classification.

  • WMTS / OGC API - Tiles: Fastest CDN-cached visual basemap pyramids.
  • WMS: Server-side dynamic reprojection and band rendering.
  • Direct COG: Raw 16-bit quantitative pixel arrays streamed on demand.

Optimizing Pagination, Retries, and Memory in Python SDKs

Large catalog queries require cursor pagination, exponential backoff on HTTP 429/503 responses, and exact GeoJSON overlap checks before ordering. In `rasterio`, streaming windowed chips prevents holding giant mosaics in RAM.

Bridging Developers and GIS Analysts in One Workspace

Pairing BUILD APIs with MAP GIS add-ins and HUB storage ensures engineers and analysts share the exact same catalog state and projections.

Geospatial Integration Protocol Comparison

Protocol / PatternData Type DeliveredLatency & CachingBest Integration Target
REST Search + COG URLRaw 16-bit multi-band rastersOn-demand Range readsPython ML pipelines, rasterio, custom analytics
OGC WMTS / OGC API TilesStyled 8-bit PNG/WebP/JPEG tilesCDN-cached; < 50 msWeb dashboards, ArcGIS Pro & QGIS basemaps
OGC WMSServer-rendered map imagesDynamic render; 200–800 msLegacy GIS portals needing dynamic EPSG
STAC API (CQL2)Standardized scene JSON metadata< 100 ms query responseMulti-provider discovery & automated triggers
Order WebhooksEvent JSON + signed asset linksEvent-driven pushZero-polling backend fulfillment pipelines

Persist STAC metadata in your database and mirror critical COGs to durable storage before signed URL TTLs expire.

Worked Illustration: Sizing Weekly API Pagination and Streaming Memory

A pipeline monitors 1,200 km² weekly with 3 m 4-band uint16 imagery. A search returns 240 candidates (50/page), and 18 intersecting clipped COGs (40 MiB compressed / 80 MiB uncompressed each) are ordered.

  1. Search pagination calls: ceil(240 / 50) = 5 HTTP GET requests.
  2. Filter 18 intersecting scenes (< 10% cloud) and submit `POST /v1/orders`.
  3. Weekly compressed egress: 18 scenes x 40 MiB = 720 MiB (~0.70 GiB/week).
  4. Peak worker RAM at 4x concurrency (2x decode buffer): 4 x 80 MiB x 2 = 640 MiB.

Calculated Result & Takeaway: Weekly monitoring takes 5 search calls, transfers 720 MiB of compressed COGs, and peaks at ~640 MiB worker RAM.

Production Geospatial API & GIS Integration Checklist

  • Store API keys in environment secrets and test in sandbox mode first.
  • Check true GeoJSON polygon overlap instead of relying on bbox hits.
  • Implement exponential backoff for HTTP 429 and transient 5xx responses.
  • Use signed HTTPS webhooks instead of polling loops for deliveries.
  • Stream COGs via /vsicurl/ or rasterio windows rather than full downloads.
  • Log STAC Item IDs and order IDs alongside every downstream output.

Frequently Asked Questions

Should I use WMS or WMTS inside ArcGIS Pro?

Use WMTS for fast cached visual basemaps and direct COG streaming when analysts need raw 16-bit bands for spectral math.

How do I avoid ordering scenes whose bounding box barely clips my AOI?

Filter with exact GeoJSON polygon intersection and check fractional overlap area before ordering.

Why do signed COG URLs expire?

Short-lived pre-signed URLs protect cloud buckets; ingest on webhook arrival or refresh via `GET /v1/deliveries`.

Can one API query both optical and SAR sensors together?

Yes. Unified APIs like Earth SAT Data normalize optical, SAR, hyperspectral, and aerial metadata behind one OpenAPI 3.1 endpoint.

Primary References & Standards

  • OGC API - Features & OGC API - Tiles Core Specifications.
  • OpenAPI Initiative Specification v3.1.0.
  • GDAL /vsicurl/ & Rasterio Windowed I/O Documentation.

Related Technical Guides