climate-resilience
Download Examples
This file requires a download_params.yml file to specify the download configurations.
We cannot directly download the data from the Google Earth Engine directly onto the local machine. So the best option is to download to the drive and then download that data to the local drive.
Preprocess Examples
The preprocessing functions will expect that the local data drive contains the downloaded data.
If the data is on drive, the drive needs to be mounted. This is easier to do in a google colab session. Once the drive is mounted, the path of the mounted drive can be used with the functions as normal.
Expected file and directory structure:
The input file and directory structure for functions calculate_Nth_percentile(), calculate_pr_count_amount(), and calculate_temporal_mean() in the preprocessing code should be as follows:
datadir
├── scenario1_variable1_ensemble
│ ├── name1_state1_scenario1_variable1.csv
│ └── name2_state2_scenario1_variable1.csv
├── scenario1_variable2_ensemble
│ ├── name1_state1_scenario1_variable2.csv
│ └── name2_state2_scenario1_variable2.csv
├── scenario2_variable1_ensemble
│ ├── name1_state1_scenario2_variable1.csv
│ └── name2_state2_scenario2_variable1.csv
└── scenario2_variable2_ensemble
├── name1_state1_scenario2_variable2.csv
└── name2_state2_scenario2_variable2.csv
Visualization Examples
The visualization code will be easier to be used in a notebook as inline visualizations can be used.
Map visualization notebook
Below is a screenshot of the interactive map with the sites marked.
Box plot visualization notebook
Below is a screenshot of boxplot of annual precipitation in different regions of the United States.
Library Features:
Downloader
- Class SiteDownloader member functions:
- download_model_average_daily()
- download_historical_daily()
- download_historical_monthly()
- download_samples()
Preprocessing functions
- calculate_Nth_percentile()
- calculate_pr_count_amount()
- calculate_temporal_mean()
- get_climate_ensemble()
- get_per_year_stats()
- get_sub_period_stats()
Vizualization functions
Contributors
Metadata
Release files for climate-resilience 0.4.10
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 |
|---|---|---|---|---|
| climate-resilience-0.4.10.tar.gz | 26.8 kB | Without provenance | Details for climate-resilience-0.4.10.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| climate_resilience-0.4.10-py3-none-any.whl | Python 3 | none | any | Details for climate_resilience-0.4.10-py3-none-any.whl |
Total release size: 54.5 kB
Release files / climate-resilience-0.4.10.tar.gz
| Download URL | climate-resilience-0.4.10.tar.gz |
|---|---|
| Size | 26.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
eae990acb2862ac331c587d130805136782bb343dc610d29797e3764823ace4e
|
|
BLAKE2b-256 checksum How to use checksums |
f34f639c645a90d3153c1434dc5a9a01e2d2ec0ea7de5e7332a2fb2b8a47a023
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.7
|
Release files / climate_resilience-0.4.10-py3-none-any.whl
| Download URL | climate_resilience-0.4.10-py3-none-any.whl |
|---|---|
| Size | 27.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d383edf943d6359bf39098382f02a0f40dc12179cf6fd4306d2450a932f66620
|
|
BLAKE2b-256 checksum How to use checksums |
a3ae75d388cd9b9acaf1aa661ae2840b609348d766434f52a62bdc56fcf8cc09
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.7
|
Security for climate-resilience 0.4.10
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.