Features

fetch features

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.

get/collections/{collectionId}/items

Path parameters

collectionIdstring required

local identifier of a collection

Query parameters

limitinteger

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.

bboxnumber[]

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.

datetimestring

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.

Response

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).

Changes

Changed in 3 of the 8 revisions of this API.7413

    • api tag Features added

      api-tag-added

    • api tag Data removed

      api-tag-removed

  • 3220e999390419See the full diff
    • added the new path request parameter collectionId

      new-request-path-parameter

    • added the new optional query request parameter bbox

      new-optional-request-parameter

    • added the new optional query request parameter datetime

      new-optional-request-parameter

    • added the new optional query request parameter limit

      new-optional-request-parameter

    • added the media type application/geo+json for the response with the status 200

      response-media-type-added

    • added the media type application/json for the response with the status 400

      response-media-type-added

    • added the media type application/json for the response with the status 500

      response-media-type-added

    • added the media type text/html for the response with the status 200

      response-media-type-added

    • added the media type text/html for the response with the status 400

      response-media-type-added

    • added the media type text/html for the response with the status 500

      response-media-type-added

  • ce8e28fd78b3642See the full diff
    • removed the media type application/geo+json for the response with the status 200

      response-media-type-removed

    • removed the media type application/json for the response with the status 400

      response-media-type-removed

    • removed the media type application/json for the response with the status 500

      response-media-type-removed

    • removed the media type text/html for the response with the status 200

      response-media-type-removed

    • removed the media type text/html for the response with the status 400

      response-media-type-removed

    • removed the media type text/html for the response with the status 500

      response-media-type-removed

    • deleted the path request parameter collectionId

      request-parameter-removed

    • deleted the query request parameter bbox

      request-parameter-removed

    • deleted the query request parameter datetime

      request-parameter-removed

    • deleted the query request parameter limit

      request-parameter-removed

    • api tag Data added

      api-tag-added

    • api tag Features removed

      api-tag-removed

    This revision also has 20 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog