Explicitly specify metadata filters for collections

[m-mohr]

Originates from Open-EO/openeo-python-client#141 (comment)

Initially the thought was that all (scalar) metadata properties could be queried. This seems not to be true and thus it's not really clear to users what they can query on (despite the limited implementations right now). It would probably good to add something that mentions what users can query on.

In STAC API this would be /queryables, but it may be enough to just add a list with properties to the collections, e.g. "openeo:properties": ["eo:cloud_cover", "proj:epsg"] for example.

[m-mohr]

It's actually possible to expose this via the process description, although it is pretty verbose:

{
  "type": "object",
  "subtype": "metadata-filter",
  "title": "Filters",
  "description": "A list of filters to check against. Specify key-value-pairs with the key being the name of the metadata property name and the value being a process evaluated against the metadata values.",
  "properties": {
    "eo:cloud_cover": {
      "type": "object",
      "subtype": "process-graph",
      "parameters": [
        {
          "name": "value",
          "description": "The cloud cover value to be checked against.",
          "schema": {
            "type": [
              "number",
              "null"
            ],
            "minimum": 0,
            "maximum": 100
          }
        }
      ]
    },
    "platform": {
      "type": "object",
      "subtype": "process-graph",
      "parameters": [
        {
          "name": "value",
          "description": "The property value to be checked against.",
          "schema": {
            "type": [
              "string",
              "null"
            ]
          }
        }
      ]
    }
  }
}

[m-mohr]

Although it would likely also be interesting to expose this per collection...

[sophieherrmann]

I think it would make a lot more sense to expose this per collections. Thinking about radar and optical data the two will provide very different queryable properties. Depending on the specific datasets it could even be that on radar collection provides a specific queryable and another radar collection does not.

I do like the idea of just adding an additional key which lists non standard queryable properties.