Hi, that’s correct. The API weight always uses a minimum of 7 days (actually now 14 days). This is because data is stored in compressed "chunks," and the API has to perform the same amount of work whether it returns 1 hour or 7 days of data. The API weight calculation is designed to approximate the workload on our servers.
Hello!
The nDays being 1 or 7 doesn't seem to affect the api call weight at all. Is this a bug?
Hi, that’s correct. The API weight always uses a minimum of 7 days (actually now 14 days). This is because data is stored in compressed "chunks," and the API has to perform the same amount of work whether it returns 1 hour or 7 days of data. The API weight calculation is designed to approximate the workload on our servers.
Great info!
How are models treatened in the formula. Do we have to multiply them like locations?
Correct. 5 weather variables from 5 different models return 25 individual data time-series and would count as `nVariables = 25` in the formula.
The API documentation shows a message, how any a single API call is weighted: "Note: This API call is equivalent to 2.5 calls because of factors like long time intervals, the number of locations, variables, or models involved." https://open-meteo.com/en/docs#hourly=temperature_2m,relative_humidity_2m,rain,wind_speed_10m,wind_direction_10m&models=ecmwf_ifs04,gfs_seamless,icon_seamless,gem_seamless,meteofrance_seamless
🚀🚀🚀