FedEO KO 5 June 2007 Slide 1 FedEO Pilot Objectives Slides assembled from various sources, mostly HMA Final Presentation, 28 February 2006, Frascati Jolyon Martin, Pier Giorgio Marchetti, ESA Didier Giacobbo, Philippe Merigot, SPOT IMAGE Yves Coene, SPACEBEL Tom Lankester, Infoterra UK George Percival, OGC et. al. …

FedEO KO 5 June 2007 Slide 2  FedEO Overview  FedEO Architecture & Specifications  FedEO Detailed objectives  Participants and component lists refined  Initial capability demonstration?  FedEO Schedule intermediate dates?

FedEO KO 5 June 2007 Slide 3 Services Categories  Map and Data Access Session #2b : Corentin GUILLO  Sensor Services and Processing Services Session #3b : Ingo SIMONIS, Philippe MERIGOT & Fabrice LEVY  FedEO Catalogue Services and Matadata Models Session #4b : Jolyon Martin  Workflow and Order Session #5b : Yves COENE

FedEO KO 5 June 2007 Slide 4 Federated EO (FedEO) Pilot Introduction  To provide broad European and international venue for operational prototyping of EO requirements Initial definition by ESA, consistent with ESA’s HMA Harmonised access to ESA, National and Eumetsat missions  OGC Interoperability Program Including additional sponsors for FEDEO Pilot Test and validate OGC specifications in a EO context Develop best practices for an operational environment Results migrate to persistent infrastructure made available from HMA-T project & OGC Network

FedEO KO 5 June 2007 Slide 5 OGC Interoperability Program Development Testbed Pilot OGC Network Experiment OGC-II Specification Program Technology Maturation Specifications Implementations Demonstrations Types of OGC-IP Initiatives

FedEO KO 5 June 2007 Slide 6  The approach to describe the architecture follows the RM-ODP model (Reference Model of Open Distributed Processing (ISO/IEC :1998)).  RM-ODP model analyses the systems through 5 different views: The enterprise viewpoint: A viewpoint on the system and its environment that focuses on the purpose, scope and policies for the system. The information viewpoint: A viewpoint on the system and its environment that focuses on the semantics of the information and information processing performed. The service viewpoint: This is the view that correspond to the computation view point. It specifies the GMES HMA services that support the syntactical and semantic interoperability between GSs, clients, EO DAIL The engineering viewpoint: A viewpoint on the system and its environment that focuses on the mechanisms and functions required to support distributed interaction between objects in the system. The technology viewpoint: A viewpoint on the system and its environment that focuses on the choice of technology in that system. Architecture – Methodology – RM-ODP Model

FedEO KO 5 June 2007 Slide 7 Architecture Objectives  Validate the FedEO architecture with use cases outside HMA GMES Contribution Missions provide a neutrally managed overarching distributed infrastructure enabling the interactions among products and data providers, service providers and with end-users, permit service interaction whilst avoiding the service de-localisation (i.e. services remain on the service provider infrastructure), allow easy publishing and orchestration of synchronous and asynchronous EO services for online and offline processes, allow chaining of services into more complex ones, support “subscription” type services and standing orders (e.g. fires active monitoring and alerting), support the evolution and maintenance of services, integrating the HMA Testbed and conformance testing environment as an integral part of the FedEO Portal. allow easy identification of, and access to requested services and products, with progress follow-up until completion, integrate services from multiple domains, e.g. geospatial, meteorological, in-situ, to exploit multi-domain synergies, allow services/data providers to register, provide and promote their products to thematic or local portals, minimise service provider investments by building on open standards.  Further validate the FedEO service specifications refining the Discussion Papers towards Implementation Specifications establish reference implementations (server example and “skeleton”) update client to latest reference versions establish compliance (team engine) tests

FedEO KO 5 June 2007 Slide 8 Enterprise View: Context within GMES

