drb-chunk-sentinel2 0.1.0__tar.gz

drb_chunk_sentinel2-0.1.0/LICENCE.txt

@@ -0,0 +1,165 @@
+                  GNU LESSER GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+
+  This version of the GNU Lesser General Public License incorporates
+the terms and conditions of version 3 of the GNU General Public
+License, supplemented by the additional permissions listed below.
+
+  0. Additional Definitions.
+
+  As used herein, "this License" refers to version 3 of the GNU Lesser
+General Public License, and the "GNU GPL" refers to version 3 of the GNU
+General Public License.
+
+  "The Library" refers to a covered work governed by this License,
+other than an Application or a Combined Work as defined below.
+
+  An "Application" is any work that makes use of an interface provided
+by the Library, but which is not otherwise based on the Library.
+Defining a subclass of a class defined by the Library is deemed a mode
+of using an interface provided by the Library.
+
+  A "Combined Work" is a work produced by combining or linking an
+Application with the Library.  The particular version of the Library
+with which the Combined Work was made is also called the "Linked
+Version".
+
+  The "Minimal Corresponding Source" for a Combined Work means the
+Corresponding Source for the Combined Work, excluding any source code
+for portions of the Combined Work that, considered in isolation, are
+based on the Application, and not on the Linked Version.
+
+  The "Corresponding Application Code" for a Combined Work means the
+object code and/or source code for the Application, including any data
+and utility programs needed for reproducing the Combined Work from the
+Application, but excluding the System Libraries of the Combined Work.
+
+  1. Exception to Section 3 of the GNU GPL.
+
+  You may convey a covered work under sections 3 and 4 of this License
+without being bound by section 3 of the GNU GPL.
+
+  2. Conveying Modified Versions.
+
+  If you modify a copy of the Library, and, in your modifications, a
+facility refers to a function or data to be supplied by an Application
+that uses the facility (other than as an argument passed when the
+facility is invoked), then you may convey a copy of the modified
+version:
+
+   a) under this License, provided that you make a good faith effort to
+   ensure that, in the event an Application does not supply the
+   function or data, the facility still operates, and performs
+   whatever part of its purpose remains meaningful, or
+
+   b) under the GNU GPL, with none of the additional permissions of
+   this License applicable to that copy.
+
+  3. Object Code Incorporating Material from Library Header Files.
+
+  The object code form of an Application may incorporate material from
+a header file that is part of the Library.  You may convey such object
+code under terms of your choice, provided that, if the incorporated
+material is not limited to numerical parameters, data structure
+layouts and accessors, or small macros, inline functions and templates
+(ten or fewer lines in length), you do both of the following:
+
+   a) Give prominent notice with each copy of the object code that the
+   Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the object code with a copy of the GNU GPL and this license
+   document.
+
+  4. Combined Works.
+
+  You may convey a Combined Work under terms of your choice that,
+taken together, effectively do not restrict modification of the
+portions of the Library contained in the Combined Work and reverse
+engineering for debugging such modifications, if you also do each of
+the following:
+
+   a) Give prominent notice with each copy of the Combined Work that
+   the Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the Combined Work with a copy of the GNU GPL and this license
+   document.
+
+   c) For a Combined Work that displays copyright notices during
+   execution, include the copyright notice for the Library among
+   these notices, as well as a reference directing the user to the
+   copies of the GNU GPL and this license document.
+
+   d) Do one of the following:
+
+       0) Convey the Minimal Corresponding Source under the terms of this
+       License, and the Corresponding Application Code in a form
+       suitable for, and under terms that permit, the user to
+       recombine or relink the Application with a modified version of
+       the Linked Version to produce a modified Combined Work, in the
+       manner specified by section 6 of the GNU GPL for conveying
+       Corresponding Source.
+
+       1) Use a suitable shared library mechanism for linking with the
+       Library.  A suitable mechanism is one that (a) uses at run time
+       a copy of the Library already present on the user's computer
+       system, and (b) will operate properly with a modified version
+       of the Library that is interface-compatible with the Linked
+       Version.
+
+   e) Provide Installation Information, but only if you would otherwise
+   be required to provide such information under section 6 of the
+   GNU GPL, and only to the extent that such information is
+   necessary to install and execute a modified version of the
+   Combined Work produced by recombining or relinking the
+   Application with a modified version of the Linked Version. (If
+   you use option 4d0, the Installation Information must accompany
+   the Minimal Corresponding Source and Corresponding Application
+   Code. If you use option 4d1, you must provide the Installation
+   Information in the manner specified by section 6 of the GNU GPL
+   for conveying Corresponding Source.)
+
+  5. Combined Libraries.
+
+  You may place library facilities that are a work based on the
+Library side by side in a single library together with other library
+facilities that are not Applications and are not covered by this
+License, and convey such a combined library under terms of your
+choice, if you do both of the following:
+
+   a) Accompany the combined library with a copy of the same work based
+   on the Library, uncombined with any other library facilities,
+   conveyed under the terms of this License.
+
+   b) Give prominent notice with the combined library that part of it
+   is a work based on the Library, and explaining where to find the
+   accompanying uncombined form of the same work.
+
+  6. Revised Versions of the GNU Lesser General Public License.
+
+  The Free Software Foundation may publish revised and/or new versions
+of the GNU Lesser General Public License from time to time. Such new
+versions will be similar in spirit to the present version, but may
+differ in detail to address new problems or concerns.
+
+  Each version is given a distinguishing version number. If the
+Library as you received it specifies that a certain numbered version
+of the GNU Lesser General Public License "or any later version"
+applies to it, you have the option of following the terms and
+conditions either of that published version or of any later version
+published by the Free Software Foundation. If the Library as you
+received it does not specify a version number of the GNU Lesser
+General Public License, you may choose any version of the GNU Lesser
+General Public License ever published by the Free Software Foundation.
+
+  If the Library as you received it specifies that a proxy can decide
+whether future versions of the GNU Lesser General Public License shall
+apply, that proxy's public statement of acceptance of any version is
+permanent authorization for you to choose that version for the
+Library.

