A resource that may be available as one or more sub-resource distributions that conform to one or more OGC API standards. (OGC API - Common - Part 2: Geospatial Data)
A resource accessible at the OGC API path /collections/{collectionId} that provides metadata about a collection.
A collection of data, published or curated by a single agent, and available for access or download in one or more representations. (Data Catalog Vocabulary (DCAT) - Version 2)
A specific representation of a dataset. A dataset might be available in multiple serializations that may differ in various ways, including natural language, media-type or format, schematic organization, temporal and spatial resolution, level of detail or profiles (which might specify any or all of the above). (Data Catalog Vocabulary (DCAT) - Version 2)
EXAMPLE: a downloadable file, an RSS feed or an API.
The (processing) job is a server-side object created by a processing service for a particular process execution. A job may be latent in the case of synchronous execution or explicit in the case of asynchronous execution. Since the client has only oblique access to a processing job, a Job ID is used to monitor and control a job.
JavaScript Object Notation is a lightweight data-interchange format. JSON is easy for humans to read and write and it is easy for machines to parse and generate.
The term "link" is commonly used as substitute for URL or URI. In this Standard, "link" refers to an element described by the schema for a link as shown at link.yaml. This is a JSON element containing properties such as "rel" (relation) and "href". The value of the "href" property is an URI.
HTTP Link header, as defined in RFC 8288 (Web Linking).
A collection that is local to the OGC API deployment currently being accessed.
A method or procedure, that conforms to an OGC API Standard, used to control how users or systems can access and interact with data.
An implementation of an OGC API Standard that is accessible to users and other system typically through the internet.
A process p is a function that for each input returns a corresponding output
where \$X\$ denotes the domain of arguments \$x\$ and \$Y\$ denotes the co-domain of values y. In this Standard, process arguments are referred to as process inputs and result values are referred to as process outputs. Processes that have no process inputs represent value generators that deliver constant or random process outputs.
The term "process" is one of the most used terms both in the information and geosciences domain. If not stated otherwise, this Standard uses the term process as an umbrella term for any algorithm, calculation or model that either generates new data or transforms some input data into output data as defined in section 4.1 of the OGC WPS 2.0 standard.
A process description is an information model that specifies the interface of a process. A process description is used for a machine-readable description of the process itself but also provides some basic information about the process inputs and outputs.
The execution of a process is an action that calculates the outputs of a given process for a given set of data inputs.
Process inputs are the arguments of a process and refer to data provided to a process. Each process input is an identifiable item.
A process offering is an identifiable process that may be executed on a particular service instance. A process offering contains a process description as well as service-specific information about the supported execution protocols (e.g. synchronous and asynchronous execution).
Process outputs are the results of a process and refer to data returned by a process. Each process output is an identifiable item.
A process output with identifier {outputID} that is explicitly specified in the "outputs" section of an execute request.
A process output that is defined in the description of a process and is generated as a result of an execute request where the "outputs" parameter has been omitted. Omitting the "outputs" parameters of an execute request is equivalent to explicitly requesting all of the outputs defined in the process description
A collection that is not local to the OGC API deployment currently being accessed.
The Representational State Transfer (REST) style is an abstraction of the architectural elements within a distributed hypermedia system. REST focuses on the roles of components, the constraints upon their interaction with other components, and their interpretation of significant data elements. It encompasses the fundamental constraints upon components, connectors, and data that define the basis of the Web architecture, and thus the essence of its behavior as a network-based application. An API that conforms to the REST architectural principles/constraints is called a RESTful API. (Source: OGC 18-088)
A server that implements one or more data access mechanisms for accessing data from an OGC API collection. The server acts as a source of values that are passed to a process being executed by an implementation of this Standard.
- API
-
Application Programming Interface
- CITE
-
Compliance Interoperability & Testing Evaluation
- CRS
-
Coordinate Reference System
- GML
-
Geography Markup Language
- HTTP
-
Hypertext Transfer Protocol
- ISO
-
International Organization for Standardization
- JSON
-
JavaScript Object Notation
- KVP
-
Key-Value Pair
- MIME
-
Multipurpose Internet Mail Extensions
- OGC
-
Open Geospatial Consortium
- REST
-
Representational State Transfer
- URI
-
Uniform Resource Identifier
- URL
-
Uniform Resource Locator
- WPS
-
Web Processing Service
- XML
-
Extensible Markup Language