CAP Support in Esris Open Source Geoportal Server WMO Information System (WIS) CAP Implementation Workshop Geneva, 6-7 April 2011 Clive Reece

CAN Geoportal Server be used to support CAP ? Outline Geoportal Server and WIS Analysis of CAP specification and system requirements Implementation of CAP using Geoportal Server Next Steps

Geoportal Server and WMO-WIS WMO Weather Information Systems (WIS) need capabilities to 1. Enable user discovery of weather data, products, and services 2. Broker user access to data, products, and services

So, what does Geoportal Server do? …

Geoportal Server Completes the SDI Platform ProvidersConsumers Inventory and Catalog Access and Distribution Search and Discovery

Geoportal Server Customizable web site starter Search metadata and preview geospatial resources Manage, publish, and store metadata View live map services Download data CSW and REST endpoints = Use in Many Other Clients

Open Source Geoportal Server

Geoportal Server Components Geoportal Website Starter Search Widgets (Flex, Silverlight, Javascript) Geoportal Catalog Service Content Management Systems (3 rd Party) Add-Ins for ArcGIS Desktop ArcGIS Explorer REST API GeoRSS/KML Expose service endpoints CSW REST (ATOM, GeoRSS, KML, HTML, JSON) OpenSearch OAI-PMH Z39.50 Support client apps and widgets

CAP Review … CAP is an XML schema 1.3 Structure of the CAP Alert Message Each CAP Alert Message consists of an segment, which may contain one or more segments, each of which may include one or more and/or segments. * * *

CAP Alerting Process Author Someone creates a CAP message Serve The message gets posted to a server and distributed Consume A client software application recieves and displays the message

Analysis: How Could CAP be leveraged in Geoportal? CAPGeoportal XML SchemaCatalogs XML documents Configurable Can handle multiple schema profiles Authoring / Ingesting CAPCan create XML online using a web form Can upload XML Can harvest from collections Serving CAPOGC CSW REST API with multiple output formats: GeoRSS, ATOM, KML, HTML, JSON Consuming CAPEsri web APIs (Flex, Silverlight, Javascript) for search and display

Implementing CAP with Geoportal Server …

Step 1. Create a CAP schema definition

Wis Catalog Step 2 – Question for deployment … Should WMO metadata from a WIS node get mixed in the same service as CAP? Recommend to keep them separate so that CAP client software doesnt get confused or need to filter between CAP messages and other WIS metadata documents Mixed catalog WIS metadata WIS metadata CAP alert CAP alert CAP Catalog WIS metadata WIS metadata CAP alert CAP alert OR

Step 3 – Display of the description? This issue really belongs in the realm of the CAP client software that reads and displays the message.

MASAS Hub II Consuming Tool for Flex

Step 4. Aggregating other CAP feeds Registry of CAP Feeds Harvest multiple feeds into a single CAP catalog Provide distributed search of CAP feeds Demo …

Summary So where does that leave us? Were we successful in supporting CAP with Geoportal? Yes … no programming needed, just custom configuration following the documentation. Things to be continued and improved upon: Customize search User Interface for the CAP-specific ontology Improve tools for creating and displaying the union of the options

Next Steps Post work to date on Geoportal sourceForge Foster user contributions and feedback Resources The one URL to know: - Documentation/JavaDoc links - How to contribute code - Link to sourceForge page

Questions?