Documentation · shared GIS pipeline · deployment patterns
Authentication, policy, catalog lookup, query planning, encoding, and telemetry converge on shared runtime services. Adapters translate covered operations into that core.
Illustrative sequence only. Latency and response behavior depend on the operation, data, and deployment.
Existing clients can retain familiar service shapes when their required operations, parameters, versions, authentication, and extensions are covered.
Documented surfaces converge on common policy, catalog, data, analytics, publishing, and job components. Capability flags make the available surface inspectable.
PostgreSQL/PostGIS is the read/write operational store. Covered relational connectors, file imports, and object-storage formats have provider- and operation-specific boundaries.
Showing documented capabilities across all editions.
Documented GeoServices REST, OGC, OData, STAC, tile, gRPC, and MCP operations with scoped coverage.
CommunityPostGIS-backed catalog and data paths, API keys, health probes, Prometheus, and OpenTelemetry.
CommunityFeatureServer editing, spatial analytics, geocoding, cloud raster paths, and multi-node caching.
ProOpt-in real-time streams and alert evaluation for event-driven workflows.
ProMulti-provider OIDC, claim-to-role mapping, branch versioning, service imports, and extension hooks.
EnterpriseThe catalog names the few pilot-access and not-yet items directly.
All editionsFeatureServer, MapServer, ImageServer, GeocodeServer, NAServer, GPServer, and Geometry Service have broad practical coverage. Check long-tail requirements before moving an endpoint.
Run the open, read-only assessment tool against the service inventory. Record services, layers, authentication, extensions, data sources, and workflows without changing the source.
honua-esri-assess → local inventory and capability map
Compare required operations with the public compatibility matrix. Long-tail renderers, extensions, and authentication flows stay visible for review.
Open the compatibility evidence →Copy selected layers from a FeatureServer or MapServer into PostGIS and publish the pilot. The importer reports content it cannot move.
Review migration evidence →Exercise the clients, operations, and data that must keep working. Keep the old service available while exceptions are fixed or accepted.
Not yet Estate-wide behavioral comparison reportingRepoint a service after its workflows pass. Keep the source as a rollback path, observe the moved workload, and repeat service by service.
Read the full migration playbook →Published tools cover supported import and call-site transformations.
Published tooling scans, translates, and runs recognized operations, with a report for manual review.
Migration guides and adapters support reimplementation.
Not yet Automated source rewritingServer MCP discovery and query use the same policy and data boundaries as other interfaces.
Discover covered services, read metadata, query features, and invoke supported analysis through server APIs. Policy checks apply to the agent identity just as they do to any other client.
Read health and telemetry, inspect deterministic findings, and prepare policy-scoped proposals. Risky and irreversible work remains approval-gated.
Health/readiness endpoints, Prometheus metrics, and OpenTelemetry signals expose the deployment state.
Operators and agents can inspect the signals behind a proposed change.
The single-environment loop produces proposals under configured release and policy controls.
Low-risk actions need an explicit policy. Risky or irreversible work requires approval.
Post-action verification and compensating rollback are implemented at the operation gateway. Signed fleet promotion across environments, and broader remediation, are not yet implemented.
Agents use scoped credentials and the same authorization boundaries as interactive or service clients.
Operators can inspect the condition, proposed action, and configured policy before execution.
Automation does not turn unknown, risky, or irreversible work into an implicit background action.
Deploy the same OCI image through the public Helm chart. Keep the serving tier stateless and use managed PostgreSQL/PostGIS, Blob storage, Redis for multi-node mode, and your observability backend.
Validate HA, sizing, upgrades, rollback, backup, and recovery during the pilot.
Deploy the same OCI image through the public Helm chart or the ECS/Fargate reference path. Keep the server tier stateless and use RDS PostgreSQL/PostGIS, S3-compatible storage, Redis, and your observability backend.
Validate HA, sizing, upgrades, rollback, backup, and recovery during the pilot.
Use the architecture to orient the evaluation, then verify compatibility, availability, and deployment boundaries before choosing a production path.