Keyword |
Description |
Sample Config |
Output Partitions |
| date | Specifies the calendar date(s) for which data is retrieved in an ECMWF MARS request. | [parameters] target_path={date}.nc partition_keys=date [selection] date=2017-01-01/to/2017-01-02 |
2017-01-01.nc 2017-01-02.nc |
| date [step] [time] [var] | Along with specifying date in the ECMWF MARS request, users can also partition data using one or more of [forecast-step, initialization-time, or varirable]. |
Case-1[parameters]target_path={date}_{time}.nc partition_keys= date time [selection] date=2025-01-01/to/2025-01-08/by/5 time=00/12 Case-2[parameters]target_path={date}_{step}.nc partition_keys= date step [selection] date=2024-12-31/to/2024-01-26/by/-3 step=0 |
Case-12025-01-01_00:00:00.nc2025-01-01_12:00:00.nc 2025-01-06_00:00:00.nc 2025-01-06_12:00:00.nc Case-22024-12-31_0.nc2024-12-28_0.nc |
| year, month, day | Specifies dates in a decomposed form (separate fields) for ECMWF MARS requests, enabling flexible selection across ranges and combinations. Supports multiple year and month inputs, allowing users to define broad time spans without enumerating each period. |
Case-1[parameters]target_path={year}/{year}-{month:02d}.grb2 partition_keys= year month [selection] year=2021 month=1/to/2 day=all Case-2: Full year[parameters]target_path=full_{year}.nc partition_keys=year [selection] year=2001/to/2002 month=1/to/12 day=all Case-3: Odd months[parameters]target_path=odd_{year}.nc partition_keys=year [selection] year=2001/to/2002 month=1/to/12/by/2 day=all Case-4: Specific days[parameters]target_path=misc_{year}.nc partition_keys=year [selection] year=2001/to/2002 month=1/to/12 day=1/5/10/15 |
Case-12021/2021-01.grb22021/2021-02.grb2 Case-2full_2001.ncfull_2002.nc Case-3odd_2001.ncodd_2002.nc Case-4misc_2001.ncmisc_2002.nc |
| year-month | Added support for a year‑month key, allowing users to specify downloads using month granularity instead of ranged formats. | [parameters] target_path={year-month}.gb partition_keys=year-month [selection] year-month=2024-11/to/2025-02 |
2024-11.gb 2024-12.gb 2025-01.gb 2025-02.gb |
| date_range | Added support for specifying one or more date-range values, enabling users to download data across multiple date intervals in a single run. Note: date_range must be specified in partition_keys. |
[parameters] target_path={date_range}.nc partition_keys=date_range [selection] date_range= 2017-01-01/to/2017-01-10 2017-01-21/to/2017-01-31 |
2017-01-01_to_2017-01-10.nc 2017-01-21_to_2017-01-31.nc |
| hdate | This parameter allows weather‑dl to explicitly specify historical target dates for downloads, giving users precise control over which past dates are retrieved. | [parameters] target_path={date}.gb [selection] date=2020-01-02 hdate=1/to/3 |
2019-01-02 2018-01-02 2017-01-02 |
| (no partition keys specified) | Introduced support for creating a single output-file when no partition_keys are specified, ensuring that all data is written into one consolidated file. | [parameters] target_path=data.nc [selection] date=2017-01-01/to/2017-01-05 time=00/06/12/18 |
data.nc |
weather-dl-v2 pingweather-dl-v2 download add weather-dl-v2 download list weather-dl-v2 download get weather-dl-v2 download show weather-dl-v2 download remove weather-dl-v2 download refetch weather-dl-v2 license add weather-dl-v2 license get weather-dl-v2 license remove weather-dl-v2 license list weather-dl-v2 license update weather-dl-v2 queue list weather-dl-v2 queue get weather-dl-v2 queue edit weather-dl-v2 config show-ip weather-dl-v2 config set-ip