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.
      explode: false
      in: query
      name: bbox
      required: false
      schema:
        items:
          type: number
        maxItems: 6
        minItems: 4
        type: array
      style: form
    bbox-crs:
      description: The coordinate reference system of the `bbox` parameter. Default
        is WGS84 longitude/latitude.
      explode: false
      in: query
      name: bbox-crs
      required: false
      schema:
        default: http://www.opengis.net/def/crs/OGC/1.3/CRS84
        enum:
        - http://www.opengis.net/def/crs/OGC/1.3/CRS84
        - http://www.opengis.net/def/crs/EPSG/0/28992
        - http://www.opengis.net/def/crs/EPSG/0/3857
        - http://www.opengis.net/def/crs/EPSG/0/4258
        format: uri
        type: string
      style: form
    collectionId:
      description: local identifier of a collection
      explode: false
      in: path
      name: collectionId
      required: true
      schema:
        type: string
      style: simple
    crs:
      description: The coordinate reference system of the geometries in the response.
        Default is WGS84 longitude/latitude
      explode: false
      in: query
      name: crs
      required: false
      schema:
        default: http://www.opengis.net/def/crs/OGC/1.3/CRS84
        enum:
        - http://www.opengis.net/def/crs/OGC/1.3/CRS84
        - http://www.opengis.net/def/crs/EPSG/0/28992
        - http://www.opengis.net/def/crs/EPSG/0/3857
        - http://www.opengis.net/def/crs/EPSG/0/4258
        format: uri
        type: string
      style: form
    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_".
      explode: false
      in: query
      name: cursor
      required: false
      schema:
        type: string
      style: form
    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.
      explode: false
      in: query
      name: datetime
      required: false
      schema:
        type: string
      style: form
    datetime_notsupported:
      description: __The `datetime` parameter is not currently supported for this
        collection__
      explode: false
      in: query
      name: datetime
      required: false
      schema:
        type: string
      style: form
    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.
      explode: false
      in: query
      name: f
      required: false
      schema:
        default: json
        enum:
        - json
        - html
        type: string
      style: form
    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.
      explode: false
      in: query
      name: f
      required: false
      schema:
        default: json
        enum:
        - json
        - jsonfg
        - html
        type: string
      style: form
    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.
      example: json
      explode: false
      in: query
      name: f
      required: false
      schema:
        enum:
        - json
        type: string
      style: form
    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.
      example: json
      explode: false
      in: query
      name: f
      required: false
      schema:
        enum:
        - json
        - html
        type: string
      style: form
    featureId:
      description: local identifier of a feature
      explode: false
      in: path
      name: featureId
      required: true
      schema:
        type: string
      style: simple
    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.
      explode: false
      in: query
      name: limit
      required: false
      schema:
        default: 10
        maximum: 1000
        minimum: 1
        type: integer
      style: form
    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.
      explode: false
      in: query
      name: profile
      required: false
      schema:
        items:
          enum:
          - rel-as-link
          - rel-as-uri
          - rel-as-key
          type: string
        type: array
      style: form
    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".
      example: results
      explode: false
      in: query
      name: resultType
      required: false
      schema:
        default: results
        enum:
        - hits
        - results
        type: string
      style: form
  responses:
    "200":
      description: General Success response.
      headers:
        API-Version:
          description: Semantic version (semver) of the API according to [API Design
            Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
          example: 1.0.0
          schema:
            example: 1.0.0
            pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
            type: string
    "400":
      content:
        application/problem+json:
          schema:
            $ref: '#/components/schemas/exception'
      description: 'Bad request: For example, invalid or unknown query parameters.'
      headers:
        API-Version:
          description: Semantic version (semver) of the API according to [API Design
            Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
          example: 1.0.0
          schema:
            example: 1.0.0
            pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
            type: string
    "404":
      content:
        application/problem+json:
          schema:
            $ref: '#/components/schemas/exception'
      description: 'Not found: The requested resource does not exist on the server.
        For example, a path parameter had an incorrect value.'
      headers:
        API-Version:
          description: Semantic version (semver) of the API according to [API Design
            Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
          example: 1.0.0
          schema:
            example: 1.0.0
            pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
            type: string
    "406":
      content:
        application/problem+json:
          schema:
            $ref: '#/components/schemas/exception'
      description: 'Not acceptable: The requested media type is not supported by this
        resource.'
      headers:
        API-Version:
          description: Semantic version (semver) of the API according to [API Design
            Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
          example: 1.0.0
          schema:
            example: 1.0.0
            pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
            type: string
    "500":
      content:
        application/problem+json:
          schema:
            $ref: '#/components/schemas/exception'
      description: 'Internal server error: An unexpected server error occurred.'
      headers:
        API-Version:
          description: Semantic version (semver) of the API according to [API Design
            Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
          example: 1.0.0
          schema:
            example: 1.0.0
            pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
            type: string
    "502":
      content:
        application/problem+json:
          schema:
            $ref: '#/components/schemas/exception'
      description: 'Bad Gateway: An unexpected error occurred while forwarding/proxying
        the request to another server.'
      headers:
        API-Version:
          description: Semantic version (semver) of the API according to [API Design
            Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
          example: 1.0.0
          schema:
            example: 1.0.0
            pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
            type: string
    ConformanceDeclaration:
      content:
        application/json:
          example:
            conformsTo:
            - http://www.opengis.net/spec/ogcapi-common-1/1.0/conf/core
            - http://www.opengis.net/spec/ogcapi-common-1/1.0/conf/landingPage
            - http://www.opengis.net/spec/ogcapi-common-1/1.0/conf/oas30
            - http://www.opengis.net/spec/ogcapi-common-1/1.0/conf/html
            - http://www.opengis.net/spec/ogcapi-common-1/1.0/conf/json
          schema:
            $ref: '#/components/schemas/confClasses'
        text/html:
          schema:
            type: string
      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.
      headers:
        API-Version:
          description: Semantic version (semver) of the API according to [API Design
            Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
          example: 1.0.0
          schema:
            example: 1.0.0
            pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
            type: string
    LandingPage:
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/landingPage'
        application/vnd.oai.openapi+json;version=3.0:
          schema:
            $ref: '#/components/schemas/landingPage'
        text/html:
          schema:
            type: string
      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`).
      headers:
        API-Version:
          description: Semantic version (semver) of the API according to [API Design
            Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
          example: 1.0.0
          schema:
            example: 1.0.0
            pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
            type: string
  schemas:
    bbox:
      description: One or more bounding boxes that describe the spatial extent of
        the dataset.
      example:
      - 7.01
      - 50.63
      - 7.22
      - 50.78
      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).
        items:
          type: number
        maxItems: 6
        minItems: 4
        type: array
      minItems: 1
      type: array
    collection:
      properties:
        crs:
          default:
          - http://www.opengis.net/def/crs/OGC/1.3/CRS84
          description: The list of coordinate reference systems supported by the service.
            The first item is the default coordinate reference system.
          example:
          - http://www.opengis.net/def/crs/OGC/1.3/CRS84
          - http://www.opengis.net/def/crs/EPSG/0/4326
          items:
            type: string
          type: array
        description:
          description: a description of the collection
          example: This collection contains buildings
          type: string
        extent:
          $ref: '#/components/schemas/extent'
        id:
          description: identifier of the collection used, for example, in URIs
          example: buildings
          type: string
        itemType:
          default: feature
          description: 'indicator about the type of the items in a collection. Example
            values: ''feature'', ''record'', ''attribute''. The default value is ''feature'''
          type: string
        keywords:
          description: keywords about the elements in the collection
          items:
            $ref: '#/components/schemas/keyword'
          type: array
        links:
          example:
          - href: http://example.com/collections/buildings?f=json
            rel: item
            title: this document
            type: application/json
          - href: http://example.com/concepts/buildings?f=html
            rel: it
            title: this document as HTML
            type: text/html
          items:
            $ref: '#/components/schemas/link'
          type: array
        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
          format: uri
          type: string
        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
          example: 2017-03-25 in the Gregorian calendar is epoch 2017.23
          type: number
        title:
          description: human readable title of the collection
          example: Buildings in the city of Bonn
          type: string
      required:
      - id
      - links
      - crs
      type: object
    collections:
      properties:
        collections:
          items:
            $ref: '#/components/schemas/collection'
          type: array
        links:
          example:
          - href: http://data.example.org/collections?f=json
            rel: self
            title: this document
            type: application/json
          - href: http://data.example.org/collections?f=html
            rel: alternate
            title: this document as HTML
            type: text/html
          - href: http://schemas.example.org/1.0/dataset.xsd
            rel: describedby
            title: GML application schema for Acme Corporation dataset data
            type: application/xml
          - href: http://download.example.org/dataset.gpkg
            length: 472546
            rel: enclosure
            title: Bulk download (GeoPackage)
            type: application/geopackage+sqlite3
          items:
            $ref: '#/components/schemas/link'
          nullable: true
          type: array
      required:
      - links
      - collections
      type: object
    confClasses:
      properties:
        conformsTo:
          items:
            type: string
          type: array
      required:
      - conformsTo
      type: object
    crs:
      default: http://www.opengis.net/def/crs/OGC/1.3/CRS84
      description: |-
        Coordinate reference system of the coordinates in the spatial extent
        (property `bbox`). The default reference system is WGS 84 longitude/latitude.
      type: string
    exception:
      description: JSON schema for exceptions based on RFC 7807
      properties:
        detail:
          description: A human-readable explanation specific to this occurrence of
            the problem.
          type: string
        instance:
          description: A URI reference that identifies the specific occurrence of
            the problem. It may or may not yield further information if dereferenced.
          type: string
        status:
          description: The HTTP status code generated by the origin server for this
            occurrence of the problem.
          type: integer
        title:
          description: A short, human-readable summary of the problem type.
          type: string
        type:
          description: A URI reference that identifies the problem type.
          type: string
      required:
      - title
      type: object
    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.
      properties:
        spatial:
          $ref: '#/components/schemas/spatialExtent'
        temporal:
          $ref: '#/components/schemas/temporalExtent'
      type: object
    extent_spatial:
      description: The spatial extent of the features in the collection.
      properties:
        bbox:
          description: One or more bounding boxes that describe the spatial extent
            of the dataset.
          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.
            example:
            - -180
            - -90
            - 180
            - 90
            items:
              type: number
            type: array
          minItems: 1
          type: array
        crs:
          default: http://www.opengis.net/def/crs/OGC/1.3/CRS84
          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.
          enum:
          - http://www.opengis.net/def/crs/OGC/1.3/CRS84
          type: string
      type: object
    extent_temporal:
      description: The temporal extent of the features in the collection.
      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.
          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.
            example:
            - "2011-11-11T12:22:11Z"
            - null
            items:
              format: date-time
              nullable: true
              type: string
            maxItems: 2
            minItems: 2
            type: array
          minItems: 1
          type: array
        trs:
          default: http://www.opengis.net/def/uom/ISO-8601/0/Gregorian
          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.
          enum:
          - http://www.opengis.net/def/uom/ISO-8601/0/Gregorian
          type: string
      type: object
    featureCollectionGeoJSON_appurtenance:
      properties:
        features:
          items:
            $ref: '#/components/schemas/featureGeoJSON_appurtenance'
          type: array
        links:
          items:
            $ref: '#/components/schemas/link'
          type: array
        numberReturned:
          $ref: '#/components/schemas/numberReturned'
        timeStamp:
          $ref: '#/components/schemas/timeStamp'
        type:
          enum:
          - FeatureCollection
          type: string
      required:
      - features
      - type
      type: object
    featureCollectionJSON_appurtenance:
      properties:
        features:
          items:
            $ref: '#/components/schemas/featureJSON_appurtenance'
          type: array
        links:
          items:
            $ref: '#/components/schemas/link'
          type: array
        numberReturned:
          $ref: '#/components/schemas/numberReturned'
        timeStamp:
          $ref: '#/components/schemas/timeStamp'
        type:
          enum:
          - FeatureCollection
          type: string
      required:
      - features
      - type
      type: object
    featureCollectionJSONFG_appurtenance:
      properties:
        conformsTo:
          items:
            format: uri
            type: string
          minItems: 1
          type: array
        coordRefSys:
          format: uri
          type: string
        features:
          items:
            $ref: '#/components/schemas/featureJSONFG_appurtenance'
          type: array
        links:
          items:
            $ref: '#/components/schemas/link'
          type: array
        numberReturned:
          $ref: '#/components/schemas/numberReturned'
        timeStamp:
          $ref: '#/components/schemas/timeStamp'
      required:
      - features
      - type
      type: object
    featureGeoJSON_appurtenance:
      properties:
        geometry:
          allOf:
          - $ref: '#/components/schemas/geometryGeoJSON'
          nullable: true
        id:
          oneOf:
          - type: string
          - type: integer
        links:
          items:
            $ref: '#/components/schemas/link'
          type: array
        properties:
          $ref: '#/components/schemas/propertiesGeoJSON_appurtenance'
        type:
          enum:
          - Feature
          type: string
      required:
      - geometry
      - properties
      - type
      type: object
    featureJSON_appurtenance:
      properties:
        id:
          oneOf:
          - type: string
          - type: integer
        links:
          items:
            $ref: '#/components/schemas/link'
          type: array
        properties:
          $ref: '#/components/schemas/propertiesGeoJSON_appurtenance'
        type:
          enum:
          - Feature
          type: string
      required:
      - properties
      - type
      type: object
    featureJSONFG_appurtenance:
      properties:
        conformsTo:
          items:
            format: uri
            type: string
          minItems: 1
          type: array
        coordRefSys:
          format: uri
          type: string
        geometry:
          allOf:
          - $ref: '#/components/schemas/geometryGeoJSON'
          nullable: true
        id:
          oneOf:
          - type: string
          - type: integer
        links:
          items:
            $ref: '#/components/schemas/link'
          type: array
        place:
          allOf:
          - $ref: '#/components/schemas/geometryGeoJSON'
          nullable: true
        properties:
          $ref: '#/components/schemas/propertiesGeoJSON_appurtenance'
        time:
          nullable: true
        type:
          enum:
          - Feature
          type: string
      required:
      - time
      - place
      - geometry
      - properties
      - type
      type: object
    geometryGeoJSON:
      oneOf:
      - $ref: '#/components/schemas/pointGeoJSON'
      - $ref: '#/components/schemas/multipointGeoJSON'
      - $ref: '#/components/schemas/linestringGeoJSON'
      - $ref: '#/components/schemas/multilinestringGeoJSON'
      - $ref: '#/components/schemas/polygonGeoJSON'
      - $ref: '#/components/schemas/multipolygonGeoJSON'
      - $ref: '#/components/schemas/geometrycollectionGeoJSON'
    geometrycollectionGeoJSON:
      properties:
        geometries:
          items:
            $ref: '#/components/schemas/geometryGeoJSON'
          type: array
        type:
          enum:
          - GeometryCollection
          type: string
      required:
      - geometries
      - type
      type: object
    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.
      example:
        id: night
        links:
        - href: https://example.com/api/1.0/styles/night?f=mapbox
          rel: stylesheet
          type: application/vnd.mapbox.style+json
        - href: https://example.com/api/1.0/styles/night?f=sld10
          rel: stylesheet
          type: application/vnd.ogc.sld+xml;version=1.0
        title: Topographic night style
      properties:
        id:
          type: string
        links:
          items:
            $ref: '#/components/schemas/link'
          minItems: 1
          type: array
        title:
          type: string
      required:
      - id
      - links
      type: object
    jsonSchema:
      description: A JSON Schema definition
      properties:
        $id:
          description: URI that serves as the schema identifier
          type: string
        $schema:
          description: URI that identifies the JSON Schema version
          type: string
        description:
          description: Human-readable description of the schema
          type: string
        properties:
          description: Schema for object properties
          type: object
        required:
          description: List of required property names
          items:
            type: string
          type: array
        title:
          description: Human-readable title of the schema
          type: string
        type:
          type: string
      required:
      - type
      - $id
      - $schema
      type: object
    keyword:
      nullable: true
      properties:
        code:
          example: "4612"
          type: string
        codeSpace:
          example: https://www.eionet.europa.eu/gemet/en/concept/
          type: string
        keyword:
          example: land cover
          type: string
      required:
      - keyword
      type: object
    landingPage:
      example:
      - href: http://data.example.org/?f=json
        rel: self
        title: this document
        type: application/json
      - href: http://data.example.org/?f=html
        rel: alternate
        title: this document in HTML
        type: text/html
      - href: http://data.example.org/api?f=json
        rel: service
        title: the API definition in OpenAPI 3.0 JSON
        type: application/vnd.oai.openapi+json;version=3.0
      - href: http://data.example.org/api?f=html
        rel: service
        title: the API definition in HTML
        type: text/html
      - href: http://data.example.org/conformance?f=json
        rel: conformance
        title: the list of conformance classes implemented by this API
        type: application/json
      - href: http://data.example.org/collections?f=json
        rel: data
        title: The collections in the dataset in JSON
        type: application/json
      - href: http://data.example.org/collections?f=html
        rel: data
        title: The collections in the dataset in HTML
        type: text/html
      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.
          type: string
        links:
          items:
            $ref: '#/components/schemas/link'
          type: array
        title:
          example: Buildings in Bonn
          type: string
      required:
      - links
      type: object
    linestringGeoJSON:
      properties:
        coordinates:
          items:
            items:
              type: number
            minItems: 2
            type: array
          minItems: 2
          type: array
        type:
          enum:
          - LineString
          type: string
      required:
      - coordinates
      - type
      type: object
    link:
      properties:
        href:
          description: Supplies the URI to a remote resource (or resource fragment).
          example: http://data.example.com/buildings/123
          type: string
        hreflang:
          description: A hint indicating what the language of the result of dereferencing
            the link should be.
          example: en
          type: string
        length:
          type: integer
        rel:
          description: The type or semantics of the relation.
          example: alternate
          type: string
        templated:
          description: This flag set to true if the link is a URL template.
          type: boolean
        title:
          description: Used to label the destination of a link such that it can be
            used as a human-readable identifier.
          type: string
        type:
          description: A hint indicating what the media type of the result of dereferencing
            the link should be.
          type: string
        varBase:
          description: A base path to retrieve semantic information about the variables
            used in URL template.
          type: string
      required:
      - href
      - rel
      type: object
    multilinestringGeoJSON:
      properties:
        coordinates:
          items:
            items:
              items:
                type: number
              minItems: 2
              type: array
            minItems: 2
            type: array
          type: array
        type:
          enum:
          - MultiLineString
          type: string
      required:
      - coordinates
      - type
      type: object
    multipointGeoJSON:
      properties:
        coordinates:
          items:
            items:
              type: number
            minItems: 2
            type: array
          type: array
        type:
          enum:
          - MultiPoint
          type: string
      required:
      - coordinates
      - type
      type: object
    multipolygonGeoJSON:
      properties:
        coordinates:
          items:
            items:
              items:
                items:
                  type: number
                minItems: 2
                type: array
              minItems: 4
              type: array
            type: array
          type: array
        type:
          enum:
          - MultiPolygon
          type: string
      required:
      - coordinates
      - type
      type: object
    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.
      example: 10
      minimum: 0
      type: integer
    pointGeoJSON:
      properties:
        coordinates:
          items:
            type: number
          minItems: 2
          type: array
        type:
          enum:
          - Point
          type: string
      required:
      - coordinates
      - type
      type: object
    polygonGeoJSON:
      properties:
        coordinates:
          items:
            items:
              items:
                type: number
              minItems: 2
              type: array
            minItems: 4
            type: array
          type: array
        type:
          enum:
          - Polygon
          type: string
      required:
      - coordinates
      - type
      type: object
    propertiesGeoJSON_appurtenance:
      properties:
        begin_lifespan_version:
          description: ""
          nullable: true
          type: string
        date:
          description: ""
          nullable: true
          type: string
        date_time:
          description: ""
          nullable: true
          type: string
        end_lifespan_version:
          description: ""
          nullable: true
          type: string
        gml_id:
          description: ""
          nullable: true
          type: string
        gml_parent_id:
          description: ""
          nullable: true
          type: string
        gml_parent_property:
          description: ""
          nullable: true
          type: string
        gml_remote_schema:
          description: ""
          nullable: true
          type: string
        local_id:
          description: ""
          nullable: true
          type: string
        namespace:
          description: ""
          nullable: true
          type: string
        nil_reason:
          description: ""
          nullable: true
          type: string
        owns:
          description: ""
          nullable: true
          type: boolean
        valid_from:
          description: ""
          nullable: true
          type: string
        valid_to:
          description: ""
          nullable: true
          type: string
        version_id:
          description: ""
          nullable: true
          type: string
        vertical_position:
          description: ""
          nullable: true
          type: string
        xlink_href:
          description: ""
          nullable: true
          type: string
        xlink_role:
          description: ""
          nullable: true
          type: string
        xlink_title:
          description: ""
          nullable: true
          type: string
        xsi_nil:
          description: ""
          nullable: true
          type: boolean
      type: object
    spatialExtent:
      description: The spatial extent of the element in the collection.
      properties:
        bbox:
          $ref: '#/components/schemas/bbox'
        crs:
          $ref: '#/components/schemas/crs'
      required:
      - bbox
      type: object
    temporalExtent:
      description: The temporal extent of the element in the collection.
      nullable: true
      properties:
        interval:
          $ref: '#/components/schemas/temporalInterval'
        trs:
          $ref: '#/components/schemas/trs'
      type: object
    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.
      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.
        example:
        - "2010-02-15T12:34:56Z"
        - null
        items:
          format: date-time
          nullable: true
          type: string
        maxItems: 2
        minItems: 2
        type: array
      minItems: 1
      nullable: true
      type: array
    timeStamp:
      description: This property indicates the time and date when the response was
        generated.
      example: "2017-08-17T08:05:32Z"
      format: date-time
      type: string
    trs:
      default: http://www.opengis.net/def/uom/ISO-8601/0/Gregorian
      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.
      enum:
      - http://www.opengis.net/def/uom/ISO-8601/0/Gregorian
      type: string
info:
  contact:
    email: beheerpdok@kadaster.nl
    name: PDOK Support
    url: https://www.pdok.nl/support
  description: Naar INSPIRE thema Nutsdiensten en overheidsdiensten geharmoniseerde
    lozingspunten zoals gerapporteerd naar de Europese Commissie tbv EU rapportage
    Stedelijk Afvalwater 2020.
  license:
    name: CC0 1.0
    url: http://creativecommons.org/publicdomain/zero/1.0/deed.nl
  termsOfService: ""
  title: Nuts- en Overheidsdiensten - Riool - Leidingelementen - RSA (INSPIRE geharmoniseerd)
  version: 1.0.0
openapi: 3.1.0
paths:
  /:
    get:
      description: The landing page provides links to the API definition and the conformance
        statements for this API.
      operationId: getLandingPage
      parameters:
      - $ref: '#/components/parameters/f'
      responses:
        "200":
          $ref: '#/components/responses/LandingPage'
        "400":
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/exception'
          description: 'Bad request: For example, invalid or unknown query parameters.'
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
        "404":
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/exception'
          description: 'Not found: The requested resource does not exist on the server.
            For example, a path parameter had an incorrect value.'
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
        "406":
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/exception'
          description: 'Not acceptable: The requested media type is not supported
            by this resource.'
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
        "500":
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/exception'
          description: 'Internal server error: An unexpected server error occurred.'
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
        "502":
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/exception'
          description: 'Bad Gateway: An unexpected error occurred while forwarding/proxying
            the request to another server.'
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
      summary: Landing page
      tags:
      - Common
  /api:
    get:
      description: This document
      operationId: getOpenApi
      parameters:
      - $ref: '#/components/parameters/f'
      responses:
        "200":
          $ref: '#/components/responses/200'
        "400":
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/exception'
          description: 'Bad request: For example, invalid or unknown query parameters.'
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
        "404":
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/exception'
          description: 'Not found: The requested resource does not exist on the server.
            For example, a path parameter had an incorrect value.'
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
        "406":
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/exception'
          description: 'Not acceptable: The requested media type is not supported
            by this resource.'
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
        "500":
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/exception'
          description: 'Internal server error: An unexpected server error occurred.'
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
        "502":
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/exception'
          description: 'Bad Gateway: An unexpected error occurred while forwarding/proxying
            the request to another server.'
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
      summary: This document
      tags:
      - Common
  /collections:
    get:
      description: A list of all collections (geospatial data resources) in this dataset.
      operationId: getCollections
      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.
        example: json
        explode: false
        in: query
        name: f
        required: false
        schema:
          enum:
          - json
          - html
          type: string
        style: form
      responses:
        "200":
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/collections'
            text/html:
              schema:
                type: string
          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.
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
        "400":
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/exception'
          description: 'Bad request: For example, invalid or unknown query parameters.'
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
        "404":
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/exception'
          description: 'Not found: The requested resource does not exist on the server.
            For example, a path parameter had an incorrect value.'
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
        "406":
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/exception'
          description: 'Not acceptable: The requested media type is not supported
            by this resource.'
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
        "500":
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/exception'
          description: 'Internal server error: An unexpected server error occurred.'
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
        "502":
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/exception'
          description: 'Bad Gateway: An unexpected error occurred while forwarding/proxying
            the request to another server.'
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
      summary: the collections in the dataset
      tags:
      - Collections
  /collections/appurtenance:
    get:
      description: appurtenance collection (geospatial data resource) in this dataset.
      operationId: getCollection.appurtenance
      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.
        example: json
        explode: false
        in: query
        name: f
        required: false
        schema:
          enum:
          - json
          - html
          type: string
        style: form
      responses:
        "200":
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/collection'
            text/html:
              schema:
                type: string
          description: Metadata about the collection.
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
        "400":
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/exception'
          description: 'Bad request: For example, invalid or unknown query parameters.'
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
        "404":
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/exception'
          description: 'Not found: The requested resource does not exist on the server.
            For example, a path parameter had an incorrect value.'
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
        "406":
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/exception'
          description: 'Not acceptable: The requested media type is not supported
            by this resource.'
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
        "500":
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/exception'
          description: 'Internal server error: An unexpected server error occurred.'
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
        "502":
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/exception'
          description: 'Bad Gateway: An unexpected error occurred while forwarding/proxying
            the request to another server.'
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
      summary: describes a appurtenance collection
      tags:
      - Collections
  /collections/appurtenance/items:
    get:
      description: |-
        Fetch features of the feature collection with id `appurtenance`.

        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.
      operationId: appurtenance.getFeatures
      parameters:
      - $ref: '#/components/parameters/f-features'
      - $ref: '#/components/parameters/limit'
      - $ref: '#/components/parameters/crs'
      - $ref: '#/components/parameters/bbox'
      - $ref: '#/components/parameters/bbox-crs'
      - $ref: '#/components/parameters/datetime_notsupported'
      - $ref: '#/components/parameters/profile'
      - $ref: '#/components/parameters/cursor'
      - description: Filter features by this property
        explode: false
        in: query
        name: local_id
        required: false
        schema:
          type: string
        style: form
      responses:
        "200":
          content:
            application/geo+json:
              schema:
                $ref: '#/components/schemas/featureCollectionGeoJSON_appurtenance'
            application/vnd.ogc.fg+json:
              schema:
                $ref: '#/components/schemas/featureCollectionJSONFG_appurtenance'
            text/html:
              schema:
                type: string
          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`).
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
            Content-Crs:
              description: a URI, in angular brackets, identifying the coordinate
                reference system used in the content / payload
              example: <http://www.opengis.net/def/crs/EPSG/0/3395>
              schema:
                type: string
        "400":
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/exception'
          description: 'Bad request: For example, invalid or unknown query parameters.'
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
        "404":
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/exception'
          description: 'Not found: The requested resource does not exist on the server.
            For example, a path parameter had an incorrect value.'
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
        "406":
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/exception'
          description: 'Not acceptable: The requested media type is not supported
            by this resource.'
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
        "500":
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/exception'
          description: 'Internal server error: An unexpected server error occurred.'
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
        "502":
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/exception'
          description: 'Bad Gateway: An unexpected error occurred while forwarding/proxying
            the request to another server.'
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
      summary: fetch features
      tags:
      - Features
  /collections/appurtenance/items/{featureId}:
    get:
      description: |-
        Fetch the feature with id `featureId` in the feature collection
        with id `appurtenance`.

        Use content negotiation to request HTML or GeoJSON.
      operationId: appurtenance.getFeature
      parameters:
      - description: local identifier of a feature
        explode: false
        in: path
        name: featureId
        required: true
        schema:
          type: string
        style: simple
      - $ref: '#/components/parameters/f-features'
      - $ref: '#/components/parameters/crs'
      - $ref: '#/components/parameters/profile'
      responses:
        "200":
          content:
            application/geo+json:
              schema:
                $ref: '#/components/schemas/featureGeoJSON_appurtenance'
            application/vnd.ogc.fg+json:
              schema:
                $ref: '#/components/schemas/featureJSONFG_appurtenance'
            text/html:
              schema:
                type: string
          description: |-
            fetch the feature with id `featureId` in the feature collection
            with id `collectionId`
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
            Content-Crs:
              description: a URI, in angular brackets, identifying the coordinate
                reference system used in the content / payload
              example: <http://www.opengis.net/def/crs/EPSG/0/3395>
              schema:
                type: string
        "400":
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/exception'
          description: 'Bad request: For example, invalid or unknown query parameters.'
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
        "404":
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/exception'
          description: 'Not found: The requested resource does not exist on the server.
            For example, a path parameter had an incorrect value.'
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
        "406":
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/exception'
          description: 'Not acceptable: The requested media type is not supported
            by this resource.'
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
        "500":
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/exception'
          description: 'Internal server error: An unexpected server error occurred.'
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
        "502":
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/exception'
          description: 'Bad Gateway: An unexpected error occurred while forwarding/proxying
            the request to another server.'
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
      summary: fetch a single feature
      tags:
      - Features
  /collections/appurtenance/schema:
    get:
      description: |-
        Fetch the schema of the collection with id `appurtenance`. The schema describes the features such as the available fields and data types.

        Use content negotiation to request HTML or JSON schema.
      operationId: appurtenance.getSchema
      parameters:
      - $ref: '#/components/parameters/f'
      responses:
        "200":
          content:
            application/schema+json:
              schema:
                $ref: '#/components/schemas/jsonSchema'
            text/html:
              schema:
                type: string
          description: The response is a document containing the schema that describes
            the features in this collection.
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
        "400":
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/exception'
          description: 'Bad request: For example, invalid or unknown query parameters.'
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
        "404":
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/exception'
          description: 'Not found: The requested resource does not exist on the server.
            For example, a path parameter had an incorrect value.'
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
        "406":
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/exception'
          description: 'Not acceptable: The requested media type is not supported
            by this resource.'
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
        "500":
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/exception'
          description: 'Internal server error: An unexpected server error occurred.'
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
        "502":
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/exception'
          description: 'Bad Gateway: An unexpected error occurred while forwarding/proxying
            the request to another server.'
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
      summary: fetch the schema of this collection
      tags:
      - Features
  /conformance:
    get:
      description: A list of all conformance classes specified in a standard that
        the server conforms to.
      operationId: getConformanceDeclaration
      parameters:
      - $ref: '#/components/parameters/f'
      responses:
        "200":
          $ref: '#/components/responses/ConformanceDeclaration'
        "400":
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/exception'
          description: 'Bad request: For example, invalid or unknown query parameters.'
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
        "404":
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/exception'
          description: 'Not found: The requested resource does not exist on the server.
            For example, a path parameter had an incorrect value.'
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
        "406":
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/exception'
          description: 'Not acceptable: The requested media type is not supported
            by this resource.'
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
        "500":
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/exception'
          description: 'Internal server error: An unexpected server error occurred.'
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
        "502":
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/exception'
          description: 'Bad Gateway: An unexpected error occurred while forwarding/proxying
            the request to another server.'
          headers:
            API-Version:
              description: Semantic version (semver) of the API according to [API
                Design Rules](https://gitdocumentatie.logius.nl/publicatie/api/adr/2.0.2/#/core/version-header).
              example: 1.0.0
              schema:
                example: 1.0.0
                pattern: ^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$
                type: string
      summary: API conformance definition
      tags:
      - Common
servers:
- description: API endpoint
  url: https://api.pdok.nl/rws/rioolnetwerk-leidingelementen/ogc/v1
