Observation Integration across Disciplines in the GEOSS Architecture
Observation Integration across Disciplines in the GEOSS Architecture Implementation Pilot George Percivall and Bart de Lathouwer The Open Geospatial Consortium (OGC) IGARSS 2013
GEOSS connects Observations to Decisions
Developing GEOSS Information System • GEOSS is a distributed, voluntary, Earth observation spatial data infrastructure. • Defining an agile development process for GEOSS • Co-evolution of implementations and architecture • Observation integration across disciplines in the GEOSS Architecture Implementation Pilot (AIP)
Agile development benefits from prototyping • Manifesto for Agile Software Development – Individuals and interactions over processes and tools – Working software over comprehensive documentation – Customer collaboration over contract negotiation – Responding to change over following a plan • Innovation and creativity in development occurs most reliably with multiple prototypes
Prototyping vs. Specifying • Multi-project experiments concluded each has merits 1. Prototyping yielded 40% less code; 45% less effort 2. Prototyped products rated lower on functionality and robustness, but higher on ease of use and ease of learning 3. Specifying produced more coherent designs and software that was easier to integrate. • In general – Prototypes provide optimal solutions for local conditions and current needs, whereas – Specifying provides completeness for a broader community and easier evolution over time
Development approach for GEOSS AIP • GEOSS characteristics – Development must meet variety of SBA needs – System of systems requires a vision be shared by GEO members and participating organizations • GEOSS Architecture Implementation Pilot (AIP) development process – Co-evolution of architecture, delivered systems, and stakeholders needs – Architecture framework for development, basis to evaluate deliveries – Development in collaboration with users
AIP Development Phases • AIP-1 Kickoff: Jun 2007; Alpha operations Nov 2007; Arch Workshop Feb 2008 – "Core" Architecture defined initial version of GCI • AIP-2 Kickoff Sep 2008; demo ISRSE May 2009; Beta operations Sep 2009 – SBA implementations of common cross-cutting architecture; Refined GCI concept supporting transition to operations • AIP-3 Kickoff Mar 2010; results to Beijing Plenary; Complete Feb 2011 – Network building in GEOSS SBA communities; Piloted Broker and Processing capabilities • AIP-4 Kickoff May 2011; results to Istanbul Plenary; Complete Dec 2011 – Increase access to priority earth observation data; via server software, tutorials and application clients • AIP-5 Kickoff May 2012; results to Brazil Plenary; Complete Dec 2012 – SBA application scenarios; Research prototypes • AIP-6 Kickoff March 2013; results planned for EO Ministerial, Jan 204 More than 120 organizations have contributed to AIP over 5 phases
GEOSS AIP Architecture Community Objectives GEOSS Vision and Targets Societal Benefit Areas System of Systems/ Interoperability Enterprise Viewpoint Information Framework Earth Observations Geographic Features Spatial Referencing Metadata and Quality GEOSS Data-CORE Abstract/Best Practices Information Computational Viewpoint Services Catalog/Registry Access and Order Processing Services Sensor Web User Identity Optimized Design/Development Component Types Use Cases Engineering Viewpoint Technology Viewpoint Tutorials RM-ODP Viewpoints
Engineering Components: Host data, Interact thru Services Main GEO Web Site GEOSS Common Infrastructure Registries Components & Services GEO Web Portal CSW WMS Registered Community Resources Client Tier Community Portals CSW Standards and Interoperability Best Practices Wiki User Requirements EO Vocabulary WMS Client Applications CSW WMS WPS GEOSS Clearinghouse Discovery Brokers Mediation Tier CSW Community Catalogues Test Facility Portrayal Servers WFS OPe. NDAP Order Workflow User Management WPS WMS WCS WFS Processing Servers Access FTP Data Servers SOS SAS SPS Sensor Web Servers WCS WFS Access Brokers Access Tier WCS GEONETCast Access CSW Model Web Servers
Use Cases Publish Resources Discover Resources Visualize and Access GEOSS Users Process and Automate Maintain and Support GEOSS Resource Providers
Integration of disciplines thru architecture • Geo-informatics results… – Fusing EO data with other geospatial information, e. g. , maps, SDI, alerts – based on standards – Moving from “order” to “access” for rapid delivery to speed analysis and response – Brokering to span communities – Reducing loss of information between formats – Sensor Web to hide complexity of diverse sensing systems and associated control structures. – Model Web vision promising with initial steps • …apply across SBAs: Disaster Management, Biodiversity Models, Energy, Water, Health
AIP: Disaster Management Satellite Programing Telemetry(Data) Receiving station Satellite Scheduling User Interface http: //140. 134. 48. 12: 443/quasi. ST/login Receiving station Satellite Scheduling
AIP: Disaster Management
AIP: Disaster Management GEOSS and CEOS coordination on DM • GEO and CEOS are advancing the use of Earth Observations (EO) in Disaster Management (DM) • Systems in GEOSS informing risk management and disaster reduction with EO-derived information. – Architecture Implementation Pilot (AIP) to describe, interconnect, capitalize, share • CEOS developing GEOSS Architecture for the Use of Satellites for DM and Risk Assessment – GA. 4. Disasters • Coordinated GEOSS and CEOS activities
AIP: Biodiversity models on Web • Observations plus modeling systems to predict pika distributions change with climate • Interoperability to determine predictors for the impact of climate change on biodiversity
AIP Energy – Solar Atlas GEOSS Data Core Help Application for dataset High-Resolution Solar Atlas • MINES Paris. Tech – ENDORSE Bio-energy assessment for Pakistan • DLR – RSA – Suparco – Ener. GEO
AIP-6: Hydrology on the web Watersheds Global to Local Maps Models Observations World Water Online – Univ Texas Austin. Leadership in AIP-6 along with many participants
Health Case Studies for GEOSS Environmental effects on allergies and cardiovascular diseases in Dresden and the Free State of Saxony, Germany Environmental challenges to health in South Durban, South Africa, due to human exposure on atmospheric pollution Investigating the impact of environmental and climatic variables on the cholera outbreaks in Uganda
Summary: Integration across disciplines in GEOSS • AIP development combines the best of prototyping and specifying • Architecture developed in AIP provides a basis to scale to multi-disciplinary needs in GEOSS. • Standards and interoperability arrangements support fusion of EO observations across disciplines • AIP and other GEO Tasks show the value of GEOSS in application of EO to meet societies needs
References • GEO and GEOSS – earthobservations. org • GEO Architecture Implementation Pilot (AIP) – www. ogcnetwork. net/AIpilot • GEOSS Web Portal – www. geoportal. org • The Open Geospatial Consortium (OGC) – www. opengeospatial. org
- Slides: 20