atlas-python 0.9.0__tar.gz → 0.9.1__tar.gz

{atlas_python-0.9.0 → atlas_python-0.9.1}/Cargo.lock

@@ -71,7 +71,7 @@ dependencies = [
 
 [[package]]
 name = "atlas-python"
-version = "0.9.0"
+version = "0.9.1"
 dependencies = [
  "atlas-rust",
  "ndarray",
@@ -86,7 +86,7 @@ dependencies = [
 
 [[package]]
 name = "atlas-rust"
-version = "0.9.0"
+version = "0.9.1"
 dependencies = [
  "array-format",
  "chrono",

{atlas_python-0.9.0 → atlas_python-0.9.1}/Cargo.toml

@@ -5,11 +5,11 @@ members = ["atlas-python"]
 # Registry name on crates.io (`atlas` is taken). The library is still
 # imported as `atlas` — see `[lib]` below.
 name = "atlas-rust"
-version = "0.9.0"
+version = "0.9.1"
 edition = "2024"
 description = "Directory-based store for thousands of N-dimensional datasets local or remote using object storage."
 license = "Apache-2.0"
-repository = "https://github.com/robinskil/atlas"
+repository = "https://github.com/maris-development/atlas"
 readme = "README.md"
 keywords = ["array", "ndarray", "scientific", "storage", "object-store"]
 categories = ["science", "data-structures", "filesystem"]

{atlas_python-0.9.0 → atlas_python-0.9.1}/LICENSE

@@ -186,7 +186,7 @@
       same "printed page" as the copyright notice for easier
       identification within third-party archives.
 
-   Copyright [yyyy] [name of copyright owner]
+   Copyright 2026 Robin Kooyman
 
    Licensed under the Apache License, Version 2.0 (the "License");
    you may not use this file except in compliance with the License.

atlas_python-0.9.1/PKG-INFO

@@ -0,0 +1,269 @@
+Metadata-Version: 2.4
+Name: atlas-python
+Version: 0.9.1
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Science/Research
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Rust
+Classifier: Operating System :: OS Independent
+Classifier: Topic :: Scientific/Engineering
+Requires-Dist: numpy>=1.23
+Requires-Dist: xarray>=2023.1
+Requires-Dist: dask>=2023.1
+Requires-Dist: zarr>=3 ; extra == 'bench'
+Requires-Dist: numcodecs ; extra == 'bench'
+Requires-Dist: netcdf4 ; extra == 'bench'
+Requires-Dist: obstore>=0.9 ; extra == 'cloud'
+Requires-Dist: pytest ; extra == 'test'
+Requires-Dist: netcdf4 ; extra == 'test'
+Provides-Extra: bench
+Provides-Extra: cloud
+Provides-Extra: test
+License-File: LICENSE
+Summary: Python bindings for the ATLAS array store
+Keywords: array,ndarray,xarray,scientific,storage,object-store
+Author-email: Robin Kooyman <robin.kooyman.work@gmail.com>
+License-Expression: Apache-2.0
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown; charset=UTF-8; variant=GFM
+Project-URL: Homepage, https://github.com/maris-development/atlas
+Project-URL: Issues, https://github.com/maris-development/atlas/issues
+Project-URL: Repository, https://github.com/maris-development/atlas
+
+# atlas-python
+
+Python bindings for **ATLAS** (Aggregated Tensor Large Array Store) — a directory-based store
+for many similarly-shaped N-dimensional arrays, backed by local files or any object store
+(S3 / GCS / Azure / HTTP). Built on a Rust core with a synchronous, NumPy-native API and
+first-class [xarray](https://docs.xarray.dev) integration.
+
+```bash
+pip install atlas-python
+```
+
+```python
+import atlas
+```
+
+| Extra | Install | Adds |
+| --- | --- | --- |
+| cloud | `pip install "atlas-python[cloud]"` | S3 / GCS / Azure / HTTP backends via [obstore](https://github.com/developmentseed/obstore) |
+
+`numpy`, `xarray`, and `dask` are installed automatically.
+
+## Quick start
+
+```python
+import numpy as np
+import atlas
+
+# The `with` block flushes (== close) on exit. Nothing is persisted before that.
+with atlas.Atlas.create("/tmp/my_store", codec="zstd") as store:   # "zstd" | "lz4" | "none"
+    ds = store.create_dataset("jan_2024")
+    ds.define_array(
+        "temperature",
+        dtype="float32",
+        dims=["lat", "lon"],
+        shape=[8, 16],
+        chunk_shape=[4, 8],
+        fill_value=float("nan"),   # unwritten cells read back as NaN; NaN cells count as nulls in stats
+    )
+    ds.write_array("temperature", start=[0, 0], data=np.full((8, 16), 20.0, dtype=np.float32))
+    ds.set_attribute("month", 1)
+    ds.set_attribute("station", "KNMI")
+
+# Reopen and read
+store = atlas.Atlas.open("/tmp/my_store")
+ds = store.open_dataset("jan_2024")
+arr = ds.read_array("temperature")                    # full read -> np.ndarray
+chunk = ds.read_array("temperature", [0, 0], [4, 8])  # partial read
+stats = ds.array_stats("temperature")                 # {"row_count", "null_count", "min", "max"}
+month = ds.get_attribute("month")                     # 1
+```
+
+## Durability model
+
+This is the one concept to internalise: **writes are buffered in memory and only hit disk on
+`flush()`.**
+
+The store's metadata is loaded once on `open`/`create`. Every subsequent mutation — creating
+datasets, defining arrays, `write_array`, `set_attribute` — updates in-memory state only.
+**Nothing reaches disk until `store.flush()` (equivalently `store.close()`, or the `with store:`
+block exiting).** Dropping an `Atlas` without flushing abandons every pending write.
+
+The payoff: N consecutive writes amortise to a single flush — one delta file per touched array
+name and one metadata rewrite, no matter how many datasets you touched.
+
+```python
+store = atlas.Atlas.create("/tmp/my_store")
+# ... many create_dataset / write_array calls ...
+store.flush()   # the single durability boundary
+```
+
+## xarray integration
+
+Importing `atlas` registers an accessor at `xr.Dataset.atlas`, so the integration is always
+available. The store must exist first; you then append xarray datasets to it.
+
+```python
+import numpy as np, xarray as xr, atlas
+
+ds = xr.Dataset(
+    data_vars={
+        "temperature": (["lat", "lon"], np.arange(8 * 16, dtype=np.float32).reshape(8, 16),
+                        {"units": "C", "long_name": "surface temperature"}),
+    },
+    coords={"lat": np.arange(8, dtype=np.float32), "lon": np.arange(16, dtype=np.float32)},
+    attrs={"month": 1, "station": "KNMI"},
+)
+
+with atlas.Atlas.create("/tmp/my_store") as store:
+    store.add_xr_dataset(ds, "jan_2024")     # store-side method
+    ds.atlas.write(store, "jan_2025")        # xarray accessor (same effect)
+
+# Read back as an xr.Dataset
+store = atlas.Atlas.open("/tmp/my_store")
+ds_back = store.to_xarray("jan_2024")
+xr.testing.assert_identical(ds, ds_back)
+```
+
+### Bulk ingestion
+
+`add_xr_dataset` never flushes by itself — N consecutive calls accumulate in memory and a single
+`flush()` (or the `with` exit) persists everything.
+
+```python
+import glob, os, atlas, xarray as xr
+
+with atlas.Atlas.create("/tmp/store") as store:
+    for nc_path in sorted(glob.glob("*.nc")):
+        name = os.path.splitext(os.path.basename(nc_path))[0]
+        store.add_xr_dataset(xr.open_dataset(nc_path), name)
+# One delta file per array name across the whole batch (not one per file).
+```
+
+### Streaming dask-backed writes
+
+If a variable's `.data` is a `dask.array.Array` (e.g. from `xr.open_dataset(path, chunks=...)`
+or `ds.chunk({...})`), `add_xr_dataset` / `ds.atlas.write` stream **one dask block at a time**
+into the store rather than materialising the whole array. The dask chunk shape becomes the
+on-disk `chunk_shape`, so the layout maps 1:1. Peak memory ≈ one chunk per variable.
+
+```python
+ds = xr.open_dataset("big.nc", chunks={"time": 100, "lat": -1, "lon": -1})
+with atlas.Atlas.create("/tmp/store") as store:
+    store.add_xr_dataset(ds, "big")     # streams chunk-by-chunk
+```
+
+Pass `chunks={var: [...]}` to `add_xr_dataset` / `ds.atlas.write` to override the on-disk chunk
+shape independently of dask's chunking.
+
+### Lazy dask-backed reads
+
+`store.to_xarray(name)` returns each variable dask-backed whenever it was stored with non-trivial
+chunking (`chunk_shape != shape`); the dask `chunks` tuple mirrors the on-disk chunk grid and each
+on-disk chunk is one dask task. Full-shape arrays (and 0-D scalars) come back eager as numpy. Call
+`.compute()` to materialise, or slice / `map_blocks` to operate lazily.
+
+```python
+ds_back = atlas.Atlas.open("/tmp/store").to_xarray("big")
+ds_back["temperature"].data              # -> dask.array.Array
+ds_back["temperature"][0:100].compute()  # reads exactly one chunk
+```
+
+Reads run under dask's **threaded** scheduler only — the `DatasetView` captured in the graph isn't
+picklable, so call `.compute()` before handing off to distributed/multiprocessing schedulers.
+
+### How xarray maps onto the store
+
+| Item | How it's stored |
+| --- | --- |
+| Each coord / data variable | A separate array, with `dims` mapped 1:1. |
+| Dataset attrs | Dataset attributes, plain keys. |
+| Per-variable attrs | Flattened as `{var}.{attr}` at the dataset attr level. |
+| Per-variable `_FillValue` | Consumed by `define_array` as a typed fill value (source `Dataset.attrs` is not mutated). |
+| Coord vs data_var distinction | JSON list in the internal `_pyatlas_coords` attr. |
+| Non-scalar attr values (list, ndarray) | JSON-encoded string with a `json:` prefix marker. |
+
+Each `add_xr_dataset` / `ds.atlas.write` creates a *new* dataset — there is no append-into-existing
+mode.
+
+## Supported dtypes
+
+| numpy dtype | atlas dtype |
+| --- | --- |
+| `int8/16/32/64`, `uint8/16/32/64`, `float32/64` | matching numeric |
+| `datetime64[ns]` | `timestamp_nanoseconds` (aliases: `timestamp_ns`, `datetime64[ns]`) |
+| `object` (`str`/`bytes`), `\|S<n>`, `\|U<n>` | `string` (variable-length; reads return Python `str`) |
+
+- 0-D scalar arrays (`shape=[]`) are supported for every dtype above.
+- `bool` is available as an *attribute* type but not as an array dtype.
+- `binary`, `list[...]`, `fixed_size_list[...,N]` are reserved for a later release.
+
+## Cloud / object storage
+
+With the `cloud` extra, `Atlas.open` / `Atlas.create` accept an
+[obstore](https://github.com/developmentseed/obstore)-constructed S3 / GCS / Azure / HTTP store
+handle instead of a local path. The path-based local-filesystem API works without it. See the
+[cloud storage guide](https://github.com/maris-development/atlas/blob/main/atlas-python/docs/guides/cloud-storage.md).
+
+## API reference
+
+### `atlas.Atlas`
+
+| Method | Description |
+| --- | --- |
+| `Atlas.create(path, codec="zstd")` | Create a new store at `path`. |
+| `Atlas.open(path)` | Open an existing store. |
+| `create_dataset(name) -> DatasetView` | New dataset (in-memory until flush). |
+| `open_dataset(name) -> DatasetView` | Existing dataset. |
+| `delete_dataset(name)` | Remove a dataset (persisted on next `flush`). |
+| `list_datasets() -> list[str]` | All dataset names. |
+| `list_arrays() -> list[str]` | Distinct array names across datasets. |
+| `dataset_exists(name) -> bool` | Existence check. |
+| `add_xr_dataset(ds, name, chunks=None)` | Append an `xarray.Dataset` (does **not** flush). |
+| `to_xarray(name) -> xr.Dataset` | Read a dataset back (chunked vars come back dask-backed). |
+| `flush()` | The single durability boundary — persist everything. |
+| `close()` | Alias for `flush()`; also the `with`-block exit. |
+| `compact()` | Reclaim tombstoned space across cached array files. |
+| `__enter__` / `__exit__` | Context-manager support (`__exit__` calls `close()`). |
+
+### `atlas.DatasetView`
+
+| Method | Description |
+| --- | --- |
+| `name` (property) | Dataset name. |
+| `list_arrays() -> list[str]` | Array names in this dataset. |
+| `define_array(name, dtype, dims, shape, chunk_shape=None, fill_value=None)` | Declare a new array. `fill_value` is a Python scalar matching the dtype; unwritten cells read back as it, and *written* cells equal to it count as nulls in `array_stats`. Dtype is enforced (`TypeError` on mismatch, `OverflowError` for out-of-range ints). |
+| `write_array(name, start, data)` | Write a numpy ndarray (matching the stored dtype). |
+| `read_array(name, start=None, shape=None) -> np.ndarray \| None` | Read full or partial; `None` if the array isn't in this dataset. |
+| `delete_array(name)` | Tombstone the array within this dataset. |
+| `array_meta(name) -> dict \| None` | `{"dtype", "shape", "chunk_shape", "dimension_names"}`. |
+| `array_stats(name) -> dict \| None` | `{"row_count", "null_count", "min", "max"}` — populated after `flush()`. |
+| `set_attribute(key, value, dtype=None)` | Type inferred from the Python value; pass `dtype` to override (e.g. `"int8"`, `"float32"`, `"timestamp_nanoseconds"`). On disk: bool, int64, float64, string, timestamp_nanoseconds. |
+| `get_attribute(key)` / `attributes()` | Single attribute or dict of all. |
+
+`DatasetView` does **not** expose its own `flush` / `compact` — both go through the parent `Atlas`.
+
+## Examples
+
+Runnable, self-contained scripts (each writes to a temp directory):
+
+- [01_basics.py](https://github.com/maris-development/atlas/blob/main/atlas-python/examples/01_basics.py) — create a store, define arrays, set attributes, reopen, read back.
+- [02_xarray.py](https://github.com/maris-development/atlas/blob/main/atlas-python/examples/02_xarray.py) — round-trip an `xr.Dataset` via both `store.add_xr_dataset(...)` and the `ds.atlas.write(...)` accessor.
+- [03_dask_streaming.py](https://github.com/maris-development/atlas/blob/main/atlas-python/examples/03_dask_streaming.py) — stream a dask-chunked `xr.Dataset` in one chunk at a time.
+
+## Performance
+
+ATLAS is tuned for collections of many similarly-shaped datasets. On a "1000 datasets" benchmark
+against netCDF4 and Zarr v3, the bulk read paths (`Atlas.to_xarray_many` /
+`Atlas.read_array_across_stacked`) beat Zarr by ~2.8× on large chunked slice reads, and on small
+per-dataset workloads ATLAS leads on both reads and writes. See the
+[benchmarks](https://github.com/maris-development/atlas/tree/main/atlas-python/benchmarks) for the full
+methodology, numbers, and an API picker for the fastest read path per workload.
+
+## Links
+
+- Source & issues: <https://github.com/maris-development/atlas>
+- License: Apache-2.0
+

{atlas_python-0.9.0 → atlas_python-0.9.1}/README.md

@@ -2,6 +2,12 @@
 
 A directory-based store for thousands of named datasets, each holding N-dimensional typed arrays. Built on top of the [`array-format`](https://github.com/robinskil/array-format) (`.af`) binary format, with configurable compression (Zstd, LZ4, or none), chunked I/O, and an [`object_store`](https://crates.io/crates/object_store) backend that works on local disk, S3, GCS, Azure Blob, and in-memory.
 
+**Think of it as a "zip" for N-dimensional datasets.** Where a `.zip` bundles many files into one archive, ATLAS gathers many NetCDF / Zarr-style datasets — anything that's a set of named N-dimensional arrays — into a single high-performance collection. But it's more than a bundle: instead of storing each dataset whole, ATLAS lays the data out **variable-first**, so every dataset's `temperature` lives in one file. That makes it cheap to scan or slice a single variable across thousands of datasets at once, while still reading back any individual dataset as a normal NetCDF/xarray-like object.
+
+> **Looking for Python?** The Python bindings live in [`atlas-python/`](atlas-python/) — `pip install atlas-python`, then `import atlas`. They add a NumPy-native API and first-class [xarray](https://docs.xarray.dev) integration. See the [atlas-python README](atlas-python/README.md) for usage.
+>
+> The rest of this document covers **how the format works and the Rust crate**.
+
 ---
 
 ## What it does

{atlas_python-0.9.0 → atlas_python-0.9.1}/atlas-python/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "atlas-python"
-version = "0.9.0"
+version = "0.9.1"
 edition = "2021"
 readme = "README.md"
 

atlas_python-0.9.1/atlas-python/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   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
+      (except as stated in this section) 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 Robin Kooyman
+
+   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.