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
The gtsm3-era5-cds source was added to the subset/retrieve observations functions in #1153. The original dataset is available on CDS and includes a user guide. Both the frequencies 10-minute and hourly were implemented (default is 10-minute). It was assumed the hourly data was instantaneous, just like the 10-minute values. This seems to be not the case when comparing the two datasets:
The hourly timeseries can approximately be reproduced by resampling to hours and taking the mean, so this seemed to have been the method with which the hourly timeseries was derived. All hourly means are however snapped to the start-of-interval times, which causes a 30-minute timeshift with the original 10-minute timeseries. In an "observation" context the hourly mean dataset is therefore not of added value, a hourly subset would have been more useful instead. To avoid confusion, it might be better to remove the possiblility to retrieve the hourly dataset from dfm_tools.
The text was updated successfully, but these errors were encountered:
veenstrajelmer
changed the title
Remove hourly freq from gtsm3-era5-cds subset retrieve functions
Remove hourly gtsm3 data from subset retrieve functions
Mar 19, 2025
This offset in the orange line is not observed for the year 2010. So it seems that the hourly average has a different time administration in the CDS extension (start-of-interval, years 1980-2018), compared to the orginal CDS (center-of-interval, from 2019 onwards):
The
gtsm3-era5-cds
source was added to the subset/retrieve observations functions in #1153. The original dataset is available on CDS and includes a user guide. Both the frequencies 10-minute and hourly were implemented (default is 10-minute). It was assumed the hourly data was instantaneous, just like the 10-minute values. This seems to be not the case when comparing the two datasets:Gives:

The hourly timeseries can approximately be reproduced by resampling to hours and taking the mean, so this seemed to have been the method with which the hourly timeseries was derived. All hourly means are however snapped to the start-of-interval times, which causes a 30-minute timeshift with the original 10-minute timeseries. In an "observation" context the hourly mean dataset is therefore not of added value, a hourly subset would have been more useful instead. To avoid confusion, it might be better to remove the possiblility to retrieve the hourly dataset from dfm_tools.
The text was updated successfully, but these errors were encountered: