update write for char and str auxiliary coords #174
Merged
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.
Fix: Properly handle string coordinates with CF-compliant encoding
Summary
This PR fixes the incorrect handling of string/character coordinates during NetCDF file writing. String coordinates (e.g.,
typein land variables) are now written with proper CF-compliant encoding and remain as coordinates rather than being converted to data variables.Problem
The current
write()method incorrectly handles string coordinates:typeare written as data variables instead of remaining inds.coords|S11(byte string) to<U11(Unicode), which is not CMIP6 compliantImpact: Land variables with
typecoordinate (e.g.,baresoilFrac,grassFrac,treeFrac) produce non-compliant CMIP6 output files.#166 #172 solved