Curryer
A library for SPICE extensions and geospatial data product generation.
Documentation
Our documentation is hosted on readthedocs
Core Features
- Extensions and wrappers for SPICE routines and common data patterns.
- Automation of SPICE kernel creation from JSON definition files and modern data file formats and third-party data structures.
- Level-1 geospatial data processing routines (e.g., geolocation).
Install
pip install lasp-curryer
Releases are available on PyPi
Setup
Please read this page for setup, initialization, and examples.
Contributions
We welcome contributions! Please check out our developer guide and follow our pull request standards to make a contribution.
When you are interacting with this repository, we ask that you follow the LASP open source code of conduct.
Citations
If you use Curryer in your work, we kindly ask you to acknowledge Curryer in your publications and presentations.
3 maintainers
Release files for lasp-curryer 0.5.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 | |
|---|---|---|---|
| lasp_curryer-0.5.2.tar.gz | 222.2 kB | Details |
Release files / lasp_curryer-0.5.2.tar.gz
| Download URL | lasp_curryer-0.5.2.tar.gz |
|---|---|
| Size | 222.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c804f074160c8e8c46c45518af5da4cf87fe48620a8de3d4b107a802d89617da
|
|
BLAKE2b-256 checksum How to use checksums |
e76f8d613445faf92af1d5714c100b56b0cb8c7cbc9d9b62970028cacfc1cd0b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 8, 2026.
Transparency log
