Transcript Update on OGC involvement in GEOSS

GEOSS ADC
Architecture Workshop
Initial Operating Capability (IOC)
Doug Nebert
U.S. Geological Survey
[email protected]
February 4, 2008
GEOSS Architecture Workshop
• Development of the IOC
– AI Pilot Phase 1
– Registration demo
• Elements of the IOC
– Registries
– Web Portal candidates
– Clearinghouse
– Community portals
– Client applications
Initial Operating Capability
• An Initial Operating Capability (IOC) was established
for GEOSS in November 2007 largely as a result of
the Architecture Implementation Pilot, Phase 1.
Several demonstrations portray the IOC functionality.
– Users can access the GEOSS IOC functionality
through the GEOSS Web Portal Candidates,
Community Portals and Decision Support Clients.
– Providers can register their services as part of the
IOC at the GEOSS registry system.
– Developers can view a description of the GEOSS
IOC architecture through the website:
http://www.ogcnetwork.net/GEOSS_IOC
GEOSS Architecture: IOC Summary
• GEOSS Registries established for Components, Services, and
Standards
– 66 Components & 74 Services registered (1 Feb 08)
• User access: GEO Web Portal Candidates (3), Community
Portals (27) and Decision Support Clients (13)
• Several organizations capable of providing
– GEO Web Portal solutions
– GEOSS Clearinghouse solutions
• IOC Summary Web Presence
– http://www.ogcnetwork.net/GEOSS_IOC
– Recommend hosting on a GEO web site
GEOSS IOC Architecture: Input to AIPilot-II
• Core architecture refined by increasing collaboration with
GEOSS SBAs
– Work with GEO Committees, Communities of Practice and
other relevant GEO Tasks.
• Increase commitment to Operational requirements to support
persistence
• Clarify operational approach for core components: GEO Web
Portal, GEOSS Clearinghouse & user “help desk”
• Architecture refinement and extension:
– scenarios using an enterprise modeling approach;
– workflow for observation processing and decision support,
e.g., results of Fed Earth Observation (FedEO) pilot;
– include observation/sensor nodes to support such use cases
as inter-calibration
(Click to Start)
IOC Architecture – Technology Viewpoint
IOC Architecture – Technology Viewpoint
Client Tier
GEOSS
Web
Portal
GEO Web
Site
CSW/SRU/UDDI
GEOSS
Registries
CSW/ISO23950
Get list
Components
GEOSS
Clearinghouse
Services
Decision-Support
Applications
Business Process Tier
Portrayal
Services
Workflow
Management
Processing
Services
Other
Services
CSW/ISO23950
Standards
Requirements
Community
Portals
Register
Community
Catalogues
Access Tier
GEONETCast
Data
Access
Services
Sensor
Access
Services
Model
Access
Services
Other
Services
GEO Web Portal Candidates
GEO-wide Web Portal candidates were requested to
demonstrate capabilities against common
requirements. Web Portals can be re-deployed for
communities, countries, or SBAs but retain access to
common architecture (Registries, Clearinghouse,
Component Services).
Three offered candidates:
– Compusult, Ltd.
– European Space Agency (ESA)
– ESRI, Inc.
Compusult
esa
ESRI
Community Portals
The community portals listed on this page are part of the GEOSS Initial Operating
Capability (IOC). Portals provide end-user access to data and analytical capabilities for
specific domains. Items registered in the GEOSS Component and Service Registry are
shown with an ®.
•
•
•
•
•
•
•
•
•
Mapufacture (Africa wild fire
scenario)
SEDAC Map Client (Polar E&B
scenario)
GEO Connections Discovery Portal
(Polar E&B scenario) ®
ESA Service Support Environment
(Oil Spill scenario)
SERVIR data portal (Hurricane
scenario) ®
DataFed ®
Earth Observation Grid Processing
on Demand ®
GEO-UA ®
GeoConnections Discovery Portal ®
•
•
•
•
•
•
•
•
•
Global Biodiversity Information
Facility Data Portal ®
INSPIRE geo-portal ®
Incorporated Research Institutions
for Seismology, Data Management
Center ®
GI-go GeoBrowser ®
Information System and Data
Center ®
International Directory Network: A
Portal for Group on Earth
Observations ®
NASA Earth Science Gateway ®
NASA Socioeconomic Data and
Applications Center ®
U.S. Geospatial One-Stop Portal ®
Decision Support Clients
The following Decision-Support Clients are part of the GEOSS
Initial Operating Capability (IOC) and were used in
demonstration scenarios as indicated.
–
–
–
–
–
–
–
–
ESRI ArcGIS Explorer (African Fire Scenario)
Google Earth (African Fire Scenario)
Carbon Project Gaia (African E&B Scenario)
Refractions Research uDig (African E&B Scenario)
gvSIG (African E&B Scenario)
METIS viewer Astrium (oil Spill scenario)
JAXA Earth Monitoring Browser (Volcano scenario)
GI-go Client (IP3 scenario)
GEOSS registry system objectives
•
•
•
•
•
To register components and have them approved by the GEO
Secretariat,
To register services and associate them with GEOSS-recognized
standards -- and special arrangements for implementations using nonrecognized approaches,
To register special arrangements and GEOSS-recognized standards.
– Taxonomy of standards types is also proposed to assist in the
discovery and classification of GEOSS service implementations.
Best practices (wiki) and EO User Requirements
On-line access
– http://geossregistries.info/
– http://seabass.ieee.org/groups/geoss/
GEOSS Registries
The Registries store organizational, system, and
service information in the context of existing standards
and practices within the GEO community.
GEOSS Clearinghouse
• Clearinghouse is a broker to Community Catalogues
• Searches GEOSS Service Registry to identify services that can
be searched
• Community Catalogues may either be “harvested” in advance or
“searched” at the time of a user query
• Searches received from GEO Web Portal, Community Portals or
any other external application acting as a catalog client
• Brief or full responses are marshaled and returned to requesting
client as XML
GEOSS Clearinghouse
Web Portal, Client, DS Client,
Desktop application
Clearinghouse and Community Catalogues
• Three Clearinghouse candidates were demonstrated as part of
AIPilot, Phase 1 – FAO GeoNetwork, Compusult, and ESRI
• Catalogues used and/or registered ® :
–
–
–
–
–
–
–
–
–
–
–
–
–
Global Change Master Directory (African Wildfire Scenario) ®
METOP EUMETSAT CSW (oil Spill Scenario)
SPOT Image Ionic CSW (oil Spill Scenario)
MUIS Catalogue (oil Spill Scenario)
SAR ESA CSW (oil Spill Scenario)
Ionic Catalog CSW (oil Spill Scenario)
JAXA CSW (volcano Scenario)
GeoConnections Discovery Portal Catalog (Polar E&B scenario)
INSPIRE catalogue ®
ECHO ®
GI-cat Federated Catalog ®
NASA Earth Science Gateway ®
U.S. Geospatial One-Stop ®
Workflow Management, Processing Services
The following Workflow Management components are
part of the GEOSS Initial Operating Capability (IOC)
and were used in demonstration scenarios as
indicated:
– Catalogue Workflow Spacebel (Oil Spill)
– SPS EO Profile Workflow Spacebel (Oil Spill)
– EO-1 Workflow Chaining Service (Africa fires) ®
One Processing Services component was
demonstrated:
– EO-1 Thermal Classification Web Processing Service (Africa
fires) ®
Other Business Tier Services
• RSS feed for Fires (African fire scenario)
• RSS CAP server USGS (Oil Spill Scenario)
• RSS Volcanic Ash Advisory Service CAP server
USGS (Volcano Scenario)
• Standard Archive Format for Europe
Earth Observation (Data) Access Services
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
EO1 SPS – EO1 Satellite Sensor Tasking (African Fire Scenario)
EO1 data (African Fire Scenario)
Image Data JAXA WMS/CSW (Africa E&B)
Landsat 7 WMS Global Mosaic (Africa E&B)
Feasibility Server MISEO Astrium (Oil Spill Scenario)
MERIS SPS Datamat/ESA ((Oil Spill Scenario)
SPOT Image SPS (Oil Spill Scenario)
Sea Surface Temp NERC WMS (Oil Spill Scenario)
PALSAR Image JAXA WCS (Oil Spill Scenario)
Wind ASA WMS (Oil Spill Scenario)
ASAR Image Infoterra/ESA WMS (Oil Spill Scenario)
SPOT Image WMS/WCS (Oil Spill Scenario)
ALOS Image JAXA WMS/WCS (Volcano Scenario)
EO-1 image JAXA WMS/WCS (Volcano Scenario)
DataFed WCS ®
IMAGE 2000 ®
Integrated CEOS European Data Server ®
JAXA Web Coverage Service ®
JAXA Web Map Server ®
NASA-SSE-HelioClim-1 ®
WGISS Test Facility for CEOP prototype system ®
Other Data Access Services
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Gridded Population Data SEDAC WMS (African wildfire scenario)
Global Land Cover 2000 JRC WMS/WCS server (African E&B
scenario)
Soils data JRC WMS/WCS server (Africa E&B scenario)
Protected Areas JRC WMS/WFS (Africa E&B scenario)
Global Biodiversity GBIF Information Facility (data.gbif.org) (African
E&B scenario)
CARMA Caribou migration data Cubwerx WMS (Polar E&B scenario)
Geology NRCan WMS (Polar E&B scenario)
Vegetation and Wetlands NRCan WMS (Polar E&B scenario)
Snow and Ice Data Center - NSIDC WMS (Polar E&B scenario)
Atlas of the Cryosphere (Polar E&B scenario) ®
Land Cover and Population FAO WMS (Volcano scenario)
Land Use and Population JAXA WMS/WCS (Volcano Scenario)
Geogratis (Canada) ®
NASA Socioeconomic Data and Applications Center ®
IOC Issues – Going to the next level
•
•
•
•
Systematic registration of Components and Services
Support of registered standards by offerings
Quality and availability of services
Promoting the ability to integrate data and services
towards additional SBA application domains
• Strengthening the use of the Web Portals to access
and integrate all GEOSS resources
• Improving the interaction of the GEOSS Web Portals,
Registries, and Clearinghouse
Systematic registration of Components and
Services
• Request by ADC co-chairs on behalf of ADC to get
the message out – message content, tools,
assistance
• Tools: powerpoint walkthrough of registration, screen
captures, tutorials,
• UIC assistance in getting the word out?
• Develop small package to brief other committees
• Identify benefits of registration
• Identify how non-members (non-countries M&PO)
organizations can participate, also commercial
• Identify what user types/requirements can be handled
Support of registered standards by offerings
• Clarify Component, Service and find out why
incomplete registrations are taking place
• Increase awareness and understanding of service
registration (process and benefits) for both
standards-based and special arrangement cases
• Is there a possibility to have a read-only access
license for GEO participants to ISO (for-fee)
standards? Users may need to view a standard
before it can be applied…
• National and Intl standard cross-walk or equivalency
support in Standards reg?
Quality and availability of services
•
•
•
•
•
•
•
•
•
•
Identify metrics of numbers and types of resources, users, applications
for mid-term review (2009)
Monitor queries, types of users, support feedback loops on core
services
Encourage a public service level declaration/intention (assertion) GEOwide to improve quality of service
What are the issues of “liability” (commitment) in meeting SLA targets?
Consider having service checking and testing mechanism, who would
evaluate QoS?
Communities of Practice could evaluate services for ‘fitness for use’
What would QoS values look like, how would it be organized?
Track the operational/experimental nature (QoS) for services, including
maintenance, lifecycle stage
Some qualities are not easily measured (qualitative vs quantitative)
Identify small set of properties on services that characterize QoS from
service and consumer points of view
Organizational commitment
Promoting data and services integration
•
•
•
•
•
•
•
•
How to promote access to services to encourage their use in more
complex ‘service chains’?
Back the data content behind a service with a standard ontology
(activities, processes, observables) re-use existing systems/ontologies
Integrating local data into regional/global data: demonstrate how to
engage local authorities to promote data/service integration – scaling
data local/regional/global as similarly structured
Can we promote templates to develop access to data and services?
Integrate services into local solutions
Involve different levels of data provider in the integration task
Use registries to include more data schema/descriptions and compile
best practices or as “special arrangements” as GEO-wide standards
(global, national, regional)
Develop better understanding of human interface to the invocation and
presentation of interaction with Web Services Track and promote
access
Focus on decision support clients to use the Core infrastructure and
standards to tailor access to GEOSS resources
Infrastructure maturity (registries, web portals, etc)
• Core services need to be reliable
• Quantify reliability of the core services “.999”
availability
• Define QoS assertions by the service operators,
identify what level of commitment is required
• Performance, reliability, accuracy, failover, model for
user loads – web portals, clearinghouse, registries
Interaction between Registries, Portal, and the
Clearinghouse
Messages for CFP?
• What is the scope of the IOC?
• Who are the users?
• What are the next steps?
• How to clarify/differentiate OGC versus GEO activity?
• Identify the foci of the upcoming CFP/AIP
– Increase the role of the end-user/client/DSS
– Improve the uptake of the core infrastructure
– Operational end-user needs are met (real-world
systems and solutions)
– Carefully define the objectives of Phase 2 and
service expectations