1
ECHO and EDGStatus
May 9, 2006
Beth Weinstein, Beth.Weinstein@nasa.gov
Yonsook Enloe, yonsook@mindspring.com
2
Modeling,
Applications,
Decision Support
Systems
Collection
& Granule
Catalog
BrowseImages
What is ECHO?
ECHO is middleware between Data, Service, and Client Partners
•Data Partners provide information about their Earth science-related data holdings
•Client Partners develop software (“clients”) to access ECHO’smetadata using ECHO’s open APIs
End users search ECHO's metadata using an ECHO client; ECHOis not a user interface
ECHO
Extended
WebServices
Data
Partner
APIs
Client
Partner
APIs
Machine – to –
Machine
Tailored
Graphical UserInterfaces
Client Partners
Data Partners
End User
Other Data
Partners
NASA
DAACs
3
ECHO Capability Today
User Registration and Login
Metadata ingest, validation, and reconciliation
Search Parameters
•Spatial (e.g. point, line, polygon, multipolygon, circle)
•Temporal (e.g. date range, day/night/both)
•Keyword (e.g. dataset id, sensor name)
•Numeric (e.g. cloud cover percentage )
•Boolean (e.g. Only data with browse data, Only data that is online)
Open interfaces for human-machine or machine-to-machine clients
Data Access
•Direct On-line Access
•Brokering of Orders
•Price Quotes
•Subscriptions
Interoperability with other systems (OGC/NSDI Client support)
Service Catalog based on web services standards
4
ECHO Data Partner Status
ECHO’s Current Holdings (May 2006) from 10 Data Partners
•Collections2,237
•Granules56 million
•Browse14 million
All NASA ECS DAACs are actively participating in ECHO (GES, LARC,LP, NSIDC)
•Atmospheric Composition and Dynamics, Global Precipitation, OceanBiology, Ocean Dynamics, Solar Irradiance
•Radiation Budget, Clouds, Aerosols and Tropospheric Chemistry
•Land Processes
•Snow and Ice, Cryosphere and Climate
V0 DAACs are participating (ASF, GES, JPL, ORNL, SEDAC, PO)
•Synthetic Aperture Radar (SAR), Sea Ice, Polar Processes, Geophysics
•Biogeochemical Dynamics, Ecological Data, Environmental Processes
•Oceanic Processes, Air-Sea Interactions
•Population, Sustainability
MODIS Data Processing System (MODAPS) and JAXA CEOP are in testmode
5
ECHO Client Partner Status
Current ECHO Clients
•General purpose geospatial and temporalsearching
•Customized user interfaces to facilitatespecific communities and tasks
•Back-end harvesting tools to support client-side caching of key information
•Additional value-added processing by clients(e.g. subset, resample, reproject, reformat)
Client Partner: 17
•Operational2
•In evaluation or test7
•Active development3
•Planning/requirements3
•Proposed 2
6
EDG Transition to ECHO’s WIST Client
Warehouse Inventory Search Tool (WIST)
•ECHO client being developed by NASA ESDIS
•General search and order interface
•Will offer all EDG functionality
•Public access to current ECHO operational version
WIST is expected to be fully operational for EOSdatasets by 2Q 2007
ECHO must meet criteria (e.g. search performance,available, up-to-date metadata) before EDG is turnedoff
U.S. EDG clients and servers will continue to operateuntil the GSFC EDG is turned off
7
ECHO Schedule
ECHO 7.0 operational
•Browse Data Insert, Update, and Deletes
•Multiple Collections and Groups for Access Control Rules
•Spatial Query Based on Lat/Lon Point
Mar 2006
ECHO 8.0 operational
•Web Services API
•Asynchronous Queries
4Q 2006
WIST operational
2Q 2007
ECHO 9.0 operational
•Improved performance
•More Comprehensive Error Handling
•Enhanced Security
•Metrics
2Q 2007
ECHO 10.0 operational
•EOSDIS Evolution Items
4Q 2007
8
Why Use ECHO?
Open system provides Earth science data and services to large,diverse pool of users enabling scientific community interaction andcollaboration
Control in the hands of the data partner
•Automate mapping between your metadata and ECHO catalogmetadata
•Control visibility and access to your contributed resources
•Select the best spatial search approach for your data
•Check the history of orders and provide status on open orders
Users search for collection and inventory-level data
•Search and order data through a customized user interface
•Directly access online data and/or order data on media
ECHO offers high system availability
•99% system availability
•Even if your system is down, ECHO users can still search yourmetadata
9
International Activities of Interest
CEOP (Coordinated Enhanced Observing Period) program
•Plans to use ECHO and OPeNDAP enabled clients and servers
•Satellite data used by CEOP will be represented in ECHO
JAXA is currently evaluating ECHO through its CEOP activity
Israel Space Agency would like to become an ECHO Data Partner
Dundee (Scotland) and the IRE RAS (Russia) considering becomingECHO Data Partners
Studying interoperability with ESA and other internationalpartners
10
ECHO/OPeNDAP Activities
CEOP program will ingest metadata from satellite dataof interest into ECHO. The satellite data is fromJAXA, NASA, ESA, and Eumetsat
WTF-CEOP developing extensions to OPeNDAP basedtools to provide access to satellite data to the CEOPscience community
Direct search and access of ECHO through the webservice APIs by OPeNDAP clients – prototype Matlabclient will be demoed in July 2006 with operationalcapability expected when ECHO 8.0 is operational
11
ECHO and IDN
GCMD and ECHO are working together to shareinformation from its registries and give users a moreunified experience when interacting with the twosystems
GCMD Portal to ECHO data operational in 2Q 2007
12
ECHO Project Website
Contact information andmailing lists
Information on how to getstarted as an ECHO Data,Client, or Service Partner
Reference materials and tools
System access information
Real-time systems status
Operations metrics updatedweekly
Info on various ECHOcommunity meetings
13
ECHO Contact Information
ECHO International contact
Contact ECHO Operations (Ops)
•+1 301 867-2071 (Weekdays, 08:00–19:00 ET)
Visit the ECHO Project Website
Schedule bi-lateral telecons to discuss potentialcollaboration!
15
ECHO Mission/Vision Statement
ECHO Mission
•ECHO’s mission is to enable a global marketplace of EarthObservation resources that will make Earth Observation datautilization more efficient and will spark innovation. ECHOprovides Earth Observation communities with the ability topublish, discover, access and integrate directory and inventorylevel data and services through community-developed userinterfaces.
ECHO Vision
•ECHO will…
•be highly recognized, trusted and valued by the Earth Observationcommunity
•be a critical building block in distributed information, modeling,decision support and public access systems
•have a low cost of participation to encourage broad communityinvolvement
16
Technologies and Standards used by ECHO
Technologies
•J2EE- Java 2 Enterprise Edition
•Provides a scalable (in terms of simultaneous accesses) application server which hosts ourbusiness logic
•Oracle 9i
•Provides a highly tunable relational database engine with spatial search capabilities
•XML
•Provides a cross-platform, cross-language basis for interacting with ECHO
•A layered, compartmentalized architecture is used to allow for updates withminimal impact to the other components of the system, including replacing thedata model
Standards
•Basic Profile Compliant Web Services
•Provides a cross-platform, cross-language basis for requesting ECHO to perform certainfunctions on the behalf of a client user, or for ECHO to request functions of a provider
•OGC Catalog Service Specification
•ECHO’s current API is based on this spec, and an adapter has been built to offer truestandards compliance
•The layered architecture includes a place for protocol adapters, order adaptersand ingest adapters that accommodate the differences among participatingsystems, minimizing the impact on those existing systems
17
ECHO Background – How did we get here?
ECHO initiated as an enhancement to EOSDIS in response to:
•User feedback on complexity and limitations of the “system-wide”view of EOSDIS data provided by EOS Data Gateway (EDG).
•Belief that the community could and would develop better clientcapabilities tailored to their needs.
•Evolving NASA Earth science vision of multiple, distributed,heterogeneous data and service providers.
•Availability of emerging technologies (e.g. web services).
Response was development of ECHO as enabling infrastructure.
•“Externalized” metadata and made it accessible via APIs thatsupported development of custom clients.
•Extensible architecture that allows standard client and providerinterfaces to be added.
•Support for data services.
Centralized “clearinghouse” model based on industry feedback.
•Driven by performance and availability requirements.
18
SUPPORTING A COLLABORATIVE EARTH SCIENCE COMMUNITY WITH INFRASTRUCTURE SERVICES
Publishing Resources: Making them available for the Earth Science Community
Discovery of Resources: Finding resources that meet science needs
Consuming Resources: Accessing and using valuable resources, individually or in combination, to meet science needs
21
EOSDIS Today
EOSDIS provides
•A production capability for standard science data products from EOS instruments
•An “active archive” of Earth science data from EOS and other past and presentmissions
•A distributed information framework (data centers, SIPS, networks,interoperability, other system elements) with partners supporting EOSinvestigators and other users in science, government, industry, education, andpolicy
22
As middleware for a service-oriented enterprise, ECHO offersentrée to its capabilities through a set of publicly availableApplication Program Interfaces (APIs) (see Figure 1).
These ECHO APIs are based on industry standards for performingweb-based computing, specifically web services profile. Theseservice interfaces are defined in the Web Services DefinitionLanguage (WSDL) and are accessible through Simple Object AccessProtocol (SOAP).
Using these standards, clients written in most contemporaryprogramming languages are isolated from the underlying technologiesthat support the distributed communication and functionality. Theseclients may call the ECHO web services much like a local functioncall. Most current developer tools support these standardtechnologies (e.g. WSDL, SOAP) natively. More information aboutECHO, including a user’s guide and the API specification is availableat http://eos.nasa.gov/echo.