[Action Item: Build TIE Status Diagram]

At the meetings in ESRIN we struggled a little in terms of building a diagram. I think it may make sense to start with a table, figure out what we're really trying to do, and then we can build a diagram.

This table can help us with the following question: Given a list of data sets deemed necessary for a WTF-GOFC demo, which ones can be found in a directory level search, which inventory are they found in, which, if any WMS, WFS, and WCS are they available in.

For a given data set, there may be more than one WMS/WFS/WCS provider or instance. We can add additional sub-tables in any given cell in order to handle that.

Please send your comments and entries for this table to either Allan Doyle or to the WTF-GOFC TT mailing list.

Items in bold are from the January, 2001 list made by Dave Skole and Chris Justice as captured by Yonsook Enloe. The blue headings are also from that list.

Here's the list we're starting from (minus some Word formatting)

D,L. Skole

Forest Cover and Characteristics Implementation Team Leader

The WGISS-GOFC Testbed Facility has an important role to play in the development of prototype information systems and services supporting the needs of the GOFC Forest Cover IT. As these prototype efforts make progress, demonstrating current progress at various venues is appropriate, as long as these demonstrations reflect an on-going process of prototype development directly relevant to the needs of GOFC. The design and focus for technology development should be guided by the science and user requirements of GOFC. In previous meetings these science drivers have been laid out, and can also be found in the design specification documents for GOFC (at the GOFC web site) as well as in various published papers provided to the WTF participants previously.

This document outlines a general approach for the next phase of WGISS-GOFC prototype development; it builds extensively on previous discussions and results from the first demonstration effort in Bangkok.

Component 1: catalog and services directory. Develop a common portal for pointing users to access points for GOFC information, including raw data products (e.g. Landsat 7 data), derived products, information about the program, published papers and documents. This need only be a very well design web site. It should provide links query and browse services, features servers, and other reference and data search tools (e.g. GCMD).

Component 2: archive and database access and deliver,. The current systems operated by space agencies are stove-piped and not well connected. Moreover, search and retrieval of data and products should have interoperable GIS functions such as feature or map servers. Initial access include: L7, MODIS, VGT, GLI, ERS, ATSR, JERS, Radarsat through existing demos, but open -- provision of specific data bundles, services for registration, atmos. correction, etc. This component allows a user have one-stop shopping and overlay data or products on top of maps using a distributed system of servers.

Component 3: distributed network of nodes at GOFC partner and user sites. Extend the network of sites far beyond nodes and servers at CEOS partners to include GOFC partners in the regional networks. This will involve working through the GOFC network to link systems and services developed by the GOFC partners to those in the space agencies. This would, for example, include installation of feature servers and software at specific locations one (or more at a later time) of the GOFC regional networks where GOFC partners are producing or using data products

Component 4 (optional) Acquisition models and mission planning tools on-line . Provide useful tools for GOFC product producers and data users to plan missions and observation schedules and targets. For example special tools for dedicated missions or GOFC users, such as global change science campaigns or international programs (e.g. of the latter include FAO FRA, and MA).

Component 5: Multi-node integration of data and products. This would provide capabilities to integrate a series of independent products into a larger synthetic product using distributed feature servers. For example merging of national Forest Inventory map datasets on Forest cover and changes into a harmonized dataset on-the-fly. It would also provide capabilities for cross-node interrogation and analysis, such as uploading data from one server to another.

Component 6: Cross-Product/Cross-IT integration and visualization. Provide capabilities for user sot cross integrate products from each of the ITs. For example cross-mapping of fires on logging sites to first visualize the spatial coincidence of these disturbances, then having capabilities to perform analyses using each layer as "independent variables" for derived output product.

Example Scenario for a WGISS-TF GOFC Fire Demonstration

Chris Justice

Preamble
Text/Graphic - Intro to WGISS - TF /GOFC
Goal: Improving access to and use of data to meet GOFC objectives

Text/Graphic GOFC- Fire Regional Needs (NRM and GC research)
The GC research issues
The NRM issues

Text/Graphic - The Data System Services Needed
Data Portals tailored to user groups
Distributed databases serving multiple fire related satellite data sets
Merging observations and geographic data from multiple sources and locations
Delivery of on-line internet provided data to users desktop for analysis
Timely delivery (but not for designed yet for fire fighting)

A. Regional Scale
1. Text/Graphic Fire susceptibility and risk
Data set - ENSO - NOAA - long lead forecast (TBD)
Data set - AVHRR Fire Risk Product - ANDES (see below)
2. Location and timing of fires
Text/Graphic Diurnal cycle of activity - TRMM and the Multi-source rationale
Live Demo Data sets - Regional fire distribution - merged MODIS (GSFC)/ ATSR (ESRIN)/ AVHRR (WFW)/ DMSP (NGDC) /TRMM (GSFC) fire data
(Depending on how the data are used in the region - there could be a rapid fire management Graphic here - but this is not the focus of GOFC)
Data set - active fires (U. Hawaii)
3. Geographic context (fires superimposed on land cover and GIS layers)
Live Demo Data sets - SEARIN regional/national land cover
4. Smoke / Haze / Emissions
Text / Graphic Radiative forcing / human health (TBD)
Data set - TOMS or MODIS Aerosols Time series - NASA/GSFC (TBD)
Data set - SeaWiFS Smoke (TBD)
Data set - CO movie loop from MOPPIT (TBD)
B. National/Local
5. Text/Graphic Post-fire Assessment (this could be Thailand but should be discussed)
Burned extent - Landsat (TRFIC)
Function - Graphic Search of Availability
Data set - Landsat Products (TRFIC)
Data set - Spot data (CRISP) (see below)
Data set - MODIS 250m (TBD)
Data set- ASTER (TBD)
Function- Overlay Fire Locations
6. Text/Graphic Fire as proximate cause of land use change
Data set - SEARIN Local GIS Overlay
Date set - Landsat Time Sequence

(I consider the parts in bold to be critical elements of the Demo and for that reason I have tasked my lab, as our contribution to work to develop a capability to make this happen - the parts that are not in bold I am hoping that others will contribute). I will also help with the MODIS 250m as the distribution system matures.

GOFC Fire Implementation Team Leader Contribution to the Demo
The Southeast Asia GOFC Regional Information System for Fire (SEAGRIF) project will have the following implementation steps:

1) Ordering and configuring node servers

This work will be coordinated and implemented in part by the GOFC-Fire Implementation Team Leader. This step will involve configuration and testing of selected systems for distribution to node sites using readily-available off the shelf software for data management and feature serving.

2) Site Installation and Integration Visits
--DMSP Fire Locations: POC Chris Elvidge, NOAA National Geophysical Data Center in Boulder, CO USA
--ATSR Fire Locations: POC Ivan Petitville, Christophe Caspar, ESA ESRIN in Frascati, Italy
--TRMM Fire Locations: POC Louis Giglio, MODIS Land Discipline Group in Greenbelt, MD
--MODIS Fire Locations: POC Christopher Justice, MODIS Land Discipline Group in Greenbelt, MD
--Regional Fire Client, GIS Layer Serving: POC: Dr. Chaowit Silapathong, Geo-informatics and Space Technology Development Agency, Thailand
--Regional Fire Client, GIS Layer Serving: POC: Dr. Iwan Gunawan, Agency of the Assessment and Application of Technology, Indonesia
--Regional Fire Client, GIS Layer Serving: POC: Ms. Mastura Mahmud, Universiti Kebangsaan Malaysia, Malaysia