PERSPECTIVES FROM GODAE
9
Figure 2. Illustration of the process for taking in situ and remotely sensed data (left) through a
model-based assimilation system to produce a self-consistent analysis, which is then used to
produce products such as a climate or regional/coastal forecast.
The scope and international nature of GODAE requires distributed data
assembly and serving, a multiplicity of assimilation products, distributed
product serving and archiving, and a multiplicity of application centers
(Figure 3).
5.1
GODAE observational and data needs
Data needed for GODAE model/assimilation systems can be separated
into four main classes: atmospheric forcing (wind stress, wind speed, air
temperature, specific humidity, precipitation) and sea-ice, data for
assimilation (e.g., altimetry, Argo, SST), validation data (e.g., hydrography)
and ancillary data (climatologies, bathymetry). Note, however, that the
separation into data types is neither definitive nor unique (e.g., forcing data
can be used as one of the controls on the assimilation process).
Koblinsky and Smith (2001) discusses the data system and other papers
of this Volume discuss details and issues that are of specific concern for
GODAE. Remote sensing data is naturally central to the success of GODAE
and GODAE has placed particular emphasis on surface topography, surface
wind and sea surface temperature data.
GODAE itself has taken two specific initiatives to address specific gaps.
In the early stages of GODAE it became clear that the in situ coverage was
inadequate for both climate and ocean assimilation purposes. The Argo Pilot
Project (Argo Science Team, 1998) was established soon after GODAE was
born, and has realized a near-revolution in our capability to observe the
ocean in real-time (see papers by Send and by Pouliquen, this Volume). A
9
Figure 2. Illustration of the process for taking in situ and remotely sensed data (left) through a
model-based assimilation system to produce a self-consistent analysis, which is then used to
produce products such as a climate or regional/coastal forecast.
The scope and international nature of GODAE requires distributed data
assembly and serving, a multiplicity of assimilation products, distributed
product serving and archiving, and a multiplicity of application centers
(Figure 3).
5.1
GODAE observational and data needs
Data needed for GODAE model/assimilation systems can be separated
into four main classes: atmospheric forcing (wind stress, wind speed, air
temperature, specific humidity, precipitation) and sea-ice, data for
assimilation (e.g., altimetry, Argo, SST), validation data (e.g., hydrography)
and ancillary data (climatologies, bathymetry). Note, however, that the
separation into data types is neither definitive nor unique (e.g., forcing data
can be used as one of the controls on the assimilation process).
Koblinsky and Smith (2001) discusses the data system and other papers
of this Volume discuss details and issues that are of specific concern for
GODAE. Remote sensing data is naturally central to the success of GODAE
and GODAE has placed particular emphasis on surface topography, surface
wind and sea surface temperature data.
GODAE itself has taken two specific initiatives to address specific gaps.
In the early stages of GODAE it became clear that the in situ coverage was
inadequate for both climate and ocean assimilation purposes. The Argo Pilot
Project (Argo Science Team, 1998) was established soon after GODAE was
born, and has realized a near-revolution in our capability to observe the
ocean in real-time (see papers by Send and by Pouliquen, this Volume). A