GALEON Status Update

Ben Domenico
Last modified: April 27, 2007

Overall Objectives

The OGC (Open Geospatial Consortium) GALEON IE(Geo-interface for Air, Land, Earth, Oceans NetCDF Interoperability Experiment) has expanded its objectives considerably beyond its initial, focused set of goals. However, the overall mission remains the same: specify and use standard interfaces to foster interoperability between data systems used by the traditional GIS community and those in community we refer to as the fluid Earth systems (FES, mainly oceanography and atmospheric science). This strategic target is becoming increasingly important as FES observations and forecasts are achieving the high spatial resolutions (a few kilometers and better) of the GIS realm. The challenge is to enable the practitioners in each realm to continue using the powerful tools available through their traditial "stovepipe" applications while allowing for integration of data and applications between the two realms by developing and employing standard, web services-based interfaces between the two.

An Overview of GALEON is also availabl:

http://www.unidata.ucar.edu/projects/THREDDS/GALEON/Reports/GALEONoverview.htm

Phase 1 Accomplishments

The GALEON Phase 1 Team

Client/Server Interaction Experiments

The many experiments between independently-developed client and server implemetations showed that the WCS protocol does indeed have the basic functionality needed to enable access to traditional netCDF datasets. Pointers to individual GALEON experiments are given in the full GALEON Phase 1 Summary Report (http://www.unidata.ucar.edu/projects/THREDDS/GALEON/Reports/GALEONphase1Report.htm)

Recommended Modifications to OGC Interface Specifications

The GALEON experiments have resulted in many recommendations to OGC interface specifications. These are mainly to the WCS specification where they have for the most part been folded into the recommended changes for WCS 1.1. There is work still underway on key "applications schemas" related to the GML (Geography Markup Language) specification based on the work on ncML-GMS at the University of Florence and work on the CSML (Climate Sciences Modeling Language) at the British Atmospheric Data Center. However, one of the most important proposed modifications would be to do away with the list of 5 WCS encoding formats and replacing it with a requirement that WCS encoding formats be documented with a "profile" document that provides enough information for a third party developing a WCS client or server to know how to work with the dataset in that format. Such a WCS profile for a netCDF is under development.

In summary, the GALEON-related changes in WCS 1.1 are:

Pointers to documents describing recommended modifications to OGC interface specifications are given in the full GALEON Phase 1 Summary Report (http://www.unidata.ucar.edu/projects/THREDDS/GALEON/Reports/GALEONphase1Report.htm)

GALEON Phase 2 Issues

Participants have suggested a number of issues to be addressed in the second phase of the OGC GALEON (Geo-interface to Atmosphere, Land, Environment, Ocean netCDF) Interoperability Experiment (IE).  These can be divided into two broad categories.  The first has to do with testing the new WCS 1.1 specification; the second has to do with relationships among WCS and other OGC and ISO specifications such as CSW, WFS, SWE, and a number of GML profiles that have arisen recently.

  1. Is WCS 1.1 adequate for serving netCDF datasets such as those on the servers at Unidata, the University of Florence, George Mason University, NERC, NCDC, and the PFEL?


  2. In the context of serving traditional netCDF datasets, what's the relationship between WCS and other standard specifications?

Expanded Team

Additional organizations are planning to participate more actively in the GALEON phase 2.