stactools-glad-glclu2020
- Name: glad-glclu2020
- Package:
stactools.glad_glclu2020 - stactools-glad-glclu2020 on PyPI
- Owner: @hrodmn
- Dataset homepage
- STAC extensions used:
- Browse the example in human-readable form
- Browse a notebook demonstrating the example item and collection
A short description of the package and its usage.
STAC examples
Installation
pip install stactools-glad-glclu2020
Command-line usage
By default, stactools-glad-glclu2020 will assume that you are generating STAC metadata for the original files which are stored in a Google storage container and publicly available over HTTP.
stac gladlclu2020 create-collection \
--sample-asset-href https://storage.googleapis.com/earthenginepartners-hansen/GLCLU2000-2020/v2/2000/50N_090W.tif \
{destination}
stac gladlclu2020 create-item \
https://storage.googleapis.com/earthenginepartners-hansen/GLCLU2000-2020/v2/2000/50N_090W.tif \
{destination}
If you have created your own copy of the data in a different storage container, you can provide a custom URL format for the assets with the --href-format parameter in the create-item command:
stac gladlclu2020 create-collection \
--sample-asset-href {sample_tif_url} \
{destination}
stac gladlclu2020 create-item \
--href-format s3://bucket/glad/GLCLU2000-2020/{version}/{year}/{loc}.tif \
{cog_href} \
{destination}
Use stac glad-glclu2020 --help to see all subcommands and options.
Contributing
We use pre-commit to check any changes. To set up your development environment:
uv venv && uv sync --extra dev
uv run pre-commit install
To check all files:
uv run pre-commit run --all-files
To run the tests:
uv run pytest -vv
If you've updated the STAC metadata output, update the examples:
uv run scripts/update-examples
Metadata
Release files for stactools-glad-glclu2020 0.1.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_glad_glclu2020-0.1.1.tar.gz | 17.7 kB | Without provenance | Details for stactools_glad_glclu2020-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| stactools_glad_glclu2020-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for stactools_glad_glclu2020-0.1.1-py3-none-any.whl |
Total release size: 33.9 kB
Release files / stactools_glad_glclu2020-0.1.1.tar.gz
| Download URL | stactools_glad_glclu2020-0.1.1.tar.gz |
|---|---|
| Size | 17.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0910615a7f2bc33efc4b7c5d86ef81a029e81c3c8dce0ec312eb37049c0290d5
|
|
BLAKE2b-256 checksum How to use checksums |
99f17ba9302c4b389424acdb48be70d0e53923c7dbf0a58657bc8985e6938ae2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
Release files / stactools_glad_glclu2020-0.1.1-py3-none-any.whl
| Download URL | stactools_glad_glclu2020-0.1.1-py3-none-any.whl |
|---|---|
| Size | 16.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
86d543dd69f0f711ce7061ed7874b1062f9e65bd537a896f0e059b751b64fc7c
|
|
BLAKE2b-256 checksum How to use checksums |
728f1af7d1aebe8ce3dd86c277f80c64379aba1199b3705f9fec8773fa505f88
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
Security for stactools-glad-glclu2020 0.1.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.