WeathEasy
A service for easy weather data acquiring. It uses Zarr as data storage for fast time series queries.
Installation
We highly recommend to use a virtual environment:
python3 -m venv /path/to/venv
. /path/to/venv/bin/activate
On Windows:
python3 -m venv C:\path\to\venv
C:\path\to\venv\Scripts\activate
Install WeathEasy from pypi.org:
python3 -m pip install weatheasy
To install the latest (possibly unreleased) version from the GitHub repository:
python3 -m pip install git+https://github.com/AgroDT/WeathEasy.git
Check installation:
python3 -m weatheasy -v
Extras
By default WeathEasy is only available from command line interface with local storage. The following extras are available to extend its functionality:
s3- enables support for S3-compatible storage for WeathEasy dataweb- enables web API endpoint
To install WeathEasy with extras run
python3 -m pip install weatheasy[s3,web]
Configuration
WeathEasy web API service is configured with environment variables. Use
.example.env as reference. Also you can copy and edit this
file as .env or .local.env. WeathEasy will load it automatically.
cp .example.env .env
CLI applications are configured with command line arguments (see below).
Launching
Before running WeathEasy you need to download weather and climate data. As of late 2024 the CFSv2 reanalysis and actual forecast require a total about 65GiB of space. CMIP6 requires about 390GiB of space.
It is also worth updating CFSv2 daily. Just run the download command on a schedule. WeathEasy will download missing reanalysis data and update the forecast if necessary. See below for details.
‼️ The initial download of data may take a long time: from several days to several weeks, depending on network bandwidth, the state of the source data servers, and (possibly) star positions.
Download CLI
To download weather and climate data run:
python3 -m weatheasy.download -d STORE {cfs2,cmip6}
Where STORE can be a local path or an S3 link in format
s3://<bucket>/<prefix>.
For S3 you need to export AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY. For
any not-AWS S3 storages you also need to export AWS_ENDPOINT_URL_S3. See the
Boto3 docs
for details.
Optionally you can provide a local path to --download-dir to preserve
original downloaded files (GRIB2 for CFSv2 and NetCDF for CMIP6).
A full example for CFSv2:
python3 -m weatheasy.download -d s3://weatheasy/zarr --download-dir ./downloads cfs2
To display the full help message, run:
python3 -m weatheasy.download -h
Query CLI
To query downloaded data run:
python3 -m weatheasy -d STORE -o PATH {cfs2,cmip6} begin end latitude longitude var [var ...]
Where:
STOREis the same as for downloadingPATHis a path to write results to (by default, results are output to console)begin,endare the date range boundaries in ISO format (yyyy-mm-dd)latitude,longitudeare target coordinates in EPSG:4326 coordinate reference system (decimal degrees WGS84)
The command line must ends with a space separated list of target variables to query. To print a full list of available variables run:
python3 -m weatheasy list-vars
A full example for CFSv2, Moscow:
python3 -m weatheasy -d s3://weatheasy/zarr cfs2 \
2024-01-01 2024-01-31 \
55.75222 37.61556 \
TMIN TMAX TMP
To display the full help message, run:
python3 -m weatheasy -h
python3 -m weatheasy cfs2 -h
python3 -m weatheasy cmip6 -h
Web API
After configuring launch the web application with:
uvicorn weatheasy.web:app
By default it would be listening for incoming requests at http://127.0.0.1:8000.
Interactive API docs are available at http://127.0.0.1:8000/docs.
Alternative API docs are available at http://127.0.0.1:8000/redoc.
Read the Uvicorn docs for a full list of supported arguments and options.
Docker
We provide Docker images with all installed dependencies to run WeathEasy. Pull it with:
docker pull ghcr.io/agrodt/weatheasy
The default entry point is the web API. Redefine it to use WeathEasy CLI. For example, to download CFSv2 data with docker run:
docker run --rm -it \
--entrypoint python \
ghcr.io/agrodt/weatheasy \
-m weatheasy.download \
-d s3://weatheasy/zarr \
cfs2
Find an example for Docker Compose at examples/docker-compose.
Development
WeathEasy is written in Python and managed by Rye. After cloning this repository, initialize the development environment with:
rye sync --all-features
We also recommend to install and use pre-commit:
rye tools install pre-commit
pre-commit install
You can develop WeathEasy with locally running S3-compatible object storage MinIO. Launch it with:
docker compose -f compose.dev.yml up -d
Also you need to export next variables (see .example.env):
export AWS_ENDPOINT_URL_S3=http://127.0.0.1:9000
export AWS_ACCESS_KEY_ID=minioadmin
export AWS_SECRET_ACCESS_KEY=minioadmin
Metadata
Release files for weatheasy 0.2.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| weatheasy-0.2.2.tar.gz | 64.4 kB | Without provenance | Details for weatheasy-0.2.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| weatheasy-0.2.2-py3-none-any.whl | Python 3 | none | any | Details for weatheasy-0.2.2-py3-none-any.whl |
Total release size: 84.9 kB
Release files / weatheasy-0.2.2.tar.gz
| Download URL | weatheasy-0.2.2.tar.gz |
|---|---|
| Size | 64.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e4882cf3991eb522b1595106d068b0a67ddace0ad0774e24e995e108e5bf8bee
|
|
BLAKE2b-256 checksum How to use checksums |
69232e8a761f2556dbe4dd760fc09a85af216173848c325a3ffda52b4a42667f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.5.4
|
Release files / weatheasy-0.2.2-py3-none-any.whl
| Download URL | weatheasy-0.2.2-py3-none-any.whl |
|---|---|
| Size | 20.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7569e45e85a641729f0e93067ec417a6e5d7ea953d4f52476c3802d177fb2669
|
|
BLAKE2b-256 checksum How to use checksums |
b51025feceacd278ee2661813e0fb8fcc56bb146ae1d5a8087b4c466c60b567c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.5.4
|
Security for weatheasy 0.2.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.