Repository navigation
Use ASCII for CHIRPS spatial domain metadata - #1211
Merged
Merged
Conversation
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
1 participant
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.
Use
Global land, 60N-60Sfor CHIRPSspatial_domainand regenerate the final and preliminary templates. Both rootzarr.jsonfiles contain this literal ASCII string with no Unicode escapes. Geographic coverage is unchanged.After deployment, successful operational updates publish the attribute to both stores.
Validation: 638 template, serialization, CF compliance, and non-slow CHIRPS tests passed. Ruff formatting/lint and ty passed. Both generated root JSON files were checked for the exact value and absence of Unicode escapes.
🤖 Generated with Claude Code