1. GEO Architecture Implementation Pilot ESIP Federation Meeting January 2009

2. GEO AIP-2 Session at ESIP Federation Architecture Implementation Pilot, Phase 2 (AIP-2) AIP Overview – George Percivall, OGC Access Working Group – Glenn Rutledge, NOAA Air Quality Working Group – Stefan Falke, Northrop Grumman

3. GEO Task AR-07-02 Architecture Implementation Pilot George Percivall, OGC January 2009 ESIP Federation Meeting

4. GEOSS connects Observations to Decisions 4 4

5. Operational Capability Operational Capability User Needs, Scenarios User Needs, Scenarios Design, Develop, Deploy Design, Develop, Deploy Architecture Implementation Pilot (AIP) GEOSS Common Infrastructure (GCI) support persistent implementation requirements SBA Tasks, UIC Elaboration of GEOSS Architecture

6. GEOSS Interoperability Arrangements - From the GEOSS 10 Year Plan Reference Document - Interoperability through open interfaces –Interoperability specifications agreed to among contributing systems –Access to data and information through service interfaces Open standards and intellectual property rights –GEOSS adopting standards; agreed upon by consensus, preference to formal international standards –GEOSS will not require commercial or proprietary standards –Multiple software implementations compliant with the open standards should exist –Goal is that at least one of the implementations should be available to all implementers "royalty-free"

7. Slide 7 GEO Task AR-07-02 Architecture 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

8. Slide 8 AI Pilot has broad international participation that could only have occurred with GEO. High interest & momentum supporting GEOSS vision. AIP Phase 1 results in 2007 Demonstrated effective development process: –CFP, Kickoff, Execution, etc. –Approximately 120 organizations Established organization communication methods –For international coordination Produced Screencasts of Initial Operating Capability Prepared “Architecture Implementation Report”

9. AIP Phase 2 Themes Augment the GEOSS Common Infrastructure Emphasize SBAs identified by UIC/ADC collaboration Develop "persistent exemplars” Elaborate GEOSS Architecture –Scenarios and Use Cases –Service and Component types –Interoperability Arrangements Slide 9

10. DevelopmentActivities Kick-offWorkshop Call for Participation ConceptDevelopment PersistentOperations(AR-07-01) Participation ArchitectureDocumentation Updates for each step Baseline AR-07-02 Architecture Implementation Pilot Evolutionary Development Process Operational Baseline and Lessons Learned for next evolutionary spiral Continuous interaction with external activities AI Pilot Development Approach

11. AIP Phase 2 Master Schedule

12. AIP-2 CFP Responses (37 to date) ACRF BKG Caribbean Flood Team CIESIN CNES and ERDAS Compusult EPA AirNow ERDAS Titan ESA ESIP AQ Cluster ESRI ESRI Canada EuroCryoClim NOAA/NASA GOES-R and GMU CSISS NOAA IOOS NOAA NCDC NOAA SNAAP Noblis Northrop Grumman Spot Image SURA/NIMSAT/GoMO OS USGS VIEWS Washington University in St. Louis GEONETCast GEO Grid GEO-Ukraine Giovanni ICAN ICT4EO INCOSE IP3 ISPRA JAXA KDDI Mines Paris Tech NASA World Wind

13. AIP-2 Kickoff Workshop, September 2008 At NCAR Mesa Laboratory, Boulder, Colorado, USA 85 Participants 3 Plenary Sessions 12 Parallel Sessions based on CFP Responses Established Working Groups; and Development Plan

14. Registered Community Resources Community Portals Client Applications Client Tier Business Process Tier Community Catalogues Alert Servers Workflow Management Processing Servers Access Tier GEONETCast Product Access Servers Sensor Web Servers Model Access Servers GEOSS Clearinghouse GEO Web Portals GEOSS Common Infrastructure Components & Services Standards and Interoperability Best Practices Wiki User Requirements Registries Main GEO Web Site AIP-2 Augmenting GCI

15. AIP-2 Working Groups (WGs) Community WGs –Disaster Response –Climate Change and Biodiversity –Renewable Energy –Air Quality Transverse Technology WGs: –Clearinghouse, Catalogues, Registries and Metadata –Access Services: products, sensors, models –Workflow and Alerts –Portals and Application Clients –Test Facility for service registration

16. Community WG Leaders Disaster Response –Stuart Frye, NASA; –Didier Giacobbo, Spot Image Health SBA: Air Quality –David McCabe, EPA –Frank Lindsay, NASA; –Stefan Falke & Rudy Husar, Washington Univ. Biodiversity and Climate Change –Stefano Nativi, CNR; –Gary Geller, NASA/JPL Energy SBA –Thierry Ranchin & Lionel Menard, Mines Paris Tech; –Ellsworth LeDrew, Univ Waterloo;

