# info.contact.name
Vlaamse Overheid - Beleidsdomein Omgeving - MercatorNet

# paths./.get.description
The landing page provides links to the API definition, the conformance
statements and to the feature collections in this dataset.

# paths./openapi.get.description
The OpenAPI document describing the API (this document)

# paths./conformance.get.summary
information about specifications that this API conforms to

# paths./conformance.get.description
A list of all conformance classes specified in a standard that the
server conforms to.

# paths./functions.get.summary
information about functions supported in the CQL filter extension

# paths./functions.get.description
A list of supported filters and functions.

# paths./collections/{collectionId}.get.summary
describe the feature collection with id `collectionId`

# paths./collections/{collectionId}/queryables.get.summary
lists the queryable attributes for the feature collection with id `collectionId`

# paths./collections/{collectionId}/items.get.description
Fetch features of the feature collection with id `collectionId`.

Every feature in a dataset belongs to a collection. A dataset may
consist of multiple feature collections. A feature collection is often a
collection of features of a similar type, based on a common schema.

Use content negotiation to request HTML or GeoJSON.

# paths./collections/{collectionId}/items/{featureId}.get.description
Fetch the feature with id `featureId` in the feature collection
with id `collectionId`.

Use content negotiation to request HTML or GeoJSON.

# components.schemas.queryable.properties.id.description
identifier of the attribute that can be used in CQL filters

# components.schemas.collection.properties.id.description
identifier of the collection used, for example, in URIs

# components.schemas.collection.properties.description.description
a description of the features in the collection

# components.schemas.collection.properties.itemType.description
indicator about the type of the items in the collection (the default value is 'feature').

# components.schemas.collection.properties.crs.description
the list of coordinate reference systems supported by the service

# components.schemas.collection.properties.storageCrs.description
the CRS identifier, from the list of supported CRS identifiers, that may be used to retrieve features from a collection without the need to apply a CRS transformation

# components.schemas.collections.properties.crs.description
a list of CRS identifiers that are supported for more that one feature collection offered by the service

# components.schemas.exception.description
Information about the exception: an error code plus an optional description.

# components.schemas.extent.properties.spatial.properties.bbox.description
One or more bounding boxes that describe the spatial extent of the dataset.
In the Core only a single bounding box is supported. Extensions may support
additional areas. If multiple areas are provided, the union of the bounding
boxes describes the spatial extent.

# components.schemas.extent.properties.spatial.properties.bbox.items.description
Each bounding box is provided as four or six numbers, depending on
whether the coordinate reference system includes a vertical axis
(height or depth):

* Lower left corner, coordinate axis 1
* Lower left corner, coordinate axis 2
* Minimum value, coordinate axis 3 (optional)
* Upper right corner, coordinate axis 1
* Upper right corner, coordinate axis 2
* Maximum value, coordinate axis 3 (optional)

