{
  "opencollection": "1.0.0",
  "info": {
    "name": "EOC EO Products Service Capabilities STAC API",
    "version": "1.0.0"
  },
  "items": [
    {
      "info": {
        "name": "STAC",
        "type": "folder"
      },
      "items": [
        {
          "info": {
            "name": "Search STAC items with simple filtering.",
            "type": "http"
          },
          "http": {
            "method": "GET",
            "url": "https://geoservice.dlr.de/eoc/ogc/stac/v1/search",
            "params": [
              {
                "name": "bbox",
                "value": "",
                "type": "query",
                "description": "Only features that have a geometry that intersects the bounding box are selected.\nThe bounding box is provided as four or six numbers, depending on\nwhether the coordinate reference system includes a vertical axis (height\nor depth):\n\n* Lower left corner, coordinate axis 1\n* Lower left corner, coordinate axis 2\n* Minimum value, coordinate axis 3 (optional)\n* Upper right corner, coordinate axis 1\n* Upper right corner, coordinate axis 2\n* Maximum value, coordinate axis 3 (optional)\n\nThe coordinate reference system of the values is WGS 84\nlongitude/latitude (http://www.opengis.net/def/crs/OGC/1.3/CRS84).\n\nFor WGS 84 longitude/latitude the values are in most cases the sequence\nof minimum longitude, minimum latitude, maximum longitude and maximum\nlatitude. However, in cases where the box spans the antimeridian the\nfirst value (west-most box edge) is larger than the third value\n(east-most box edge).\n\nIf the vertical axis is included, the third and the sixth number are\nthe bottom and the top of the 3-dimensional bounding box.\n\nIf a feature has multiple spatial geometry properties, it is the\ndecision of the server whether only a single spatial geometry property\nis used to determine the extent or all relevant geometries.\n\nExample: The bounding box of the New Zealand Exclusive Economic Zone in\nWGS 84 (from 160.6°E to 170°W and from 55.95°S to 25.89°S) would be\nrepresented in JSON as `[160.6, -55.95, -170, -25.89]` and in a query as\n`bbox=160.6,-55.95,-170,-25.89`."
              },
              {
                "name": "datetime",
                "value": "",
                "type": "query",
                "description": "Either a date-time or an interval, open or closed. Date and time expressions\nadhere to RFC 3339. Open intervals are expressed using double-dots.\n\nExamples:\n\n* A date-time: \"2018-02-12T23:20:50Z\"\n* A closed interval: \"2018-02-12T00:00:00Z/2018-03-18T12:31:12Z\"\n* Open intervals: \"2018-02-12T00:00:00Z/..\" or \"../2018-03-18T12:31:12Z\"\n\nOnly features that have a temporal property that intersects the value of\n`datetime` are selected.\n\nIf a feature has multiple temporal properties, it is the decision of the\nserver whether only a single temporal property is used to determine\nthe extent or all relevant temporal properties."
              },
              {
                "name": "limit",
                "value": "",
                "type": "query",
                "description": "The optional limit parameter limits the number of items that are presented in the response document.\n\nOnly items are counted that are on the first level of the collection in the response document.\nNested objects contained within the explicitly requested items shall not be counted.\n\nMinimum = 1. Maximum = 10000. Default = 10."
              },
              {
                "name": "ids",
                "value": "",
                "type": "query",
                "description": "Array of Item ids to return. All other filter parameters that further\nrestrict the number of search results are ignored"
              },
              {
                "name": "collections",
                "value": "",
                "type": "query",
                "description": "Array of Collection IDs to include in the search for items.\nOnly Items in one of the provided Collections will be searched\n"
              },
              {
                "name": "sortby",
                "value": "",
                "type": "query",
                "description": "An array of property names, prefixed by either \"+\" for ascending or\n\"-\" for descending. If no prefix is provided, \"+\" is assumed."
              },
              {
                "name": "fields",
                "value": "",
                "type": "query",
                "description": "Determines the shape of the features in the response"
              },
              {
                "name": "query",
                "value": "",
                "type": "query",
                "description": "query for properties in items. Use the JSON form of the queryFilter in POST."
              }
            ]
          },
          "docs": "Retrieve Items matching filters. Intended as a shorthand API for simple\nqueries."
        },
        {
          "info": {
            "name": "Search STAC items with full-featured filtering.",
            "type": "http"
          },
          "http": {
            "method": "POST",
            "url": "https://geoservice.dlr.de/eoc/ogc/stac/v1/search",
            "body": {
              "type": "json",
              "data": "{}"
            }
          },
          "docs": "retrieve items matching filters. Intended as the standard, full-featured\nquery API.\n\nThis method is mandatory to implement if `GET /search` is implemented.\nIf this endpoint is implemented on a server, it is required to add a\nlink referring to this endpoint with `rel` set to `search` and `method`\nset to `POST` to the `links` array in `GET /`."
        }
      ]
    }
  ],
  "bundled": true
}