Skip to content

spectral-library 0.4.0

Summary

Prepared-runtime sensor schemas now go fully through rsrf.

Breaking Changes

  • prepared-runtime schema is now 2.0.0
  • older 0.2.x runtimes with schema 1.2.0 are no longer loadable and must be rebuilt
  • custom SRF JSON bands must provide response_definition; legacy top-level wavelength_nm / rsr payloads are rejected

Runtime Contract

  • sensor_schema.json now validates schema_version, canonical_wavelength_grid, and response_definition-based bands
  • invalid prepared sensor schemas now fail as prepared-runtime validation errors
  • prepared-runtime sensor_schema.json stores band responses in the same rsrf-compatible shape used by custom sensor JSON definitions

Release Assets

  • publish a regenerated pre-built runtime built with canonical rsrf sensor ids and the 2.0.0 sensor_schema.json format
  • regenerate and republish the official MODIS, Sentinel-2A, Landsat 8, and Landsat 9 example bundle so the tracked SRF JSON fixtures match the runtime contract

Operator Note

Built-in rsrf sensors and prepared-runtime sensor-schema validation now rely on rsrf exposing the custom response-definition API and registry data. If your install does not include data/registry/sensors.parquet, set RSRF_ROOT to an rsrf checkout before using the built-in sensor catalog.