Perhaps a wrapper can be written for NCI to handle these /g/data files and translate them to the corresponding THREDDS location? Not sure if the paths are always consistently 1:1 from /g/data and THREDDS, though. 🤷
This seems to be at least possible in principle, because that seems to be done for AWS - mapping from S3://dea-public-data/... -> https://dea-public-data.s3.ap-southeast-2.amazonaws.com/...
Perhaps, while we're at it we could replace the location link with the THREDDS ones too:
https://explorer.dea.ga.gov.au/products/ga_ls9c_ard_3/datasets/abe45d2b-a54f-468d-98ea-2ffb30656260
Perhaps a wrapper can be written for NCI to handle these
/g/data
files and translate them to the corresponding THREDDS location? Not sure if the paths are always consistently 1:1 from/g/data
and THREDDS, though. 🤷This seems to be at least possible in principle, because that seems to be done for AWS - mapping from![image](https://user-images.githubusercontent.com/587870/221494070-e1a7c1ea-5e64-4820-8d54-0d64c92faef4.png)
S3://dea-public-data/...
->https://dea-public-data.s3.ap-southeast-2.amazonaws.com/...
Perhaps, while we're at it we could replace the location link with the THREDDS ones too:![image](https://user-images.githubusercontent.com/587870/221494306-377a9a2b-f5c1-465c-bfa5-a9b892bbb7af.png)
Looks like it's handled here in the code: https://github.com/opendatacube/datacube-explorer/blob/e09884af0b398d30f4e4c4494f9a808146dbec95/cubedash/_utils.py#L148-L182