Describe the bug
When using different input processors besides the default one, xcube gen throws an exeption:
Internal error: invalid input: missing time coverage information in dataset e.g. for the snap-olci-cyanoalert-l2 input processor
To Reproduce
Steps to reproduce the behavior:
checkout master for xcube and xcube-gen-bc
use demo case located on fs1 in temp/forGunnar/OLCI_minimal_working_example
xcube gen --traceback --config fs1/temp/forGunnar/OLCI_miminal_working_example/l2c-cyanoalert-olci-dan-Romania-2019.yml --config fs1/temp/forGunnar/OLCI_miminal_working_example/CyanoAlert-config-general_orig.yml -a /media/fs1/temp/forGunnar/OLCI_miminal_working_example/*.nc --sort (you might have to adjust the paths)
See error - Internal error: invalid input: missing time coverage information in dataset
Expected behavior
No Error should occur, because this example was used many times before and was working.
Additional Content
I suspect that the issue occurs due to making the default input processor as default and then the input processor specified in the config file is not taken under consideration anymore:
Describe the bug When using different input processors besides the default one, xcube gen throws an exeption: Internal error: invalid input: missing time coverage information in dataset e.g. for the snap-olci-cyanoalert-l2 input processor
To Reproduce Steps to reproduce the behavior:
xcube gen --traceback --config fs1/temp/forGunnar/OLCI_miminal_working_example/l2c-cyanoalert-olci-dan-Romania-2019.yml --config fs1/temp/forGunnar/OLCI_miminal_working_example/CyanoAlert-config-general_orig.yml -a /media/fs1/temp/forGunnar/OLCI_miminal_working_example/*.nc --sort
(you might have to adjust the paths)Expected behavior No Error should occur, because this example was used many times before and was working.
Additional Content I suspect that the issue occurs due to making the default input processor as default and then the input processor specified in the config file is not taken under consideration anymore: