1. Ideas on Opening Up GEOSS Architecture and Extending AIP-5 Wim Hugo SAEON

2. GEO needs to Build more components that do not directly rely on the GEO Portal/ GCI to be useful Respect the GEOSS architecture and implement the standard interfaces – many data sets are not standardised Allow simple integration into any community portal Emphasise service orientation Additional consideration: Components should ideally be open source based on a roadmap and reference implementations The components need to be open source, because smaller contributors risk losing their investment if they do not participate in open projects.

3. SAEOS/ SAEON Platform Hosts a number of initiatives in a common infrastructure – SAEON Data Portal – SAEOS (SA-GEO conduit to GEOSS) – SA Risk and Vulnerability Atlas – SA BioEnergy Atlas – World Data Centre Prototypes – INGC (Mozambique) – … Increasingly focused on creating a community portal on demand HOWEVER – allows any web application to implement components and integrate on the interoperability standards layer

4. Portals and Platform Spatial Data Other Data Documents and Publications Meta-Data and Data Management Functions Content Visualisation and Presentation Data Analysis and Processing Main Shared Platform Services Portals: Main Stakeholders and Initiatives SAEOS Portal SAEOS Portal NSIF Application NSIF Application SAEON Nodes and Initiatives CSIR Risk and Vulnerability Atlas World Data Centre for BHH BioEnergy Atlas SAEOS WDC CSIR SAEON RAVA NSIF BEA Meta-Data and Data Services NSIF Portal Data and Meta-Data

5. SAEOS Components (ß-versions) SAEOS has recently developed open components to do the following: – CS/W harvesting point for meta-data managed in provider databases DC output for now, ISO 19115 output in the work plan – API support interface for CS/W sources – Search facility that understands CS/W Allows subsequent filtering and analysis of search results – Mapping facility that understands standardised data OGC WxS KML GeoRSS SOS NetCDF (under way) … – Mapping facility saves composite maps, incorporating multiple layers from distributed sources, as extended OGC Web Context Documents – Integration between Search components and Map components

6. Experimental Components Fully configurable web data capturing and analysis capability – used for small projects and Citizen Science Captured data is – Immediately available as OGC WFS – Maintains an EML meta-data record in real time ISO 19115 to follow Simple Mediation (brokering) between WFS and Google Charts Data (vector and raster) uploads, styling and publication, plus automated uploads of large data sets

7. On the Horizon Allowing third-party plug-ins to represent standardised data sources Allowing third-party plug-ins to perform searches Developing automated ‘Atlas’ functionality to speed up structured publication of composite maps Linking controlled vocabularies into search facilities and meta-data editors Generic Web Processing Service wrapper that links searches for data sources to parameters required by service Improved support for SOS – including being able to deal with large datasets Wizard-style creation of non-map artefacts from WFS and RDF data sources (charts, directed graphs, etc.)

8. AIP Ideas Test search GUI with GEOSS Broker GEOSS Broker as an option to extend search End-to-end use case: – Search for a web processing service – Invoke search facility/ GEOSS broker to find input data sets – Define meta-data for output, including how it should be published – WFS preferred – Match data set variables to process parameters – Invoke process and publish output/ lined meta-data – Search for result data – Include into composite map – Save map into automated atlas in a target portal – Optionally link chart views to meta-data entry

9. Samples

10. Example: CS/W API and link to DB Link to any CS/W endpoint (in this case, the DB CS/W emulator) Select a request and optionally set filters API constructs POST command for request Sample output can be previewed http://196.213.187.51/PLATFORM_2/MAP/csw_query.asp

11. Example: Search Interface Simple keyword search (‘climate’) http://196.213.187.51/PLATFORM_2/MAP/search_portal.htm Can point to any CS/W Source Some Ideas: Test as front end for GEOSS Broker

12. Example: Search Interface Basic Result Listing: Summaries of meta-data records http://196.213.187.51/PLATFORM_2/MAP/search_portal.htm Details of meta-data records Extent of data set

13. Example: Search Interface Filter the primary result (simple filter) http://196.213.187.51/PLATFORM_2/MAP/search_portal.htm

14. Example: Search Interface Filter the primary result (composite filter) http://196.213.187.51/PLATFORM_2/MAP/search_portal.htm Some Ideas: Prioritised search results based on user metrics, quality meta-data, etc.

15. Example: Search Interface Filter the primary result (composite filter) http://196.213.187.51/PLATFORM_2/MAP/search_portal.htm Some Ideas: Prioritised search results based on user metrics, quality meta-data, etc. Filter the primary result (composite filter) Chart, table and map views of data distribution

16. Example: Search Interface http://196.213.187.51/PLATFORM_2/MAP/search_portal.htm Some Ideas: ‘Density Map’ of data availability Extent of data in detailed map with links to meta-data

17. Example: Map Composition http://196.213.187.51/PLATFORM_2/MAP/index.htm Search facility is available in extended OpenLayers web mapping client. Online resources may include standardised data sources.

18. Example: Map Composition http://196.213.187.51/PLATFORM_2/MAP/index.htm Search facility is available in extended OpenLayers web mapping client. For OGC Services, GetCapabilities is interpreted to show available layers and styles Clicking an online resource leads to interpretation of the link Layer can be previewed. Download options (if any) also supported Selected layer can be added to the current map window

19. Example: Map Composition http://196.213.187.51/PLATFORM_2/MAP/index.htm Layer properties (order, transparency, naming, … can be set. Legend data is retrieved from standard services per layer

20. Example: Map Composition http://196.213.187.51/PLATFORM_2/MAP/index.htm Layer properties (order, transparency, naming, … can be set. Legend data is retrieved from standard services per layer

21. Example: Other Standards http://196.213.187.51/PLATFORM_2/MAP/index.htm Data sources can be a variety of standard services, including SOS Here we show a SOS service endpoint

22. Example: Other Standards http://196.213.187.51/PLATFORM_2/MAP/index.htm SOS GetCapabilities can be analysed to understand the offerings

23. Example: Other Standards http://196.213.187.51/PLATFORM_2/MAP/index.htm Clicking a sensor location (feature of interest) reports the latest values for each phenomenon

24. Example: Other Standards http://196.213.187.51/PLATFORM_2/MAP/index.htm Time series can be viewed based on user-selected start and end dates Some Ideas: Full capability of sensor model to be supported Download data as CSV

25. Example: Map Composition http://196.213.187.51/PLATFORM_2/MAP/index.htm Add additional layers

26. Persist Web Context Documents Load from server storage List of WCDs

27. Data Upload, Styling, and Publication

28. Meta-Data Repository Meta-Data Entry Multiple Custodians Multiple Standards

29. GeoRSS SEARCH RESULT Piped to Map Client

30. Non-Spatial Representations of Data Data captured by Schools Program directly to WFS Mediated HTTP calls to Google Charts

31. NetCDF Integration and Animation

32. Embedding in Other Platforms