# info.description
De OGC API Features service Vervoersnetwerken - Waterwegen - Netwerk bevat het INSPIRE-compliant netwerk van knooppunten (nodes) en vaarwegvakken (links)

# info.title
Vervoersnetwerken - Waterwegen - Netwerk (INSPIRE geharmoniseerd)

# paths./.get.description
The landing page provides links to the API definition and the conformance statements for this API.

# paths./.get.responses.400.description
Bad request: For example, invalid or unknown query parameters.

# paths./.get.responses.404.description
Not found: The requested resource does not exist on the server. For example, a path parameter had an incorrect value.

# paths./.get.responses.406.description
Not acceptable: The requested media type is not supported by this resource.

# paths./.get.responses.500.description
Internal server error: An unexpected server error occurred.

# paths./.get.responses.502.description
Bad Gateway: An unexpected error occurred while forwarding/proxying the request to another server.

# paths./api.get.responses.400.description
Bad request: For example, invalid or unknown query parameters.

# paths./api.get.responses.404.description
Not found: The requested resource does not exist on the server. For example, a path parameter had an incorrect value.

# paths./api.get.responses.406.description
Not acceptable: The requested media type is not supported by this resource.

# paths./api.get.responses.500.description
Internal server error: An unexpected server error occurred.

# paths./api.get.responses.502.description
Bad Gateway: An unexpected error occurred while forwarding/proxying the request to another server.

# paths./collections.get.description
A list of all collections (geospatial data resources) in this dataset.

# paths./collections.get.parameters[].description
The format of the response. If no value is provided, the standard http
rules apply, i.e., the accept header is used to determine the format.

Pre-defined values are "json" and "html". The response to other
values is determined by the server.

# paths./collections.get.responses.200.description
The collections (geospatial data resources) shared by this API.

This response can be references directly for every service that wants only essential information at the collections level. /collections/collectionId might return more information.

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

# paths./collections.get.responses.400.description
Bad request: For example, invalid or unknown query parameters.

# paths./collections.get.responses.404.description
Not found: The requested resource does not exist on the server. For example, a path parameter had an incorrect value.

# paths./collections.get.responses.406.description
Not acceptable: The requested media type is not supported by this resource.

# paths./collections.get.responses.500.description
Internal server error: An unexpected server error occurred.

# paths./collections.get.responses.502.description
Bad Gateway: An unexpected error occurred while forwarding/proxying the request to another server.

# paths./collections/beacon.get.description
beacon collection (geospatial data resource) in this dataset.

# paths./collections/beacon.get.parameters[].description
The format of the response. If no value is provided, the standard http
rules apply, i.e., the accept header is used to determine the format.

Pre-defined values are "json" and "html". The response to other
values is determined by the server.

# paths./collections/beacon.get.responses.400.description
Bad request: For example, invalid or unknown query parameters.

# paths./collections/beacon.get.responses.404.description
Not found: The requested resource does not exist on the server. For example, a path parameter had an incorrect value.

# paths./collections/beacon.get.responses.406.description
Not acceptable: The requested media type is not supported by this resource.

# paths./collections/beacon.get.responses.500.description
Internal server error: An unexpected server error occurred.

# paths./collections/beacon.get.responses.502.description
Bad Gateway: An unexpected error occurred while forwarding/proxying the request to another server.

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

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/beacon/items.get.responses.200.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 links to support paging (link relation `next`).

# paths./collections/beacon/items.get.responses.200.headers.Content-Crs.description
a URI, in angular brackets, identifying the coordinate reference system used in the content / payload

# paths./collections/beacon/items.get.responses.400.description
Bad request: For example, invalid or unknown query parameters.

# paths./collections/beacon/items.get.responses.404.description
Not found: The requested resource does not exist on the server. For example, a path parameter had an incorrect value.

# paths./collections/beacon/items.get.responses.406.description
Not acceptable: The requested media type is not supported by this resource.

# paths./collections/beacon/items.get.responses.500.description
Internal server error: An unexpected server error occurred.

# paths./collections/beacon/items.get.responses.502.description
Bad Gateway: An unexpected error occurred while forwarding/proxying the request to another server.

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

Use content negotiation to request HTML or GeoJSON.

# paths./collections/beacon/items/{featureId}.get.responses.200.description
fetch the feature with id `featureId` in the feature collection
with id `collectionId`

# paths./collections/beacon/items/{featureId}.get.responses.200.headers.Content-Crs.description
a URI, in angular brackets, identifying the coordinate reference system used in the content / payload

# paths./collections/beacon/items/{featureId}.get.responses.400.description
Bad request: For example, invalid or unknown query parameters.

# paths./collections/beacon/items/{featureId}.get.responses.404.description
Not found: The requested resource does not exist on the server. For example, a path parameter had an incorrect value.

