DEVELOPER DOCUMENTATION

Spatial Automation Developer Guide

Understand workflow exports, processing-model steps and future edge execution contracts.

Browser-based GISGeoAI + spatial analyticsSouth African context
GUIDE

Triggers

Use manual, workspace-open, interval or layer-change triggers. Automatic browser triggers only run while Studio is open and must be armed for the session.

GUIDE

Processing

Workflows can load project layers, filter features, calculate fields, summarise values or invoke saved Processing Models.

GUIDE

Delivery

Publish the resulting FeatureCollection to GeoLayers, send an HTTPS webhook or notify the user.

GUIDE

Auditability

Run History records trigger reason, duration, result counts, step evidence and failures so the workflow can be reviewed.

IMPLEMENTATION CHECKLIST

Before you move to production

Use this checklist to reduce avoidable integration problems.

  • Test the workflow with a small, known dataset before increasing scale.
  • Keep production credentials outside public source code and downloadable configuration files.
  • Handle network, validation and rate-limit errors explicitly in the client or service.
  • Record the collection, endpoint, version or workflow configuration used so the integration can be reproduced.
NEXT STEP

Continue with a practical integration

Use the related documentation pages to move from concept to a tested development workflow.

API

REST API

Review endpoint and authentication concepts.

Explore →
SDK

JavaScript SDK

Use typed client helpers in an application.

Explore →

Automation

Connect spatial workflows to integrations.

Explore →