Geospatial Data Proxy
Feature page 05

Edit, create, and update geospatial data in place

Move beyond read-only access. The Geospatial Data Proxy supports transactional editing through Esri FeatureServer endpoints, WFS-T, and simplified GeoJSON transaction APIs backed by DuckDB.

The buyer problem

Read-only access is not enough

  • Field teams need to create and update features from mobile and web applications.
  • Existing Esri clients expect FeatureServer insert, update, and delete endpoints.
  • Standards-based workflows require WFS-T support that OGC API Features does not yet provide.
  • Building custom editing backends is expensive and hard to maintain.

Commercial promise

Full-lifecycle data management from one platform

The Geospatial Data Proxy extends its delivery layer with transactional editing so teams can create, update, and delete features through the same service boundary they already use for read access, catalogs, and analytics.

Editing surfaces

Three transaction interfaces cover the broadest range of client ecosystems.

Esri FeatureServer

/arcgis/rest/services/*/addFeatures

Insert, update, delete, and applyEdits endpoints compatible with ArcGIS clients, web apps, and field collection tools.

WFS-T

/wfs

OGC WFS 2.0 Transaction support with XML Insert, Update, and Delete operations for standards-based editing workflows.

GeoJSON transactions

/wfs/collections/{id}/transactions

A simplified JSON transaction endpoint for web applications that prefer GeoJSON over XML for feature creation and updates.

DuckDB-backed storage

Spatial SQL engine

All edits are persisted through DuckDB with full spatial support, enabling SQL queries against edited data alongside existing analytics workflows.

Where it resonates

Use this message for

  • Field data collection teams using Esri clients that expect FeatureServer editing
  • Organizations with standards-based procurement requiring WFS-T compliance
  • Web application teams that need lightweight GeoJSON-based editing APIs
  • Teams consolidating read and write workflows into a single platform

Talk track

The Geospatial Data Proxy now supports full transactional editing alongside its read and delivery capabilities. Teams can insert, update, and delete features through Esri FeatureServer endpoints, WFS-T XML transactions, or simplified GeoJSON APIs, all backed by DuckDB spatial storage.

Suggested demo sequence

Show the full read-write lifecycle from one platform.

  1. Start by querying existing features through /arcgis/rest/services or /api/ogc/*.
  2. Create new features using addFeatures or the GeoJSON transaction endpoint.
  3. Update a feature attribute or geometry and show the change reflected immediately.
  4. Demonstrate applyEdits for batch operations across inserts, updates, and deletes in a single request.