# paths./collections/beacon/items/{featureId}.get.responses.406.description
Not acceptable: The requested media type is not supported by this resource.

# paths./collections/beacon/items/{featureId}.get.responses.500.description
Internal server error: An unexpected server error occurred.

# paths./collections/beacon/items/{featureId}.get.responses.502.description
Bad Gateway: An unexpected error occurred while forwarding/proxying the request to another server.

# paths./collections/beacon/schema.get.description
Fetch the schema of the collection with id `beacon`. The schema describes the features such as the available fields and data types.

Use content negotiation to request HTML or JSON schema.

# paths./collections/beacon/schema.get.responses.200.description
The response is a document containing the schema that describes the features in this collection.

# paths./collections/beacon/schema.get.responses.400.description
Bad request: For example, invalid or unknown query parameters.

# paths./collections/beacon/schema.get.responses.404.description
Not found: The requested resource does not exist on the server. For example, a path parameter had an incorrect value.

# paths./collections/beacon/schema.get.responses.406.description
Not acceptable: The requested media type is not supported by this resource.

# paths./collections/beacon/schema.get.responses.500.description
Internal server error: An unexpected server error occurred.

# paths./collections/beacon/schema.get.responses.502.description
Bad Gateway: An unexpected error occurred while forwarding/proxying the request to another server.

# paths./collections/buoy.get.description
buoy collection (geospatial data resource) in this dataset.

# paths./collections/buoy.get.parameters[].description
The format of the response. If no value is provided, the standard http
rules apply, i.e., the accept header is used to determine the format.

Pre-defined values are "json" and "html". The response to other
values is determined by the server.

# paths./collections/buoy.get.responses.400.description
Bad request: For example, invalid or unknown query parameters.

# paths./collections/buoy.get.responses.404.description
Not found: The requested resource does not exist on the server. For example, a path parameter had an incorrect value.

# paths./collections/buoy.get.responses.406.description
Not acceptable: The requested media type is not supported by this resource.

# paths./collections/buoy.get.responses.500.description
Internal server error: An unexpected server error occurred.

# paths./collections/buoy.get.responses.502.description
Bad Gateway: An unexpected error occurred while forwarding/proxying the request to another server.

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

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/buoy/items.get.responses.200.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 links to support paging (link relation `next`).

# paths./collections/buoy/items.get.responses.200.headers.Content-Crs.description
a URI, in angular brackets, identifying the coordinate reference system used in the content / payload

# paths./collections/buoy/items.get.responses.400.description
Bad request: For example, invalid or unknown query parameters.

# paths./collections/buoy/items.get.responses.404.description
Not found: The requested resource does not exist on the server. For example, a path parameter had an incorrect value.

# paths./collections/buoy/items.get.responses.406.description
Not acceptable: The requested media type is not supported by this resource.

# paths./collections/buoy/items.get.responses.500.description
Internal server error: An unexpected server error occurred.

# paths./collections/buoy/items.get.responses.502.description
Bad Gateway: An unexpected error occurred while forwarding/proxying the request to another server.

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

Use content negotiation to request HTML or GeoJSON.

# paths./collections/buoy/items/{featureId}.get.responses.200.description
fetch the feature with id `featureId` in the feature collection
with id `collectionId`

# paths./collections/buoy/items/{featureId}.get.responses.200.headers.Content-Crs.description
a URI, in angular brackets, identifying the coordinate reference system used in the content / payload

# paths./collections/buoy/items/{featureId}.get.responses.400.description
Bad request: For example, invalid or unknown query parameters.

# paths./collections/buoy/items/{featureId}.get.responses.404.description
Not found: The requested resource does not exist on the server. For example, a path parameter had an incorrect value.

# paths./collections/buoy/items/{featureId}.get.responses.406.description
Not acceptable: The requested media type is not supported by this resource.

# paths./collections/buoy/items/{featureId}.get.responses.500.description
Internal server error: An unexpected server error occurred.

# paths./collections/buoy/items/{featureId}.get.responses.502.description
Bad Gateway: An unexpected error occurred while forwarding/proxying the request to another server.

# paths./collections/buoy/schema.get.description
Fetch the schema of the collection with id `buoy`. The schema describes the features such as the available fields and data types.

Use content negotiation to request HTML or JSON schema.

# paths./collections/buoy/schema.get.responses.200.description
The response is a document containing the schema that describes the features in this collection.

# paths./collections/buoy/schema.get.responses.400.description
Bad request: For example, invalid or unknown query parameters.

# paths./collections/buoy/schema.get.responses.404.description
Not found: The requested resource does not exist on the server. For example, a path parameter had an incorrect value.

# paths./collections/buoy/schema.get.responses.406.description
Not acceptable: The requested media type is not supported by this resource.

# paths./collections/buoy/schema.get.responses.500.description
Internal server error: An unexpected server error occurred.

# paths./collections/buoy/schema.get.responses.502.description
Bad Gateway: An unexpected error occurred while forwarding/proxying the request to another server.

# paths./collections/marker_post.get.description
marker_post collection (geospatial data resource) in this dataset.

# paths./collections/marker_post.get.parameters[].description
The format of the response. If no value is provided, the standard http
rules apply, i.e., the accept header is used to determine the format.

Pre-defined values are "json" and "html". The response to other
values is determined by the server.

# paths./collections/marker_post.get.responses.400.description
Bad request: For example, invalid or unknown query parameters.

# paths./collections/marker_post.get.responses.404.description
Not found: The requested resource does not exist on the server. For example, a path parameter had an incorrect value.

# paths./collections/marker_post.get.responses.406.description
Not acceptable: The requested media type is not supported by this resource.

# paths./collections/marker_post.get.responses.500.description
Internal server error: An unexpected server error occurred.

# paths./collections/marker_post.get.responses.502.description
Bad Gateway: An unexpected error occurred while forwarding/proxying the request to another server.

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

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/marker_post/items.get.responses.200.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 links to support paging (link relation `next`).

# paths./collections/marker_post/items.get.responses.200.headers.Content-Crs.description
a URI, in angular brackets, identifying the coordinate reference system used in the content / payload

# paths./collections/marker_post/items.get.responses.400.description
Bad request: For example, invalid or unknown query parameters.

# paths./collections/marker_post/items.get.responses.404.description
Not found: The requested resource does not exist on the server. For example, a path parameter had an incorrect value.

# paths./collections/marker_post/items.get.responses.406.description
Not acceptable: The requested media type is not supported by this resource.

# paths./collections/marker_post/items.get.responses.500.description
Internal server error: An unexpected server error occurred.

# paths./collections/marker_post/items.get.responses.502.description
Bad Gateway: An unexpected error occurred while forwarding/proxying the request to another server.

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

Use content negotiation to request HTML or GeoJSON.

# paths./collections/marker_post/items/{featureId}.get.responses.200.description
fetch the feature with id `featureId` in the feature collection
with id `collectionId`

# paths./collections/marker_post/items/{featureId}.get.responses.200.headers.Content-Crs.description
a URI, in angular brackets, identifying the coordinate reference system used in the content / payload

# paths./collections/marker_post/items/{featureId}.get.responses.400.description
Bad request: For example, invalid or unknown query parameters.

# paths./collections/marker_post/items/{featureId}.get.responses.404.description
Not found: The requested resource does not exist on the server. For example, a path parameter had an incorrect value.

# paths./collections/marker_post/items/{featureId}.get.responses.406.description
Not acceptable: The requested media type is not supported by this resource.

# paths./collections/marker_post/items/{featureId}.get.responses.500.description
Internal server error: An unexpected server error occurred.

# paths./collections/marker_post/items/{featureId}.get.responses.502.description
Bad Gateway: An unexpected error occurred while forwarding/proxying the request to another server.

# paths./collections/marker_post/schema.get.description
Fetch the schema of the collection with id `marker_post`. The schema describes the features such as the available fields and data types.

Use content negotiation to request HTML or JSON schema.

# paths./collections/marker_post/schema.get.responses.200.description
The response is a document containing the schema that describes the features in this collection.

# paths./collections/marker_post/schema.get.responses.400.description
Bad request: For example, invalid or unknown query parameters.

# paths./collections/marker_post/schema.get.responses.404.description
Not found: The requested resource does not exist on the server. For example, a path parameter had an incorrect value.

# paths./collections/marker_post/schema.get.responses.406.description
Not acceptable: The requested media type is not supported by this resource.

# paths./collections/marker_post/schema.get.responses.500.description
Internal server error: An unexpected server error occurred.

# paths./collections/marker_post/schema.get.responses.502.description
Bad Gateway: An unexpected error occurred while forwarding/proxying the request to another server.

# paths./collections/traffic_separation_scheme_crossing.get.parameters[].description
The format of the response. If no value is provided, the standard http
rules apply, i.e., the accept header is used to determine the format.

Pre-defined values are "json" and "html". The response to other
values is determined by the server.

# paths./collections/traffic_separation_scheme_crossing.get.responses.400.description
Bad request: For example, invalid or unknown query parameters.

# paths./collections/traffic_separation_scheme_crossing.get.responses.404.description
Not found: The requested resource does not exist on the server. For example, a path parameter had an incorrect value.

# paths./collections/traffic_separation_scheme_crossing.get.responses.406.description
Not acceptable: The requested media type is not supported by this resource.

# paths./collections/traffic_separation_scheme_crossing.get.responses.500.description
Internal server error: An unexpected server error occurred.