The coordinate reference system of the values is WGS 84 longitude/latitude
(http://www.opengis.net/def/crs/OGC/1.3/CRS84) unless a different coordinate
reference system is specified in `crs`.

For WGS 84 longitude/latitude the values are in most cases the sequence of
minimum longitude, minimum latitude, maximum longitude and maximum latitude.
However, in cases where the box spans the antimeridian the first value
(west-most box edge) is larger than the third value (east-most box edge).

If the vertical axis is included, the third and the sixth number are
the bottom and the top of the 3-dimensional bounding box.

If a feature has multiple spatial geometry properties, it is the decision of the
server whether only a single spatial geometry property is used to determine
the extent or all relevant geometries.

# components.schemas.extent.properties.spatial.properties.crs.description
Coordinate reference system of the coordinates in the spatial extent
(property `bbox`). The default reference system is WGS 84 longitude/latitude.
In the Core this is the only supported coordinate reference system.
Extensions may support additional coordinate reference systems and add
additional enum values.

# components.schemas.extent.properties.spatial.description
The spatial extent of the features in the collection.

# components.schemas.extent.properties.temporal.properties.interval.description
One or more time intervals that describe the temporal extent of the dataset.
The value `null` is supported and indicates an open time intervall.
In the Core only a single time interval is supported. Extensions may support
multiple intervals. If multiple intervals are provided, the union of the
intervals describes the temporal extent.

# components.schemas.extent.properties.temporal.properties.interval.items.description
Begin and end times of the time interval. The timestamps
are in the coordinate reference system specified in `trs`. By default
this is the Gregorian calendar.

# components.schemas.extent.properties.temporal.properties.trs.description
Coordinate reference system of the coordinates in the temporal extent
(property `interval`). The default reference system is the Gregorian calendar.
In the Core this is the only supported temporal reference system.
Extensions may support additional temporal reference systems and add
additional enum values.

# components.schemas.extent.properties.temporal.description
The temporal extent of the features in the collection.

# components.schemas.extent.description
The extent of the features in the collection. In the Core only spatial and temporal
extents are specified. Extensions may add additional members to represent other
extents, for example, thermal or pressure ranges.

# components.schemas.landingPage.properties.description.example
Access to data about buildings in the city of Bonn via a Web API that conforms to the OGC API Features specification.

# components.schemas.numberMatched.description
The number of features of the feature type that match the selection
parameters like `bbox`.

# components.schemas.numberReturned.description
The number of features in the feature collection.

A server may omit this information in a response, if the information
about the number of features is not known or difficult to compute.

If the value is provided, the value shall be identical to the number
of items in the "features" array.

# components.schemas.timeStamp.description
This property indicates the time and date when the response was generated.

# components.schemas.limit.description
The optional limit parameter limits the number of items that are presented in the response document.

Only items are counted that are on the first level of the collection in the response document.
Nested objects contained within the explicitly requested items shall not be counted.

Minimum = 1. Maximum = 10000. Default = 10.

# components.schemas.bbox.description
Only features that have a geometry that intersects the bounding box are selected.
The bounding box is provided as four or six numbers, depending on whether the
coordinate reference system includes a vertical axis (height or depth):

* Lower left corner, coordinate axis 1
* Lower left corner, coordinate axis 2
* Minimum value, coordinate axis 3 (optional)
* Upper right corner, coordinate axis 1
* Upper right corner, coordinate axis 2
* Maximum value, coordinate axis 3 (optional)

The coordinate reference system of the values is WGS 84 longitude/latitude
(http://www.opengis.net/def/crs/OGC/1.3/CRS84) unless a different coordinate
reference system is specified in the parameter `bbox-crs`.

For WGS 84 longitude/latitude the values are in most cases the sequence of
minimum longitude, minimum latitude, maximum longitude and maximum latitude.
However, in cases where the box spans the antimeridian the first value
(west-most box edge) is larger than the third value (east-most box edge).

If the vertical axis is included, the third and the sixth number are
the bottom and the top of the 3-dimensional bounding box.

If a feature has multiple spatial geometry properties, it is the decision of the
server whether only a single spatial geometry property is used to determine
the extent or all relevant geometries.

# components.schemas.datetime.description
Either a date-time or an interval, open or closed. Date and time expressions
adhere to RFC 3339. Open intervals are expressed using double-dots.

Examples:

* A date-time: "2018-02-12T23:20:50Z"
* A closed interval: "2018-02-12T00:00:00Z/2018-03-18T12:31:12Z"
* Open intervals: "2018-02-12T00:00:00Z/.." or "../2018-03-18T12:31:12Z"

Only features that have a temporal property that intersects the value of
`datetime` are selected.

If a feature has multiple temporal properties, it is the decision of the
server whether only a single temporal property is used to determine
the extent or all relevant temporal properties.

# components.schemas.filter.description
Defines a filter that will be applied on items, only items matching the filter will be returned

# components.schemas.filterLang.description
Filter encoding used in the filter parameter

# components.schemas.filterCrs.description
Filter CRS which is being used to encode geometries in the filter parameter

# components.schemas.sortBy.description
Defines how features in a response should be ordered for presentation.

# components.schemas.ids.description
Query multiple items by ID.

WARNING:

The parameter is part of the draft proposal "Query by IDs". The syntax and semantic of the
parameter is subject to change in a future release. Its usage should be carefully considered.

# components.responses.LandingPage.description
The landing page provides links to the API definition
(link relations `service-desc` and `service-doc`),
the Conformance declaration (path `/conformance`,
link relation `conformance`), and the Feature
Collections (path `/collections`, link relation
`data`).

# components.responses.LandingPage.content.application/json.example.description
Access to data about buildings in the city of Bonn via a Web API that conforms to the OGC API Features specification.

# components.responses.LandingPage.content.application/json.example.links[].title
OGC API conformance classes implemented by this server

# components.responses.LandingPage.content.application/json.example.links[].title
Information about the feature collections

# components.responses.OpenAPI.description
The OpenAPI page provides an Open API (aka Swagger) view
of the OGC API - Feature interface.

# components.responses.ConformanceDeclaration.description
The URIs of all conformance classes supported by the server.

To support "generic" clients that want to access multiple
OGC API Features implementations - and not "just" a specific
API / server, the server declares the conformance
classes it implements and conforms to.

# components.responses.Collections.description
The feature collections shared by this API.

The dataset is organized as one or more feature collections. This resource
provides information about and access to the collections.

The response contains the list of collections. For each collection, a link
to the items in the collection (path `/collections/{collectionId}/items`,
link relation `items`) as well as key information about the collection.
This information includes:

* A local identifier for the collection that is unique for the dataset;
* A list of coordinate reference systems (CRS) in which geometries may be returned by the server. The first CRS is the default coordinate reference system (the default is always WGS 84 with axis order longitude/latitude);
* An optional title and description for the collection;
* An optional extent that can be used to provide an indication of the spatial and temporal extent of the collection - typically derived from the data;
* An optional indicator about the type of the items in the collection (the default value, if the indicator is not provided, is 'feature').

# components.responses.Collections.content.application/json.example.links[].title
GML application schema for Acme Corporation building data

# components.responses.Queryables.description
Information about the feature collection queryable properties

# components.responses.Collection.description
Information about the feature collection with id `collectionId`.

The response contains a link to the items in the collection
(path `/collections/{collectionId}/items`, link relation `items`)
as well as key information about the collection. This information
includes:

* A local identifier for the collection that is unique for the dataset;
* A list of coordinate reference systems (CRS) in which geometries may be returned by the server. The first CRS is the default coordinate reference system (the default is always WGS 84 with axis order longitude/latitude);
* An optional title and description for the collection;
* An optional extent that can be used to provide an indication of the spatial and temporal extent of the collection - typically derived from the data;
* An optional indicator about the type of the items in the collection (the default value, if the indicator is not provided, is 'feature').

# components.responses.Features.description
The response is a document consisting of features in the collection.
The features included in the response are determined by the server
based on the query parameters of the request. To support access to
larger collections without overloading the client, the API supports
paged access with links to the next page, if more features are selected
that the page size.

The `bbox` and `datetime` parameter can be used to select only a
subset of the features in the collection (the features that are in the
bounding box or time interval). The `bbox` parameter matches all features
in the collection that are not associated with a location, too. The
`datetime` parameter matches all features in the collection that are
not associated with a time stamp or interval, too.

The `limit` parameter may be used to control the subset of the
selected features that should be returned in the response, the page size.
Each page may include information about the number of selected and
returned features (`numberMatched` and `numberReturned`) as well as
links to support paging (link relation `next`).

# components.responses.Feature.description
fetch the feature with id `featureId` in the feature collection
with id `collectionId`

# components.responses.Functions.description
A document listing the server filtering capabilities

# components.parameters.bbox.description
Only features that have a geometry that intersects the bounding box are selected.
The bounding box is provided as four or six numbers, depending on whether the
coordinate reference system includes a vertical axis (height or depth):

* Lower left corner, coordinate axis 1
* Lower left corner, coordinate axis 2
* Minimum value, coordinate axis 3 (optional)
* Upper right corner, coordinate axis 1
* Upper right corner, coordinate axis 2
* Maximum value, coordinate axis 3 (optional)

The coordinate reference system of the values is WGS 84 longitude/latitude
(http://www.opengis.net/def/crs/OGC/1.3/CRS84) unless a different coordinate
reference system is specified in the parameter `bbox-crs`.

For WGS 84 longitude/latitude the values are in most cases the sequence of
minimum longitude, minimum latitude, maximum longitude and maximum latitude.
However, in cases where the box spans the antimeridian the first value
(west-most box edge) is larger than the third value (east-most box edge).

If the vertical axis is included, the third and the sixth number are
the bottom and the top of the 3-dimensional bounding box.

If a feature has multiple spatial geometry properties, it is the decision of the
server whether only a single spatial geometry property is used to determine
the extent or all relevant geometries.

# components.parameters.datetime.description
Either a date-time or an interval, open or closed. Date and time expressions
adhere to RFC 3339. Open intervals are expressed using double-dots.

Examples:

* A date-time: "2018-02-12T23:20:50Z"
* A closed interval: "2018-02-12T00:00:00Z/2018-03-18T12:31:12Z"
* Open intervals: "2018-02-12T00:00:00Z/.." or "../2018-03-18T12:31:12Z"

Only features that have a temporal property that intersects the value of
`datetime` are selected.

If a feature has multiple temporal properties, it is the decision of the
server whether only a single temporal property is used to determine
the extent or all relevant temporal properties.

# components.parameters.limit.description
The optional limit parameter limits the number of items that are presented in the response document.

Only items are counted that are on the first level of the collection in the response document.
Nested objects contained within the explicitly requested items shall not be counted.

Minimum = 1. Maximum = 10000. Default = 10.

# components.parameters.filter.description
Defines a filter that will be applied on items, only items matching the filter will be returned

# components.parameters.filter-lang.description
Filter encoding used in the filter parameter

# components.parameters.filter-crs.description
Filter CRS which is being used to encode geometries in the filter parameter

# components.parameters.sortby.description
Defines how features in a response should be ordered for presentation.

# components.parameters.ids.description
Query multiple items by ID.

WARNING:

The parameter is part of the draft proposal "Query by IDs". The syntax and semantic of the
parameter is subject to change in a future release. Its usage should be carefully considered.

# components.parameters.otherParameters.description
Allows unrecognized parameters to be added in the query string without getting a 400 back (e.g., cache busters)