Jeremy Hooke

Our validator is correctly failing the product --- should this issue go to ODC core?

Yeah, it is a little misleading. The little squiggly underline on the word is because Explorer is guessing -- it's based on a sampling of the datasets. So all datasets...

There's a good chance that the `== None`/` is None` changes found in #581 caused these performance issues, as the queries used by Explorer would no longer match the underlying...

Thanks for report. Odd, it looks like it reverted to the older readthedocs style when we fixed the build issue.

As is discussed on Teams, the approval for this as a change is going through other channels, as eo-datasets is just following the upstream "naming conventions" documents that were made....

Rerun including the datacube version: | product | datacube_version | algorithm | version | count | |------------------|----------------------|-----------------|------------|---------| | ls7_nbar_albers | 1.1.10 | datacube-ingest | 1.0.5 | 32364 | | |...

Agreed -- it would be nice to make these more consistent. They're all defined by the cloud team's deployments in the [datakube-apps repo](https://bitbucket.org/geoscienceaustralia/datakube-apps/): These are the current values in master:...

You're right, datacube is only using `absolute()`. It looks like Python's `os.getcwd()` shows different results to bash's `pwd` and `$PWD`, so the plain `absolute()` gets "resolved": ``` >>> !pwd /g/data/v10/agdc...

Python's using the underlying syscall, which doesn't remember symlinks: > Unfortunately, all the kernel maintains for each process is the i-node number and device identification for the current working directory....

It looks like it reads the `$PWD` environment variable. We _could_ do that ourselves with `os.environ['PWD']` (it's in the [posix standard](http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap08.html#tag_08_03), not specific to bash). ``` >>> import os >>>...