# paths./collections/traffic_separation_scheme_crossing.get.responses.502.description
Bad Gateway: An unexpected error occurred while forwarding/proxying the request to another server.

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

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/traffic_separation_scheme_crossing/items.get.responses.200.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 links to support paging (link relation `next`).

# paths./collections/traffic_separation_scheme_crossing/items.get.responses.200.headers.Content-Crs.description
a URI, in angular brackets, identifying the coordinate reference system used in the content / payload

# paths./collections/traffic_separation_scheme_crossing/items.get.responses.400.description
Bad request: For example, invalid or unknown query parameters.

# paths./collections/traffic_separation_scheme_crossing/items.get.responses.404.description
Not found: The requested resource does not exist on the server. For example, a path parameter had an incorrect value.

# paths./collections/traffic_separation_scheme_crossing/items.get.responses.406.description
Not acceptable: The requested media type is not supported by this resource.

# paths./collections/traffic_separation_scheme_crossing/items.get.responses.500.description
Internal server error: An unexpected server error occurred.

# paths./collections/traffic_separation_scheme_crossing/items.get.responses.502.description
Bad Gateway: An unexpected error occurred while forwarding/proxying the request to another server.

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

Use content negotiation to request HTML or GeoJSON.

# paths./collections/traffic_separation_scheme_crossing/items/{featureId.get.responses.200.description
fetch the feature with id `featureId` in the feature collection
with id `collectionId`

# paths./collections/traffic_separation_scheme_crossing/items/{featureId.get.responses.200.headers.Content-Crs.description
a URI, in angular brackets, identifying the coordinate reference system used in the content / payload

# paths./collections/traffic_separation_scheme_crossing/items/{featureId.get.responses.400.description
Bad request: For example, invalid or unknown query parameters.

# paths./collections/traffic_separation_scheme_crossing/items/{featureId.get.responses.404.description
Not found: The requested resource does not exist on the server. For example, a path parameter had an incorrect value.

# paths./collections/traffic_separation_scheme_crossing/items/{featureId.get.responses.406.description
Not acceptable: The requested media type is not supported by this resource.

# paths./collections/traffic_separation_scheme_crossing/items/{featureId.get.responses.500.description
Internal server error: An unexpected server error occurred.

# paths./collections/traffic_separation_scheme_crossing/items/{featureId.get.responses.502.description
Bad Gateway: An unexpected error occurred while forwarding/proxying the request to another server.

# paths./collections/traffic_separation_scheme_crossing/schema.get.description
Fetch the schema of the collection with id `traffic_separation_scheme_crossing`. The schema describes the features such as the available fields and data types.

Use content negotiation to request HTML or JSON schema.

# paths./collections/traffic_separation_scheme_crossing/schema.get.responses.200.description
The response is a document containing the schema that describes the features in this collection.

# paths./collections/traffic_separation_scheme_crossing/schema.get.responses.400.description
Bad request: For example, invalid or unknown query parameters.

# paths./collections/traffic_separation_scheme_crossing/schema.get.responses.404.description
Not found: The requested resource does not exist on the server. For example, a path parameter had an incorrect value.

# paths./collections/traffic_separation_scheme_crossing/schema.get.responses.406.description
Not acceptable: The requested media type is not supported by this resource.

# paths./collections/traffic_separation_scheme_crossing/schema.get.responses.500.description
Internal server error: An unexpected server error occurred.

# paths./collections/traffic_separation_scheme_crossing/schema.get.responses.502.description
Bad Gateway: An unexpected error occurred while forwarding/proxying the request to another server.

# paths./collections/traffic_separation_scheme_separator.get.parameters[].description
The format of the response. If no value is provided, the standard http
rules apply, i.e., the accept header is used to determine the format.

Pre-defined values are "json" and "html". The response to other
values is determined by the server.

# paths./collections/traffic_separation_scheme_separator.get.responses.400.description
Bad request: For example, invalid or unknown query parameters.

# paths./collections/traffic_separation_scheme_separator.get.responses.404.description
Not found: The requested resource does not exist on the server. For example, a path parameter had an incorrect value.

# paths./collections/traffic_separation_scheme_separator.get.responses.406.description
Not acceptable: The requested media type is not supported by this resource.

# paths./collections/traffic_separation_scheme_separator.get.responses.500.description
Internal server error: An unexpected server error occurred.

# paths./collections/traffic_separation_scheme_separator.get.responses.502.description
Bad Gateway: An unexpected error occurred while forwarding/proxying the request to another server.

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

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/traffic_separation_scheme_separator/items.get.responses.200.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 links to support paging (link relation `next`).

# paths./collections/traffic_separation_scheme_separator/items.get.responses.200.headers.Content-Crs.description
a URI, in angular brackets, identifying the coordinate reference system used in the content / payload

# paths./collections/traffic_separation_scheme_separator/items.get.responses.400.description
Bad request: For example, invalid or unknown query parameters.

# paths./collections/traffic_separation_scheme_separator/items.get.responses.404.description
Not found: The requested resource does not exist on the server. For example, a path parameter had an incorrect value.

# paths./collections/traffic_separation_scheme_separator/items.get.responses.406.description
Not acceptable: The requested media type is not supported by this resource.

# paths./collections/traffic_separation_scheme_separator/items.get.responses.500.description
Internal server error: An unexpected server error occurred.

# paths./collections/traffic_separation_scheme_separator/items.get.responses.502.description
Bad Gateway: An unexpected error occurred while forwarding/proxying the request to another server.

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

Use content negotiation to request HTML or GeoJSON.

# paths./collections/traffic_separation_scheme_separator/items/{featureI.get.responses.200.description
fetch the feature with id `featureId` in the feature collection
with id `collectionId`

# paths./collections/traffic_separation_scheme_separator/items/{featureI.get.responses.200.headers.Content-Crs.description
a URI, in angular brackets, identifying the coordinate reference system used in the content / payload

# paths./collections/traffic_separation_scheme_separator/items/{featureI.get.responses.400.description
Bad request: For example, invalid or unknown query parameters.

# paths./collections/traffic_separation_scheme_separator/items/{featureI.get.responses.404.description
Not found: The requested resource does not exist on the server. For example, a path parameter had an incorrect value.

# paths./collections/traffic_separation_scheme_separator/items/{featureI.get.responses.406.description
Not acceptable: The requested media type is not supported by this resource.

# paths./collections/traffic_separation_scheme_separator/items/{featureI.get.responses.500.description
Internal server error: An unexpected server error occurred.

# paths./collections/traffic_separation_scheme_separator/items/{featureI.get.responses.502.description
Bad Gateway: An unexpected error occurred while forwarding/proxying the request to another server.

# paths./collections/traffic_separation_scheme_separator/schema.get.description
Fetch the schema of the collection with id `traffic_separation_scheme_separator`. The schema describes the features such as the available fields and data types.

Use content negotiation to request HTML or JSON schema.

# paths./collections/traffic_separation_scheme_separator/schema.get.responses.200.description
The response is a document containing the schema that describes the features in this collection.

# paths./collections/traffic_separation_scheme_separator/schema.get.responses.400.description
Bad request: For example, invalid or unknown query parameters.

# paths./collections/traffic_separation_scheme_separator/schema.get.responses.404.description
Not found: The requested resource does not exist on the server. For example, a path parameter had an incorrect value.

# paths./collections/traffic_separation_scheme_separator/schema.get.responses.406.description
Not acceptable: The requested media type is not supported by this resource.

# paths./collections/traffic_separation_scheme_separator/schema.get.responses.500.description
Internal server error: An unexpected server error occurred.

# paths./collections/traffic_separation_scheme_separator/schema.get.responses.502.description
Bad Gateway: An unexpected error occurred while forwarding/proxying the request to another server.

# paths./collections/waterway_link.get.description
waterway_link collection (geospatial data resource) in this dataset.

# paths./collections/waterway_link.get.parameters[].description
The format of the response. If no value is provided, the standard http
rules apply, i.e., the accept header is used to determine the format.

Pre-defined values are "json" and "html". The response to other
values is determined by the server.

# paths./collections/waterway_link.get.responses.400.description
Bad request: For example, invalid or unknown query parameters.

# paths./collections/waterway_link.get.responses.404.description
Not found: The requested resource does not exist on the server. For example, a path parameter had an incorrect value.

# paths./collections/waterway_link.get.responses.406.description
Not acceptable: The requested media type is not supported by this resource.

# paths./collections/waterway_link.get.responses.500.description
Internal server error: An unexpected server error occurred.

# paths./collections/waterway_link.get.responses.502.description
Bad Gateway: An unexpected error occurred while forwarding/proxying the request to another server.

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

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/waterway_link/items.get.responses.200.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 links to support paging (link relation `next`).

# paths./collections/waterway_link/items.get.responses.200.headers.Content-Crs.description
a URI, in angular brackets, identifying the coordinate reference system used in the content / payload

# paths./collections/waterway_link/items.get.responses.400.description
Bad request: For example, invalid or unknown query parameters.

# paths./collections/waterway_link/items.get.responses.404.description
Not found: The requested resource does not exist on the server. For example, a path parameter had an incorrect value.

# paths./collections/waterway_link/items.get.responses.406.description
Not acceptable: The requested media type is not supported by this resource.

# paths./collections/waterway_link/items.get.responses.500.description
Internal server error: An unexpected server error occurred.

# paths./collections/waterway_link/items.get.responses.502.description
Bad Gateway: An unexpected error occurred while forwarding/proxying the request to another server.

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

Use content negotiation to request HTML or GeoJSON.

