NASA Support for WTF-CEOP Sept 11, 2006 Ken McDonald, NASA Yonsook Enloe, SGT Inc.

1. NASA Support for WTF-CEOP Sept 11, 2006 Ken McDonald, NASA Yonsook Enloe, SGT Inc.

2. CEOP Satellite Data Server • CEOP science community is using the OPeNDAP enabled clients and servers to analyze the field data and model data • CEOP science community had difficulty using satellite data because of the lack of tools • NASA’s Satellite Data Server prototype was developed that demonstrated OPeNDAP client (Grads) access to the WCS server capabilities. • Prototype was demonstrated at CEOP Implementation Planning meeting and previous WGISS meetings.

3. Grads Client Other OPeNDAP Clients OPeNDAP Request Translator Default georectification CF Attrubute Constrtuction Custom Requests (future) Grads-DODS Server (GDS) Field Data Model Output Satellite Data Server WCS Client NWGISS WCS Standard Functions e.g. subsetting Standard Functions e.g. subsetting Custom Functions (Grads) Satellite Data, Swath and Grid

4. Integration of Satellite and Model Data

5. Continuing Support • Using the prototype as a basis, the NASA team (McDonald/GSFC, Di/GMU, Enloe/SGT, Holloway/OPeNDAP) proposed to NASA’s Advancing Collaborative Connections for Earth-Sun System Science (ACCESS) Program. • NASA team awarded 2 year ACCESS funding to develop the Satellite Data Server with an optional 3rd year. • A second proposal to develop a gateway that would make OPeNDAP servers accessible to OGC clients was partially supported and merged with this effort - added two additional team members (Domenico/Unidata, Rutledge/NOAA-NCDC).

6. Status and Plans • Held kick-off meeting with combined team in March • Finalized work plan for both gateways • Satellite Data Server will be developed as proposed, allowing the CEOP scientists to inter-compare satellite data with model output data and field data • Plan to deploy the Satellite Data Server at JAXA and other sites with satellite data of interest to the CEOP community • OGC/Geoscience Gateway will focus on catalog services - WCS access will be addressed with 3rd year funding • Paper describing the Satellite Data Server and the OGC/Geoscience Gateway presented at the IGARSS 06 conference. • First phase (very basic) implementation will be completed in May 2007.

7. OPeNDAP & ECHO • OPeNDAP and ECHO team worked together to provide direct search and access to ECHO via OPeNDAP enabled clients (e.g. Matlab) using ECHO’s web services. Demo following. • ECHO search query implemented as an ECHO web service, using ECHO’s 8.0 web service APIs. • OPeNDAP Group developed a stand alone Java client to invoke the ECHO search query via a query service. This stand alone client can be invoked by matlab and other OPeNDAP enabled clients. • Michael Burnett will demonstrate this in this session.

8. JAXA/NASA Meeting Results • NASA and JAXA teams met Sept 7-8 to discuss WTF-CEOP activities • Each team presented information about future plans for the 2 prototypes • ECHO team gave an extensive briefing on metadata ingest, client development, and extended services. • NASA team gave an overview of the different types of WCS servers available. • Potential for JAXA system to access NASA satellite data through the WCS to get the data transforming capabilities • Discussed the need to improve data discovery of CEOP data • NASA and JAXA teams will work together to support multiple GEO tasks with both prototypes • The CEOP Satellite Data Server and ECHO can be contributions for selected GEO tasks identified by Satoko earlier.

9. Issues for CEOP Science • Identify data sources of interest for data discovery/search (Max Planck, UCAR, University of Tokyo, JAXA, NASA, Eumetsat, ESA, NOMADS, .....) • Discuss the CEOP data policy issues for broader data discovery – how to get online access to the CEOIP data sources; any special permissions or agreements needed? • Identify data type – product and geophysical parameter names – have this info from Prof Koike already (list of satellite products he sent out last year) but the list of NASA satellite products do not have the geophysical parameters listed like those of the ESA products • JAXA team will ask CEOP scientists what addition LAS system functions they would like to have implemented in the JAXA prototype

10. Need Future International Participation • Do you have satellite data of interest to the CEOP science community? • Select and install a WCS Server suited to your satellite data. • Install a CEOP Satellite Data Server to provide an OPeNDAP gateway to the WCS served satellite data • CEOP Satellite Data Server expected to be ready for external installation in 2008.

11. Known WCS Servers and Clients • There are many WCS servers and client software available, from both commercial software vendors and research organizations. • Many implementations are unknown because there is no requirement to register your products at a center location. • Known commercial products • Carbon Tools --- ??? – WCS 1.0 client • Compusult Limited – Service Manager 3.0 –WCS 0.7 Server • ESRI -- ??? – WCS 1.0 client • Generalitat Valenciana--gvSIG 0.6 –WCS 1.0 Client • Ionic • RedSpider ImageArchive 3.0.1 – WCS 0.7 & WCS 1.0 Server and Client • RedSpider Enterprise 3.4 - WCS 1.0 client • RedSpider Web 3.3 - WCS 1.0 server and client • MiraMon--MiraMon Map Server 5.0-WCS 0.7 server and client • Known research products • GMU – NWGISS – WCS 0.7 and 1.0 server and client • Unidata – Unidata server – WCS 1.0 server • DLR – WCS 0.7 • UK Space Agency • U. of Florence • Washington University – WCS 1.0 • Columbia University

12. GMU NWGISS WCS Server • Support WCS 1.0 • The formats the server can ingest at the back-end • HDF-EOS (both swath and grid) • Format converters are available to convert GeoTiFF and netCDF files to HDF-EOS • A test version of the server can work directly with netCDF and GeoTiFF files. • Potential satellite data that can be served • All satellite data in HDF-EOS, GeoTIFF, (and potentially netCDF-CF) can be served. • CRS • All CRSs in GCTP are supported in both input data and output data. • Provide automatic CRS conversion – not completely tested. • Provide automatic georectification to swath data. • Coverage output formats • Operational version support HDF-EOS, GeoTiFF, NITF, and plain Binary. • A GALEON test version also support netCDF-CF. • A test version supports all formats (about 40) in GDAL library. • Binary of the software is for free download • Installation at GMU sites provide access to all EOS data in data pools as well as 17 TB of Landsat data.

13. Unidata WCS Server • Support WCS 1.0 • The formats the server can ingest at the back-end • netCDF-CF. • Potential satellite data that can be served • All satellite data in netCDF-CF can be served. • The server currently serves mostly the weather data • CRS • The output is in the same CRS as in the input files at the back-end. • Not CRS conversion between input and output. • Coverage output formats • netCDF-CF. • Binary of the software is available per request.

14. WCS Installations • GMU GeoBrain WCS server – NASA EOS satellite data, Landsat. • Raytheon WCS server – developed by Ionic- Sample EOS data. • NASA data pools – Ionic server – Experimental server, not open to outside. • SPOT – Ionic server – sample SPOT image. • Zhejiang University – GMU WCS server – near real time MODIS data. • Unidata – Surface meteorological data. • Washington University – Surface air quality data (in GML). • Columbia University – socio-economic data • University College London/UK space agency – Landsat data. • DLR – some samples of satellite data

15. OPeNDAP Demo