Same Data, Two Protocols — live demo

// what this shows

One query, one result shape. The Honua JS SDK's protocol-neutral contract — Dataset → Source → Query → Result — treats the protocol as a field on a source descriptor, not an architecture decision.
GeoServices RESTCommunity
The same endpoints ArcGIS clients speak — /rest/services/…/FeatureServer/0/query.
OGC API FeaturesCommunity
The open standard, first-class — /ogc/features/collections/…/items with CQL2 filters.
OData v4Community
The same rows your spreadsheet and BI tools can reach — /odata/…?$filter=.

Every protocol surface — read, query, tiles, metadata — ships in the free Community edition (ELv2). That is the point: when every door is open and standard, the data is yours to walk out with.

view page source ↗
honua-io/honua-sdk-js ↗ (Apache 2.0)
edition split → pricing ↗

GeoServices REST

the same endpoints ArcGIS clients speak

raw response (pretty-printed, truncated)

OGC API Features

the OGC standard surface · CQL2

raw response (pretty-printed, truncated)

…and the same filter as OData `$filter`

rows for Excel / Power BI — completing the protocols story

raw response (pretty-printed, truncated)

// Full page source: assets/demos/two-protocols/two-protocols.js · endpoint & schema contract: config.json · SDK: honua-io/honua-sdk-js (Apache 2.0) · data: County of Maui · Hawaiʻi Statewide GIS Program

Same data, two protocols.

// one query

GeoServices REST

OGC API Features

…and the same filter as OData `$filter`

// one query

GeoServices REST

OGC API Features

…and the same filter as OData $filter

…and the same filter as OData `$filter`