Intake-STAC
This is an Intake data source for SpatioTemporal Asset Catalogs (STAC). The STAC specification provides a common metadata specification, API, and catalog format to describe geospatial assets, so they can more easily indexed and discovered. A 'spatiotemporal asset' is any file that represents information about the earth captured in a certain space and time.
Intake-STAC provides an opinionated way for users to load Assets from STAC catalogs into the scientific Python ecosystem. It uses the intake-xarray plugin and supports several file formats including GeoTIFF, netCDF, GRIB, and OpenDAP.
Installation
Intake-STAC has a few requirements, such as Intake, intake-xarray and pystac. Intake-stac can be installed in any of the following ways:
We recommend installing the latest release with conda:
$ conda install -c conda-forge intake-stac
Or the latest development version with pip:
$ pip install git+https://github.com/intake/intake-stac
Quickstart
import intake
catalog_url = 'https://www.planet.com/data/stac/catalog.json'
cat = intake.open_stac_catalog(catalog_url)
collection = cat['planet-disaster-data']
subset = collection['hurricane-harvey']['hurricane-harvey-0831']
item = subset['Houston-East-20170831-103f-100d-0f4f-RGB']
da = item['thumbnail'].to_dask()
da
The examples/ directory contains several Jupyter Notebooks illustrating common workflows.
STAC Index is a convenient website for finding datasets with STACs
Versions
To install a specific version of intake-stac, specify the version in the install command
pip install intake-stac==0.4.0
The table below shows the corresponding versions between intake-stac and STAC:
| intake-stac | STAC |
|---|---|
| 0.2.x | 0.6.x |
| 0.3.x | 1.0.0-betaX |
| 0.4.x | 1.0.0 |
About
intake-stac was created as part of the Pangeo initiative under support from the NASA-ACCESS program. See the initial design document.
Metadata
Release files for intake-stac 0.4.0
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 |
|---|---|---|---|---|
| intake_stac-0.4.0.tar.gz | 39.8 kB | Without provenance | Details for intake_stac-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| intake_stac-0.4.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for intake_stac-0.4.0-py2.py3-none-any.whl |
Total release size: 49.1 kB
Release files / intake_stac-0.4.0.tar.gz
| Download URL | intake_stac-0.4.0.tar.gz |
|---|---|
| Size | 39.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9243fbe85dfde12780314c4add858cd5c936174362e6096881b4a2324a11ef84
|
|
BLAKE2b-256 checksum How to use checksums |
33ba71d6e3e3aab8bb7936bd8ae700dfefbbd8efff3076c89b60fafbe4016e80
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.10.4
|
Release files / intake_stac-0.4.0-py2.py3-none-any.whl
| Download URL | intake_stac-0.4.0-py2.py3-none-any.whl |
|---|---|
| Size | 9.3 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
ac1ff728485675b75d9585cace675da5f0a371e7c4ee717314620a60ad248f4f
|
|
BLAKE2b-256 checksum How to use checksums |
658d77e28fa09342691e8bc7e250486259ce525321f75fb9446bf49c78229894
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.10.4
|
Security for intake-stac 0.4.0
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.