spectraccess 0.1.0__tar.gz

spectraccess-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,27 @@
+name: CI
+
+on:
+  push:
+  pull_request:
+
+permissions:
+  contents: read
+
+jobs:
+  tests:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        # Every version requires-python and the classifiers promise.
+        python-version: ["3.10", "3.11", "3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+      - name: Install
+        run: python -m pip install -e ".[test]"
+      - name: Run fixture tests
+        run: pytest
+

spectraccess-0.1.0/.github/workflows/commit-messages.yml

@@ -0,0 +1,53 @@
+name: Commit messages
+
+# release-please builds versions and release notes from commit subjects, so
+# every non-merge commit must follow Conventional Commits (see CONTRIBUTING.md).
+
+on:
+  push:
+  pull_request:
+
+permissions:
+  contents: read
+
+jobs:
+  conventional-commits:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - name: Check commit subjects
+        env:
+          EVENT: ${{ github.event_name }}
+          PUSH_BEFORE: ${{ github.event.before }}
+          PUSH_AFTER: ${{ github.event.after }}
+          PR_BASE: ${{ github.event.pull_request.base.sha }}
+          PR_HEAD: ${{ github.event.pull_request.head.sha }}
+        run: |
+          if [ "$EVENT" = "pull_request" ]; then
+            range="$PR_BASE..$PR_HEAD"
+          elif [ -z "${PUSH_BEFORE//0/}" ]; then
+            echo "New branch or tag push: no previous head to compare against; skipping."
+            exit 0
+          elif ! git cat-file -e "$PUSH_BEFORE^{commit}" 2>/dev/null; then
+            echo "Previous head $PUSH_BEFORE is not in history (force push); skipping."
+            exit 0
+          else
+            range="$PUSH_BEFORE..$PUSH_AFTER"
+          fi
+          pattern='^(feat|fix|docs|chore|ci|build|refactor|test|perf|style|revert)(\([A-Za-z0-9._/-]+\))?!?: [^ ].*$'
+          bad=0
+          while IFS= read -r line; do
+            sha="${line%% *}"
+            subject="${line#* }"
+            if ! printf '%s\n' "$subject" | grep -Eq "$pattern"; then
+              echo "::error::${sha:0:12} does not follow Conventional Commits: $subject"
+              bad=1
+            fi
+          done < <(git log --no-merges --format='%H %s' "$range")
+          if [ "$bad" -ne 0 ]; then
+            echo "Expected 'type(scope)?!?: subject' with type one of feat, fix, docs, chore, ci, build, refactor, test, perf, style, revert." >&2
+            exit 1
+          fi
+          echo "All commit subjects in $range follow Conventional Commits."

spectraccess-0.1.0/.github/workflows/live-smoke.yml

@@ -0,0 +1,91 @@
+name: Live connector smoke tests
+
+on:
+  schedule:
+    - cron: "17 3 * * 1"
+  workflow_dispatch:
+
+permissions:
+  contents: read
+  issues: write
+
+jobs:
+  smoke:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        connector:
+          [gsics, modis_viirs_cal, radcalnet, sentinel2_cdse, aeronet, cams, emit_earthaccess, landsat_eodag]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - name: Install
+        # The test extra carries every connector's maintained client
+        # (cdsetool, cdsapi, earthaccess on 3.12+, eodag[usgs]).
+        run: python -m pip install -e ".[test]"
+      - name: Run live smoke
+        id: smoke
+        continue-on-error: true
+        # GSICS catalog vars are optional overrides: the connector ships live
+        # defaults for EUMETSAT + CMA, so these only need to be set to point
+        # at a different catalog URL (e.g. once NOAA STAR is reachable again).
+        # VIIRS has no live default yet, so its var remains required for that
+        # smoke to do anything.
+        env:
+          SPECTRACCESS_GSICS_EUMETSAT_CATALOG_URL: ${{ vars.SPECTRACCESS_GSICS_EUMETSAT_CATALOG_URL }}
+          SPECTRACCESS_GSICS_NOAA_STAR_CATALOG_URL: ${{ vars.SPECTRACCESS_GSICS_NOAA_STAR_CATALOG_URL }}
+          SPECTRACCESS_GSICS_CMA_CATALOG_URL: ${{ vars.SPECTRACCESS_GSICS_CMA_CATALOG_URL }}
+          SPECTRACCESS_VIIRS_CATALOG_URL: ${{ vars.SPECTRACCESS_VIIRS_CATALOG_URL }}
+          # BYO-credentials: the radcalnet smoke prints SKIP and exits 0 until
+          # these repo secrets are configured (a free RadCalNet portal account).
+          RADCALNET_USERNAME: ${{ secrets.RADCALNET_USERNAME }}
+          RADCALNET_PASSWORD: ${{ secrets.RADCALNET_PASSWORD }}
+          # BYO-credentials: the landsat_eodag smoke prints SKIP and exits 0
+          # until these repo secrets are set (USGS EarthExplorer username and
+          # M2M application token; USGS needs them even for search). Names are
+          # EODAG's own USGS credential variables, read by the connector.
+          EODAG__USGS__API__CREDENTIALS__USERNAME: ${{ secrets.EODAG__USGS__API__CREDENTIALS__USERNAME }}
+          EODAG__USGS__API__CREDENTIALS__PASSWORD: ${{ secrets.EODAG__USGS__API__CREDENTIALS__PASSWORD }}
+          # BYO-credentials: the cams smoke always checks the public JASMIN
+          # mirror; its ADS half prints SKIP until this repo secret is set
+          # (free ADS account personal access token).
+          ADS_TOKEN: ${{ secrets.ADS_TOKEN }}
+        run: python scripts/live_smoke.py "${{ matrix.connector }}"
+      - name: Open or update upstream-back issue
+        # The modis_viirs_cal smoke skips while NOAA STAR THREDDS is down but
+        # probes it every week; when it answers, say so in an issue. Never
+        # fails the job.
+        if: matrix.connector == 'modis_viirs_cal' && steps.smoke.outputs.star_thredds == 'reachable'
+        continue-on-error: true
+        env:
+          GH_TOKEN: ${{ github.token }}
+        run: |
+          title="upstream-back: NOAA STAR THREDDS reachable"
+          body="Weekly live smoke found https://www.star.nesdis.noaa.gov/thredds/gsics/catalog.xml serving a THREDDS catalog again in ${GITHUB_SERVER_URL}/${GITHUB_REPOSITORY}/actions/runs/${GITHUB_RUN_ID}. Verify the NOAA STAR GSICS and VIIRS F-factor catalog URLs, then configure SPECTRACCESS_VIIRS_CATALOG_URL / the GSICS NOAA STAR default."
+          gh label create upstream-back --description "An upstream portal that was down answers again" --color 0E8A16 --force
+          existing="$(gh issue list --state open --label upstream-back --search "$title in:title" --json number --jq '.[0].number')"
+          if [ -n "$existing" ]; then
+            gh issue comment "$existing" --body "$body"
+          else
+            gh issue create --title "$title" --label upstream-back --body "$body"
+          fi
+      - name: Open or update connector-broken issue
+        if: steps.smoke.outcome == 'failure'
+        env:
+          GH_TOKEN: ${{ github.token }}
+          CONNECTOR: ${{ matrix.connector }}
+        run: |
+          title="connector-broken: ${CONNECTOR}"
+          body="Weekly live smoke failed for ${CONNECTOR} in ${GITHUB_SERVER_URL}/${GITHUB_REPOSITORY}/actions/runs/${GITHUB_RUN_ID}."
+          # Fresh repos have no such label; --force makes this idempotent.
+          gh label create connector-broken --description "A connector's live portal smoke test is failing" --color B60205 --force
+          existing="$(gh issue list --state open --label connector-broken --search "$title in:title" --json number --jq '.[0].number')"
+          if [ -n "$existing" ]; then
+            gh issue comment "$existing" --body "$body"
+          else
+            gh issue create --title "$title" --label connector-broken --body "$body"
+          fi
+

spectraccess-0.1.0/.github/workflows/publish.yml

@@ -0,0 +1,81 @@
+name: Release and publish to PyPI
+
+# One workflow on purpose: a GitHub Release created with GITHUB_TOKEN does not
+# trigger `release: published` in other workflows, so release-please and the
+# PyPI upload must run in the same run. Keep this filename and the `pypi`
+# environment: the PyPI trusted-publisher registration names both.
+
+on:
+  push:
+    branches: [main]
+
+permissions:
+  contents: read
+
+jobs:
+  release-please:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+      pull-requests: write
+    outputs:
+      release_created: ${{ steps.release.outputs.release_created }}
+      tag_name: ${{ steps.release.outputs.tag_name }}
+    steps:
+      # Opens or updates the release PR from Conventional Commits; when that PR
+      # is merged, tags v<version> and creates the GitHub Release.
+      - uses: googleapis/release-please-action@v4
+        id: release
+        with:
+          config-file: release-please-config.json
+          manifest-file: .release-please-manifest.json
+
+  build:
+    needs: release-please
+    if: ${{ needs.release-please.outputs.release_created == 'true' }}
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          ref: ${{ needs.release-please.outputs.tag_name }}
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - name: Release tag matches the package version
+        env:
+          TAG: ${{ needs.release-please.outputs.tag_name }}
+        run: |
+          version=$(python -c "import tomllib; print(tomllib.load(open('pyproject.toml', 'rb'))['project']['version'])")
+          if [ "$TAG" != "v$version" ]; then
+            echo "Release tag $TAG does not match pyproject version v$version" >&2
+            exit 1
+          fi
+      - name: Install build backend
+        run: python -m pip install build
+      - name: Build sdist and wheel
+        run: python -m build
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    environment:
+      name: pypi
+      url: https://pypi.org/p/spectraccess
+    permissions:
+      # Required for PyPI trusted publishing (OIDC). No API token/secret
+      # is stored in this repo: PyPI exchanges this token for a short-lived
+      # upload credential based on the publisher registered for this project
+      # (owner, repository, workflow filename publish.yml, and environment
+      # name pypi must match exactly).
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

spectraccess-0.1.0/.gitignore

@@ -0,0 +1,18 @@
+__pycache__/
+*.py[cod]
+*.egg-info/
+.pytest_cache/
+pytest-cache-files-*/
+.mypy_cache/
+.ruff_cache/
+.coverage
+htmlcov/
+build/
+dist/
+.venv/
+.venv_verify/
+venv/
+env/
+.env
+.spectraccess_cache/
+.tmp/

spectraccess-0.1.0/.release-please-manifest.json

@@ -0,0 +1 @@
+{".":"0.1.0"}

spectraccess-0.1.0/CHANGELOG.md

@@ -0,0 +1,52 @@
+# Changelog
+
+All notable changes to spectrAccess are documented in this file.
+
+Release entries are generated by release-please from Conventional Commit
+messages (see CONTRIBUTING.md), and this project adheres to
+[Semantic Versioning](https://semver.org/).
+
+## 0.1.0 (2026-09-26)
+
+
+### Features
+
+* **cams:** read cache dir and fallback mirror from SPECTRACCESS_* env vars ([75abb85](https://github.com/SpectraWorksOSS/SpectrAccess/commit/75abb8574a0288cda0b0af7808995617876602b2))
+
+
+### Documentation
+
+* rename front page to OVERVIEW.md ([9f81522](https://github.com/SpectraWorksOSS/SpectrAccess/commit/9f81522a20a0ec19cfd4d2933cbd445d8a9d7240))
+* state live-verification honestly; release 0.1.0 via one-shot footer ([00b87b9](https://github.com/SpectraWorksOSS/SpectrAccess/commit/00b87b9029a3d06e3d20f72a9cd28030bd993120))
+
+### 0.1.0 scope: initial public release
+
+#### Added
+
+- Core `Connector` interface (`discover()`, `fetch()`, `parse()`, `run()`) for
+  source-specific spectral reference data adapters.
+- Canonical long/tidy schema v1.0 (`spectraccess.core.schema`): one row per
+  quantity value with an uncertainty record whose status (`provided`,
+  `derived`, `prior`, `unknown`) is never null, even when the value is.
+- GSICS connector for GPPA inter-calibration products (EUMETSAT and CMA
+  catalogs; NOAA STAR as an optional override).
+- VIIRS calibration connector shape (NOAA STAR F-factor catalog pending
+  verification; MODIS planned).
+- RadCalNet connector on the official JSON API with BYO portal credentials,
+  including per-wavelength uncertainties mapped to `provided` / `prior`;
+  `.output` files parse to `toa_reflectance`, `.input` files to
+  `surface_reflectance`.
+- NASA AERONET v3 connector for the public web service, with a 550 nm AOD
+  interpolation helper.
+- Sentinel-2 L1C discovery and download via CDSETool (`spectraccess[cdse]`).
+- CAMS EAC4 access via the JASMIN mirror and ECMWF's ADS API, plus explicit
+  CAMS forecast products (`spectraccess[cams]`).
+- NASA EMIT L1B/L2A discovery and download via earthaccess
+  (`spectraccess[emit]`, requires Python 3.12 or newer).
+- Landsat 8/9 Collection-2 L1TP discovery and download via EODAG/USGS
+  (`spectraccess[landsat]`); area searches skip non-L1TP products the
+  provider returns alongside.
+- Weekly live-smoke workflow that opens or updates a `connector-broken` issue
+  when a portal stops answering as expected.
+- Fixture-based CI test suite on Python 3.10 to 3.13.
+- `py.typed` marker: the public API ships inline type hints.

spectraccess-0.1.0/CITATION.cff

@@ -0,0 +1,9 @@
+cff-version: 1.2.0
+message: "If you use spectrAccess, please cite it as below."
+title: "spectrAccess"
+authors:
+  - name: "SpectraWorks B.V."
+version: "0.1.0" # x-release-please-version
+license: "Apache-2.0"
+repository-code: "https://github.com/SpectraWorksOSS/SpectrAccess"
+

spectraccess-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,32 @@
+# Contributing
+
+Community contributions are welcome, especially new connectors for spectral reference data portals that lack maintained Python access layers.
+
+## Add a Connector
+
+1. Create a package under `src/spectraccess/connectors/<source_name>/`.
+2. Implement the `spectraccess.core.connector.Connector` interface:
+   `discover()` lists available targets, `fetch()` retrieves raw bytes or files,
+   and `parse()` converts raw content into a tidy `pandas.DataFrame` or
+   `xarray.Dataset`.
+3. Add a `DATA_TERMS.md` file in the connector package describing the source
+   portal's data license or terms of use. The Apache-2.0 project license covers
+   code only, not source data.
+4. Add fixture-based tests under `tests/` using small recorded files checked
+   into `tests/fixtures/`. Default pytest runs must not make live network calls.
+5. Add or update live-smoke coverage in `.github/workflows/live-smoke.yml` for
+   public endpoints that should be monitored weekly.
+
+Do not hardcode credentials or redistribute third-party data through this
+project. Connectors should use the BYO-credentials helpers in
+`spectraccess.core.session` when authentication is required.
+
+
+## Commit Messages
+
+Commit subjects follow [Conventional Commits](https://www.conventionalcommits.org/):
+`type(scope)!: subject`, with type one of `feat`, `fix`, `docs`, `chore`, `ci`,
+`build`, `refactor`, `test`, `perf`, `style`, `revert`; `!` marks a breaking change.
+CI rejects other subjects. Versions, `CHANGELOG.md` entries, and GitHub Releases
+are generated from these messages by release-please; do not bump the version or
+write release entries by hand.

spectraccess-0.1.0/LICENSE

@@ -0,0 +1,203 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   Copyright 2026 SpectraWorks B.V.
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      patent license to make, have made, use, offer to sell, sell, import,
+      and otherwise transfer the Work, where such license applies only to
+      those patent claims licensable by such Contributor that are necessarily
+      infringed by their Contribution(s) alone or by combination of their
+      Contribution(s) with the Work to which such Contribution(s) was
+      submitted. If You institute patent litigation against any entity
+      (including a cross-claim or counterclaim in a lawsuit) alleging that
+      the Work or a Contribution incorporated within the Work constitutes
+      direct or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate as of
+      the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 SpectraWorks B.V.
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.