Hi, I found an issue with the CDS request caching. I’m downloading ERA5 hourly maximum temperature data everyday to see if there were abnormally hot days in certain regions or not. How I formulated my requests on the old cdsapi (through era5cli) was I requested the full set of data for a current month asking for 31 days, 24 hours of the current month independent when in the month we were (1st, 15, 31st) and the updated data was returned every day with whatever ERA had at the moment, so files were constantly updated even though my request hasn’t changed every day. With the new CDS-Beta and new cdsapi, that is not the case. On the 30th of August, I sent a request (with the lag, it means that the data was available until 24th) for the full month of August 2024, a file with the data until the end of 24th was returned, I was happy. Next day I sent the same request, hoping to get data until 25th, but still the data until the 24th only was returned. By then I got that the request might be cached, but I thought the are cached for an account. I created a separate account, and the same issue. I though that maybe the cache is IP address based, so I also asked my colleagues to formulate the same request from their computers on the 6th of September (by then data for the full month of August was available), but they also got a short file only until the 24th of August. So it seems to me that the requests are cached globally, and it’s only until a matter of time that someone screws up a request for everyone, like I did for my colleagues. Please, either provide a guidance how to clear the cache, or maybe if there is a way not to cache the request for the not finalized data, that would be great!
Hi Elizaveta
On old CDS API you could ignore cache by adding to your request…
'nocache' : '123'
Where ‘123’ is a random numeric string. It should be a different value for each request.
I’m hoping same works with Beta API
M