Skip to content

THREDDS Data Server v5.9

Latest
Latest

Choose a tag to compare

View all tags
@lesserwhirls lesserwhirls released this 14 Jul 15:28
Immutable release. Only release title and notes can be modified.
v5.9
a07d440

What's Changed

The TDS v5.9 release includes multiple enhancements and bug fixes. While new feature may require configuration changes to utilize, there are no configuration changes required before upgrading from the previous release (TDS v4.8). If upgrading from a release prior to v4.8, please see the release notes of the intermediate versions for upgrade instructions.

Features and Improvements

  • Produce Software Bill of Materials (SBOMs) for thredds.war and tdm.jar using the CycloneDX standard (driven by the OWASP Foundation) by @lesserwhirls in #648
  • Allow gCDM as a data source by @lesserwhirls in #654
  • Add libblosc2 native jar to TDS to support Zarr blosc compression by @lesserwhirls in #660
  • Migrate code to use netCDF-Java's new MFile abstractions to support GRIB feature collections against object storage by @lesserwhirls in #665
  • Extend datasetScan to optionally exclude empty directories by @lesserwhirls in #666
  • Allow admins to set NCSS GRID request default format by @lesserwhirls in #674

Notable bug fixes

A critical fix to the edal-java codebase is included in this release. The fix has the potential to reduce memory usage by 1000x when opening spatially large datasets via the WMS service (as well as a reduction in opening time by a factor of 3). Additional edal-java improvements include security-related hardening. Finally, many relevant bug fixes are included in netCDF-Java (please see the netCDF-Java v5.10.0 release notes for more information).

Full Changelog: v5.8...v5.9

Downloads

For downloads of the THREDDS Data Server war and the THREDDS Data Manager jar (as well as their SBOMS), please visit https://downloads.unidata.ucar.edu/tds/. Information regarding the TDS and TDM Docker images can be found at https://github.com/unidata/thredds-docker.

Documentation

THREDDS Data Server documentation

Real-world use by the user community is integral to the process of creating and refining the TDS. Please direct all potential security issues directly to Unidata using the address security@unidata.ucar.edu. Please send all other potential issues to the TDS GitHub issue tracker, the user community mailing lists (thredds@unidata.ucar.edu), or through the Unidata support system (support-thredds@unidata.ucar.edu).

Contributors

lesserwhirls
Assets 3
Loading