ghost
commented
2 years ago For the "The limit of file size is exceeded" issue we can try to download data with a depth between 0 and 4 meters, instead of downloading data between 0 and 20 meters. In fact, I don't think we need data deeper than 2.8 meters. Another solution to this will be to download the daily data week by week instead of month by month, but I don't know if the data pretreatments are adapted to have data with one file per week.
For the "The date range is invalid" issue, we can't avoid to have this error, because the valid range changes over time. But we have to make sure that if the download fail in the archiving dataset, it will be downlaoded in the current dataset and vice versa. For example here it failed for the temperature in BALTICSEA_REANALYSIS_PHY_003_011-TDS the so the data have to be dowloaded in BALTICSEA_ANALYSISFORECAST_PHY_003_006-TDS dataset. Here the issue is that the user chosen a dataset that did not correspond to the year he choose. I see that in the web interface we can choose a single dataset, but for some years if we want to have all the data we have to download it from two different datasets.
qjutard
I have analyzed the issue raised by Margaux. And I found out that dataimport scripts cause exceptions during datasets loading. These exceptions do not prevent the script from executing. And only understanding that some dataset files are missing in the target directory proves that the whole step failed
I have collected some exceptions that I found in her model that may be of interest to us:
Temperature parameter:
Ammonium:
eastward_Water_current:
As you can see, I've added the command used to load the dataset to make it easier to reproduce.