Skip to main content

GliderDAC Compliance Checker Plugin

Tests

This ioos/compliance-checker plugin supports the following sources and standards:

Standard Checker Name
Glider DAC gliderdac

Installation

Conda

$ conda install -c conda-forge cc-plugin-glider

Pip

$ pip install cc-plugin-glider

See the ioos/compliance-checker for additional Installation notes

Usage

$ compliance-checker -l
IOOS compliance checker available checker suites (code version):
  ...
  - gliderdac (x.x.x)
  ...
$ compliance-checker -t gliderdac [dataset_location]

See the ioos/compliance-checker for additional Usage notes

Summary of the Checks

The checks have been designed to help data providers submit the highest quality data to the GliderDAC. Submitting uncompliant data to the DAC may result in services not working. For example, not providing the correct Sea Name in the GLobal attributes may put your glider deployment into the wrong region on the GliderMap. Not providing proper metadata about the platform and instruments, and attribution may prevent NCEI from archiving your data. And not making your files CF compliant could prevent the files from showing up on ERDDAP and THREDDS servers all together.

High priority checks

Failures in these checks should be addressed before submitting to the GliderDAC!

  • check_required_variables
  • check_dimensions
  • check_lat_lon_attributes
  • check_time_attributes
  • check_pressure_depth_attributes
  • check_ctd_variable_attributes
  • check_profile_variable_attributes_and_types
  • check_global_attributes
  • check_standard_names
  • check_monotonically_increasing_time
  • check_dim_no_data
  • check_depth_array

Medium priority checks:

  • check_qc_variables
  • check_primary_variable_attributes
  • check_trajectory_variables
  • check_container_variables
  • check_qartod
  • check_ancillary_variables
  • check_dtype
  • check_valid_min_dtype
  • check_valid_max_dtype

Low priority checks

  • check_ioos_ra
  • check_valid_lon
  • check_ncei_tables

Optional environment variables

A cached version of the NCEI seanames.xml file can be provided with a filesystem path in SEA_NAME_TABLE environment variable.

The table below indicates the relationship of the environment variables for cached table locations on disk to their usual remote locations.

Environment Variable Remote Table Location
INSTITUTION_TABLE https://gliders.ioos.us/ncei_authority_tables/institutions.txt
PROJECT_TABLE https://gliders.ioos.us/ncei_authority_tables/projects.txt
INSTRUMENT_TABLE https://gliders.ioos.us/ncei_authority_tables/instruments.txt
PLATFORM_TABLE https://gliders.ioos.us/ncei_authority_tables/platforms.txt
SEA_NAME_TABLE https://www.ncei.noaa.gov/data/oceans/ncei/vocabulary/seanames.xml

Release files for cc-plugin-glider 2.3.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for cc-plugin-glider 2.3.0
File Size Uploaded
cc_plugin_glider-2.3.0.tar.gz 166.1 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for cc-plugin-glider 2.3.0
File Interpreter ABI Platform
cc_plugin_glider-2.3.0-py3-none-any.whl Python 3 none any Details

Total release size: 354.1 kB

Release files / cc_plugin_glider-2.3.0.tar.gz

Download URL cc_plugin_glider-2.3.0.tar.gz
Size 166.1 kB
Tags Source
SHA-256 checksum
How to use checksums
5056dd333fd6f11af0a5c36de1193ca689889e5d682167bc220307895f933209
BLAKE2b-256 checksum
How to use checksums
d0aaf17edacad99d1d9036c3d9e3b1a5c01c58d8f4ddb8e4acbda8823e492a4c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 13, 2026.

Transparency log

Release files / cc_plugin_glider-2.3.0-py3-none-any.whl

Download URL cc_plugin_glider-2.3.0-py3-none-any.whl
Size 188.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
c9d82460895767dbb35eb0d18b8ca222c32498bf4781d74d80a3c23548c40004
BLAKE2b-256 checksum
How to use checksums
c5bac6bc572f3a29f25f35df80677eb0c2bcb81ac8cce6b78e7b7a24f6650fb1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 13, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

2.3.0 This release

2 release files

2.2.1

2 release files

2.2.0

2 release files

2.1.0

2 release files

2.0.4

2 release files

2.0.3

1 release file

2.0.2

1 release file

2.0.0

1 release file

1.0.6

3 release files

1.0.5

1 release file

1.0.4

1 release file

1.0.2

1 release file

1.0.1

1 release file

1.0.0

1 release file

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page