Enable uduints based time coordinates on scan aggregations #1439
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
Scan-based aggregations with a dateFormatMark produce a String time variable with ISO time string formatted values. This commit enables users to configure the aggregation to produce numeric, udunits based time variables. This improves compatibility with popular clients, such as xarray. Addresses Unidata#1327
lesserwhirls
added
enhancement
5 tasks
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.
Description of Changes
Scan-based aggregations with a dateFormatMark produce a String time variable with ISO time string formatted values. This commit enables users to configure the aggregation to produce numeric, udunits based time variables. This improves compatibility with popular clients, such as xarray. Closes #1327
As part of this PR, I've added a version attribute to the NcML xsd. As the xsd remains fully backwards compatiable, the namespace has not changed, but the point version of the scheme has been incremented from (previously undefined) v2.2 to v2.2.1.
PR Checklist
until ready for review