List view
- No due date•4/4 issues closed
Milestone for release 4.4.0. Contains backwards-compatible API changes, such as ensuring datasets which use the CF Contiguous Ragged Array format and Indexed Ragged Array format are considered valid.
No due date•1/1 issues closedMilestone for release 4.3.4; bugfixes and small edits for the IOOS-1.2 checker.
No due date•14/15 issues closedUpdate the IOOS checker (https://github.com/ioos/compliance-checker/blob/master/compliance_checker/ioos.py) to reflect the new 1.2 standards (https://ioos.github.io/ioos-metadata/ioos-metadata-profile-v1-2.html).
Due by March 24, 2020•10/10 issues closedPerformance Increase, MetaData References, and Bug Fix: Pull Request #600 enhances compliance checker speed with the use of an lru-cache (Least Recently Used) from `functools`. It also allows backwards-compatibility with the lru-cache for python2.7 via the [`functools32`](https://pypi.org/project/functools32/) backport module. PR #599 updates the Climate and Forecasting integration tests. PR #598 puts reference links to metadata schemas into the compliance-checker output. PR #603 supports loading CF standard names table from an alternate path. PR #604 fixes the deallocation error associated with the memoization. For bug fixes, this release fixes the TravisCI build failures in `conda` environments found which initially caused #598 and #599 to fail.
No due dateThis milestone will upgrade the compliance checker output scoring system in a backwards compliant manner.
Due by April 13, 2018•10/10 issues closedImplement additional features and changes in CF-1.7. http://cfconventions.org/Data/cf-conventions/cf-conventions-1.7/cf-conventions.html
No due date•5/5 issues closedBug fixes, and documentation
Due by October 13, 2017•14/14 issues closedVersion 3.0 will provide improved feature detection for the CF Checker. The CF Checker will be refactored so that it checks each section of the CF conventions based on the detected feature. The feature detection code written for the [NCEI plugin](https://github.com/ioos/cc-plugin-ncei/blob/master/cc_plugin_ncei/util.py), which defined features by the combination and order of dimensions/coordinate variables in variables, will likely be leveraged in this refactor.
Due by November 19, 2016•44/44 issues closedConsistent language for prescribing corrective actions Result attributes that will allow plugin writers and software clients to test for checks status
Due by October 3, 2016•13/13 issues closed- No due date•14/14 issues closed
- No due date•5/5 issues closed
This milestone encompasses the work needed to upgrade the compliance checker to provide a complete report against the Glider DAC v2.0 submission file format. Date TBD during the next phase of release planning.
No due date•1/1 issues closedKnown unknowns - things we know we don't know, aka the date of when these issues will be done
No due date•4/4 issues closed- No due date•3/3 issues closed
Initial public release of the compliance checker with documentation, examples etc.
Due by July 18, 2014•22/22 issues closed