Additional Digital Object Identifiers (DOIs) have been created for Unidata technologies. We encourage you to use the DOIs when citing or otherwise referring to these technologies, because they provide a mechanism by which the information referred to can be found even if the web address underlying the DOI changes over time.
DOIs are strings of characters assigned by a registering organization to uniquely idenfity a digital resource such as a document, software package, data set, or other electronic “object.” Once a DOI is registered, metadata about the object can be associated with the identifier and maintained separately from the object itself, so that changes to the object's location can be reflected in the DOI's metadata.
LDM Version 6.13.0 is now available. It has a new logging system that, by default, doesn't use the system logging daemon though this change should be invisible. It also has several other improvements and bug fixes.
Version 6.11.7 of the LDM has been released. It fixes a bug that caused the NOAAPORT ingest component to crash.
Here's the story:
The NOAAPORT Satellite Broadcast System contains a lot of GRIB-2 messages. Such messages require external tables in order to be interpreted. The NOAAPORT ingest component of the LDM uses the tables that come with GEMPAK to interpret GRIB-2 messages in order to generate meaningful LDM product-identifiers. Unfortunately, not all tables are complete and creators of GRIB-2 messages are free to add data for which no corresponding table-entry exists.
Version 6.11.6 of the LDM has been released. Continuing the trend of version 6.11.5, this version doesn't have the PNG or ZLIB packages bundled-in -- and for the same reasons: bundling is no longer necessary, security is enhanced by removing them, and the size of the LDM package is reduced. You must have the PNG and ZLIB development packages installed in order to build this version of the LDM.
Version 6.11.5 of the LDM has been released. This version doesn't have the "libxml2" package bundled-in; consequently, the "libxml2" development package must be installed on the host system before the LDM package can be built. The development package is necessary because the runtime package doesn't have the required header-files (development packages usually have the word "devel" in their name). If you're using version 6.11.4 of the LDM, have not encountered any problems with it, and don't care which "libxml2" package the LDM uses, then there's no need to upgrade to LDM 6.11.5.
Version 6.11.4 of the Local Data Manager (LDM) has been released. This version fixes and improves the defense against a denial-of-service attack, which is new with version 6.11. Getting the defense right was trickier than initially thought.