17. Transverse Technology WG Leaders Catalogues, Clearinghouse, Registries and Metadata –Doug Nebert, USGS; –Ted Haberman, NOAA –Kengo Aizawa, JAXA; –Josh Lieberman OGC/Traverse; Workflow and Alerts –Satoshi Sekiguchi, AIST; –Eugene Yu, GMU; –Greg Yetman, CIESIN Test Facility for service registration –Mauro Semerano, ESA Portals and application clients –Nadine Alameh, OGC/MobileAps; –Herve' Caumont, OGC/ERDAS Access Services: products, sensors, models –Glenn Rutledge NOAA, –Herve' Caumont, OGC/ERDAS; –Hans Peter Plag, UNR; –Anwar Vahed, ICT4EO; –Luis Bermudez SURA;

18. Scenarios and Use Cases Transverse Use Cases support Community Scenarios Scenarios: end user view of the value of GEOSS –Focused on topics of interest to a community –Occur in a geographic Area of Interest (AOI) –Steps in a scenario are Use Cases –Scenarios developed by Community WGs Use Cases: reusable service oriented architecture –Use cases for discovery, data access, etc –Utilize Interoperability Arrangements –Use Cases developed by Transverse Technology WGs

19. Community Scenarios - Draft Air Quality and Health: –Use of earth observations to inform three decision-makers: policy-maker, AQ compliance manager, and the public Disasters: –Disaster cycle for Flooding events Biodiversity and Climate Change –Polar scenario(s) –CC impact on Pikas in North America; Renewable Energy –Site selection process for solar and wind energy

20. Transverse Technology Use Cases - DRAFT Client search of metadata Portal / Client Visualize & Analyze DataPortal / Client Client access of services and alertsPortal / Client Publish Component and Services Access WG Bind to ServicesAccess WG Register ResourceCCRM Register Standards and Best PracticesCCRM Clearinghouse Harvest and SearchCCRM Construct and publish workflowWorkflow Test registered serviceTesting

21. AIP-2 Deliverables - 2009 Demonstration –Demonstration of community Scenarios implemented through transverse Use Cases –Demonstrations to be recorded and made available via WWW. Engineering Reports To be considered for GEOSS Best Practice Registry –Community of Practice Scenarios, –Transverse Technology Use Cases –AIP-2 Summary Report Persistent Exemplars –Registered services (‘continuous operation’) with 99% availability (~7 hours down time a month); on a reliable network; plan for performance scaling –Nomination to operational task (AR-09-01a)

22. References GEO –earthobservations.orgearthobservations.org GEO Architecture Implementation Pilot –www.ogcnetwork.net/AIpilotwww.ogcnetwork.net/AIpilot GEOSS registries and SIF –geossregistries.infogeossregistries.info George Percivall percivall@myogc.org

23. GEO AIP-2 Session at ESIP Federation Architecture Implementation Pilot, Phase 2 (AIP-2) AIP Overview – George Percivall, OGC Access Working Group – Glenn Rutledge, NOAA Air Quality Working Group – Stefan Falke, Northrop Grumman

24. GEO Architecture and Data Committee Task AR-07-02 Architecture Implementation Pilot Access Services: Products, Sensors, Models WG Access Services Co-Chairs: Glenn Rutledge, NOAA Hervé Caumont, ERDAS Luis Bermudez, SURA Terence Van Zyl, CSIR ESIP Winter Meeting January 8th, 2009

25. Data Product Access 23 Primary responses: CIESIN, CNES, EPA, ESA, GEO-Ukraine, ICAN, ICT4EO, IP3, ISPRA, JAXA, Mines Paris Tech, NASA World Wind, NOAA IOOS, NOAA NCDC GOSIC, NOAA NCDC NEXRAD, NOAA NCDC NIDIS, NOAA NCDC NOMADS, NOAA/NASA GOES-R and GMU CSISS, Northrop Grumman, SURA/NIMSAT/GoMOOS, Spot Image, USGS, Washington Univ St. Louis 15 Contributing responses: ACRF, Caribbean Flood Team, ERDAS, ESIP AQ Cluster, ESRI, ESRI Canada, NOAA SNAAP

26. Data Product Access Topics Services: WMS, WCS and WFS Broker Services: access OGC Web services, THREDDS/OPeNDAP, Encodings Formats : NetCDF/CF, GRIB, KML, GML, JPEG2000, PNGs, GeoTIFF, MrSID, Geolocated JPEGs, CADRG, CIB, Shapefile EO Data: Radar, Optical, Weather, Precipitation, TRMM flash flood potential ALOS Imagery: Panchromatic, Near IR, SAR General Circulation Models High-frequency radar in situ oceanographic data Coastal Web Atlas holdings Multistandard platform (MapServer, ArcIms Server, SDE, etc) SPIDR web services IP3 ENM Species Distribution Analysis service SoDa W*S is already a Special Argmt THREDDS

27. Sensors and Models Access 8 Primary responses: GEO-Ukraine, ICT4EO, IP3, NOAA IOOS NOAA NCDC NOMADS, Northrop Grumman, Spot Image, SURA/NIMSAT/GoMOOS 4 Contributing responses: Caribbean Flood Team,Compusult, NASA World Wind, NCDC NEXRAD, Noblis

28. Goal, audience, and usage of the 'Use cases' Use Cases are provided to model the interactions of a (sub) system under study with its environment (actors are a user interface or other system) –Co-authored by systems analysts and end users –A starting point for tests design Use Cases are developed by the AIP Transverse Technology WG Scenarios are developed by the AIP Community WG Both support AI Pilot storyboards, to test & demonstrate inter- operability among online persistent systems and services –Running a scenario over several systems –Activating systems functions as described in the use cases

