STAC API

[juansensio]

Our initial intention was to proxy the geodb STAC API to serve the datasets, but after a revision on how it works we have decided is better to define the STAC API directly in the EOTDL API.

geodb is a database to store arbitrary data in a tabular form. When using the geodb STAC API it serves all the rows in the tables as STAC items (features) while providing catalog / collections around it with the minimal set of required STAC fields.

However, we use geodb to store our datasets metadata in STAC format. Thanks to our wrapper STACDataFrame we can parse entire STAC catalogs to a geodataframe and vice versa. This means that using the geodb STAC API would serve our STAC metadata in the way described above, which would lead to incorrect metadata.

Implement a STAC endpoint in the EOTDL api that levearges STACDataFrame to read the STAC metadata from geodb for our datasets and serve it in the appropriate format.