Upload
eileen-teresa-jefferson
View
216
Download
0
Tags:
Embed Size (px)
Citation preview
GEO Architecture and Data Committee
Architecture Workshop
Hosted by the European Commission
At the Joint Research Centre
February 2008
DRAFT
Architecture Workshop Opening PlenaryStart Topic Speaker
1300 Opening George Percivall
1305 Welcome to EC/JRC Allesandro Annoni
1320 Logistics JRC
1325 Recap of 2007 - IOC for GEOSS Core Architecture
Percivall, et. al.
1355 UIC/ADC Collaboration Ellsworth LeDrew
1405 User & Architecture Workshop Series
Francoise Pearlman
1420 Plan for Workshop George Percivall
1430 Adjourn Plenary
Recap of 2007 - Initial Operating Capability for the GEOSS Core Architecture
George Percivall, et. al.
GEOSS Core ArchitectureInitial Operating Capability (IOC)
• Core Architecture– GEO Web Portal, Clearinghouse, and Registry – Process to register, discover and use services – GEOSS Interoperability Arrangements
• During 2007, GEO ADC guided development of IOC through its core tasks:– AR-07-01 - Enabling Deployment of Architecture– AR-07-02 - Architecture Implementation Pilot
• Results demonstrated at EO Summit and GEO-IV
Core Architecture
GEOSSComponent,
Service registry
Standards,Special
ArrangementsRegistries
references
GEO Web Portal and other Clients
searches
Offerors
contribute to register
GEOSSClearinghouse
Catalogues
Services
User
accesses
list ofcatalogues
accesses
searches invokes
reference
AI Pilot Milestones - 2007
• Call for Participation (CFP)– CFP Preparation based on RFIs February & March– CFP Release April 13 – CFP Responses Due May 11
• Pilot Kickoff meeting June 5&6 – Hosted at ESA-ESRIN
• Deploy, Integrate, Test 4 mo. June to September
• Demo Capture Workshop September 10&11 • Core Architecture Implementation Report November
GEO Task AR-07-02
GEO Architecture Implementation Pilot - 2007
• Demonstrated effective development process: – CFP, Kickoff, Execution, etc.– Approximately 120 organizations
• Established effective communication methods – For international coordination– www.ogcnetwork.net/AIpilot
• Produced Screencasts of Initial Operating Capability– www.ogcnetwork.net/AIPdemos
• Prepared “Core Architecture Implementation Report”
GEOSS Architecture Status
• Architecture validated through ADC core tasks
• Deployed, tested and demonstrated in 2007
• Component types and interactions confirmed
• Recommendations for Interoperability Arrangements
• Consistent with GEOSS Strategic Guidance Document and Tactical Guidance Document
GEOSS Architecture
• Initial Operating Capability (IOC) established• 64 Components & 75 Services registered (21 Nov 07)• GEO Web Portals (3), Community Portals (27) and
Decision Support Clients (13) for User access to services
• Several organizations capable of providing – GEO Web Portal solutions– GEOSS Clearinghouse solutions
GEO Web Portal
• Demonstrated that organizations are capable of providing workable GEO Web Portal solutions– Compusult: http://www.geowebportal.org – ESA-FAO: http://www.geoportal.org– ESRI: http://keel.esri.com/Portal
• Though visibly similar & meeting basic requirements, the three offer different feature sets.
• Cape Town Declaration: “We commit to explore ways and means for the sustained operations of the shared architectural GEOSS components and related information infrastructure.”
GEOSS Architecture - Further Development
• Increase collaboration with GEO Committees, Communities of Practice and relevant GEO Tasks.
• Increase commitment to Operational requirements to support persistence– Portal, Clearinghouse and other services
• Add Sensor Component Types– Task, acquire and process observations– Inter-calibration scenario, e.g., CEOS
• Workflow for observation processing and decision support, e.g., Fed Earth Observation (FedEO) pilot
AR-07-02 Task Definition
• Task Sheet slightly revised at ADC-5, September 2007
• Architecture Implementation Pilot emphasis retained: Portals, Clearinghouse, Catalogues, and Services– Including sensors interoperability services
• Two items added– Persistent Infrastructure for Service Integration– GEOSS User and Architecture Workshops
GEO Architecture Workshop
• February 4&5, 2008 – Co-located at JRC Ispra with ADC-6
• Purpose: Consensus building in support of CFP• Topics
– Scenario candidates: interactions with UIC & CoP re scenarios
– Begin refinement of the CFP-2007 architecture– Sustained operations for information architecture– Other Implementation Report topics
GEOSS User & Architecture Workshop Series - Summary of Proceedingshttp://www.ieee-earth.org/default.taf?menu=conferences&feature=geossworkshops&title=GEOSS%20Workshops
Francoise Pearlman
IEEE
GEOSS User & Architecture Workshop Series
For Proceedings go to http://www.ieee-earth.org and select conferences
GEOSS Architecture and Societal Benefit Areas Addressed in 15 Workshops
Canberra-07Models
Tshwane-05Disasters & water
Beijing-06Energy
Seoul-05Disasters
Yellowknife-07Climate &biodiversity
Denver-06Climate
Boulder-07Energy
Corte-06Energy &Ecosystems
Barcelona-07SoS interop. &biodiversity
San JoseCosta Rica-07Agriculture
Ouagodougou-07Water & health
Goa-06Water &Health
San Diego-07Comm &Networks
Honolulu-07SoS Engineering& Architecture Kuala-Lumpur-07
Disasters
A typical Proceedings includes
• Workshop Flyer• Description• Agenda• Briefings• Breakout Session
Reports• Conclusions
IEEE GEOSS WorkshopThe User and the GEOSS
Architecture XIV -
Organized by:Dr. Changyong Cao - NOAA/NESDIS, Washington DCProf. Al Gasiewski – University of Colorado, Boulder, CODr. Siri Jodha Singh Khalsa – University of Colorado NSIDC, Boulder, CODr. Jay Pearlman – The Boeing CorporationMr. Ivan Petiteville – ESA
Opening
GEOSS Architecture & Interoperability
User Perspective (Societal Benefit focus)
Demonstrations
Break-out Sessions
Summary
Selected briefingsAre recorded andAvailable on the ICEOSite under Resources(Audio & slide lectures)
Demonstrations materialAnd video clips are uploadedTo the OGC Web site
Breakout Sessions – User/Developer’s Perspective
Sample Questions– What is a user?– What are the needs and concerns for GEOSS
from a user perspective?– What are the most important information from
GEOSS for user applications?– If the architecture is developed over a number of
years, what features should be developed early?– What features are missing that you would like to
see included
Breakout Sessions – Summary Findings I
• A spectrum of Users– End Users (Top level Decision/policy makers, managers) in
need of user friendly information– Researchers more focused on source and quality of data– Accommodate different needs & level of expertise
• Users versus Providers– Encourage connectivity between the two and between
models and data providers– Iterative, interactive feedback from users & ability to correct
errors• Models
– Need for interoperable cross-domain models– Improved connection between modeling and observation
communities
Breakout Sessions – Summary findings IIEmphasis on Data• Key data characteristics
– Discovery, accessibility, distribution, visualization/layering, sharing• Data packaging
– Clear documentation – especially when cutting across benefit areas– Standards– Meta-data
• Frequently mentioned concerns– Timeliness (from real time to paleo-data)– Security/authentication (access to proprietary data...)– Quality (Trusted source; Quality Assurance and Control; Data lineage)– Continuity of data source– Compatibility– Sharing policies
• Data distribution mechanism– Internet vs mobile access (including ad-hoc networking)– Feedback mechanism
Breakout Sessions – Summary Findings III
• SoS Architecture key desired characteristics– Offer simple, seamless services– Supports high availability, reliability, security, authentication– Facilitate interoperability– Allows for technology evolution & new technology insertion
• Thoughts on interoperability• Focus on connecting systems within a community• Interfaces are abstracted in “wrappers” developed cooperatively
by Providers & Users• Include ontology in Interoperability registry
• Build a little, test a little: demonstrations, prototypes and pilots are essential
Demos and Pilots
• Demonstration of the core architecture– Service registration and discovery
process– Application of the architecture to
eight societal benefit scenarios– use of the portal candidates
• Screencast videos of the demonstrations are available on-line: http://www.ogcnetwork.net/AIPdemos
Demo team in Yellowknife, Canada
A look forward- Workshops for 2008
Accra, Ghana - 08Water Security & Ecosystems
Beijing, China-08Air Quality & Health
Kobe, Japan-08Oceans & Water
Quebec, Canada-08Science Modeling &Data Policy
Toronto, Canada-08UIC workshop
Boston, USA-08Air Quality & coastalEcosystems
Spain-08ArchitectureOf GEOSS
Honolulu, Hawaii-08CommunicationsFor disaster management
Architecture Workshop
• Interactive meeting to develop requirements for GEOSS Architecture developments.
• Results will become part of a Call for Participation in 2008.
• Scenarios identified through collaboration of the GEO UIC and ADC
• Domain-specific GEO Tasks can utilize AIP (AR-07-02) to utilize the GEOSS Core Architecture
Workshop - Monday’s AgendaStart
(Duration)
Activity
1300 (90) Opening Plenary
1430 (20) Refreshment Break
1450 (90) Session 1a:Air Quality &
Health Scenario- John White -
Session 1b:Inter-calibration
Scenario- Stephen Ungar -
Session 1c:Initial Operating
Capability- Doug Nebert -
1700 Adjourn
Workshop - Tuesday Morning AgendaStart (Duration)
Activity
0900(90)
Session 2a:Biodiversity Scenario
- Doug Muchoneyand IP3 group
Session 2b:Energy - Solar
Scenario- Lionel Menard
Session 2c:Clearinghouse,
Catalogues, Registries
- Doug Nebert
1030(20)
Refreshment Break
1050(90)
Session 3a:Disaster Response
Scenario- Guy Séguin
Session 3b:Sensors
Interoperability- Ingo Simonis
Session 3c:Test Facility for
GEO Registration- Paul Smits
1220(70)
Lunch
Workshop - Tuesday Afternoon AgendaStart (Duration)
Activity
1330(60)
Session 4a:Water/Drought
Scenario- David Arctur -
Session 4b:Workflow
- Pier Giorgio Marchetti -
Session 4c:User Portals and
Applications- Ingo Simonis -
1430(20)
Refreshment Break
1450(90)
Closing Plenary
1700 Adjourn
Position Papers
• Data Policy white paper for GEOSS - overall
• Energy data centre STFC - Energy Session
• GEO ADC IP3 Proposed Activities 2008 - Biodiversity Session
• Satellites for risk management - Natural Disaster Session
• ESA-FAO GeoPortal position paper - User Interface Session
• GEOSS: A Global SDI Framework - Clearinghouse Session
• Standards in a Distributed Digital Library of Geospatial Services - Workflow
• WGCV's Data Quality Framework - Inter-calibration
• Global Space-based Inter-Calibration System (GSICS) - Inter-calibration session
• OGC Sensor Web Enablement Standards - Sensors
Things to consider in all sessions
• User needs• User and Architecture Workshop outcomes• Architecture Modeling• Data Policy Paper
Coordinating Tasks
Session Task # Task Short Title
Disasters DI-06-09 Use of Satellites for Risk Management
Biodiversity BI -06-02 Biodiversity Requirements in Earth Observation
Biodiversity EC-07-01 Global Ecosystem Observation and Monitoring Network
Biodiversity BI -06-03 Capturing Historical Biodiversity Data
Energy EN-06-04 Using New Observation Systems for Energy
Air Quality HE-07-02 TBD Environment and Health Monitoring and Modelling
Water WA-08-01 TBD In tegration of In -situ and Satellite Data for Wat er Cycle Monitoring
In tercalibration DA-06-02 Data Quality Assurance Framework
AG Mon AG-07-03 Operational Agricultural Monitoring System
Sensors DA-07-03 Virtual Constellations
Sensors DA-07-04 Sensor Web Enablement for In-Situ
Registry DA-06-04 Data, Metadata and Products Harmonisation
Overall DA-06-01 Application of the Agreed GEOSS Data Sharing Principles
Overall AR-07-01 Enabling Deployment of a GEOSS Architecture
Overall AR-07-02 GEOSS Architecture Implementation Pilot
GEO Task AR-07-02Architecture Implementation Pilot
• Lead incorporation of contributed components consistent with the GEOSS Architecture…
• …using a GEO Web Portal and a GEOSS Clearinghouse search facility
• …to access services through GEOSS Interoperability Arrangements
• …in support of GEOSS Societal Benefit Areas
GEOSS Core ArchitectureImplementation Report
• GEOSS Architecture– Initial Operating Capability– Engineering viewpoint: Component Types– GEOSS Interoperability Process
• Registry System and Clearinghouse– Use Case and Requirements– Clearinghouse Candidates assessment– Distributed search vs. harvest trade study
• GEO Web Portal– GEO Web Portal Definition and Requirements– GEO Web Portal candidates assessment
AI Pilot Development Approach
DevelopmentDevelopmentActivitiesActivities
Phase DPhase D
Kick-offKick-offWorkshopWorkshop
Phase CPhase C
Call for Call for ParticipationParticipation
Phase BPhase B
ConceptConceptDevelopmentDevelopment
Phase APhase A
PersistentPersistentDeploymentDeployment
Phase EPhase E
SBA Scenario Demonstrations
• Registry & Clearinghouse workflow• GEO Web Portal - Compusult• GEO Web Portal - ESA/FAO• GEO Web Portal - ESRI• Wildland Fires in Africa • Ecosystems & Biodiversity in Africa • Ecosystems & Biodiversity in Polar Regions• Response to Oil Spill• Response to Volcano• Response to Hurricane
AI Pilot Screencast Participants
• CIESIN• Compusult• Cubewerx• EADS Astrium• EC/JRC• EPA• ESONET• ESRI• FAO• FGDC • GBIF• Generalitat Valenciana
• GeoConnections• GIM• GMU• JAXA• JRC• Meraka/52north• NASA• NOAA • NRCAN• NSIDC• OGC
• PCI Geomatics• Sapienza
Consulting • SDSC• Spacebel• UK BADC • University of
Maryland• USGS• Vightel• WCMC