destination folder path example works fine for baseline products, when it comes to derivated products that are processed based on baseline products, it isn't flexible enough to avoid conflict.
Example: ``"ga_ls8c_ard_3/092/084/2016/06/28"``
i.e. when both ls7 and ls8 passes on the same region on the same day, both tiles will produce the same region/time path and the first processed dataset will be lost when the second dataset is processed for the same region and day.
Proposed solution: to add platform as part of the path
destination folder path example works fine for baseline products, when it comes to derivated products that are processed based on baseline products, it isn't flexible enough to avoid conflict.
i.e. when both
ls7andls8passes on the same region on the same day, both tiles will produce the sameregion/timepath and the first processed dataset will be lost when the second dataset is processed for the same region and day.Proposed solution: to add platform as part of the path
https://github.com/opendatacube/eo-datasets/blob/develop/eodatasets3/names.py#L293