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 cubes with time averaged data (here daily) it does not make sense to keep the hour parameter visible, as seen below.
the hour is then often listed as 00:00 UTC (and as pictured here shows as 02:00 for CEST) which does not make sense.
The text was updated successfully, but these errors were encountered:
Right, good point! But we currently have no clue whether the data in a time span has been aggregated or if it comprises an overlay of observations or it is a specific observation. We'd need to agree on some metadata field and then add it to the cubes or the xcube server.
For the water-services cubes at least we do have this information: either in the cube names (e.g. ws-s2-l3-llur for a daily aggregated cubes, ws-s2-l2-hamburg for a L2C cube) or the metadata parameter processing_level which either has L3 or L2C
For cubes with time averaged data (here daily) it does not make sense to keep the hour parameter visible, as seen below.
the hour is then often listed as 00:00 UTC (and as pictured here shows as 02:00 for CEST) which does not make sense.
The text was updated successfully, but these errors were encountered: