How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

OGC API - DGGS

Standards-compliant OGC API - Discrete Global Grid Systems endpoint exposing the GeoInsight Spatial Token store for zone-based queries. Fourteen read operations across four resource families: a landing page and service description, a collection catalogue (22 published collections), the DGGRS registry (H3, ISEA3H via both DGGRID and DGGAL, IGEO7, IVEA3H), zone discovery and zone data retrieval with relative-depth aggregation, and an OGC API - Features style /items surface backed by a GeoParquet lake with CQL2 filtering. Zone data requests accept COG raster statistics parameters (band, no-data, sampling factor, all-touched) and STAC search strategies (single, latest, mosaic) with cloud-cover and intersection thresholds. Reads answer anonymously at the time of probing; the official Python package documents a GeoInsight Personal Token (GPT) plus API Private Key (APK) issued from the dashboard.

This API exposes 14 operations across 14 paths, organized into 9 resource areas, and defines 29 schemas. It is described by OpenAPI 3.1.0, at version 3.0.0.

Requests are made against a single base URL, https://api.geoinsight.ai.

14 operations 14 paths 29 schemas 14 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
3.0.0
Base URL
https://api.geoinsight.ai
Resource Areas
9

Paths & Operations 14

Across 14 paths, the API surfaces 14 operations — 14 GET. They span 9 resource areas: root, Collections, Collection ID, DGGS, DGGRS ID, Zones, Zone ID, Data, Items. Each is listed below with its method, path, parameters, and response codes.

root 1
GET
/
root_handler → 200
Collections 1
GET
/collections
utoipa_doc → 200
Collection ID 1
GET
/collections/{collection_id}
collection_id_utoipa_doc 1 param → 200
DGGS 2
GET
/collections/{collection_id}/dggs
collection_id_utoipa_doc 1 param → 200
GET
/dggs
utoipa_doc → 200
DGGRS ID 2
GET
/collections/{collection_id}/dggs/{dggrs_id}
collection_id_dggrs_id_utoipa_doc 2 params → 200
GET
/dggs/{dggrs_id}
dggrs_id_utoipa_doc 1 param → 200
Zones 2
GET
/collections/{collection_id}/dggs/{dggrs_id}/zones
collection_id_dggrs_id_utoipa_doc 3 params → 200422
GET
/dggs/{dggrs_id}/zones
dggrs_id_utoipa_doc 2 params → 200422
Zone ID 2
GET
/collections/{collection_id}/dggs/{dggrs_id}/zones/{zone_id}
collection_id_dggrs_id_zone_id_utoipa_doc 4 params → 200
GET
/dggs/{dggrs_id}/zones/{zone_id}
dggrs_id_zone_id_utoipa_doc 3 params → 200
Data 1
GET
/collections/{collection_id}/dggs/{dggrs_id}/zones/{zone_id}/data
collection_id_dggrs_id_zone_id_data_utoipa_doc 18 params → 200422
Items 2
GET
/collections/{collection_id}/items
items_utoipa_doc 10 params → 200400404406
GET
/collections/{collection_id}/items/{feature_id}
item_id_utoipa_doc 9 params → 200400404406

Schemas 29

The contract defines 29 schemas that model the data the API accepts and returns. The most detailed are SchemaProperty (16 properties), ZoneIdResponse (13 properties), RawItemsResponse (10 properties), DggrsIdResponse (9 properties). Each schema is shown below with its type and property counts.

ApiError
object
API error response body for JSON error messages.
4 properties 2 required
CollectionId
object
8 properties 2 required
CollectionIdResponse
object
8 properties 2 required
CollectionsResponse
object
2 properties 2 required
DataResponse
object
7 properties 4 required
DggrsId
object
4 properties 4 required
DggrsIdResponse
object
9 properties 3 required
DggsResponse
object
2 properties 2 required
Dimension
object
6 properties 3 required
Extent
object
2 properties
FeatureCollectionResponse
object
OGC API Features getFeatures response over the collection's lake parquet.
6 properties 6 required
FeatureResponse
object
A single GeoJSON Feature read from the lake parquet. id is the 0-based row index in glob scan order (the raw parquet carries no guaranteed id column) — only st…
5 properties 4 required
FileInfo
object
One parquet file under the collection's lake data prefix with its row count.
2 properties 2 required
Grid
object
6 properties 1 required
Link
object
6 properties 2 required
LinkTemplate
object
3 properties 3 required
NumStr
PropertyType
string
RawItemResponse
object
Raw inspection view of a single row (/items/{featureid}?f=json).
6 properties 6 required
RawItemsResponse
object
Raw inspection view (f=json): rows exactly as they sit in the lake parquet (geometry as a truncated WKB hex preview), plus the file list and row counts a local…
10 properties 10 required
RootResponse
object
4 properties 1 required
Schema
object
3 properties 2 required
SchemaProperty
object
16 properties
SchemaType
string
Spatial
object
2 properties
Temporal
object
2 properties
ValueItem
object
4 properties
ZoneIdResponse
object
13 properties 2 required
ZonesResponse
object
4 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

geoinsight-ogc-api-dggs-openapi.yml Raw ↑
Where this information came from

This is an independent, third-party profile of OGC API - DGGS, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.