prevent xarray from changing variable types on open_dataset #254
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.
GitHub Issue: 253
Description
Stitchee is inadvertently changing the data type for the main_data_quality_flag variable in TEMPO data, from int16 to float32. This impacts the SAMBAH service chain for certain edge cases (multi-file scans combining with single-file scans), because CONCISE raises an error when it encounters differing data types for the same variable.
Local test steps
Checked
product/main_data_quality_flag
in the output using standalone stitchee and in local Harmony environment before and after addingmask_and_scale
parameter in thexarray.open_dataset
function:mask_and_scale
mask_and_scale
Overview of integration done
PR Acceptance Checklist
CHANGELOG.md
updated📚 Documentation preview 📚: https://stitchee--254.org.readthedocs.build/en/254/