# CF Checker
The CF Checker is a utility that checks the contents of a NetCDF file complies with the Climate and Forecasts (CF) Metadata Convention.
## Dependencies
The package runs on [Linux](http://en.wikipedia.org/wiki/Linux) and [Mac OS](http://en.wikipedia.org/wiki/Mac_OS) operating systems.
[Python 3.x](https://www.python.org/)
[netcdf4-python](https://pypi.python.org/pypi/netCDF4) at version 1.2.5 or newer. This package requires [netCDF](https://www.unidata.ucar.edu/software/netcdf/), [HDF5](https://www.hdfgroup.org/solutions/hdf5/) and [zlib](ftp://ftp.unidata.ucar.edu/pub/netcdf/netcdf-4) libraries.
[cfunits-python](https://bitbucket.org/cfpython/cfunits-python) package version 3.0.0 or newer
[numpy](https://pypi.python.org/pypi/numpy) version 1.15 or newer
## Installation
To install from [PyPI](https://pypi.python.org/pypi/cfchecker):
pip install cfchecker
Alternatively, to install from source:
Download the cfchecker package from [cfchecker releases](https://github.com/cedadev/cf-checker/releases)
Unpack the library:
tar -zxf cfchecker-${version}.tar.gz
cd cfchecker-${version}
Install the package:
To install to a central location:
python setup.py install
To install to a non standard location:
python setup.py install –prefix=<directory>
If directory you are installing into is not on PYTHONPATH you will need to add it.
## Running the CF Checker
cfchecks [-a <area-types.xml>] [-r <regions.xml>] [-s <std_names.xml>] [-v <CFVersion>] [-x] [-t <cache_time_days>] file1 [file2…]
For further details and for other available command line options please see the help by running cfchecks -h
### Environment Variables
The following parameters can be set on the command-line or through environment variables:
CF_STANDARD_NAMES or (CL option -s) : The path or URL to the CF standard names table
CF_AREA_TYPES or (CL option -a) : The path or URL to the CF area types table
CF_REGION_NAMES or (CL option -r): The path or URL to the CF region names table
### Running the Test script
In the release tarball there is a test_files directory containing a test.sh script which runs a series of test files through the CF Checker and confirms the checker is working as expected. It is a very elementary system, which will be rewritten soon. Before running it you will need to edit the location of the cfchecks script in the tests.sh file:
cfchecker=”<location of cfchecks>”
Then just run the tests.sh script:
./tests.sh
Metadata
Release files for cfchecker 4.1.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 |
|---|---|---|---|---|
| cfchecker-4.1.0.tar.gz | 37.4 kB | Without provenance | Details for cfchecker-4.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cfchecker-4.1.0-py3-none-any.whl | Python 3 | none | any | Details for cfchecker-4.1.0-py3-none-any.whl |
Total release size: 73.4 kB
Release files / cfchecker-4.1.0.tar.gz
| Download URL | cfchecker-4.1.0.tar.gz |
|---|---|
| Size | 37.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
10b86748565c9e0f4c959e4d82fe83b00344551db3db3c7d0d2f8c31449aa1b9
|
|
BLAKE2b-256 checksum How to use checksums |
87f915583ac34fb3525864c72c47c8f2949f71e9c4b7559cba8fe4aeac8958e8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.0.1 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.9.1
|
Release files / cfchecker-4.1.0-py3-none-any.whl
| Download URL | cfchecker-4.1.0-py3-none-any.whl |
|---|---|
| Size | 36.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
97d58377acda15f34977e14928329e6311081d6a56e0bcaee06f516724b66873
|
|
BLAKE2b-256 checksum How to use checksums |
c08a816c1c8736c44f10c22b6b26718a6960d41e99c1e723322b837bf07aa79f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.0.1 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.9.1
|
Security for cfchecker 4.1.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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.