# paths./collections/waterway_link/items/{featureId}.get.responses.200.description
fetch the feature with id `featureId` in the feature collection
with id `collectionId`

# paths./collections/waterway_link/items/{featureId}.get.responses.200.headers.Content-Crs.description
a URI, in angular brackets, identifying the coordinate reference system used in the content / payload

# paths./collections/waterway_link/items/{featureId}.get.responses.400.description
Bad request: For example, invalid or unknown query parameters.

# paths./collections/waterway_link/items/{featureId}.get.responses.404.description
Not found: The requested resource does not exist on the server. For example, a path parameter had an incorrect value.

# paths./collections/waterway_link/items/{featureId}.get.responses.406.description
Not acceptable: The requested media type is not supported by this resource.

# paths./collections/waterway_link/items/{featureId}.get.responses.500.description
Internal server error: An unexpected server error occurred.

# paths./collections/waterway_link/items/{featureId}.get.responses.502.description
Bad Gateway: An unexpected error occurred while forwarding/proxying the request to another server.

# paths./collections/waterway_link/schema.get.description
Fetch the schema of the collection with id `waterway_link`. The schema describes the features such as the available fields and data types.

Use content negotiation to request HTML or JSON schema.

# paths./collections/waterway_link/schema.get.responses.200.description
The response is a document containing the schema that describes the features in this collection.

# paths./collections/waterway_link/schema.get.responses.400.description
Bad request: For example, invalid or unknown query parameters.

# paths./collections/waterway_link/schema.get.responses.404.description
Not found: The requested resource does not exist on the server. For example, a path parameter had an incorrect value.

# paths./collections/waterway_link/schema.get.responses.406.description
Not acceptable: The requested media type is not supported by this resource.

# paths./collections/waterway_link/schema.get.responses.500.description
Internal server error: An unexpected server error occurred.

# paths./collections/waterway_link/schema.get.responses.502.description
Bad Gateway: An unexpected error occurred while forwarding/proxying the request to another server.

# paths./collections/waterway_node.get.description
waterway_node collection (geospatial data resource) in this dataset.

# paths./collections/waterway_node.get.parameters[].description
The format of the response. If no value is provided, the standard http
rules apply, i.e., the accept header is used to determine the format.

Pre-defined values are "json" and "html". The response to other
values is determined by the server.

# paths./collections/waterway_node.get.responses.400.description
Bad request: For example, invalid or unknown query parameters.

# paths./collections/waterway_node.get.responses.404.description
Not found: The requested resource does not exist on the server. For example, a path parameter had an incorrect value.

# paths./collections/waterway_node.get.responses.406.description
Not acceptable: The requested media type is not supported by this resource.

# paths./collections/waterway_node.get.responses.500.description
Internal server error: An unexpected server error occurred.

# paths./collections/waterway_node.get.responses.502.description
Bad Gateway: An unexpected error occurred while forwarding/proxying the request to another server.

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

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/waterway_node/items.get.responses.200.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 links to support paging (link relation `next`).

# paths./collections/waterway_node/items.get.responses.200.headers.Content-Crs.description
a URI, in angular brackets, identifying the coordinate reference system used in the content / payload

# paths./collections/waterway_node/items.get.responses.400.description
Bad request: For example, invalid or unknown query parameters.

# paths./collections/waterway_node/items.get.responses.404.description
Not found: The requested resource does not exist on the server. For example, a path parameter had an incorrect value.

# paths./collections/waterway_node/items.get.responses.406.description
Not acceptable: The requested media type is not supported by this resource.

# paths./collections/waterway_node/items.get.responses.500.description
Internal server error: An unexpected server error occurred.

# paths./collections/waterway_node/items.get.responses.502.description
Bad Gateway: An unexpected error occurred while forwarding/proxying the request to another server.

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

Use content negotiation to request HTML or GeoJSON.

# paths./collections/waterway_node/items/{featureId}.get.responses.200.description
fetch the feature with id `featureId` in the feature collection
with id `collectionId`

# paths./collections/waterway_node/items/{featureId}.get.responses.200.headers.Content-Crs.description
a URI, in angular brackets, identifying the coordinate reference system used in the content / payload

# paths./collections/waterway_node/items/{featureId}.get.responses.400.description
Bad request: For example, invalid or unknown query parameters.

# paths./collections/waterway_node/items/{featureId}.get.responses.404.description
Not found: The requested resource does not exist on the server. For example, a path parameter had an incorrect value.

# paths./collections/waterway_node/items/{featureId}.get.responses.406.description
Not acceptable: The requested media type is not supported by this resource.

# paths./collections/waterway_node/items/{featureId}.get.responses.500.description
Internal server error: An unexpected server error occurred.

# paths./collections/waterway_node/items/{featureId}.get.responses.502.description
Bad Gateway: An unexpected error occurred while forwarding/proxying the request to another server.