29. The Access WG provides coordination and guidance to achieve interoperable Access Services to products, sensors and models. This relies on the AIP-2 particapants offerings and contributions to the pilot. There are two priority use cases being developed by the Access WG: - Publish Component and Services - Interact with service(s) Access WG Charter

30. Template for Access Use Cases

31. Simple example

32. Publish & Interact NameDescriptionWorking GroupPreconditionPostcondition Deploy Components and Services Develop and deploy a component with associated services Access Organizational capability to host a service network- accessible offerings Interact with Services Interactions between client and services for datasets, sensors, models, workflows Access User request for a client to access a service or alert Client received information from the service or alert 32 A key goal is to reduce the complexity when it is not needed. This means that an “Interaction” should be similar for products, sensors, models and for workflows.

33. AIP-2 Initial Access To succeed – initially, AIP aims to reduce the variations arising from different communities. At first cut “Bind” will be the same for everyone, then advance to a dialog on what few things need to be the same so that everything else can be different. To the larger communities WFS, WCS, SOS, etc. are more alike than they are different. Data Access Services – OGC WCS/WMS Discovery Metadata – OGC CSW and ISO 19115/ISO 19119 Together this allows users to find and access data 33

34. ACCESS WG Contact Information Working Group Leads : Glenn Rutledge, Hervé Caumont, Luis Bermudez, Terence Van Zyl, Hans Peter Plag, Anwar Vahed, Getting to the Access WG Web page: –http://sites.google.com/site/geosspilot2http://sites.google.com/site/geosspilot2 Subscribing to the Access WG Mailing List: –https://lists.opengeospatial.org/mailman/listinfo/aip_accesshttps://lists.opengeospatial.org/mailman/listinfo/aip_access Access WG weekly telecons to discuss issues arising and new use cases that need to be addressed –Announcements through Access WG mailing list

35. Global Earth Observation System of Systems (GEOSS) Architecture Implementation Pilot (AIP) Air Quality and Health Working Group Stefan Falke, Rudy Husar, Frank Lindsay, David McCabe, Erin Robinson

36. Air Quality & Health Scenario Scenario Overview The AQ Scenario envisions multiple types of AQ observations… satellite observations of AQ and meteorology in-situ, ambient observations models of meteorology and chemical transport other: emissions data, fire observations, LIDAR, etc. …being registered, discovered and accessed via GEOSS and used to inform diverse decision-makers: Air Quality Managers, Policy-Makers, and the Public. Scenario community-developed ; AIP participation diverse (next slide) Initial sub-scenario testing AIP Use Cases describes a Wildfire/Smoke event Challenges Persistent, standardized AQ data network Interface to GCI: Community Catalog, Portal Implementing scenarios which can integrate the offerings using GCI-compatible Service Oriented Architecture

37. AQ&H WG Core Participants Catalog/ Metadata Data Access Sensors/ Models WorkflowClientsScenario EPA ESIP AQ Cluster GIOVANNI GMU NOAA NGDC Northrop Grumman VIEWS WUStL

38. ESA/FAO ESRI Compusult WAF DataSpaces Catalog Z39.50 CS/W Portal AQ Community Infrastructure DRAFT Future Considerations Direct Access to GEOSS Clearinghouse Community Portal/DataSpace input to GEO Portals DataSpaces part of Community Portal? Evolving Architecture Metadata DB FGDC, ISO, SERF

39. AQ AIP Linkages AQ Community Catalog AQ Community Portal CS-W WMSWCSW*SKML Capability GEOSS App Provider Community Data Server Community AQ Apps CS-W, W*S Portals Applications, Clients Testing Workflow Processing Serv, Alerts Clearinghouse Catalog, Metadata Access Services Products, Sensors GEOSS AIP WorkgroupsCore AQ System AQ Apps Workflow Processing Serv, Alerts AQ Apps Workflow Processing Serv, Alerts AQ Apps Workflow Proc. Services, Alerts AQ IT Cast

40. Key Standards for AQ: CSW, WCS Where are we now? Where do we want to be? How to get there? Automatically extract discovery metadata from Capabilities & KML CSW – Queriable Fields for Discovery WCS – Data Access Service Extensions Collaboration with UNIDATA & GALEON 4D Grids for Models, Satellite Data netCDF – CF Convention Station Time Series (STS) for Point Data netCDF – STS Convention

41. Community Portal A user interface between GEOSS CGI and AQ Community Catalog A content aggregator and connector Help air quality data/service providers and data/service users make use of the GEOSS Common Infrastructure Forum for dialogue among the community in shared interests in air pollution events, analysis tools, models, datasets, etc. Development Portal: http://128.252.167.3http://128.252.167.3 Help in finding and using search, visualization and analysis tools Latest data analyses, publications, etc Latest activity on AIP AQ&H WG Google Sites as RSS Components /Services filtered for ‘air’ from search on ESRI GEO Portal as GeoRSS Data/services metadata from DataSpaces