FedEO KO 5 June 2007 Slide 9 Information Viewpoint: Overview  Information Viewpoint main components ISO19115 Collection Metadata ISO Service Metadata GML Schema for Earth Observation Products

FedEO KO 5 June 2007 Slide 10 Information Viewpoint: OGC Earth Observation Products  A base schema (hma) with specializations for Optical High Resolution (ohr), Synthetic Aperture Radar (sar), Atmospheric Instruments (atm) and mission specific (e.g. phr)  GML payload aligned with ISO (19139 schema) and part II draft  Based on GML observation  Radar Altimetery specialisation currently being added sar.xsdohr.xsdatm.xsd hma.xsd smXML - gmd (ISO 19139) Catalogue metadata for mission type Catalogue metadata for EO products gml Schema/ namespace for radar missions Schema/ namespaces for optical missions Schema/ namespaces for atmospheric missions Generic and geometric catalogue metadata phr.xsd xyz.xsd Catalogue metadata for specific mission

FedEO KO 5 June 2007 Slide 11 Information Objectives  Refine GML Application Schema Determine suitability for GEO-Stationary Satellite Data Last Chance to improve the schema before implementation vs. SAR & OHR?  Multi-footprint products?  Occultation measurements?  Others

FedEO KO 5 June 2007 Slide 12 Service Viewpoint: Overview  Overall Goal: a standardized, harmonized set of interfaces that support a service oriented view of the heterogeneous mission ground segments, which can be implemented in a cost-effective manner; enabling the construction of compound / value added services from basic interfaces. Discovery (collection, services) Catalogue (earth observations) Order (archive, subscription, on-line access) Programming (order for acquisitions, mission planning feasibility) Data Access (wcs, Data Portrayal wms) Service Orchestration [ User Management, Monitoring & Control...]

FedEO KO 5 June 2007 Slide 13 ISO Interfaces Overview GML Appl Schema OGC CAT ISO profile EO profile (ISO) OrderProgramming OGC SPS ISO part2 ISO Discovery Catalogue ebRIM profile EO profile (ebRIM) OGC WMS OGC WCS  Intend to depreciate for HMA

FedEO KO 5 June 2007 Slide 14 Service Viewpoint: Discovery  Use of UDDI for service configuration management, and for COTS tools oriented schema interrogation and service chaining  CSW ISO profile found broadly applicable for collection and service metadata discovery providing association between collection and service providing geographic extent to services  ESA supporting development of ebRIM extension pacakage for 19115/19119 OGC

FedEO KO 5 June 2007 Slide 15 Collection Discovery Prototype

FedEO KO 5 June 2007 Slide 16 Discovery Objectives  Establish Reference Implementation of CIM  Establish Best Practices for Collection/Service Discovery in light of use of ebRIM Collection and Sensor relationship Collection Heirarchy representations Harvesting possibilities for HMA Services (capabilities) Critical point is link between Service & Collection Metadata: use of consistent (Universal) Unique Identifiers for collection metadata referenced from within service metadata!  Update Client for Collection Discovery  Establish Conformance test for CIM

FedEO KO 5 June 2007 Slide 17 Service Viewpoint: Catalogue  Catalogue Profiles (supporting EO GML schema) have been prototyped in two flavours  EO AP (based on ISO AP) – intended to be depricated  ebRIM extension package – OGC  Discussion Papers presented to OGC CAT WG to be refined during the FEDEO pilot, intended to become implement specifcations by Dec. latest – requires rapid advancement of ebRIM AP

FedEO KO 5 June 2007 Slide 18 Catalogue Prototype Example - Spot - GetRecords

FedEO KO 5 June 2007 Slide 19 Catalogue Prototype Spot - GetRecordByID

FedEO KO 5 June 2007 Slide 20 Service Viewpoint: Catalogue Prototype Conclusions  ebRIM findings: Client complexity - no greater than other profiles Server complexity – slightly more complex but still basic style-sheet translation from e.g. EO GML Supports Legacy Catalogues (Proxy Implementation Architecture prototyped) Rich and extensible for future developements OGC EO CAT OGC EO CAT Proxy Impl. X CAT Legacy Catalog A GetRecords Legacy native query Legacy native response OGC EO CAT Proxy Impl. Y CAT Legacy Catalog B Replicate Catalogue federation Harvest OGC EO CAT Standalone Impl. Z EO GML  request

FedEO KO 5 June 2007 Slide 21 Catalogue Objectives  Establish reference implementations of ebRIM EO extension package  Update Client for latest version ebRIM EO extension package  Establish Conformance tests for EO profile Extension of ebRIM AP team scripts Schematron validation of EO GML?

FedEO KO 5 June 2007 Slide 22 Service Viewpoint: Order

FedEO KO 5 June 2007 Slide 23 Order Prototype

FedEO KO 5 June 2007 Slide 24 Order Objectives  Complete on-line data access (order) prototype  Revisit? soft type vs. schema for options management user identity within order request or independent? url result access applicable to ftp and wcs?  Update Client for order prototype  Establish compliance tests

FedEO KO 5 June 2007 Slide 25 Service Viewpoint: Programming – Sensor Planning Service operation nameReqdProtocolmand GetCapabilitiesKVPHTTP/GETYesS DescribeSensorXMLSOAP messaging via HTTP/POST NoS DescribeGetFeasibilityXMLSOAP messaging via HTTP/POST NoS DescribeSubmitXMLSOAP messaging via HTTP/POST YesS GetFeasibilityXMLSOAP messaging via HTTP/POST NoA SubmitXMLSOAP messaging via HTTP/POST YesA GetStatusXMLSOAP messaging via HTTP/POST NoS UpdateXMLSOAP messaging via HTTP/POST NoS CancelXMLSOAP messaging via HTTP/POST NoS DescribeResultAccessXMLSOAP messaging via HTTP/POST YesS EstimateSensorWorkloadXMLSOAP messaging via HTTP/POST NoS DelegatedMissionPlanXMLSOAP messaging via HTTP/POST NoS

FedEO KO 5 June 2007 Slide 26 SPS for Earth Observation: New operation : DescribeSensor Request: DescribeSensor SensorID Service: SPS Version Spot SPS Façade DescribeSensor request DescribeSensor response SensorID (should be a virtual sensor) SensorML Document (related to the SensorID) example:

FedEO KO 5 June 2007 Slide 27 SPS for EO: DescribeGetFeasibility operation Request: DescribeGetFeasibility Service: SPS Version SensorID: composed with the following argument sensorShortName: SPOT InstrumentshortName: HRV, HRG, HRS or HRVIR SensorMode: XS, I, J, P, HM or THR Spot SPS Façade DescribeGetFeasibility request DescribeGetFeasibility response

FedEO KO 5 June 2007 Slide 28 Formosat SPS FaçadeSPOT SPS Façade Option 1: meshes level SPS for EO multi sensors: getFeasibility operation: coverage use case Pseudo scene G S Feasibility assessment SPS for EO Constellations and Multi Use SensorID: Formosat Sensor -Feasibility -FeasibilityID: ID issued possibly by the multi-mission level or GS level -Description: Footprint of meshes in GML and attributes User AOI: in GML getFeasibility request SensorID: Spot Sensor SensorID: Formosat Sensor Notification target Parameters: - Region Of Interest in GML - Time Frame - Tasking Parameters applicable for the two sensors Pseudo scene G S Feasibility assessment getFeasibility request SensorID: Spot Sensor -Feasibility -FeasibilityID: ID issued possibly by the multi-mission level or GS level -Description: Footprint of meshes in GML and attributes getFeasibility request getFeasibility response

