Speaks GeoServices REST.
Speaks OGC.
SDK parity by design.
Covered clients can stay on the scoped wire protocols and response shapes documented in the evidence ledger. Your code can stay on familiar SDK surfaces while Honua keeps the public contract and reshapes the infrastructure underneath.
Tested in CI. Reviewed in public.
Compatibility isn't a marketing claim. Every supported surface ships with a public test suite or evidence doc. See the claims matrix for the wording rules that govern the numbers below.
Honua's GeoServices REST surface targets FeatureServer, MapServer, ImageServer, Geometry Service, and GPServer. Parity is scoped per service — what's covered, what's pending, and what's deferred is recorded in the parity matrix and JSON data file in honua-server.
Honua's OGC conformance is captured in a CITE-evidence snapshot in honua-server. Counts below are passing assertions in the current published snapshot — exact, scoped, and audit-linked.
Each Honua SDK is shaped around familiar GIS workflows — not a fork. Conversion happens through the honua-migrate codemod on the JavaScript SDK today; other languages ship their parity surface and gain codemod coverage on the roadmap.
// public wording rules · claims.html · CITE numbers track the snapshot in honua-server
The databases & data sources Honua reads, writes, and serves from.
PostGIS as the operational store, the file and geodatabase formats your team already exchanges, and cloud-native formats on object storage for the workloads that don't want a database in the path.
// operator import paths documented in honua-server; warehouse pass-through tracked in the open backlog