stactools-glad-global-forest-change
- Name: glad-global-forest-change
- Package:
stactools.glad_global_forest_change - stactools-glad-global-forest-change 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
STAC examples
Installation
pip install stactools-glad-global-forest-change
Command-line usage
By default, stactools-glad-global-forest-change 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 gladglobalforestchange create-collection {destination}
stac gladglobalforestchange create-item \
https://storage.googleapis.com/earthenginepartners-hansen/GFC-2023-v1.11/Hansen_GFC-2023-v1.11_gain_40N_080W.tif \
https://storage.googleapis.com/earthenginepartners-hansen/GFC-2023-v1.11/Hansen_GFC-2023-v1.11_treecover2000_40N_080W.tif \
https://storage.googleapis.com/earthenginepartners-hansen/GFC-2023-v1.11/Hansen_GFC-2023-v1.11_lossyear_40N_080W.tif \
https://storage.googleapis.com/earthenginepartners-hansen/GFC-2023-v1.11/Hansen_GFC-2023-v1.11_datamask_40N_080W.tif \
/tmp/item.json
Use stac gladglobalforestchange --help to see all subcommands and options.
Create COGs
The original files hosted on the Google Earth Engine are not cloud-optimized geotiffs (COGs).
This is a problem for many applications so we added the create-cogs function to convert the underlying
assets to COGs and copy them to a new storage location (either a local directory or an S3 bucket).
stac gladglobalforestchange create-cogs {assets} {destination}
Contributing
We use pre-commit to check any changes. To set up your development environment:
uv sync
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-global-forest-change 0.1.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 |
|---|---|---|---|---|
| stactools_glad_global_forest_change-0.1.2.tar.gz | 13.7 kB | Without provenance | Details for stactools_glad_global_forest_change-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| stactools_glad_global_forest_change-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for stactools_glad_global_forest_change-0.1.2-py3-none-any.whl |
Total release size: 26.5 kB
Release files / stactools_glad_global_forest_change-0.1.2.tar.gz
| Download URL | stactools_glad_global_forest_change-0.1.2.tar.gz |
|---|---|
| Size | 13.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cd9fed12224f140e27e2fb9061333d9f9db8832438761a3dda472fe013f582f7
|
|
BLAKE2b-256 checksum How to use checksums |
5abd5bf01d6a1e0937b62d02509a3c21a6276755c59ead7c8b7e8a44a0ff0f6d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.2
|
Release files / stactools_glad_global_forest_change-0.1.2-py3-none-any.whl
| Download URL | stactools_glad_global_forest_change-0.1.2-py3-none-any.whl |
|---|---|
| Size | 12.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
061107446295a4f022d9bd0af75134ef6a22bcdc9b61743bda577aceece7f73f
|
|
BLAKE2b-256 checksum How to use checksums |
0a3c0540471511ecdb8e718b3e73fa7a34f83d7f9593d1069e4f5d04474560cb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.2
|
Security for stactools-glad-global-forest-change 0.1.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.