FedEO KO 5 June 2007 Slide 29 Formosat SPS Façade SPOT SPS Façade SPS for multi sensors: submit operation G S Submit assessment SPS for EO Constellations and Multi Use SensorParam: -SensorID: Spot Sensor -FeasibilityID -Description: Footprint of meshes in GML and Time Frame -SensorID: Formosat Sensor -FeasibilityID -Description: Footprint of meshes in GML and Time Frame submit request G S Submit assessment submit response Submit (collage): submit request submit response taskID:¨SPOTid Status Description estimatedToC taskID:¨Formosatid Status Description estimatedToC taskID:¨SPOTid -Status -Description -estimatedToC taskID:¨Formosatid -Status -Description -estimatedToC taskID:¨SPOTid -Status -Description -estimatedToC taskID:¨Formosatid -Status -Description -estimatedToC

FedEO KO 5 June 2007 Slide 30 Sensor Planning for EO Objectives  Establish Reference Implementation of SPS EO  Establish Best Practices for SPS EO Virtual Sensors vs. flexible options?  Schema dependencies Programming requests defined/refined by roi and meshes? Core plus extensions  Update Client for SPS EO  Establish Conformance test for SPS EO

FedEO KO 5 June 2007 Slide 31 Data Access Services WMS EO profile  Mapping of the EO product structure to WMS service metadata  Default GetMap request / response: &REQUEST=GetMap&CRS=CRS:84 &BBOX=78.105,24.913,94.794, &WIDTH=560&HEIGHT=350 &LAYERS=MER_RR__2P&STYLES=&FORMA T=image/png &TIME= / greyscale false colour pseudo-colour (SAR)(optical) (geo/bio-physical) Copyright ESA 2006

FedEO KO 5 June 2007 Slide 32  Reference Implementation further development and interoperability testing  Best practicises or updates for Link to catalogue? Workflow or Discovery? Discussed in Data Access session  Reference to Image Archive architecture

FedEO KO 5 June 2007 Slide 33 Data Access and Processing Objectives  WCS, WCST  Orthorectification  Objectives

FedEO KO 5 June 2007 Slide 34 Service Orchestration  Objectives

FedEO KO 5 June 2007 Slide 35 Technology view Selected technologies & protocols:  Service Oriented Architecture (SOA)  XML Schema  Message-based SOAP (Simple Object Access Protocol) over HTTP or HTTPS for secure communication  WSDL (Web Services Description Language)  Business Process Execution Language (BPEL)  UDDI service registry  Ws-addressing  Security/Identity management  Security Assertion Markup Language (SAML)  Lightweight Directory Access Protocol (LDAP)  WS-Security  WS-Policy  Inspire  Open Geospatial Consortium GML,WMS, WFS,WCS  OGC CSW2.0 Application Profile ISO19115/19119

FedEO KO 5 June 2007 Slide 36 Technology Objectives  Standard SOAP/HTTP operations for all services e.g. no SOAP attachment for repository objects  Asynch (ws-addressing) response for federated catalogues?

FedEO KO 5 June 2007 Slide 37 FedEO Participants  Others Noted that ESA contribution contains many participants Objectives and contributions further elaborated in break-out- session

FedEO KO 5 June 2007 Slide 38  SSE Demonstration, Registration etc.

FedEO KO 5 June 2007 Slide 39 FedEO Schedule  Mid-September schedule is too optimistic  Mid-October more realistic …  Intermediate results? ebRIM proxy framework mid-July Eumetsat optimistic catalogue search mid-July SPS prototype preliminary feasibility end-June

FedEO KO 5 June 2007 Slide 40  Engineering view … spare slides

FedEO KO 5 June 2007 Slide 41 Engineering view

FedEO KO 5 June 2007 Slide 42 Engineering view – EO DAIL Architecture

FedEO KO 5 June 2007 Slide 43 Engineering view Identity Management Users Mission GS k Policy Management EODAIL (local) Policy store LDAP User Directory Service ws-security ws-addressing SOAP HTTP LDAP User Directory Service DAIL Server Client Identity Server Federation Server Policy Enforcement Point k Identity Server WS - order WS - catalogue Existing GS k systems

FedEO KO 5 June 2007 Slide 44 My Notes – Data Access