IDV Development Status Report
May 15, 2004
This report updates the status of Unidata's IDV development
efforts since the last report
During the 1998-2003 Unidata proposal period, the MetApps project goals
- Deliver turn-key platform-independent applications for the
analysis and visualization of meteorological data. These
applications must provide and extend the most important capabilities
of currently-available applications such as GEMPAK, GARP, and
McIDAS. Use of these applications should require no knowledge
of Java or component architectures.
- Deliver easily installed executables, user documentation, and
test cases for the turn-key applications.
- Identify or create a component-oriented framework that supports
construction of custom applications from components used to
build the turn-key applications. This framework should be
useful to create new combinations of components that provide
subsets of the capabilities of the turn-key applications,
connect them in unanticipated ways, or provide tailored
mini-applications for embedding in educational materials. Use
of these components may require knowledge of component
architectures or Java.
- Deliver full source code, class documentation, and test cases
for the MetApps components.
- Enlist other developers in enhancing components and developing
new components for the framework by providing an
archive, mailing list, developers' forums, documentation, web
site, and support for the components.
The Integrated Data Viewer (IDV) was released in June 2003 and is the
culmintation of this effort. The IDV reference application embodies
goals #1 and #2 listed above. The IDV framework supports the development
of custom applications as specified in #3 such as the specialized
IDV based visualization tool in the Visual Geophysical Exploration
Environment (VGEE). Source code, documentation and example applications are
provided with the IDV release. Other developers are starting to provide
enhancements to the IDV framework (VGEE and EPA) and many of the items
in #5 are already in place. The UPC is currently investigating ways to
make it easier for developers to contribute to all software projects and
the IDV development will benefit from such a system.
We feel that we have met the goals of the MetApps project in
the timeframe specified and are now moving on to the next phase of IDV
Unidata 2008 proposal, IDV development will continue under
the proposed Endeavor 4 "Software to Analyze and Visualize Geoscience
Data". Under this endeavor, the following goals are outlined:
- Supporting analysis and visualization of local modeling efforts
(e.g., WRF and MM5 output)
- Incorporating new datasets and data types
- Exploring new approaches to visualizing and interacting with Earth
system data, focusing on novel 3-D techniques that fuse data from
- Expanding IDV capabilities to support the creation of exploration
based, interactive, pedagogic materials and integration with digital
- Developing collaborative tools to make effective use of shared
- Developing a framework that allows end-user assembly and
integration of IDV components
- Adapting to GIS frameworks (OpenGIS and ISO standards),
content-based data mining, and other evolving technologies
Progress since last report
Testing is underway for IDV 1.1 beta4 which will be released only
to the IDV Steering Committee for feedback. New features include:
- New map control which allows users to add their own maps
into the system. This replaces the Map preferences.
- New side legends. Steering committee will provide feedback
on the usefulness and functionality of this feature.
- New template framework allowing users to set up the properties
for a particular display (i.e. 500 mb height display). This
is sort of a subset of the bundling mechanism.
- Implementation of some skew-T enhancements suggested during the
Steering Committee conference call.
- various and sundry bug fixes.
Ongoing efforts include:
- Collaborating in the development of
- Keeping up with new Java interfaces and developments
- Various and sundry IDV bug fixes and enhancements.
This document is maintained by
Don Murray <email@example.com>