Skip to content

THREDDS Data Server v5.6

Latest
Compare
Choose a tag to compare
@lesserwhirls lesserwhirls released this 22 Jan 21:03

Version 5.6

The THREDDS Data Server (TDS) version 5.6 release was announced on January 22nd, 2024. his release contains a number of fixes for user-reported problems, as well as several upgrades to third party libraries. For details on TDS 5, and tips on how to migrate from version 4, please visit https://docs.unidata.ucar.edu/tds/5.6/userguide/upgrade.html.

Important information about this release

  1. TDS v5.6 moved from Spring v5 to v6, and as a result, the TDS now requires the use of Java 17 and a Jakarta EE 9+ compatible servlet container (e.g. Tomcat 10).
  2. The move to Java 17 requires the use of additional JVM options to allow for the chronicle-map dependency to work properly. Please see the example setEnv.sh contents in the TDS documentation.
  3. The version of edal-java used by the TDS has been updated. This dependency implements the WMS service provided by the TDS. The edal-java update includes an update to one of its 3rd party dependencies in which the existing coordinate transform database may be incompatible with the new release. If this is the case, the TDS will fail to start after the upgrade, and the stacktrace in the log files will hint at a possible h2 database incompatibility. To fix this issue, you will need to remove the ${tds.content.root.path}/hredds/cache/edal-java/epsg/.h2 directory.

Notable additions

Features and Improvements

Notable bug fixes

Additionally, this release contains many 3rd party dependency upgrades and documentation improvements.

Full Changelog: v5.5...v5.6

Downloads

For downloads of the THREDDS Data Server war, THREDDS Data Manager jar, and threddsISO plugin, please visit https://downloads.unidata.ucar.edu/tds/

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 [email protected]. Please send all other potential issues to the TDS GitHub issue tracker, the user community mailing lists ([email protected]), or through the Unidata support system ([email protected]).