OpenADDE: Open Source ADDE Servers

1
OpenADDE Open Source ADDE Servers
Dave Santek 7 - 8 October 2004
2
Overview

• What is Open Source?
• An overview of ADDE
• Why should we make ADDE available as Open Source?
• Status and future plans

3
Open Source Definitionfrom www.opensource.org

• Free redistribution
• Source code available
• Derived works
• Integrity of the authors source code

4
ADDE ServersAbstract Data Distribution
Environment

• In use for nearly 10 years
• Sectorizing of geographic coverage and bands
• Compressed transmission
• TCP/IP protocol through port 112
• Variety of clients can access the servers
• All data returned in common format, not the
  stored format

5
ADDE Servers

• McIDAS format image, grid, point, text
• netCDF image
• McIDAS (write)
• AWIPS (read/write)
• TRMM (read)
• SSM/I (read)
• Radar from NOAAPORT
• HDF as point

6
ADDE Servers

• HDF image data
• MODIS Level 1b and Level 2 atmosphere products
• AIRS Level 1b
• AMSR-E Level 1b
• GRIB
• Raw satellite
• Meteosat-8

7
ADDE Clients

• McIDAS-X
• McIDAS-Lite
• IDV Integrated Data Viewer
• Matlab
• IDL

8
McIDAS-X
9
McIDAS-Lite
10
IDV
11
Matlab
import edu.wisc.ssec.mcidas. aAreaFile(adde//i
mage?) b getData(a) csqueeze(b) imagesc(c)
12
Why OpenADDE?

• Encourage data providers to write servers
• SSEC, Unidata, MSFC have written servers that are
  currently in core
• Enable ADDE to become more of an accepted data
  transmission standard
• OPeNDAP is being considered by NASA as their
  standard

13
Open Source Issues

• Are MUG funds being used in this effort?
• No. This is being supported by other projects
  within SSEC. We are also searching for external
  funds to improve the documentation, examples, and
  protocol to further encourage others to develop
  servers.
• What code will be Open Source?
• Initially, servers that are of general interest
  and the necessary McIDAS library functions to
  build the servers. These servers will be working
  examples as a starting point for new servers.

14
Open Source Issues

• Why give away code that is supported by the MUG?
• Most of the initial development of the servers
  was paid for by other projects, not the MUG. The
  MUG tests, maintains, and ensures that the code
  is compatible with the core applications. We
  decide case-by-case which servers the MUG
  supports, and to what extent. For example, we
  include the AIRS server in core, although it has
  not been fully tested with all applications.

15
Open Source Issues

• How does Open Source ADDE benefit the MUG?
• Having others develop servers for data sources we
  dont have access to
• The developers are the users of the data
• New ideas Thinking outside-the-box
• Community involvement enhances performance,
  reliability, and facilitates wide acceptance

16
Status

• An experiment with a binary installation of MODIS
  servers was successful
• Installed at 4 locations 2 polar Direct
  Broadcast sites, the GSFC DAAC, and the NOAA bent
  pipe
• Free access to the global MODIS data in realtime
  from the bent pipe
• These same MODIS servers will be available soon
  as Open Source
• Working on packaging issues now

17
Future Plans

• A proposal is being written to solicit funds to
  maintain and enhance the OpenADDE concept.
• After a period of time, we will evaluate the
  impact of the initial release of the MODIS
  servers.
• Other core servers may be added to the OpenADDE
  package. Most likely these will be servers that
  read/write AWIPS compatible netCDF files or AVHRR
  Level 1b.
• At this time, we have only considered image
  servers.