Repository navigation
Decision framework - #209
Merged
Merged
Conversation
Adds a two-page decision framework that takes a reader from "I have
geospatial data to publish or migrate" to a short list of cloud-optimized
format candidates and the layout choices that make each one work.
decision-framework/index.qmd
- Preconditions P1 (partial/parallel reads over HTTP) and P2 (no opaque
bundles), written on top of the guide's existing cloud-optimized
format pattern and glossary rather than as a parallel definition.
- The spine: a control fork (existing data, reprocessable) then a
topology gate that opens a candidate set, with a Mermaid flowchart.
- Refinements: intent, the object-size / grouping lever, ecosystem
maturity, and interpretation encoding.
- Cross-cutting notes: metadata and cataloging (STAC recommended, not
prescribed), within-format depth, and dead ends framed as "unlock
this".
- A short optional section on making the choice quantitative, linking
out rather than reproducing the full spec.
decision-framework/case-studies.qmd
- Six products run through the spine, five backed by measurements,
leading with the measured outcome and the recurring lesson that
cloud-optimized is rarely smaller and the gap is usually the codec.
Also registers both pages in _quarto.yml (placement flagged for review),
adds them to the Welcome table of contents, and credits CNES and the
Copernicus / NASA source missions in _thankyous.qmd.
Refs #183
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The optional scoring section named two measured criteria (size and performance) but had no outbound link, so a reader had no way to reproduce a number. Point both pages at the open-source harness the case-study measurements actually came from. - Framework page: a "where the measured numbers come from" paragraph after the criteria table, naming what the harness measures (object-size distribution and tier fitness, write, range-request-aware read, tile display), that datasets are described in config files rather than baked in, and linking the docs and configuration guide. - Case studies: provenance in the measurement caveat, plus a note in the acknowledgements that the harness is maintained outside this guide so its methodological choices stay debatable on their own terms (ADR 0002). Refs #183 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The recurring-lesson callout paired the "rarely smaller" headline with a measurement-hygiene warning. Replace it with the mechanism that actually explains the gap: overviews, levels of detail and spatial indexes are structures the source never carried, so they add volume, and that volume is the feature being bought. Anchored to the two cases that show it (the COG carrying overviews, the GeoParquet row-group index). The like-for-like-on-content caveat is dropped from the summary only. It stays inline in cases 3 and 5, where it is concrete and actionable. Also aligns the same paragraph on the framework page. Refs #183 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
… split The maturity refinement was a three-row table with no definitions, which made it the weakest of the four axes. Replace it with the substance from the strategic-report state-of-the-art work: - An explicit L1-L5 scale, so the judgement is stated rather than impressionistic, and a per-format table giving specification status, tooling and level. This also separates FlatGeobuf (L3) from GeoParquet and COPC (L4), which the old table lumped together. - The distinction that is easiest to get wrong: Zarr v3 the substrate is dependable (core spec final in 2024, sharding stable in zarr-python 3.x and readable by GDAL and xarray), while GeoZarr the convention layer is still being ratified in an OGC SWG. The L2 belongs to the conventions, not to Zarr. - "Maturity is a warning, not a veto", which reconciles the topology gate offering GeoZarr as the primary N-D cube candidate with that candidate sitting at L2: there is no mature alternative at that topology, so a low level means plan for change, pin versions, and expect the tooling to improve. Points at geozarr.org for current status rather than quoting a ratification date that will age badly. Refs #183 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…y in decision framework section on Zarr v3
…ies and updating case study references for improved context and accuracy.
Co-authored-by: Pete Gadomski <pete.gadomski@gmail.com>
Co-authored-by: Pete Gadomski <pete.gadomski@gmail.com>
Co-authored-by: Pete Gadomski <pete.gadomski@gmail.com>
…mat selection and enhancing the explanation of topology and control stages.
…ifying definitions for improved understanding and context.
…n for improved accuracy and understanding.
…d explanations for reprocessing and virtualization processes.
…ion encoding and enhancing the explanation of the two-stage process for format selection. Update theme configuration in Quarto settings for improved clarity.
…a shapes and clarifying candidate selections for improved guidance on cloud-optimized formats.
…f data objects, enhancing the explanation of access patterns and their impact on format performance.
… of "N-D cube" to "N-D cubes" and enhancing consistency in data shape descriptions.
…not yet possible" for improved accuracy in describing virtualization limitations.
…terminology from "impossible" to "not yet implemented" and providing context on HDF5's evolution to enhance reader understanding of format capabilities.
…data and clarifying format family choices for N-D cubes, improving guidance on cloud-optimized formats.
…ions of on-the-fly and batched processing, improving guidance on layout needs for visualization and data fusion.
Co-authored-by: Alex I. Mandel <alex@developmentseed.org>
Co-authored-by: Alex I. Mandel <alex@developmentseed.org>
…initions and clarifying its impact on chunking and storage tiers, improving user understanding of data handling.
…existing data status, and grouping lever information, enhancing clarity for users on data handling and processing choices.
…improvements in reader tooling and performance metrics, enhancing user understanding of format evolution and library capabilities.
…ional aspect of the octree and its impact on bounding box queries, improving user understanding of data access and measurement relevance.
… and fusion advantages, enhancing user understanding of format performance and access patterns.
Co-authored-by: Aimee Barciauskas <aimee@developmentseed.org>
… framework documentation
Co-authored-by: Aimee Barciauskas <aimee@developmentseed.org>
…ision framework documentation
Co-authored-by: Aimee Barciauskas <aimee@developmentseed.org>
Co-authored-by: Aimee Barciauskas <aimee@developmentseed.org>
Co-authored-by: Alex I. Mandel <alex@developmentseed.org>
…minology in decision framework
Minor wording changes
✅ Deploy Preview for harmonious-cajeta-5542ab ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Closed
✅ Deploy Preview for harmonious-cajeta-5542ab ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
emmanuelmathot
marked this pull request as ready for review
November 2, 2026 09:01
emmanuelmathot
requested review from
abarciauskas-bgse,
maxrjones and
wildintellect
November 2, 2026 09:01
wildintellect
approved these changes
Nov 4, 2026
wildintellect
left a comment
wildintellect
left a comment
Contributor
There was a problem hiding this comment.
Preview Looks good. Content was already reviewed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR to track the integration in main
Fixes #183