Implement support for multiple boundary specification when working with multiple data sources. This will affect the structure of the configuration files, since we will need a way to link a data source to a specific bounds object.
An example of why we need this is our NSOG case study. In this case study, two of our data sources (era5 & nemo) exist at very different levels of granularity. This means that using a single boundary would result in either way too much nemo data (an unnecessary and infeasible amount of data to download) or way too little era5 data (not enough data to make interpolation).
Implement support for multiple boundary specification when working with multiple data sources. This will affect the structure of the configuration files, since we will need a way to link a data source to a specific bounds object.
An example of why we need this is our NSOG case study. In this case study, two of our data sources (era5 & nemo) exist at very different levels of granularity. This means that using a single boundary would result in either way too much nemo data (an unnecessary and infeasible amount of data to download) or way too little era5 data (not enough data to make interpolation).