# paths./collections/waterway_node/schema.get.description
Fetch the schema of the collection with id `waterway_node`. The schema describes the features such as the available fields and data types.

Use content negotiation to request HTML or JSON schema.

# paths./collections/waterway_node/schema.get.responses.200.description
The response is a document containing the schema that describes the features in this collection.

# paths./collections/waterway_node/schema.get.responses.400.description
Bad request: For example, invalid or unknown query parameters.

# paths./collections/waterway_node/schema.get.responses.404.description
Not found: The requested resource does not exist on the server. For example, a path parameter had an incorrect value.

# paths./collections/waterway_node/schema.get.responses.406.description
Not acceptable: The requested media type is not supported by this resource.

# paths./collections/waterway_node/schema.get.responses.500.description
Internal server error: An unexpected server error occurred.

# paths./collections/waterway_node/schema.get.responses.502.description
Bad Gateway: An unexpected error occurred while forwarding/proxying the request to another server.

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

# paths./conformance.get.responses.400.description
Bad request: For example, invalid or unknown query parameters.

# paths./conformance.get.responses.404.description
Not found: The requested resource does not exist on the server. For example, a path parameter had an incorrect value.

# paths./conformance.get.responses.406.description
Not acceptable: The requested media type is not supported by this resource.

# paths./conformance.get.responses.500.description
Internal server error: An unexpected server error occurred.

# paths./conformance.get.responses.502.description
Bad Gateway: An unexpected error occurred while forwarding/proxying the request to another server.

# components.parameters.bbox.description
Only features that have a geometry that intersects the bounding box are selected.
The bounding box is provided as four numbers
* Lower left corner, coordinate axis 1
* Lower left corner, coordinate axis 2
* Upper right corner, coordinate axis 1
* Upper right corner, coordinate axis 2

The coordinate reference system 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`.

The query parameter `bbox-crs` is specified in OGC API - Features - Part 2: Coordinate
Reference Systems by Reference.

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 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.
The given coordinates should be separated by commas.

# components.parameters.bbox-crs.description
The coordinate reference system of the `bbox` parameter. Default is WGS84 longitude/latitude.

# components.parameters.crs.description
The coordinate reference system of the geometries in the response. Default is WGS84 longitude/latitude

# components.parameters.cursor.description
The optional cursor parameter identifies the page in the features result set. You shouldn't specify the cursor value yourself, instead you should obtain the cursor value from the `next`-link in the features response.

This API uses "_cursor-based pagination_" which has the advantage of allowing users to pagination though all features regardless of the size of the dataset. This wouldn't be possible using traditional "_offset-based pagination_".

# components.parameters.datetime.description
A date-time (intervals are currently not supported). Date and time expressions adhere to RFC 3339.

Examples:

* A date-time: "2018-02-12T23:20:50Z"

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.datetime_notsupported.description
__The `datetime` parameter is not currently supported for this collection__

# components.parameters.f.description
The optional f parameter indicates the output format that the server shall provide as part of the response document.  The default format is JSON.

# components.parameters.f-features.description
The optional f parameter indicates the output format that the server shall provide as part of the response document.  The default format is JSON.

# components.parameters.f-json.description
The format of the response. If no value is provided, the standard http
rules apply, i.e., the accept header is used to determine the format.

The only pre-defined value is "json". The response to other values is
determined by the server.

# components.parameters.f-json-html.description
The format of the response. If no value is provided, the standard http
rules apply, i.e., the accept header is used to determine the format.

Pre-defined values are "json" and "html". The response to other
values is determined by the server.

# 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 = 1000. Default = 10.

# components.parameters.profile.description
Select the profile to be used for the response. Available profiles:

* `rel-as-link`: When the data contains relations between features, each relation is represented by a property with suffix `.href` which contains a URL to the linked feature.
* `rel-as-uri`: When the data contains relations between features, each relation is represented by a property containing the URL to the linked feature.
* `rel-as-key`: When the data contains relations between features, each relation is represented by a property containing only the ID of the linked feature.

# components.parameters.resultType.description
This service will respond to a query in one of two ways (excluding an
exception response). It may either generate a complete response document
containing resources that satisfy the operation or it may simply
generate an empty response container that indicates the count of the
total number of resources that the operation would return. Which of
these two responses is generated is determined by the value of the
optional resultType parameter.

The allowed values for this parameter are "results" and "hits".

If the value of the resultType parameter is set to "results", the server
will generate a complete response document containing resources that
satisfy the operation.

If the value of the resultType attribute is set to "hits", the server
will generate an empty response document containing no resource
instances.

The default value is "results".

# components.responses.400.description
Bad request: For example, invalid or unknown query parameters.

# components.responses.404.description
Not found: The requested resource does not exist on the server. For example, a path parameter had an incorrect value.

# components.responses.406.description
Not acceptable: The requested media type is not supported by this resource.

# components.responses.500.description
Internal server error: An unexpected server error occurred.

# components.responses.502.description
Bad Gateway: An unexpected error occurred while forwarding/proxying the request to another server.

# 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.LandingPage.description
The landing page provides links to the API definition
(link relations `service-desc` and `service-doc`),
and the Conformance declaration (path `/conformance`,
link relation `conformance`).

# components.schemas.bbox.description
One or more bounding boxes that describe the spatial extent of the dataset.

# components.schemas.bbox.items.description
West, south, east, north edges of the bounding box. Specified as coordinates separated by commas. The coordinates
are in the coordinate reference system specified in `crs`. By default
this is WGS 84 longitude/latitude (CRS84).

# components.schemas.collection.properties.crs.description
The list of coordinate reference systems supported by the service. The first item is the default coordinate reference system.

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

# components.schemas.collection.properties.itemType.description
indicator about the type of the items in a collection. Example values: 'feature', 'record', 'attribute'. The default value is 'feature'

# components.schemas.collection.properties.keywords.description
keywords about the elements in the collection

# 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.collection.properties.storageCrsCoordinateEpoch.description
point in time at which coordinates in the spatial feature collection are referenced to the dynamic coordinate reference system in `storageCrs`, that may be used to retrieve features from a collection without the need to apply a change of coordinate epoch. It is expressed as a decimal year in the Gregorian calendar

# components.schemas.collection.properties.storageCrsCoordinateEpoch.example
2017-03-25 in the Gregorian calendar is epoch 2017.23

# components.schemas.collections.properties.links.example[].title
GML application schema for Acme Corporation dataset data

# components.schemas.crs.description
Coordinate reference system of the coordinates in the spatial extent
(property `bbox`). The default reference system is WGS 84 longitude/latitude.

# components.schemas.exception.description
JSON schema for exceptions based on RFC 7807

# components.schemas.exception.properties.detail.description
A human-readable explanation specific to this occurrence of the problem.

# components.schemas.exception.properties.instance.description
A URI reference that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.

# components.schemas.exception.properties.status.description
The HTTP status code generated by the origin server for this occurrence of the problem.

# components.schemas.exception.properties.title.description
A short, human-readable summary of the problem type.

# components.schemas.exception.properties.type.description
A URI reference that identifies the problem type.

# components.schemas.extent.description
The extent of 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.
It is recommended that the statial extent is expected in CRS84 except if this is not possible.

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

# components.schemas.extent_spatial.properties.bbox.description
One or more bounding boxes that describe the spatial extent of the dataset.

# components.schemas.extent_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 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.
The given coordinates should be separated by commas.

# components.schemas.extent_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_temporal.description
The temporal extent of the features in the collection.

# components.schemas.extent_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 unbounded interval end.
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_temporal.properties.interval.items.description
Begin and end times of the time interval. The timestamps are in the
temporal coordinate reference system specified in `trs`. By default
this is the Gregorian calendar.

# components.schemas.extent_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 coordinate reference system.
Extensions may support additional temporal coordinate reference systems and add
additional enum values.

# components.schemas.id-link.description
Reusable object that contains an id to a resource and links where the object is described or a representation retrieved. Typically it is useful for paths like `\resources` and `\resources\{resourceId}`.   `\resources` will respond an array of id-link listing the `resourceId` and the links to get it. \collections and \collections\{collectionId} is an exception to this pattern.
The fact that `links` is an array can be used to advertise the same object representation in different formats.

# components.schemas.jsonSchema.properties.$id.description
URI that serves as the schema identifier

# components.schemas.jsonSchema.properties.$schema.description
URI that identifies the JSON Schema version

# components.schemas.jsonSchema.properties.description.description
Human-readable description of the schema

# components.schemas.landingPage.example[].title
the list of conformance classes implemented by this API

# 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.link.properties.href.description
Supplies the URI to a remote resource (or resource fragment).

# components.schemas.link.properties.hreflang.description
A hint indicating what the language of the result of dereferencing the link should be.

# components.schemas.link.properties.templated.description
This flag set to true if the link is a URL template.

# components.schemas.link.properties.title.description
Used to label the destination of a link such that it can be used as a human-readable identifier.

# components.schemas.link.properties.type.description
A hint indicating what the media type of the result of dereferencing the link should be.

# components.schemas.link.properties.varBase.description
A base path to retrieve semantic information about the variables used in URL template.

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

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

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

# components.schemas.spatialExtent.description
The spatial extent of the element in the collection.

# components.schemas.temporalExtent.description
The temporal extent of the element in the collection.

# components.schemas.temporalInterval.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.temporalInterval.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.timeStamp.description
This property indicates the time and date when the response was generated.

# components.schemas.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.