ECHO by ajizai


									                 ECHO and EDG

                                 May 9, 2006
Beth Weinstein,
Yonsook Enloe,          1
           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’s
       metadata using ECHO’s open APIs
    End users search ECHO's metadata using an ECHO client; ECHO
    is not a user interface
               Client Partners      ECHO                   Data Partners
                                    & Granule
              Graphical User
                Interfaces           Catalog
                                     Browse       Data
             Machine – to –          Images      Partner
End User        Machine

                                                            Other Data
                Modeling,           Extended                 Partners
              Applications,           Web
             Decision Support       Services
                 Systems                                                   2
     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

    ECHO Data Partner Status

ECHO’s Current Holdings (May 2006) from 10 Data Partners
 • Collections         2,237
 • Granules            56 million
 • Browse              14 million
All NASA ECS DAACs are actively participating in ECHO (GES, LARC,
 • Atmospheric Composition and Dynamics, Global Precipitation, Ocean
    Biology, 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 test

     ECHO Client Partner Status

Current ECHO Clients
 • General purpose geospatial and temporal
 • Customized user interfaces to facilitate
    specific 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
 • Operational                   2
 • In evaluation or test         7
 • Active development            3
 • Planning/requirements         3
 • Proposed                      2

   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 EOS
datasets by 2Q 2007
ECHO must meet criteria (e.g. search performance,
available, up-to-date metadata) before EDG is turned
U.S. EDG clients and servers will continue to operate
until the GSFC EDG is turned off

      ECHO Schedule

ECHO 7.0 operational                                           Mar 2006
   •Browse Data Insert, Update, and Deletes
   •Multiple Collections and Groups for Access Control Rules
   •Spatial Query Based on Lat/Lon Point
ECHO 8.0 operational                                           4Q 2006
   •Web Services API
   •Asynchronous Queries
WIST operational                                               2Q 2007
ECHO 9.0 operational                                           2Q 2007
   •Improved performance
   •More Comprehensive Error Handling
   •Enhanced Security
ECHO 10.0 operational                                          4Q 2007
   •EOSDIS Evolution Items

    Why Use ECHO?

Open system provides Earth science data and services to large,
diverse pool of users enabling scientific community interaction and
Control in the hands of the data partner
 • Automate mapping between your metadata and ECHO catalog
 • 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 your

    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 becoming
ECHO Data Partners
Studying interoperability with ESA and other international

   ECHO/OPeNDAP Activities

CEOP program will ingest metadata from satellite data
of interest into ECHO. The satellite data is from
JAXA, NASA, ESA, and Eumetsat
WTF-CEOP developing extensions to OPeNDAP based
tools to provide access to satellite data to the CEOP
science community
Direct search and access of ECHO through the web
service APIs by OPeNDAP clients – prototype Matlab
client will be demoed in July 2006 with operational
capability expected when ECHO 8.0 is operational

   ECHO and IDN

GCMD and ECHO are working together to share
information from its registries and give users a more
unified experience when interacting with the two
GCMD Portal to ECHO data operational in 2Q 2007

    ECHO Project Website

Contact information and
mailing lists
Information on how to get
started as an ECHO Data,
Client, or Service Partner
Reference materials and tools
System access information
Real-time systems status
Operations metrics updated
Info on various ECHO
community meetings

   ECHO Contact Information

ECHO International contact
 • Yonsook Enloe (
Contact ECHO Operations (Ops)
 • +1 301 867-2071 (Weekdays, 08:00–19:00 ET)
Visit the ECHO Project Website
Join ECHO Mailing List:
Schedule bi-lateral telecons to discuss potential

Backup Slides

    ECHO Mission/Vision Statement

ECHO Mission
 • ECHO’s mission is to enable a global marketplace of Earth
   Observation resources that will make Earth Observation data
   utilization more efficient and will spark innovation. ECHO
   provides Earth Observation communities with the ability to
   publish, discover, access and integrate directory and inventory
   level data and services through community-developed user
ECHO Vision
 • ECHO will…
   • be highly recognized, trusted and valued by the Earth Observation
   • be a critical building block in distributed information, modeling,
     decision support and public access systems
   • have a low cost of participation to encourage broad community

     Technologies and Standards used by ECHO

 • J2EE- Java 2 Enterprise Edition
    • Provides a scalable (in terms of simultaneous accesses) application server which hosts our
      business 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 with
   minimal impact to the other components of the system, including replacing the
   data model
 • Basic Profile Compliant Web Services
    • Provides a cross-platform, cross-language basis for requesting ECHO to perform certain
      functions 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 true
      standards compliance
 • The layered architecture includes a place for protocol adapters, order adapters
   and ingest adapters that accommodate the differences among participating
   systems, minimizing the impact on those existing systems

    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 client
     capabilities 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 that
   supported development of custom clients.
 • Extensible architecture that allows standard client and provider
   interfaces to be added.
 • Support for data services.
Centralized “clearinghouse” model based on industry feedback.
 • Driven by performance and availability requirements.

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
                 EOSDIS Context Diagram

                                    Flight Operations,                    Science Data                     Distribution,
                                    Data Capture,         Data            Processing,                      Access,
                                    Initial Processing,                   Info Mgmt, Data                  Interoperability,
             Data Acquisition       Backup Archive                         Archive, & Distribution         Reuse
                                                          to DAACS/SIPS


   EOS             Tracking                                                                                                        ESIP
Spacecraft          & Data                                                                                                         2/3’s
                Relay Satellite
                                                                          Distributed                                            Research

                                        Data                                Active                        Internet                Users

                                     Processing                            Archive                     (Search,order
                                         &                                 Centers                      distribution)           Education
                      White Sands     Mission
                                       Control                                                             Media
                        (WSC)                                                                           (Distribution)            Public


                                                                            Teams and                                     Int’l Partners
                                                                                                                         & Data Centers
                     EOS Polar Ground Stations                                SIPSs                     Data

EOS Missions/Instruments

              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 present
   • A distributed information framework (data centers, SIPS, networks,
     interoperability, other system elements) with partners supporting EOS
     investigators and other users in science, government, industry, education, and
  E S D IS F u n d e d E n t it ie s                                                 No.
DAACs                                                                                    8                                      P a r t n e r s h ip s          No.
S IP S s                                                                        9 of 13                                   U .S .                                 8
                                                                                                                          In te r n a tio n a l                 13

                                                                                              E O S D IS
          E O S D IS O v e r a ll M e t r ic s ( F Y 2 0 0 4 )
                                                                                             S y s te m s
                                                                                                                            M is s io n s                       No.
S y s te m In te r f a c e C o n tr o l D o c u m e n ts ( IC D s )                               58
U n iq u e D a ta P r o d u c ts                                                                3 ,9 1 1       S c ie n c e D a ta P r o c e s s in g           11
D is tin c t u s e r s a c c e s s in g D A A C s                                            2 ,0 8 5 ,5 9 7   A r c h iv in g a n d D is tr ib u tio n         28
D is tin c t u s e r s o b ta in in g d a ta f r o m D A A C s                                2 0 2 ,8 1 5     In s tr u m e n ts s u p p o r te d              65

                                                                                                                      ECS              V 0 , T S S , L a T IS
                                             E O S D IS S y s t e m s M e t r ic s ( F Y 2 0 0 4 )
                                                                                                                    S y s te m              S ys te m s
                            D a ily In g e s t V o lu m e ( L e v e l 0 )                                           341 G B             8 3 G B ( e s t.)
                            D a ily A r c h iv e G r o w th                                                         4 .0 2 T B              0 .1 7 T B
                            E n d U s e r D a ily D is tr ib u tio n V o lu m e                                     1 .5 6 T B              0 .3 0 T B
                            E n d U s e r D is tr ib u tio n P r o d u c ts                                          1 1 .4 M                2 2 .7 M
                            T o ta l A r c h iv e V o lu m e a t e n d F Y 0 4 ( L 0 - L 4 )                        3 .2 5 P B              702 TB
                            T o ta l A r c h iv e P r o d u c ts a t e n d F Y 0 4 ( L 0 - L 4 )                      53 M              N o t a v a ila b le
                            F ile n a m e : E O S D IS _ T o d a y _ 1 2 2 8 2 0 0 4 .x ls
As middleware for a service-oriented enterprise, ECHO offers
entrée to its capabilities through a set of publicly available
Application Program Interfaces (APIs) (see Figure 1).
These ECHO APIs are based on industry standards for performing
web-based computing, specifically web services profile. These
service interfaces are defined in the Web Services Definition
Language (WSDL) and are accessible through Simple Object Access
Protocol (SOAP).
Using these standards, clients written in most contemporary
programming languages are isolated from the underlying technologies
that support the distributed communication and functionality. These
clients may call the ECHO web services much like a local function
call. Most current developer tools support these standard
technologies (e.g. WSDL, SOAP) natively. More information about
ECHO, including a user’s guide and the API specification is available


To top