Test file for the OSDF reader with float dimension coordinates#250
Open
srherbener wants to merge 1 commit into
Open
Test file for the OSDF reader with float dimension coordinates#250srherbener wants to merge 1 commit into
srherbener wants to merge 1 commit into
Conversation
lewisn-met
approved these changes
Jul 9, 2026
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
2 participants
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.
Description
This PR adds a new test file for verifying that the OSDF reader can handle dimensions (eg, Channel) with float coordinate values in an input netcdf file.
Issue(s) addressed
Partially addresses jcsda-internal/ioda/issues/1787
Dependencies
List the other PRs that this PR is dependent on:
Impact
Expected impact on downstream repositories:
Manual Testing Instructions (optional)
If you would like your reviewers to manually build and test the change, please include
instructions on how the change should be built and tested. Also include a short
justification on why manual testing is necessary for this change.
Checklist
- [ ] I have made corresponding changes to the documentation