A common use case is locating a certain dataset on Explorer, then wanting to do a deeper dive to inspect this dataset by looking into its files stored on S3. This can be particularly useful for accessing files that aren't exposed by Datacube (e.g. thumbnails etc).
Currently Explorer includes a "location" link on each dataset page that typically links to the dataset's JSON or YAML:
However, when a user clicks on this file, it simply downloads the JSON/YAML file rather than taking the user to the data itself. It would be far more useful if this link took users to the location of the data on S3 using the "https://data.dea.ga.gov.au/" browser.
A challenge here would be making this work across our different Explorers (e.g. dev and prod). I suspect it won't be suitable for the NCI Explorer as there's no way to browse those files without direct access to the NCI.
A common use case is locating a certain dataset on Explorer, then wanting to do a deeper dive to inspect this dataset by looking into its files stored on S3. This can be particularly useful for accessing files that aren't exposed by Datacube (e.g. thumbnails etc).
Currently Explorer includes a "location" link on each dataset page that typically links to the dataset's JSON or YAML:
However, when a user clicks on this file, it simply downloads the JSON/YAML file rather than taking the user to the data itself. It would be far more useful if this link took users to the location of the data on S3 using the "https://data.dea.ga.gov.au/" browser.
For example, for this dataset:
You could be taken to this location:
A challenge here would be making this work across our different Explorers (e.g. dev and prod). I suspect it won't be suitable for the NCI Explorer as there's no way to browse those files without direct access to the NCI.