You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For some datasets, requesting a timeseries will result in a ValueError. We observed this for datasets on our development DOORS xcube-viewer (from partners METU and ISMAR-CNR). If you set a geometry and request a time series for it, you will be given a non-telling error message. Browsing through the xcube-server logs, we found stack traces posted below.
Our initial assumption was that the time values were unsorted or non-unique, but this wasn't the case. We now assume that the problem occurs because the datasets in question hold four-dimensional variables (ordered time, xxx, lat, lon). stacktrace1.txt stacktrace2.txt
The text was updated successfully, but these errors were encountered:
For some datasets, requesting a timeseries will result in a ValueError. We observed this for datasets on our development DOORS xcube-viewer (from partners METU and ISMAR-CNR). If you set a geometry and request a time series for it, you will be given a non-telling error message. Browsing through the xcube-server logs, we found stack traces posted below.
Our initial assumption was that the time values were unsorted or non-unique, but this wasn't the case. We now assume that the problem occurs because the datasets in question hold four-dimensional variables (ordered time, xxx, lat, lon).
stacktrace1.txt
stacktrace2.txt
The text was updated successfully, but these errors were encountered: