Open standards access to the engine
Every capability of HyPlica Cloud is exposed through Open Geospatial Consortium API standards, so any conformant client, library, or platform can work with the engine without proprietary integration. All endpoints require authentication — see the authentication guide to get a token in one minute.
Service root: GET /api/
OGC API — Definition
The machine-readable description of this server: the landing page document and the OpenAPI definition every OGC API client reads first to discover what the service offers.
OGC API — Conformance
The conformance declaration lists exactly which OGC standards and conformance classes this server implements, so clients can negotiate capabilities without guesswork.
OGC API — DGGS
The heart of the service: enumerate the HyPlica discrete global grid reference systems, query zones by spatial, temporal, and vertical extent, and retrieve data joined to any zone. Zone geometry is served as GeoJSON footprints or — faithful to the 4D zone — as JSON-FG prisms with height bounds and temporal band (?f=jsonfg / ?f=ubjsonfg); raster-indexed collections additionally serve per-zone GeoTIFF with zone-depth pyramids (?f=geotiff).
OGC API — Collections & collection-DGGS
Indexed datasets and DGGRS instances as OGC API collections (Common Part 2), each navigable to its feature zoneSets and to a collection-scoped DGGS tree — including collection-level zone data (which of the dataset's features cover a zone). Raster-indexed collections additionally carry their zone-level(s) and lon/lat extent, a browser PNG preview (data or categorical zone-mask rendition), and per-zone GeoTIFF with zone-depth pyramids.
OGC API — Processes
Long-running HyPlica operations — bulk dataset indexing, large asynchronous zone queries — exposed as processes you execute and monitor rather than wait on.
OGC API — Jobs
Track every asynchronous execution: poll status, retrieve results when successful, and inspect failures — each job owned by the account that created it.
OGC API — Features
Feature access over the indexed data: Part 1 (Core), Part 2 (CRS by Reference) and Part 3 (Filtering with CQL2-Text) are implemented and declared — retained source features are served per collection alongside their HyPlica zoneSets, filterable over each collection's queryables.
OGC API — Coverages
In developmentCoverage (gridded/raster) access aggregated to HyPlica resolution tiers, for analysis-ready sampling at any zoom. Rolling out with the first hosted datasets.