Repository navigation
Conversation
…ssing-value standard Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Problem
Several changes to how the pipeline stores and lays out raster data (grid definition, tiling, chunking, data types, missing values) keep coming up in discussion, but they were not written down anywhere the team could review them together, or in the order they depend on each other.
Change
Documentation only, for discussion; no code changes.
docs/improvements.md: a numbered list of proposed changes in dependency order. Each entry has a description of how it works today, the motivation for changing it, and the proposed change. An entry is meant to be removed once it lands.docs/improvement_spatial.md: a detailed proposal bringing together improvements 1–3, a shared spatial standard: an explicit lattice, the processing tiles, and the storage chunks and shards, so every layer admitted to an analysis grid shares the same cells.docs/improvement_dtype.md: a detailed proposal for a shared standard for data types and missing values: the smallest type that holds each layer's values, and an explicit, per-layer meaning for fill values.docs/figures/spatial-chunk-alignment.png,docs/image/improvement_spatial/…png).Done when
Must have
docs/and link to each other and toarchitecture.mdNice to have
improvements.mdTesting
pre-commitpasses (mdformat reformatted the tables only; the text is unchanged). Internal links checked.mainbefore feat: switch emit to sparse format and make linear amortization annual #31 (sparse emit format, annual amortization) and feat: parametrize assessment year to 2020, 2022, or 2024 #32/chore: some quick follow-ups to the assessment-year parametrization #34 (assessment-year parametrization); descriptions of how emit works today may need refreshing for those changes. Flagging it here rather than rewriting them in this PR.Impact on outputs
None.
Dependencies
None. Independent of the collaboration-setup PR.
Prepared with Claude Code (Claude Opus 5.5).
🤖 Generated with Claude Code