fix(grib-index): support querying float values #520
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
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.
When indexing GRIB files using the
anemoi-datasets grib-index, it might occur that the program fails due to duplicated messages even though they are not really duplicates. This occurs for instance with soil variables, where by default values forlevelare interpreted as integers which leads to values such as 0.01, 0.004, etc. to all be decoded as "0".To solve this, one needs to use the
key:typesyntax to decode a key in a specific type, e.g.level:d. However, this leads to another error because SQLite does not support column names that contain colons.As a simple fix, the proposed solution is to replace colons with underscores.
By opening this pull request, I affirm that all authors agree to the Contributor License Agreement.