Honua
// compatibility

Keep the interfaces that work.
Migrate one workflow at a time.

Honua exposes documented GeoServices REST, OGC, OData, tile, gRPC, MCP, and SDK surfaces. Existing clients can keep using familiar interfaces where their required operations are supported. Check each protocol, operation, client version, and evidence boundary before planning a cutover.

URL & SDK mapping · scoped compatibility
Service endpoints
/arcgis/rest/services/Parcels/FeatureServer/0/rest/services/Parcels/FeatureServer/0
/arcgis/rest/services/Zoning/MapServer/rest/services/Zoning/MapServer
/arcgis/rest/services/NAIP/ImageServer/rest/services/NAIP/ImageServer
/arcgis/rest/services/Route/GPServer/rest/services/Route/GPServer
/geoserver/wfs · wms · wmts · wcs/ogc/wfs · wms · wmts · wcs
SDK · compatibility layer
@arcgis/core/Map@honua/sdk-esri-compat → MapCompat
@arcgis/core/views/MapView@honua/sdk-esri-compat → MapViewCompat
@arcgis/core/layers/FeatureLayer@honua/sdk-esri-compat → FeatureLayerCompat
@arcgis/core/Graphic · Symbol · Renderer@honua/sdk-esri-compat → matching Compat surface
// compatibility with boundaries

Check the operation, not just the protocol name.

Published support claims link to a public test suite, parity matrix, or evidence document. The summaries below separate partial GeoServices REST parity, a dated OGC CITE snapshot, and SDK package maturity. Use the claims matrix for the underlying evidence.

GeoServices REST · partial parityPARTIAL
Use compatible URLs where the operations your workflow needs are covered.

Honua targets selected FeatureServer, MapServer, ImageServer, Geometry Service, GeocodeServer, NAServer, and GPServer operations. Coverage differs by service and operation. The public parity matrix and JSON file in honua-server identify implemented, pending, and deferred behavior.

FeatureServerpartial parity
MapServerpartial parity
Geometry Servicedocumented operations
GeocodeServerpartial parity
ImageServerpartial parity
GPServertask runtime
NAServerpartial · five solve families · provider-dependent
OGC CITE conformanceSNAPSHOT
A dated, self-run standards snapshot.

The 2026-05-17 snapshot reports 952/952 passing applicable, basic, or core assertions across 11 CITE suites. This is Honua's own test evidence, not formal OGC certification. The link below records the suite profiles, run scope, and audit trail.

OGC API Features137 / 137
OGC API Tiles16 / 16
WMS 1.3.0199 / 199
WMTS 1.0.060 / 60
WFS 1.0.0162 / 162
WFS 1.1.039 / 39
WFS 2.0.0167 / 167
WCS 2.082 / 82
GeoPackage 1.231 / 31
GML 3.217 / 17
KML 2.242 / 42
11 suites · total952 / 952
Records · Processes · STACsupported (not part of the 952 CITE count)
SDK · compatibility layerJS PUBLIC PRERELEASE · OTHERS SOURCE PREVIEW
Familiar workflow shapes, with availability stated per language.

The JavaScript SDK and migration companions are public prereleases. Python and .NET remain source previews, and Honua does not yet publish an automated .NET or MAUI source rewriter. Review the migration page and package evidence before choosing a path.

JavaScript SDKpublic prerelease · 0.1.0-beta.0
Python SDKsource preview
.NET SDKsource preview
Mobile · .NET MAUIsource preview · connected field private beta
honua-migrate codemod · JSpublic prerelease · 0.1.0-beta.0

// availability and evidence are separate: a passing snapshot is not a support window or certification

// data sources

Connect the data sources your workflow actually needs.

Use PostGIS as the operational store, import supported exchange formats, or serve supported cloud-native formats from object storage. Confirm provider and operation coverage for your workload before deployment.

01 · Relational PostGIS first, with additional relational connectors.

Honua uses stock PostGIS as its read/write operational store, without a proprietary geometry type. MySQL/MariaDB, SQL Server, Oracle Spatial, and DuckDB are additional read/query-only providers. Validate schema features, authentication, and supported query operations for each provider.

PostGIS 3.x · PostgreSQL 14+primary store
MySQL/MariaDB · SQL Server · Oracle · DuckDBread/query only
PostgreSQL/PostGIS on RDS · Azure Database for PostgreSQL · self-hosteddeployment paths
02 · File & geodatabase Import the formats your team already exchanges.

Operator-facing import paths cover common file and geodatabase formats. Import is one-way today, and preservation details vary by format; review the documented parity before moving production data.

Shapefile · GeoPackage · FileGDBimport
GeoJSON · KML · GML · WKT · CSVimport
FlatGeobuf · TinyWKBimport
03 · Cloud-native object storage Range-fetched paths for supported read-heavy workloads.

Honua can serve supported COG, PMTiles, STAC, and Zarr paths from object storage; COG and PMTiles use range requests. NetCDF4, HDF5, and GRIB sources are registered by URL and optionally converted by a GDAL worker to derived Zarr; when that build-time reader is disabled, refresh and pixel-read paths return 501 rather than serving incomplete data.

COG · PMTilesserved direct, range-fetched
STAC catalogs & itemsserve direct
Zarrbounded OGC API Coverages reads
NetCDF4 · HDF5 · GRIBURL register · optional GDAL → Zarr
S3 · Azure Blob · MinIOsupported backends

// review provider, format, and operation coverage in the public documentation before production use

// next

Validate the workflows that cannot break.
Then migrate in stages.