u.s. department of the interior u.s. geological survey web services interest group wgiss #28...
TRANSCRIPT
U.S. Department of the Interior
U.S. Geological Survey
Web Services Interest Group Web Services Interest Group
WGISS #28September, 2009 Pretoria, South Africa
Lyndon R. OlesonU.S. Geological SurveyEarth Resources Observation and Science (EROS) CenterSioux Falls, SD, USA
2
Web Services Interest GroupWeb Services Interest Group
Agenda
11:00 – 11:15 Web Services IG Status and Overview Lyn Oleson
11:15 – 11:30 Polar Mapping Update and WMS Experience Shinobu Kawahito
11:30 – 12:00 Web Services Technologies for GEO Group
12:00 – 12:15 WGISS Findings – Lessons Learned, Group Best Practices, links to relevant files/web sites
12:15 – 12:20 Future meetings and workshops Group
12:20 - 12:30 Recommendations to WGISS Lyn Oleson
3
Web Services Interest GroupWeb Services Interest Group
Web Services Interest Group Status and Overview Purpose of WSIG: Serve as a forum for exchange of
technical information and lessons-learned experience about Web services and other WWW / Internet related software technologies.
In order to facilitate construction of interoperable service infrastructures, the Interest Group closely observes and interacts with OGC and ISO standardization activities and OGC testbeds (e.g. WCS, CS-W, and WMS) and makes the results available to WGISS and Projects.
Goal: How can we employ SOA and particularly standard Web Services interfaces (e.g. OGC) to enable or enhance information systems interoperability.
Following topics will explore lessons learned to date and ideas for continuing to move forward toward our goal.
4
Web Services Interest GroupWeb Services Interest Group
What is the goal we are pursuing? Allow an EO client to search and obtain data from multiple
agency information systems via a “standard” Web Service interface.
Allow an agency data provider to have many compliant clients from various user communities (e.g. GEO societal benefit communities, various earth science communities, various emergency disaster communities) search and obtain their EO data via a “standard” Web Service interface.
Why employ Web Services?
5
Web Services Interest GroupWeb Services Interest Group
Background: At WGISS 27 in Toulouse
Focused on lessons learned from attempting to employ OGC WCS and CSW specifications.
Many found it difficult to accomplish EO satellite data searches and downloads through the existing OGC specifications.
Concluded that a better strategy might be to identify our own requirements and possibly pursue our own Web Services specifications modeling after the OGC specs in order to achieve our goal if not also contribute to enhancing OGC.
6
Why Employ Web Services?Why Employ Web Services?
Data and Information
Common Service Interface
Client
Server
7
Why Employ Web Services?Why Employ Web Services?
Data and Information
Common Service Interface
Client
Server
Data and Information
Common Service Interface
Data and Information
Common Service Interface
8
Why Employ Web Services?Why Employ Web Services?
Data and Information
Common Service Interface
Client
Server
9
Web Services Interest GroupWeb Services Interest Group
Data and Information
EO Client
EO Agency Servers
Data and Information
Common Service Interface
Data and Information
Can we formulate a technical strategy/proposal?
Common Service Interface
Common Service Interface
10
Vision for EO Clients/Servers Vision for EO Clients/Servers
Inventory
“Standard” Service
Interfaces
Catalog
SearchesTypical EO
“Client”
An Agency Set of EO Servers
CWS
Browse Images
View
Browse
WMS
Online Data
Direct Data
Download
WCS
?
Registration, Shopping Basket, On-demand
Product Orders, other?
Registration, Shopping Basket Services, etc.
ISO 19115 based WS interface
11
Vision for an EO ClientVision for an EO Client
CWS WMS WCS
Earth Observations Client
NASA ECHO Servers
Other Agency Servers
NOAA CLASS Servers
ISO 19115 based WS interface
12
Web Services Interest GroupWeb Services Interest Group
Actions from WGISS #27 (27-1): Web Services Interest Group will prepare a draft Web
services requirements document for wider WGISS review and comment. The requirements document will have two parts:
(1) the definition of a set of core satellite data query and search refinement parameters that would be needed to support effective cross-satellite, catalogue searching and product selection; and
(2) a set of associated scenarios that illustrate how these search parameters might be employed in a standard Web services interface between a client portal and the satellite data servers they are querying and requesting data from.
Draft and present at WGISS-28, and then decide how best to share with others and describe deliverable to CEOS Plenary and GEOSS.
13
Web Services Interest GroupWeb Services Interest Group
Action part (2): Scenarios to illustrate EO search and order requirements
Employing a typical Landsat search and order process on USGS Earth Explorer or GloVis portals
Look at other EO information systems via LSI portal
14
Web Services Interest GroupWeb Services Interest Group
Recommendations to WGISS? Base search interface requirements on ISO 19115 Create generic scenario that includes the additional
requirements for browsing, ordering, and user registration/validation
Generate technical proposal that Prototype as part of WADC “clearinghouse” effort?
15
Web Services Interest GroupWeb Services Interest Group
Scenarios bring additional requirements beyond catalog searching
Browse images (could employ WMS) User registration User profiles and validation where restrictions are involved Product ordering options
Product parameters (e.g. map projections, resolution) Delivery options (e.g. ftp, shipped media) May involve purchase process
Product direct download for online products (WCS?)
16
Web Services Interest GroupWeb Services Interest Group
USGS/EROS Landsat Search/Order Scenario Possibly initiated by a link to Earth Explorer or GloVis from
IDN or LSI Portal Identify a data set of interest – Landsat ETM+ Specify an area of interest
Interactive map Uploading an area of interest file (Shape File, Simple Features
File, GML, etc.) Keying in latitude/longitude rectangle or point Specifying a Landsat Path/Row
Specify one or more date and time periods of interest Possibly specify cloud cover % Initiate inventory search
17
Web Services Interest GroupWeb Services Interest Group
USGS/EROS Landsat Search/Order Scenario View results and possibly refine search parameters and
submit new search View footprints of selected images on a map Request to view one or more reduced resolution browse
images to aid in the selection Select one or more specific scenes for download Before download, register as new user or provide previous
login (users are not validated) Initiate http download to user’s local storage Other functions available:
Request an “on-demand” product to be made and staged Set up a “standing request” Make arrangements for bulk data delivery
18
Web Services Interest GroupWeb Services Interest Group
Explore LSI links for insight into requirements http://wgiss.ceos.org/lsip/
19
Web Services Interest GroupWeb Services Interest Group
Conclusions? OGC too sparse to effectively support EO catalog searches OGC does not include temporal parameters CIP still excellent and applicable ISO 19115 is more current “standard” for CIP Base our parameter requirements on ISO 19115
20
Web Services Interest GroupWeb Services Interest Group
Presentation by Shinobu Kawahito, JAXA/RESTEC: Polar Mapping Update and WMS Experience