Releases: nasa/earthdata-varinfo
Version 4.0.1
Changed:
-
get_umm_varis updated so that the UMM-VarDefinitionproperty will use
long_namebefore the default of the variable name. The full ordering of
precedence for metadata attributes used as UMM-VarDefinitionis now:- description
- Description
- definition
- Definition
- title
- Title
- long_name
If none of the metadata attributes above are present, the variable name is
used as a default value for the UMM-VarDefinition, as before.
Commits
issue-76: Use long_name as a possible UMM-Var description before the variable name default (#91)
Version 4.0.0
Changed:
- VariableFromNetCDF4 is updated to use fully qualified paths to variable
dimensions. This update allows dimensions in parent groups to be found
without special handling.
Commits
DAS-2435: Support "up-level" variable dimensions. (#84)
Version 3.3.1
Changed:
-
Release notes for
earthdata-varinfowill now include the commit history for
that release. -
urllib3dependency is pinned to ~2.6.1 to handle vulnerabilies CVE-2025-66471 and CVE-2025-66418.
Commits
DAS-2435: Updates deps. for mitigation of CVE-2025-66471,66418 (#83)
IP-254: Add pytest-cov minimum threshold of 95%. (#79)
TRT-315: Include commit history in release notes. (#70)
Version 3.3.0
v3.3.0
2025-09-11
Changed:
- DAS-2373 - Updated the retrieval of data type from
netCDF4.Variableobjects
to first consider thenetCDF4.Variable.datatype.nameand then fall back to
netCDF4.Variable.datatype.dtype.
Version 3.2.0
v3.2.0
2025-07-25
Changed:
- DAS-2339 - Clarified documentation regarding
RequiredVariablesin the
configuration file schema,CFConfigclass and
VarInfoBase.get_required_variables. Variables specified in
RequiredVariableswill be included as required variables for all variables
variable subsets of the relevant collection defined in the configuration file
rule. There is no filtering based on the variable path of the requested
variables in the input set toVarInfoBase.get_required_variables.
Added:
- Support for getting an OPeNDAP url with
cmr_search.get_dmr_xml_urland
ause_dmr=Trueflag tovarinfo/generate_umm_var.generate_collection_umm_var
Version 3.1.0
v3.1.0
2025-03-25
Added:
VariableBase::is_projection_xandVariableBase::is_projection_yadded to
determine a variable's exact projected coordinate.
Changed:
- earthdata-varinfo's numpy requirements relaxed to allow numpy v2.
Version 3.0.3
v3.0.3
2025-03-21
Changed:
- Updated to
netCDF4~=1.7.2to enablemypytype hints for the package.
Version 3.0.2
v3.0.2
2025-02-07
This version of earthdata-varinfo enables support for VariableFromDmr
variable dimension shape data in NetCDF-4 files with named dimensions
and HDF-5 files with anonymous size-only dimensions.
Added:
VariableFromDmr::_get_shape()returns dimension shape data for NetCDF-4
files with named dimensions and HDF-5 files with anonymous size-only dimensions.
Changed:
*Update DRM unittest to validate variable dimension shape data.
Version 3.0.1
v3.0.1
2024-10-18
Changed:
- CMR native IDs generated from variable names with spaces in them will replace
those space characters with underscores to avoid errors when trying to ingest
such variables. - The
python-cmrrequirement is updated to v0.12.0, which adds type hints for
that package. A couple of type hints inearthdata-varinfohave been updated
accordingly. - The
numpyrequirement has been relaxed to allow broader compatibility with
client software. Note: This enables Python 3.12 compatibility. - To ensure compatibility with Python 3.12, the tests are now run using
pytest. This allows JUnit style output to be produced, as the previously
usedunittets-xml-runnerpackage was not compatible with Python 3.12. The
tests themselves are still written using classes and syntax fromunittest.
The CI/CD for running the tests has been updated to also run the tests under
Python 3.12.
Version 3.0.0
v3.0.0
2024-09-11
The configuration file schema for earthdata-varinfo is significantly updated
in this release. For more information, see the release notes for schema v1.0.0
in config/CHANGELOG.md.
Added:
- Groups within a NetCDF-4 or DMR file are now assigned to the
VarInfo*.groups
dictionary, allowing for their metadata attributes to be accessed after parsing
an input file.
Changed:
CFConfig.get_cf_attributeshas been renamedCFConfig.get_metadata_overrides,
as there are now only overrides to be returned from this method. Calls to
CFConfig.get_metadata_overridesnow must specify a variable path. All
overrides from a configuration file for a given collection are now retrievable
from the newly publicCFConfig.metadata_overridesclass attribute.- Metadata overrides retrieved for a matching file path are ordered such that
the most specific applicable override to the variable takes precedence. For
example, when requesting the value of the "units" metadata attribute for
variable "/nested/variable", an applicability rule that exactly matches this
variable path will take precedence over rules matching to either the group,
or all variables in the file. - Handling of nested
Applicability_Groupshas been removed from theCFConfig
class, as the configuration file no longer nests these items in overrides.
Removed:
CFConfig._cf_supplementshas been deprecated in favour of specifying all
in-file metadata changes via aMetadataOverridesitem (formerly
CFOverrides) instead.