Developing

Overview

Service Categories

ECHO Service Partner can register the following web services with the ECHO system:

• Web Service GUI
• The location of a remote user interface.
• Associated with implementations and interfaces registered in ECHO.
• Examples:
  • WIST Search Tool
  • Domain Specific User Client for subsetting
• Advertisement
• Advertisement for other data services, not specifically "Web Services".
• Example:
  • Service for expert advice on a specific application area
  • Ability to drop sensors in the Chesapeake Bay
• Interface
• An interface to a web service (WSDL) but not an actual endpoint to implementing the web service.
• Hosted within the ECHO system to encourage standardization and reuse between ECHO partners.
• Examples:
  • Common Subsetting interface.
  • Common Access service interface (OPeNDAP)
  • WMS service
• Implementation
• An executable web service implementing interfaces registered in or outside of ECHO.
• Hosted outside the ECHO system by an ECHO Service Partner.
• Examples:
  • An application-specific service (OPeNDAP Query adapter).
  • Specific WMS server

See the Extended Services Presentation PPT (1.5 MB).

Partners may interact with ECHO through the standard ECHO Web Service API. This method will be most practical for partners who wish to write their own client software applications which interact with ECHO.

Example WSDL Files

The "MODISLevel2BrowseService-interface" file provides an example of a standard WSDL service interface definition for a MODIS Level-2 browse service:

• MODISLevel2BrowseService-interface.wsdl - .wsdl (2 KB)

The "MODISLevel2BrowseService" file provides an example of an implementation of a MODIS Level-2 browse service:

• MODISLevel2BrowseService.wsdl - .wsdl (2 KB)

Service Partners