The NetCDF-Java/Common Data Model (CDM) library and THREDDS Data Server (TDS) version 4.6.4 were released on February 12th, 2016. This is a stable release, and as such, the development team recommends this upgrade to anyone using the CDM or TDS. The latest update can be downloaded from:
Version 4.6.3 was released on August 31st, 2015. The 4.6.4 release addresses the following issues from the 4.6.3 release:
New features and enhancements
- Added a command-line utility to replay tomcat access logs against a different server. Useful to test upgrades to a new TDS.
- Gradle now generates a thredds-parent Maven BOM publication
- The build is now done completely in gradle — the maven pom files have been removed.
- Copy / paste functionality in ToolsUI using the Mac OS X keybindings
- Bug fixes / improvements to base TDS docker image.
- Fix URLs for subdirs with spaces in a DatasetScan.
- Major refactor of GINI IOSP code.
- Ensure files following CF and COARDS get a calendar attribute added in the event that the attribute is missing.
- Fixed bug that caused FileCache to remove entries for closed datasets
- CSV output from GridAsPoint and PointFeatureCollections now return consistent headers.
- ToolsUI now uses a file chooser to save binary output.
- Fix VectorLayer components look up in wms server (TDS side code)
- Fix bug in which PointFeatureCollections were not updating
- Updated httpservices to properly use Apache httpclient 4.5
- Improved performance of reading data from Amazon S3
All users are strongly encouraged to move to 4.6. For more information about the 4.6 release and how to upgrade, please see Upgrading to TDS 4.6.
Many thanks to our external contributors John Caron (@JohnLCaron), R. Schmunk (@msdsoftware), @massonjr, Joan Pau Beltran (@joanpau), @geoneubie, @pacioos, as well as those who reported bug on the github issue tracker!
For a full list of changes between v4.6.3 and v4.6.4, as well as links to the original GitHub issues, please see the Github Issue Tracker.
Real-world use of new features by the user community is integral to the process of creating and refining these libraries. Please send any potential issues to the development team via the THREDDS GitHub issue tracker, Unidata's support system (firstname.lastname@example.org or email@example.com) or the user community mailing lists (firstname.lastname@example.org or email@example.com).