GliderDAC Compliance Checker Plugin
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 |
3 maintainers
Metadata
3 maintainers
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)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| cc_plugin_glider-2.3.0.tar.gz | 166.1 kB | With provenance | Details for cc_plugin_glider-2.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cc_plugin_glider-2.3.0-py3-none-any.whl | Python 3 | none | any | Details for cc_plugin_glider-2.3.0-py3-none-any.whl |
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 logRelease 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 logSecurity for cc-plugin-glider 2.3.0
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for cc_plugin_glider-2.3.0.tar.gz
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 logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
