Now support index for GRIB2 files > 2 GB #606
Closed
Conversation
This file contains 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
edwardhartnett
changed the title
|
@AlexanderRichert-NOAA or @Hang-Lei-NOAA please review... |
|
Never mind, this PR superseded by #607 |
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.
Part of #550
This adds more code to support an index for files > 2 GB. There are a lot of changes necessary to support this one additional 64-bit value in the index file. ;-)
More changes coming in the next PR, but this one can be merged. All changes are made in a backward compatible way, so that all existing code continues to work just as it always has.
To get the index files for files > 2 GB, new functions must be called, wtih an index version argument.