You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add filtering for datasets that are out of compliance with the latest IOOS_Glider_NetCDF version to prevent failure when loading into ERDDAP.
Reference
The GliderDAC Compliance Checker Plugin generates a report detailing any existing issues and recommended corrective actions, in accordance with the NGDAC NetCDF File Format Version 2.
We can use this tool to enhance the report capabilities, determine whether a dataset passes or fails, and avoid ERDDAP errors, such as the case with the dataset sg658-20220408T0000 reported by Amber York.
The text was updated successfully, but these errors were encountered:
We already do run the Glider Compliance Checker against datasets, and the whole IOOS Gliders spec is used, however, we only actually apply the standard names section of the compliance report to see if the aggregation can be archived by NCEI. We had tried running against the full spec, but if I recall correctly, currently no dataset passes this.
What should we add?
Add filtering for datasets that are out of compliance with the latest IOOS_Glider_NetCDF version to prevent failure when loading into ERDDAP.
Reference
The GliderDAC Compliance Checker Plugin generates a report detailing any existing issues and recommended corrective actions, in accordance with the NGDAC NetCDF File Format Version 2.
We can use this tool to enhance the report capabilities, determine whether a dataset passes or fails, and avoid ERDDAP errors, such as the case with the dataset sg658-20220408T0000 reported by Amber York.
The text was updated successfully, but these errors were encountered: