Check the workflow, not just the product name.
Honua supports selected Esri-client workflows through its GeoServices REST surface, but compatibility is operation-scoped. Record the client version, operation, parameters, authentication flow, and extensions you depend on, then check each requirement against the public matrix. For Honua SDK packages, see SDK availability & compatibility.
Compatibility has a stated scope. “Compatible” here means the named operation or workflow is covered by public source, documentation, and test evidence. It does not mean 100% ArcGIS parity, and Honua is not certified, sponsored, or endorsed by Esri.
GeoServices REST coverage
The public GeoServices parity matrix ↗ is the current source for operation and parameter details. This summary omits operation counts so it does not become a second, stale matrix.
| Service surface | Current boundary | What to verify before migration |
|---|---|---|
| FeatureServer | Partial | Query parameters, editing operations, attachments, relationships, and versioned workflows used by your applications. |
| MapServer | Partial | Dynamic export, identify, legends, layer definitions, and renderer behavior used by each map. |
| ImageServer | Partial | Raster functions, export-image parameters, mosaics, and multidimensional workflows. |
| GeocodeServer / NAServer / GPServer | Partial | The exact tasks, solvers, providers, and execution modes in the migration scope. |
| Geometry Service | Documented operations implemented | Validate parameter-level caveats and spatial-reference behavior for your workload. |
Desktop-client boundary
The public client compatibility and limitations page ↗ is the source for ArcGIS Pro, ArcPy, QGIS, and other client workflows. A migration assessment should capture the client's version, connection type, operations exercised, authentication flow, and any extension-specific behavior rather than relying on a product-name checkbox.
OGC and STAC evidence
Open-standard conformance is tracked separately from Esri compatibility. The dated public snapshot reports 952/952 applicable/basic/core CITE assertions across 11 suites; this is Honua's own test evidence, not formal OGC certification.
- Dated CITE suite status ↗
- Conformance classes and caveats ↗
- Live STAC root ↗
- Historical GeoBench snapshot, methodology, and limits
Evaluate your estate in four steps
- Inventory the exact service types, operations, parameters, authentication flows, and clients in use.
- Map each requirement to the public parity and client-limitations documentation.
- Run the workload against the exact Honua revision or pilot build under evaluation, using representative data.
- Record supported, workaround, and gap outcomes before cutover.
Use the migration playbook to start independently, or discuss your migration scope with Honua.