Climate Data Records from Environmental Satellites Interim Report (2004) / Chapter Skim
Currently Skimming:
Appendix D: EOSDIS Lessons Learned
Appendix D: EOSDIS Lessons Learned
Pages 123-130
The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.
From page 123... ...
As NASA entered the age of launching great astronomical observatories in the late 1980s, the notion of specialized information processing and distribution centers emerged. These centers were organized around such instrument spectral domains as the visible spectral data at the Hubble Science Telescope Institute at Johns Hopkins University, the Infra Red Center at Cal tech, the High Energy X Ray Institute at the Marshall Space Flight Center, and the Upper Atmosphere Research Satellite instrument-processing teams.
|
From page 124... ...
In addition to the processing of the instrument data from these satellites, the EOSDIS has responsibility for the archival and manage ment of all NASA Earth science mission data products prior to EOS as well as data from NASA instruments flown on foreign satellites. The NASA Earth Science Enterprise is responsible for assuring the long-term permanent preservation of these data and has negotiated agreements with the opera tional agencies (NOAA and USGS)
|
From page 125... ...
An additional contribution supported by the EOSDIS is the number of Pathfinder climate data studies from similar or nearly identical instruments flown since the inception of high-resolution satellite remote sensing in the early 1970s on multiple spacecraft from operational and research satellites, some spanning decades. The lessons learned provided by the EOSDIS itself as well as through the experience gained by supporting science instrument processing teams, the core DAAC processing capabilities, and the Earth science information partner processing capabilities afford ample examples to evaluate the advantages of and drawbacks to producing various datasets that should prove useful in the design of the NPOESS/NPP operational EDRs and CDRs.
|
From page 126... ...
The development of the EOS Clearing House with open applications programmer interfaces enables development of user interfaces tailored to specific communities; for example, MODIS provides L1 process ing source code to direct broadcast users and have an open source code policy with respect to science algorithms. There has not yet been much demand for such software other than for direct broadcast stations.
|
From page 127... ...
If anything, the functionality has expanded to support a much larger community than originally envisaged. In fact, a community of EOS partners has been established by NASA's Earth Science Enterprise to participate in broadening the EOSDIS in many different ways: data and portal providers; algorithm product processors and producers; data services and distribution nodes to research and educational users; value added providers; international and interagency centers; and low cost direct broadcast reception to universities, state and local agencies, and commercial organizations.
|
From page 128... ...
As a result various stakeholders found themselves engaged in conflict over priorities and requirements, with no realistic mechanism to reach closure between information technology sys tem development teams, the science instrument teams, and external science communities. New systems must allow users to gain ownership of require ments through sponsored workshops to reach community consensus, and initiating processes to enable users to prioritize requirements allowed stake holders to feel more comfortable with the direction the system and project were taking.
|
From page 129... ...
, SeaWiFS processing system adapted to MODIS and the Ozone Monitoring Instrument Science Investigation Processing System, GSFC DAAC-developed Version 0 systems reused in Aura SIPSs at the Jet Propulsion Laboratory. This was enabled by the maturation of a stable, base-lined ECS and the implementation and publication of standard interfaces to its components.
|
Key Terms
This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More
information on Chapter Skim is available.