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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Cognite

Cognite Geospatial API

The Geospatial API allows to model a problem domain when data has a geometric or geographic nature.The geospatial data is organized in feature types that are homogeneous collections of features (geospatial items), each having the same spatial representation, such as points, lines, or polygons, and a common set of typed properties. The Geospatial API is aware of Coordinate Reference Systems, and allows transformations.To learn more about geospatial concepts, see the [concept guide](https://developer.cognite.com/dev/concepts/resource_types/geospatial.html).

Documentation Provider Profile APIs.io OpenAPI GitHub

Cognite Geospatial API is one of 90 APIs that Cognite publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Geospatial. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 22 operations across 19 paths, and defines 105 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, https://{cluster}.cognitedata.com/api/v1/projects/{project}.

22 operations 19 paths 105 schemas 2 GET19 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://api.cognitedata.com
Authentication
HTTP Bearer, OAuth 2.0, OAuth 2.0, OAuth 2.0, OpenID Connect
Contact
Cognite Support
Resource Areas
1

Authentication & Security 5

Cognite Geospatial API declares 5 security schemes for authenticating requests. It accepts HTTP bearer tokens (OpenID Connect or OAuth2 token) (oidc-token). It supports OAuth 2.0 (oauth2-client-credentials) using the clientCredentials flow, exposing 1 scope. It supports OAuth 2.0 (oauth2-auth-code) using the authorizationCode flow, exposing 1 scope. It supports OAuth 2.0 (oauth2-open-industrial-data) using the clientCredentials flow, exposing 1 scope. It supports OpenID Connect (org-oidc-token) discovered at https://auth.cognite.com/.well-known/openid-configuration. By default, every request must be authenticated.

  • oidc-token — Access token issued by the CDF project's configured identity provider. Access token must be an OpenID Connect token, and the project must be configured to acce…
  • oauth2-client-credentials — Access token issued by the CDF project's configured identity provider. Access token must be an OpenID Connect token, and the project must be configured to acce…
  • oauth2-auth-code — Access token issued by the CDF project's configured identity provider. Access token must be an OpenID Connect token, and the project must be configured to acce…
  • oauth2-open-industrial-data — Auth flow for Open Industrial Data. Get your client secret from https://hub.cognite.com/open-industrial-data-211.
  • org-oidc-token — Access token issued by the Cognite authorization server, and valid for the target organization. The token must be an OpenID Connect token, and it can be obtain…

Paths & Operations 22

Across 19 paths, the API surfaces 22 operations — 2 GET, 19 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Geospatial 22

The Geospatial API allows to model a problem domain when data has a geometric or geographic nature. The geospatial data is organized in feature types that are homogeneous collecti…

GET
/geospatial/crs
List Coordinate Reference Systems
listGeospatialCoordinateReferenceSystems 1 param → 200400
POST
/geospatial/crs
Create Coordinate Reference Systems
createGeospatialCoordinateReferenceSystems body → 201400
POST
/geospatial/crs/byids
Get Coordinate Reference Systems
getCoordinateReferenceSystem body → 200400
POST
/geospatial/crs/delete
Delete Coordinate Reference Systems
deleteGeospatialCoordinateReferenceSystems body → 200400
POST
/geospatial/featuretypes
Create feature types
createFeatureTypes body → 201400
POST
/geospatial/featuretypes/byids
Retrieve feature types
getFeatureTypesByIds body → 200400
POST
/geospatial/featuretypes/list
List feature types
listFeatureTypes → 200400
POST
/geospatial/featuretypes/update
Update feature types
updateFeatureTypes body → 200400
POST
/geospatial/featuretypes/delete
Delete feature types
GeospatialDeleteFeatureTypes body → 200400
POST
/geospatial/featuretypes/{featureTypeExternalId}/features
Create features
createFeatures 1 param body → 201400
GET
/geospatial/featuretypes/{featureTypeExternalId}/features
Get features
getFeatures 5 params → 200400
POST
/geospatial/featuretypes/{featureTypeExternalId}/features/list
Filter all features
listFeatures 1 param body → 200400
POST
/geospatial/featuretypes/{featureTypeExternalId}/features/byids
Retrieve features
getFeaturesByIds 1 param body → 200400
POST
/geospatial/featuretypes/{featureTypeExternalId}/features/update
Update features
updateFeatures 1 param body → 200400
POST
/geospatial/featuretypes/{featureTypeExternalId}/features/delete
Delete features
deleteFeatures 1 param body → 200400
POST
/geospatial/featuretypes/{featureTypeExternalId}/features/search
Search features
searchFeatures 1 param body → 200400
POST
/geospatial/featuretypes/{featureTypeExternalId}/features/search-streaming
Search and stream features
searchFeaturesStreaming 1 param body → 200400
POST
/geospatial/featuretypes/{featureTypeExternalId}/features/aggregate
Aggregate features
aggregateFeatures 1 param body → 200400
POST
/geospatial/compute
Compute
compute body → 200
PUT
/geospatial/featuretypes/{featureTypeExternalId}/features/{featureExternalId}/rasters/{rasterPropertyName}
Put a raster into a feature property
putRaster 8 params body → 200400
POST
/geospatial/featuretypes/{featureTypeExternalId}/features/{featureExternalId}/rasters/{rasterPropertyName}
Get a raster from a feature property
getRaster 3 params body → 200400
POST
/geospatial/featuretypes/{featureTypeExternalId}/features/{featureExternalId}/rasters/{rasterPropertyName}/delete
Delete a raster from a feature property
deleteRaster 3 params → 200400

Schemas 105

The contract defines 105 schemas that model the data the API accepts and returns. The most detailed are GeospatialRasterMetadata (10 properties), GeospatialFeatureAggregateRequest (8 properties), GeospatialError (6 properties), GeospatialFeatureSearchRequest (6 properties). Each schema is shown below with its type and property counts.

GeospatialFeatureInFilter
object
1 property
GeospatialFeatureRangeFilter
object
1 property
GeospatialCoordinateReferenceSystemList
object
1 property 1 required
GeospatialFeatureOrFilter
object
1 property
GeospatialPropertyAndValues
object
2 properties
GeospatialFeatureSearchResult
object
1 property 1 required
GeospatialFeatureAggregateRequest
object
Feature Aggregation Request
8 properties
GeospatialFeaturesWithCursor
A list of objects along with possible cursors to get the next page of results
GeospatialFeatureMissingFilter
object
1 property
GeospatialPropertyAndValue
object
2 properties
GeospatialSumAggregationOutput
object
1 property 1 required
GeospatialFeatureAggregates
object
1 property 1 required
GeospatialFeatureContainsAnyFilter
object
1 property
GeospatialError
object
Cognite API error.
6 properties 2 required
GeospatialReferenceIds
object
1 property 1 required
GeospatialMinAggregationOutput
object
1 property 1 required
GeospatialConvexHullAggregationOutput
object
1 property 1 required
GeospatialFeatureStIntersectsFilter
object
1 property
GeospatialFeatureProperties
object
GeospatialFeatureTypeExternalId
string
GeospatialFeatureTypeSpec
object
4 properties 2 required
GeospatialFeatures
GeospatialCountAggregationOutput
object
1 property 1 required
GeospatialAggregateOutputSpec
GeospatialUnionAggregationOutput
object
1 property 1 required
GeospatialPropertyName
string
GeospatialPropertyType
string
Property type
GeospatialCoordinateReferenceSystem
object
3 properties 3 required
GeospatialJsonComputeOutput
object
1 property 1 required
SetLongField
object
1 property 1 required
GeospatialPropertyReference
object
References a feature property in the context of a filter The support for arrays is forward looking for when the geospatial api will have complex properties.
1 property
GeospatialComputeFunction
GeospatialVarianceAggregationOutput
object
1 property 1 required
GeospatialFeatureSearchStreamingRequest
object
Search and streaming feature request
5 properties
GeospatialRangeCondition
object
Range condition can be open (i.e. having one of the properties) or closed (i.e. having two opposite properties). Can be applied to numeric types as well as str…
4 properties
EpochTimestamp
integer
The number of milliseconds since 00:00:00 Thursday, 1 January 1970, Coordinated Universal Time (UTC), minus leap seconds.
GeospatialIndexSpec
object
1 property 1 required
GeospatialGeometryValueComputeFunction
object
1 property 1 required
GeospatialProjString
string
The projection specification string as described in https://proj.org/usage/quickstart.html
GeospatialFeatureTypes
object
1 property 1 required
GeospatialProperty
object
1 property
GeospatialRasterCommonOutputSpec
object
3 properties
GeospatialRecursiveDelete
boolean
Indicates if feature types should be deleted together with all related features. Optional parameter, defaults to false.
GeospatialFeatureNotFilter
object
1 property
GeospatialFeatureEqualsFilter
object
1 property
GeospatialFeatureStWithinProperlyFilter
object
1 property
SinglePatchLong
object
Set a new value for the long, or remove the value.
CogniteExternalId
string
The external ID provided by the client. Must be unique for the resource type.
DataSetId
integer
The dataSet Id for the item.
GeospatialFeatureTypeProperty
object
5 properties 1 required
GeospatialAggregateOutput
object
A list of aggregations which are requested.
GeospatialFeatureSearchRequest
object
Feature Search Request
6 properties
GeospatialFeature
GeospatialRange
GeospatialAvgAggregationOutput
object
1 property 1 required
GeospatialItemExternalId
object
1 property 1 required
GeospatialRasterGtiffOutputSpec
object
GTiff specification for the output raster
2 properties 1 required
Cursor
object
Cursor for paging through results. In general, if a response contains a nextCursor property, it means that there may be more results, and you should pass that…
1 property
GeospatialFeatureStWithinDistanceFilter
object
1 property
GeospatialCollectAggregationOutput
object
1 property 1 required
GeospatialAllowCrsTransformation
boolean
Optional parameter indicating if input geometry properties should be transformed into the respective Coordinate Reference Systems defined in the feature type s…
GeospatialCentroidAggregationOutput
object
1 property 1 required
GeospatialFeatureStContainsProperlyFilter
object
1 property
GeospatialFeatureRegexFilter
object
Regular expression pattern matching.
1 property
GeospatialFeatureType
GeospatialFeatureStContainsFilter
object
1 property
RemoveField
object
1 property 1 required
GeospatialFeatureStIntersects3dFilter
object
1 property
GeospatialOutput
object
Desired output specification.
2 properties
GeospatialFeatureSpec
GeospatialComputedItems
object
1 property
GeospatialCustomCoordinateReferenceSystem
object
5 properties 5 required
GeospatialFeatureLikeFilter
object
Simple pattern maching. Use for single character and % for string of any length. Backslash \ is an escape character.
1 property
GeospatialFeatureListRequest
Feature List Request
GeospatialUpdateFeatureTypeSpec
object
2 properties 2 required
GeospatialFeatureStWithinFilter
object
1 property
SearchLimit
integer
Limits the number of results to be returned.
GeospatialFeatureTypeSpecs
object
1 property 1 required
GeospatialRasterOutputSpec
GeospatialReferenceId
integer
EPSG code, e.g. 4326. Only valid for geometry types. See https://en.wikipedia.org/wiki/Spatialreferencesystem
GeospatialFeatureAndFilter
object
1 property
GeospatialFeatureSpecs
GeospatialMaxAggregationOutput
object
1 property 1 required
GeospatialPropertyAndPattern
object
2 properties
GeospatialAllowDimensionalityMismatch
boolean
Optional parameter indicating if the spatial filter operators allow input geometries with a different dimensionality than the properties they are applied to. F…
GeospatialPropertyValueAndDistance
object
3 properties
GeospatialFeatureStWithinDistance3dFilter
object
1 property
GeospatialGeometryTransformComputeFunction
object
1 property 1 required
GeospatialExtendedWellKnownText
string
Well-known text of the geometry prefixed with a spatial reference identifier, see https://docs.geotools.org/stable/javadocs/org/opengis/referencing/doc-files/W…
GeospatialFeatureTypeExternalIds
object
1 property 1 required
GeospatialRasterXyzOutputSpec
object
XYZ specification for the output raster
2 properties 1 required
GeospatialUpdateFeatureTypeSpecs
object
1 property 1 required
GeospatialDeleteFeatureType
object
2 properties 1 required
GeospatialComputedItem
object
GeospatialGeometryComputeFunction
GeospatialCustomCoordinateReferenceSystemSpecs
object
1 property 1 required
GeospatialFeatureFilter
GeospatialFeatureIds
object
1 property 1 required
GeospatialComputeRequest
GeospatialAggregate
GeospatialWellKnownText
string
Well-known text of the geometry, see https://docs.geotools.org/stable/javadocs/org/opengis/referencing/doc-files/WKT.html
GeospatialOutputStreaming
object
Desired output specification for streaming.
3 properties
GeospatialIntersectionAggregationOutput
object
1 property 1 required
GeospatialFeatureIdsWithOutput
GeospatialRasterMetadata
object
10 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cognite-geospatial-api-openapi.yml Raw ↑

Other APIs Cognite publishes across the network.

Cognite Data Fusion API
AE Profile APIs.io
Cognite 3D Asset Mapping API
AE Profile APIs.io
Cognite 3D Files API
AE Profile APIs.io
Cognite 3D Jobs API
AE Profile APIs.io
Cognite 3D Model Revisions API
AE Profile APIs.io
Cognite 3D Models API
AE Profile APIs.io
Cognite Annotations API
AE Profile APIs.io
Cognite Assets API
AE Profile APIs.io
Cognite Connections API
AE Profile APIs.io
Cognite Containers API
AE Profile APIs.io
Cognite Data models API
AE Profile APIs.io
Cognite Data point subscriptions API
AE Profile APIs.io
#Geospatial
← Back to C APIs
API Details
ID
cognite:cognite-geospatial-api
Base URL
https://api.cognitedata.com
Docs
https://api-docs.cognite.com/
Provider
Cognite
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=cognite-geospatial-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/cognite-geospatial-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Cognite Geospatial API, 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.