Skip to main content

Python library to monkeypatch SpiceyPy to allow JSON kernels (and Python dictionaries).

CI Status last-commit PyPI Downloads Conda Downloads

Description

The standard text kernel format for the SPICE Toolkit is the "PCK" file (with extension .tpc). Examples of these files can be seen here. The PCK file is a data file format that exists in no other domain. So, it may be more convenient to use a standard file format such as JSON, as well as native Python dictionaries. The jsonspice library allows you to do this by monkey patching SpiceyPy so that JSON kernels will "just work".

Installation

PyPi

pip install jsonspice

conda

conda install conda-forge::jsonspice

JSON kernel format

The following PCK file:

KPL/PCK

\begintext
An example kernel

\begindata
TIME3      = @1972-JAN-1
AAA        = 1
AAA       += 2
VARIABLE   = (1.0 2.0 3.0)
VARIABLE2  = 42.0

Has the equivalent JSON kernel representation:

// An example kernel
{
    "TIME3": "@1972-JAN-1",
    "AAA" : 1,
    "+AAA" : 2,
    "VARIABLE": [1.0, 2.0, 3.0],
    "VARIABLE2": 42.0
}

Some things to note about the JSON version:

  • Optional comments are supported (using the JSON5 library). Other than this, the file is a standard JSON file.
  • The SPICE "@" format for time variables is supported using a normal string that begins with the "@" character.
  • The SPICE "+=" assignment to append to an existing variable is supported by prepending the variable name with the "+" character.

The JSON version of SPICE "meta-kernels" is also supported. See the SPICE documentation for details of that format.

Example usage

To use this library, if must be imported BEFORE SpiceyPy. Once that is done, the normal furnsh() method can be used.

import jsonspice  # import first to monkeypatch spiceypy
import spiceypy

# load a normal kernel
spiceypy.furnsh('de-403-masses.tpc')

# load a JSON kernel
spiceypy.furnsh('de-403-masses.json')

# also works with dicts:
spiceypy.furnsh({"BODY8_GM": 6836534.064})
spiceypy.furnsh({"time": '@1972-JAN-1'})
spiceypy.furnsh({"+abc": [4,5,6]})

Documentation

The API documentation for the latest master branch can be found here.

See also

Metadata

Release files for jsonspice 1.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for jsonspice 1.2.0
File Size Uploaded Provenance Actions
jsonspice-1.2.0.tar.gz 72.4 kB With provenance Details for jsonspice-1.2.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for jsonspice 1.2.0
File Interpreter ABI Platform Actions
jsonspice-1.2.0-py3-none-any.whl Python 3 none any Details for jsonspice-1.2.0-py3-none-any.whl

Total release size: 78.6 kB

Release files / jsonspice-1.2.0.tar.gz

Download URL jsonspice-1.2.0.tar.gz
Size 72.4 kB
Tags Source
SHA-256 checksum
How to use checksums
81f09e741f30163d5c887d10a7ecf917759b258f244d24ecc4caeb093c948a92
BLAKE2b-256 checksum
How to use checksums
b517053107af8ca5ab8252c7c78a9e58c1b1f01a66e605deaa14ed9e3ccfbfdc
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.12.9

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 May 3, 2025.

Transparency log

Release files / jsonspice-1.2.0-py3-none-any.whl

Download URL jsonspice-1.2.0-py3-none-any.whl
Size 6.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
0ba441b119cb9064e56940b6e55580600540ee6475cf9ae371251a07f4af0c39
BLAKE2b-256 checksum
How to use checksums
0378851bb874ee0709a46bd14ea745f0752706ff85b98deab0db630e3d72ec2c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.12.9

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 May 3, 2025.

Transparency log

Security for jsonspice 1.2.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.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for jsonspice-1.2.0.tar.gz

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 May 3, 2025.

Transparency log

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page