stactools-noaa-mrms-qpe
- Name: noaa-mrms-qpe
- Package:
stactools.noaa_mrms_qpe - PyPI: https://pypi.org/project/stactools-noaa-mrms-qpe/
- Owner: @m-mohr
- Dataset homepage: https://mrms.nssl.noaa.gov
- STAC extensions used:
- Extra fields:
- See the NOAA MRMS QPE extension for details
A stactools package for NOAA's Multi-Radar Multi-Sensor (MRMS) Quantitative Precipitation Estimation (QPE) dataset.
This package can generate STAC files from (gzipped) GRIB2 files that link to the original GRIB2 files and/or to Cloud-Optimized GeoTiffs (COGs) in the original or any other EPSG projection.
STAC Examples
Installation
pip install stactools-noaa-mrms-qpe
Command-line Usage
Collection
Create a collection, e.g. 24-hour Pass 2:
stac noaa-mrms-qpe create-collection collection.json --period 24 --pass_no 2
Get information about all options for collection creation:
stac noaa-mrms-qpe create-collection --help
Item
Create an item for continentel US with a GRIB2 and COG asset:
stac noaa-mrms-qpe create-item MRMS_MultiSensor_QPE_24H_Pass2_00.00_20220530-120000.grib2.gz item_grib.json --collection collection.json
Create an item for ALASKA with only a COG asset converted to EPSG:3857:
stac noaa-mrms-qpe create-item MRMS_MultiSensor_QPE_24H_Pass2_00.00_20220530-120000.grib2.gz item.json --aoi ALASKA --collection collection.json --nogrib TRUE --epsg 3857
Get information about all options for item creation:
stac noaa-mrms-qpe create-item --help
Use stac noaa-mrms-qpe --help to see all subcommands and options.
Note: This package can only read files that contain the timestamp in the file name. It can NOT read the files that contain latest instead of a timestamp in the file name.
Contributing
We use pre-commit to check any changes. To set up your development environment:
$ pip install -e .
$ pip install -r requirements-dev.txt
$ pre-commit install
To check all files:
$ pre-commit run --all-files
To run the tests:
$ pytest -vv
Metadata
Release files for stactools-noaa-mrms-qpe 0.3.1
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 |
|---|---|---|---|---|
| stactools-noaa-mrms-qpe-0.3.1.tar.gz | 11.4 kB | Without provenance | Details for stactools-noaa-mrms-qpe-0.3.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| stactools_noaa_mrms_qpe-0.3.1-py3-none-any.whl | Python 3 | none | any | Details for stactools_noaa_mrms_qpe-0.3.1-py3-none-any.whl |
Total release size: 23.7 kB
Release files / stactools-noaa-mrms-qpe-0.3.1.tar.gz
| Download URL | stactools-noaa-mrms-qpe-0.3.1.tar.gz |
|---|---|
| Size | 11.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a34278a92dac7d5ace3ea5c7af53553cc7e54a7eb99402bdd95c9e3283d3bc2d
|
|
BLAKE2b-256 checksum How to use checksums |
771a52838296e55b962f0879722cced03f25d830ecaa2b15ae3b95b57b445964
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.8
|
Release files / stactools_noaa_mrms_qpe-0.3.1-py3-none-any.whl
| Download URL | stactools_noaa_mrms_qpe-0.3.1-py3-none-any.whl |
|---|---|
| Size | 12.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
60b146727b71be770f257b825a8a7fc18879d3424961744a2be4f145e1863759
|
|
BLAKE2b-256 checksum How to use checksums |
42b856b84afc2251f34e946c19827730d05b28d80ca204ddb7f75d674503c934
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.8
|
Security for stactools-noaa-mrms-qpe 0.3.1
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.