Skip to content

Add time & time bnds#70

Merged
joshuatorrance merged 10 commits into66-clone-of-schemafrom
69-add-time-time_bnds
Apr 15, 2026
Merged

Add time & time bnds#70
joshuatorrance merged 10 commits into66-clone-of-schemafrom
69-add-time-time_bnds

Conversation

@joshuatorrance
Copy link
Copy Markdown
Collaborator

Add time and time_bnds to the schema.

The current proposal requires the bounds to be name time_bnds. If this is relaxed to allow time_bounds then some further updates will be required. Could just use a regex to allow the alternative but this might permit a mix of the two. Compelling them to match will require additional some extra chicanery.

Contributes to #68
Closes #69

@joshuatorrance joshuatorrance self-assigned this Mar 17, 2026
@joshuatorrance joshuatorrance changed the base branch from main to 66-clone-of-schema March 17, 2026 01:02
@joshuatorrance joshuatorrance changed the title 69 add time time bnds Add time & time bnds Mar 18, 2026
@joshuatorrance joshuatorrance marked this pull request as ready for review March 20, 2026 01:19
Comment thread au.org.access-nri/model/output/file-metadata/2-1-0/variable/time.json Outdated
Comment thread au.org.access-nri/model/output/file-metadata/2-1-0/variable/time.json Outdated
Comment thread au.org.access-nri/model/output/file-metadata/2-1-0/variable/time/calendar.json Outdated
Comment thread au.org.access-nri/model/output/file-metadata/2-1-0/variable/time.json Outdated
@joshuatorrance joshuatorrance merged commit 6f53631 into 66-clone-of-schema Apr 15, 2026
1 check passed
@joshuatorrance joshuatorrance deleted the 69-add-time-time_bnds branch April 15, 2026 05:58
joshuatorrance added a commit that referenced this pull request Apr 16, 2026
* Made copy of 2-0-0 for new version, only updating version number

* Add geospatial extent to model ouput schema (#67)

* Added files for geospatial extent

* CI is failing to install? Updating to latest release

* Added exclusions for 2 linting rules, split command over multiple lines

* Does this work for adding another directory to run commands over?

* Updated 2-1-0 test with new attributes

* Updating schema testing to handle multiple versions

* Fixed typo

* Trying to fix looping in shell script

* Added rules to geospatial attributes

* Reordered new rules to satisfy formatter

* Apply suggestion from @aidanheerdegen

Co-authored-by: Aidan Heerdegen <aidan.heerdegen@anu.edu.au>

* Added simple tests for global attrs and geospatial attrs

* Added some simple tests for geospatial bounds

* Changed geospatial_*_units to use const instead of a pattern

* Removed examples from now const units

* Removed limits on lat/lon values, updated tests

---------

Co-authored-by: Aidan Heerdegen <aidan.heerdegen@anu.edu.au>

* Add time & time bnds (#70)

* Added time and time_bnds

* Added option for units of reference datetime to have seconds

* Now supporting alternative calendar options from CF.

* Added required to time

* Moved non-const time attrs into sub-schemas

* Added type to time units

* Added additional tests. These won't be run yet, should run after merge from neighbouring branch '66-model-ouput-adding-geospatial'

* Removed bounds from the required list.

* Added a test for missing bounds

* Updated calendar recommendations. @blimlim & @aidanheerdegen

* Tweaked time.json to satisfy formatter

---------

Co-authored-by: Aidan Heerdegen <aidan.heerdegen@anu.edu.au>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Update model output schema to dictate the requirements for time & time_bnds

3 participants