LOONE_DATA_PREP
LOONE_DATA_PREP
Prepare data for the LOONE water quality model.
Line to the LOONE model: https://pypi.org/project/loone Link to LOONE model repository: https://github.com/Aquaveo/LOONE
Installation:
pip install loone_data_prep
Development Installation:
cd /path/to/loone_data_prep/repo
pip install -e .
Examples
From the command line:
# Get flow data
python -m loone_data_prep.flow_data.get_inflows /path/to/workspace/
python -m loone_data_prep.flow_data.get_outflows /path/to/workspace/
python -m loone_data_prep.flow_data.S65E_total /path/to/workspace/
# Get water quality data
python -m loone_data_prep.water_quality_data.get_inflows /path/to/workspace/
python -m loone_data_prep.water_quality_data.get_lake_wq /path/to/workspace/
# Get weather data
python -m loone_data_prep.weather_data.get_all /path/to/workspace/
# Get water level
python -m loone_data_prep.water_level_data.get_all /path/to/workspace/
# Interpolate data
python -m loone_data_prep.utils interp_all /path/to/workspace/
# Prepare data for LOONE
python -m loone_data_prep.LOONE_DATA_PREP /path/to/workspace/ /path/to/output/directory/
From Python:
from loone_data_prep.utils import get_dbkeys
from loone_data_prep.water_level_data import hydro
from loone_data_prep import LOONE_DATA_PREP
input_dir = '/path/to/workspace/'
output_dir = '/path/to/output/directory/'
# Get dbkeys for water level data
dbkeys = get_dbkeys(
station_ids=["L001", "L005", "L006", "LZ40"],
category="SW",
param="STG",
stat="MEAN",
recorder="CR10",
freq="DA",
)
# Get water level data
hydro.get(
workspace=input_dir,
name="lo_stage",
dbkeys=dbkeys,
date_min="1950-01-01",
date_max="2023-03-31"
)
# Prepare data for LOONE
LOONE_DATA_PREP(input_dir, output_dir)
Metadata
Release files for loone-data-prep 1.3.4
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 |
|---|---|---|---|---|
| loone_data_prep-1.3.4.tar.gz | 68.2 kB | Without provenance | Details for loone_data_prep-1.3.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| loone_data_prep-1.3.4-py3-none-any.whl | Python 3 | none | any | Details for loone_data_prep-1.3.4-py3-none-any.whl |
Total release size: 153.8 kB
Release files / loone_data_prep-1.3.4.tar.gz
| Download URL | loone_data_prep-1.3.4.tar.gz |
|---|---|
| Size | 68.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9b31d85beda143ee1ddc190e0d91948c00f0847b7e1eb2fd7ad1e58558da44a3
|
|
BLAKE2b-256 checksum How to use checksums |
229d1d3b631ce1462d997a9b1c765f8a62054c65c1af9f3a6790d60121189b21
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Release files / loone_data_prep-1.3.4-py3-none-any.whl
| Download URL | loone_data_prep-1.3.4-py3-none-any.whl |
|---|---|
| Size | 85.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
137fd3180c552b6eb91325018a883dfbbf0dbfa97dad0b174f26c2ce9a3855e4
|
|
BLAKE2b-256 checksum How to use checksums |
63ddc49d3b6cd51a67ca6d80d02bc880edc236ba2d83ed483268816c5038fd6a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Security for loone-data-prep 1.3.4
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.