Kirill Kouzoubov

@clausmichele there is no plan to add this functionality within 1.8 series, it's a 2.0 thing. Reason is simple: as far as database layer is concerned it does not model...

@Massetting thank you for your suggestion, it is indeed a commonly requested feature to have more control over time dimension of the query. I would not go with proposed solution...

Not sure when any work might be done on this, for right now I recommend using `.find_datasets()` combined with `.load(datasets=[])` ```python dss = [] query = dict(...) # lat/lon/product dates_of_interest...

At the very least we should detect absence of expected keys and generate descriptive exception. But we should probably just abandon the whole 4 corner system, and supply envelope or...

Related issue and an annoying discrepancy is #556 when working with `EPSG:4326`. Have to use `lat|lon` names in your product spec, but `y,x` in your dataset yaml :nauseated_face:

make it `latitude|longitude` not `lat|lon`

I think a more proper solution is to support 1. Selecting one part of multi-part document for both add/update 2. Treating each one as a separate invocation and have an...

sorry wrong button press

So you'd like "update or add" functionality? Or like "sync to this state if safe". Should it be - separate command (`sync`?) - option for add - option for update...

+1 for `apply` not sure about `datacube apply` vs `datacube product|metadata|dataset apply` do agree that having metadata and product in one yaml would be nice. Skipping `non-product` documents when calling...