drb_chunk_sentinel2-0.1.0/MANIFEST.in

@@ -0,0 +1,3 @@
+include drb/addons/chunk/sentinel2/cortex.ttl
+include versioneer.py
+include drb/addons/chunk/sentinel2/_version.py

drb_chunk_sentinel2-0.1.0/PKG-INFO

@@ -0,0 +1,266 @@
+Metadata-Version: 2.4
+Name: drb-chunk-sentinel2
+Version: 0.1.0
+Summary: Sentinel-2 product chunk descriptors (drb-chunk)
+Author: GAEL Systems
+Author-email: drb-python@gael.fr
+License: LGPLv3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: License :: OSI Approved :: GNU Lesser General Public License v3 (LGPLv3)
+Requires-Python: <3.14,>=3.11
+Description-Content-Type: text/markdown
+License-File: LICENCE.txt
+Requires-Dist: rdflib
+Dynamic: license-file
+
+# drb-chunk-sentinel2
+
+Chunk descriptors for the Sentinel-2 **L2A** product type, built on top of the
+[drb-chunk](../../core/README.md) add-on.
+
+## What it is
+
+`drb-chunk-sentinel2` ships a generated `cortex.ttl` that declares **68 chunk
+descriptors**, grouped into **4 collections** (`R10m`, `R20m`, `R60m`, `QI`),
+on the Sentinel-2 L2A class URI:
+
+```
+http://knowledge-base.gael.fr/drb/sentinel-2/product_user_level-2a
+```
+
+Each descriptor is a `drb:chunk` entry linking a logical chunk name (e.g.
+`B04_10m`) and a `drb:collection` (e.g. `R10m`) to an XQuery expression that
+navigates the product tree to the corresponding JP2 raster node.
+
+The package does **not** modify the Sentinel-2 topic TTL and registers **no
+entry-point group**. It is a pure descriptor extension merged into the topic
+graph at runtime (see [How attachment works](#how-attachment-works)).
+
+**L1C** support is planned — same pattern, different `IMG_DATA` layout — but is
+not present in this release.
+
+---
+
+## Chunks exposed
+
+68 chunks in total, grouped into 4 **collections** (tile 512 × 512). The three
+`IMG_DATA` resolution collections hold the spectral + ancillary bands (named
+`<LAYER>_<RES>`); the `QI` collection holds the `QI_DATA` quality masks and the
+preview.
+
+| Collection | Count | Contents |
+|------------|-------|----------|
+| `R10m`     | 7     | B02 B03 B04 B08 AOT WVP (uint16) · TCI (uint8 RGB) |
+| `R20m`     | 14    | B01–B07 B8A B11 B12 AOT WVP (uint16) · SCL TCI (uint8) |
+| `R60m`     | 15    | B01–B07 B8A B09 B11 B12 AOT WVP (uint16) · SCL TCI (uint8) |
+| `QI`       | 32    | CLDPRB_{20m,60m}, SNWPRB_{20m,60m}, CLASSI_B00, DETFOO_B01–B12+B8A, QUALIT_B01–B12+B8A, PVI (all uint8) |
+
+### R10m — 10 980 × 10 980 pixels, tile 512 × 512
+
+| Chunk name | Band  | dtype  |
+|------------|-------|--------|
+| `B02_10m`  | B02   | uint16 |
+| `B03_10m`  | B03   | uint16 |
+| `B04_10m`  | B04   | uint16 |
+| `B08_10m`  | B08   | uint16 |
+| `AOT_10m`  | AOT   | uint16 |
+| `WVP_10m`  | WVP   | uint16 |
+| `TCI_10m`  | TCI   | uint8 (RGB) |
+
+### R20m — 5 490 × 5 490 pixels
+
+| Chunk name | Band  | dtype  |
+|------------|-------|--------|
+| `B01_20m`  | B01   | uint16 |
+| `B02_20m`  | B02   | uint16 |
+| `B03_20m`  | B03   | uint16 |
+| `B04_20m`  | B04   | uint16 |
+| `B05_20m`  | B05   | uint16 |
+| `B06_20m`  | B06   | uint16 |
+| `B07_20m`  | B07   | uint16 |
+| `B8A_20m`  | B8A   | uint16 |
+| `B11_20m`  | B11   | uint16 |
+| `B12_20m`  | B12   | uint16 |
+| `AOT_20m`  | AOT   | uint16 |
+| `WVP_20m`  | WVP   | uint16 |
+| `SCL_20m`  | SCL   | uint8  |
+| `TCI_20m`  | TCI   | uint8 (RGB) |
+
+### R60m — 1 830 × 1 830 pixels
+
+| Chunk name | Band  | dtype  |
+|------------|-------|--------|
+| `B01_60m`  | B01   | uint16 |
+| `B02_60m`  | B02   | uint16 |
+| `B03_60m`  | B03   | uint16 |
+| `B04_60m`  | B04   | uint16 |
+| `B05_60m`  | B05   | uint16 |
+| `B06_60m`  | B06   | uint16 |
+| `B07_60m`  | B07   | uint16 |
+| `B8A_60m`  | B8A   | uint16 |
+| `B09_60m`  | B09   | uint16 |
+| `B11_60m`  | B11   | uint16 |
+| `B12_60m`  | B12   | uint16 |
+| `AOT_60m`  | AOT   | uint16 |
+| `WVP_60m`  | WVP   | uint16 |
+| `SCL_60m`  | SCL   | uint8  |
+| `TCI_60m`  | TCI   | uint8 (RGB) |
+
+### QI — quality masks & preview (`QI_DATA`)
+
+All `uint8`. Probability masks carry a resolution suffix; the per-band
+detector-footprint and quality masks are named after their band.
+
+| Chunk name | Layer |
+|------------|-------|
+| `CLDPRB_20m`, `CLDPRB_60m` | cloud probability |
+| `SNWPRB_20m`, `SNWPRB_60m` | snow probability |
+| `CLASSI_B00` | classification mask |
+| `DETFOO_B01`…`DETFOO_B12`, `DETFOO_B8A` | detector footprint (per band) |
+| `QUALIT_B01`…`QUALIT_B12`, `QUALIT_B8A` | quality mask (per band) |
+| `PVI` | preview image |
+
+Each chunk's `drb:source` is an XQuery expression of the form:
+
+```
+GRANULE/*/IMG_DATA/R10m/*[fn:matches(fn:name(),'.*_B04_10m\.jp2$')]
+```
+
+> **Note:** the leading `.*` is required because `fn:matches` in drb's XQuery
+> engine uses full-match semantics (`re.fullmatch`), not search semantics.
+> The pattern must match the entire filename, not just a suffix.
+
+---
+
+## How attachment works
+
+`cortex.ttl` extends the L2A class **by URI**, targeting
+`sentinel-2:product_user_level-2a`. It does not include a `setup.cfg`
+entry-point group — the TTL is not auto-discovered by the resolver on its own.
+
+At runtime the chunk TTL must be **merged into the topic graph** in one of two
+ways (see [Bootstrap](#bootstrap)):
+
+- In a **Fuseki** deployment, add the packaged TTL to the named-graph list
+  loaded into the dataset.
+- In an **offline** setup, compose it together with the S2-SAFE topic TTL in a
+  single `RDFDao([path_to_s2_ttl, cortex_path()])`.
+
+Once merged, `drb-chunk` reads the descriptors via `get_dao(topic).graph` and
+makes them available through the standard chunk API.
+
+The packaged TTL path is returned by:
+
+```python
+from drb.addons.chunk.sentinel2 import cortex_path
+print(cortex_path())   # /path/to/drb/addons/chunk/sentinel2/cortex.ttl
+```
+
+---
+
+## Bootstrap
+
+### Mode 1 — Fuseki (recommended for production)
+
+Set the environment variables before resolving any node:
+
+```bash
+export FUSEKI_URL=http://localhost:3030
+export DATASET=drb
+export DRB_FUSEKI_GRAPHS="http://drb.gael.fr/graph/kb/drbx-kb-topics-sentinel-2-safe/latest,http://drb.gael.fr/graph/kb/drbx-kb-topics-safe/latest"
+```
+
+`DRB_FUSEKI_GRAPHS` is a comma-separated list of Fuseki named-graph URIs; the
+chunk-descriptor graph (loaded from this package's `cortex.ttl`) must also be
+merged into the same dataset/graph set.
+
+### Mode 2 — Offline vendored TTL
+
+Compose the two TTL files into a single `RDFDao` and register it before
+resolving:
+
+```python
+from drb.topics.dao import ManagerDao
+from drb.topics.dao.rdf_dao import RDFDao
+from drb.addons.chunk.sentinel2 import cortex_path
+
+s2_ttl = "/path/to/vendored/sentinel-2-safe-topics.ttl"
+# Merge the S2 topic descriptors and the chunk descriptor into one graph.
+ManagerDao().add_dao_instance(RDFDao([s2_ttl, str(cortex_path())]))
+```
+
+See [`examples/demo_s2_l2a_chunk.py`](examples/demo_s2_l2a_chunk.py) for a
+complete runnable demonstration of both modes.
+
+---
+
+## Worked example
+
+```python
+import numpy
+from drb.topics import resolver
+from drb.addons.addon import AddonManager
+from drb.chunk.selection import WindowSelection
+
+# 1. Resolve the S3 product (bootstrap the KB topics first; see Bootstrap)
+topic, node = resolver.resolve(
+    "s3://my-sentinel2-bucket/"
+    "S2A_MSIL2A_20220101T000000_N0400_R000_T19VCG_20220101T000000.SAFE")
+
+# 2. Discover the chunks, by collection, declared for this topic
+addon = AddonManager().get_addon("chunk")
+print(addon.available_collections(topic))
+#   {'R10m': ['B02_10m', ...], 'R20m': [...], 'R60m': [...], 'QI': [...]}
+
+# 3a. Build one chunk and read a 512x512 window
+chunk = addon.apply(node, chunk_name="B04_10m")
+window = WindowSelection(x=0, y=0, w=512, h=512)
+array = chunk.select(window).get_impl(numpy.ndarray)
+print(array.shape)          # (1, 512, 512) — single band, uint16
+
+# 3b. Or build every chunk of a whole collection at once
+r10m_chunks = addon.apply(node, collection="R10m")   # list[Chunk] (7 here)
+```
+
+---
+
+## Limitations
+
+- **Windowing is correct but not partial-fetch:** `WindowSelection` returns the
+  right pixel values, but the current implementation materialises the **full JP2
+  member** from the archive before slicing. There is no partial network fetch
+  (e.g. HTTP range request on a cloud-hosted SAFE). This is a drb-chunk v1
+  limitation.
+- **Single-tile materialisation:** each `apply` / `select` call opens one JP2
+  node. Multi-tile mosaicking is not supported in this release.
+
+See [`docs/evolution-requests.md`](docs/evolution-requests.md) for tracked
+improvement requests.
+
+---
+
+## Regenerating the descriptor
+
+The `cortex.ttl` is generated from a band×resolution table embedded in
+`_generate.py`. To regenerate after editing the table:
+
+```bash
+python -m drb.addons.chunk.sentinel2._generate
+```
+
+The file is written next to the module (i.e. `drb/addons/chunk/sentinel2/cortex.ttl`).
+Commit the result.
+
+---
+
+## Installation
+
+```bash
+pip install drb-chunk-sentinel2
+```
+
+Requires `drb-chunk` (installed as a dependency). A working drb-chunk setup
+with either a Fuseki instance or a vendored S2 topic TTL is needed at runtime
+(see [Bootstrap](#bootstrap)).

drb_chunk_sentinel2-0.1.0/README.md

@@ -0,0 +1,249 @@
+# drb-chunk-sentinel2
+
+Chunk descriptors for the Sentinel-2 **L2A** product type, built on top of the
+[drb-chunk](../../core/README.md) add-on.
+
+## What it is
+
+`drb-chunk-sentinel2` ships a generated `cortex.ttl` that declares **68 chunk
+descriptors**, grouped into **4 collections** (`R10m`, `R20m`, `R60m`, `QI`),
+on the Sentinel-2 L2A class URI:
+
+```
+http://knowledge-base.gael.fr/drb/sentinel-2/product_user_level-2a
+```
+
+Each descriptor is a `drb:chunk` entry linking a logical chunk name (e.g.
+`B04_10m`) and a `drb:collection` (e.g. `R10m`) to an XQuery expression that
+navigates the product tree to the corresponding JP2 raster node.
+
+The package does **not** modify the Sentinel-2 topic TTL and registers **no
+entry-point group**. It is a pure descriptor extension merged into the topic
+graph at runtime (see [How attachment works](#how-attachment-works)).
+
+**L1C** support is planned — same pattern, different `IMG_DATA` layout — but is
+not present in this release.
+
+---
+
+## Chunks exposed
+
+68 chunks in total, grouped into 4 **collections** (tile 512 × 512). The three
+`IMG_DATA` resolution collections hold the spectral + ancillary bands (named
+`<LAYER>_<RES>`); the `QI` collection holds the `QI_DATA` quality masks and the
+preview.
+
+| Collection | Count | Contents |
+|------------|-------|----------|
+| `R10m`     | 7     | B02 B03 B04 B08 AOT WVP (uint16) · TCI (uint8 RGB) |
+| `R20m`     | 14    | B01–B07 B8A B11 B12 AOT WVP (uint16) · SCL TCI (uint8) |
+| `R60m`     | 15    | B01–B07 B8A B09 B11 B12 AOT WVP (uint16) · SCL TCI (uint8) |
+| `QI`       | 32    | CLDPRB_{20m,60m}, SNWPRB_{20m,60m}, CLASSI_B00, DETFOO_B01–B12+B8A, QUALIT_B01–B12+B8A, PVI (all uint8) |
+
+### R10m — 10 980 × 10 980 pixels, tile 512 × 512
+
+| Chunk name | Band  | dtype  |
+|------------|-------|--------|
+| `B02_10m`  | B02   | uint16 |
+| `B03_10m`  | B03   | uint16 |
+| `B04_10m`  | B04   | uint16 |
+| `B08_10m`  | B08   | uint16 |
+| `AOT_10m`  | AOT   | uint16 |
+| `WVP_10m`  | WVP   | uint16 |
+| `TCI_10m`  | TCI   | uint8 (RGB) |
+
+### R20m — 5 490 × 5 490 pixels
+
+| Chunk name | Band  | dtype  |
+|------------|-------|--------|
+| `B01_20m`  | B01   | uint16 |
+| `B02_20m`  | B02   | uint16 |
+| `B03_20m`  | B03   | uint16 |
+| `B04_20m`  | B04   | uint16 |
+| `B05_20m`  | B05   | uint16 |
+| `B06_20m`  | B06   | uint16 |
+| `B07_20m`  | B07   | uint16 |
+| `B8A_20m`  | B8A   | uint16 |
+| `B11_20m`  | B11   | uint16 |
+| `B12_20m`  | B12   | uint16 |
+| `AOT_20m`  | AOT   | uint16 |
+| `WVP_20m`  | WVP   | uint16 |
+| `SCL_20m`  | SCL   | uint8  |
+| `TCI_20m`  | TCI   | uint8 (RGB) |
+
+### R60m — 1 830 × 1 830 pixels
+
+| Chunk name | Band  | dtype  |
+|------------|-------|--------|
+| `B01_60m`  | B01   | uint16 |
+| `B02_60m`  | B02   | uint16 |
+| `B03_60m`  | B03   | uint16 |
+| `B04_60m`  | B04   | uint16 |
+| `B05_60m`  | B05   | uint16 |
+| `B06_60m`  | B06   | uint16 |
+| `B07_60m`  | B07   | uint16 |
+| `B8A_60m`  | B8A   | uint16 |
+| `B09_60m`  | B09   | uint16 |
+| `B11_60m`  | B11   | uint16 |
+| `B12_60m`  | B12   | uint16 |
+| `AOT_60m`  | AOT   | uint16 |
+| `WVP_60m`  | WVP   | uint16 |
+| `SCL_60m`  | SCL   | uint8  |
+| `TCI_60m`  | TCI   | uint8 (RGB) |
+
+### QI — quality masks & preview (`QI_DATA`)
+
+All `uint8`. Probability masks carry a resolution suffix; the per-band
+detector-footprint and quality masks are named after their band.
+
+| Chunk name | Layer |
+|------------|-------|
+| `CLDPRB_20m`, `CLDPRB_60m` | cloud probability |
+| `SNWPRB_20m`, `SNWPRB_60m` | snow probability |
+| `CLASSI_B00` | classification mask |
+| `DETFOO_B01`…`DETFOO_B12`, `DETFOO_B8A` | detector footprint (per band) |
+| `QUALIT_B01`…`QUALIT_B12`, `QUALIT_B8A` | quality mask (per band) |
+| `PVI` | preview image |
+
+Each chunk's `drb:source` is an XQuery expression of the form:
+
+```
+GRANULE/*/IMG_DATA/R10m/*[fn:matches(fn:name(),'.*_B04_10m\.jp2$')]
+```
+
+> **Note:** the leading `.*` is required because `fn:matches` in drb's XQuery
+> engine uses full-match semantics (`re.fullmatch`), not search semantics.
+> The pattern must match the entire filename, not just a suffix.
+
+---
+
+## How attachment works
+
+`cortex.ttl` extends the L2A class **by URI**, targeting
+`sentinel-2:product_user_level-2a`. It does not include a `setup.cfg`
+entry-point group — the TTL is not auto-discovered by the resolver on its own.
+
+At runtime the chunk TTL must be **merged into the topic graph** in one of two
+ways (see [Bootstrap](#bootstrap)):
+
+- In a **Fuseki** deployment, add the packaged TTL to the named-graph list
+  loaded into the dataset.
+- In an **offline** setup, compose it together with the S2-SAFE topic TTL in a
+  single `RDFDao([path_to_s2_ttl, cortex_path()])`.
+
+Once merged, `drb-chunk` reads the descriptors via `get_dao(topic).graph` and
+makes them available through the standard chunk API.
+
+The packaged TTL path is returned by:
+
+```python
+from drb.addons.chunk.sentinel2 import cortex_path
+print(cortex_path())   # /path/to/drb/addons/chunk/sentinel2/cortex.ttl
+```
+
+---
+
+## Bootstrap
+
+### Mode 1 — Fuseki (recommended for production)
+
+Set the environment variables before resolving any node:
+
+```bash
+export FUSEKI_URL=http://localhost:3030
+export DATASET=drb
+export DRB_FUSEKI_GRAPHS="http://drb.gael.fr/graph/kb/drbx-kb-topics-sentinel-2-safe/latest,http://drb.gael.fr/graph/kb/drbx-kb-topics-safe/latest"
+```
+
+`DRB_FUSEKI_GRAPHS` is a comma-separated list of Fuseki named-graph URIs; the
+chunk-descriptor graph (loaded from this package's `cortex.ttl`) must also be
+merged into the same dataset/graph set.
+
+### Mode 2 — Offline vendored TTL
+
+Compose the two TTL files into a single `RDFDao` and register it before
+resolving:
+
+```python
+from drb.topics.dao import ManagerDao
+from drb.topics.dao.rdf_dao import RDFDao
+from drb.addons.chunk.sentinel2 import cortex_path
+
+s2_ttl = "/path/to/vendored/sentinel-2-safe-topics.ttl"
+# Merge the S2 topic descriptors and the chunk descriptor into one graph.
+ManagerDao().add_dao_instance(RDFDao([s2_ttl, str(cortex_path())]))
+```
+
+See [`examples/demo_s2_l2a_chunk.py`](examples/demo_s2_l2a_chunk.py) for a
+complete runnable demonstration of both modes.
+
+---
+
+## Worked example
+
+```python
+import numpy
+from drb.topics import resolver
+from drb.addons.addon import AddonManager
+from drb.chunk.selection import WindowSelection
+
+# 1. Resolve the S3 product (bootstrap the KB topics first; see Bootstrap)
+topic, node = resolver.resolve(
+    "s3://my-sentinel2-bucket/"
+    "S2A_MSIL2A_20220101T000000_N0400_R000_T19VCG_20220101T000000.SAFE")
+
+# 2. Discover the chunks, by collection, declared for this topic
+addon = AddonManager().get_addon("chunk")
+print(addon.available_collections(topic))
+#   {'R10m': ['B02_10m', ...], 'R20m': [...], 'R60m': [...], 'QI': [...]}
+
+# 3a. Build one chunk and read a 512x512 window
+chunk = addon.apply(node, chunk_name="B04_10m")
+window = WindowSelection(x=0, y=0, w=512, h=512)
+array = chunk.select(window).get_impl(numpy.ndarray)
+print(array.shape)          # (1, 512, 512) — single band, uint16
+
+# 3b. Or build every chunk of a whole collection at once
+r10m_chunks = addon.apply(node, collection="R10m")   # list[Chunk] (7 here)
+```
+
+---
+
+## Limitations
+
+- **Windowing is correct but not partial-fetch:** `WindowSelection` returns the
+  right pixel values, but the current implementation materialises the **full JP2
+  member** from the archive before slicing. There is no partial network fetch
+  (e.g. HTTP range request on a cloud-hosted SAFE). This is a drb-chunk v1
+  limitation.
+- **Single-tile materialisation:** each `apply` / `select` call opens one JP2
+  node. Multi-tile mosaicking is not supported in this release.
+
+See [`docs/evolution-requests.md`](docs/evolution-requests.md) for tracked
+improvement requests.
+
+---
+
+## Regenerating the descriptor
+
+The `cortex.ttl` is generated from a band×resolution table embedded in
+`_generate.py`. To regenerate after editing the table:
+
+```bash
+python -m drb.addons.chunk.sentinel2._generate
+```
+
+The file is written next to the module (i.e. `drb/addons/chunk/sentinel2/cortex.ttl`).
+Commit the result.
+
+---
+
+## Installation
+
+```bash
+pip install drb-chunk-sentinel2
+```
+
+Requires `drb-chunk` (installed as a dependency). A working drb-chunk setup
+with either a Fuseki instance or a vendored S2 topic TTL is needed at runtime
+(see [Bootstrap](#bootstrap)).

drb_chunk_sentinel2-0.1.0/drb/addons/chunk/sentinel2/__init__.py

@@ -0,0 +1,17 @@
+"""Sentinel-2 chunk descriptor package.
+
+Ships a generated ``cortex.ttl`` that declares ``drb:chunk`` on the
+Sentinel-2 L2A product class. It carries no engine and registers no
+entry point: the descriptor is merged into the topic graph at bootstrap
+and read by the ``drb-chunk`` add-on through ``get_dao(topic).graph``.
+"""
+from importlib.resources import files
+
+from . import _version
+
+__version__ = _version.get_versions()['version']
+
+
+def cortex_path() -> str:
+    """Return the filesystem path to the packaged cortex.ttl descriptor."""
+    return str(files("drb.addons.chunk.sentinel2") / "cortex.ttl")