Feature request: expose dataset metadata fields in Feature Info

[robbibt]

Datacube datasets can contain a range of useful metadata fields that provide important context about a dataset (e.g. information about a dataset's cloud cover or GQA georeferencing accuracy).

It would be fantastic if these metadata fields could be exposed to via GetFeatureInfo, so that users could easily obtain additional information about a dataset by querying our web services.

This would be particularly valuable in combination with a delivery platform like Terria, where a custom Terria config could be used to format these additional metadata fields into an accessible format for our users.

[robbibt]

@SpacemanPaul

[SpacemanPaul]

The existing custom_feature_info function is passed data, but not metadata. As Robbi notes three a bunch of interesting use cases that would be served by exposing metadata here.

[robbibt]

@SpacemanPaul If product and dataset IDs were some of the fields we could pass through, I think that would allow us to include direct links to Explorer in Terria, effectively giving users an easy option for downloading data from S3:

https://explorer.dea.ga.gov.au/products/{product_id}/datasets/{dataset_id}

https://explorer.dea.ga.gov.au/products/ga_ls8c_ard_3/datasets/3b02ddba-4e3e-40f9-adf5-b8bc13e8f67f

(hmm, maybe product ID isn't one of our metadata fields...)

[robbibt]

We have had additional use cases for this in DEA Intertidal recently too, where it would have been very useful to be able to expose certain tidal metadata fields to our users to better contextualise some of the processes they are seeing on the map.

With the Expanded AOI project, it would also be useful to expose certain metadata fields that explain how those offshore ARD datasets differ from our other ARD datasets (as well as other useful info like GQA).