in1 client library
This is the Python client library for the in1 service. It allows super-resolving Sentinel-2 raster straight from Python.
Installation
Use a Python package manager to install in1.
pip install in1
Usage client library
Consult the online documentation for details.
import in1
lores = "/path/to/lores.tif"
in1_api_key = "<IN1_API_KEY>"
hires, profile, metrics = in1.sisr(lores, api_key=in1_api_key)
in1.write(hires, "/path/to/outdir/hires.tif", profile)
Usage in1 executable
The Python client library also installs an in1 executable that allows super-resolving directly from the terminal. Consult the online documentation for how to use optional flags.
in1 upsample --source path/to/source.tif --result path/to/result.tif --api <IN1_API_KEY>
License
Metadata
Release files for in1 2.0.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 |
|---|---|---|---|---|
| in1-2.0.1.tar.gz | 10.4 kB | Without provenance | Details for in1-2.0.1.tar.gz |
Release files / in1-2.0.1.tar.gz
| Download URL | in1-2.0.1.tar.gz |
|---|---|
| Size | 10.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c208c68a3b06bd1177f83f2fc0e6697551cad7eabd8993c947ec01ee34c16447
|
|
BLAKE2b-256 checksum How to use checksums |
172917056cb938fb95279526750fb63d89ce36a5b0774435fb2f7eeb137e3dee
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.5.0.1 requests/2.25.1 setuptools/53.0.0 requests-toolbelt/0.9.1 tqdm/4.62.1 CPython/3.9.7
|
Security for in1 2.0.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.