1 / 16

INSPIRE Service Architecture

INSPIRE Service Architecture. EuroGeographics Network Services Workshop 5-6 February 2008 graham.vowles@ordnancesurvey.co.uk Input provided by Network Services Drafting Team. INSPIRE Documents. INSPIRE Directive. INSPIRE Technical Architecture Overview.

zanta
Download Presentation

INSPIRE Service Architecture

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. INSPIRE Service Architecture EuroGeographics Network Services Workshop 5-6 February 2008 graham.vowles@ordnancesurvey.co.uk Input provided by Network Services Drafting Team

  2. INSPIRE Documents INSPIRE Directive INSPIRE Technical Architecture Overview INSPIRE Network Services Architecture Draft Implementing Rules forDiscovery and View Services (IR1) http://www.ec-gis.org/inspire/reports.cfm#NetworkImplementtingRules

  3. INSPIRE Directive • Requirements for the INSPIRE Network Services are defined in the INSPIRE Directive • Network Services Drafting Team are responsible for defining the INSPIRE Network Services Architecture and the Implementing Rules for the Network Services • Network Services Drafting Team worked with the Metadata and Data Specification Drafting Team to develop the high-level architecture as defined in the INSPIRE Technical Architecture Overview

  4. INSPIRE Technical Architecture Overview • provides a high-level overview of the technical architecture of INSPIRE • supports the discussion within and between the Commission, Drafting Teams, Thematic Working Groups, LMOs and SDICs

  5. DT NS INSPIRE Technical Architecture - Overview Appl. Layer Application and Geoportals Service Bus Service Layer GeoRM layers Registry Service Discovery Service Transf. Service ViewService DownloadService InvokeSDService DT MD DT DS Registers Service Metadata Data Set Metadata Spatial Data Set Data Layer TWG TWG TWG Thematic DS Framework for harmonized DS

  6. Spatial Data • Framework for data specifications (based on ISO 19100 series of standards) • description of each of the 34 spatial data themes • a Generic Conceptual Model • a methodology for the development of harmonised data specifications • guidelines for the encoding of spatial data • Data specifications for the spatial data themes will be developed in the next years based on this framework Up to 34 theme-specific data specifi-cations DT DS Spatial Data Set TWG TWG TWG Thematic DS Framework for harmonized DS

  7. Metadata • Service Metadata • enables the discovery of spatial data services. • service type • operations parameters • geographic information • Data Set Metadata • discover, evaluation and use • keywords • simple search criteria about key characteristics about the data set • Spatial and temporal extent • Metadata • Must be kept consistent with the actual resource DT NS Discovery Service DT MD Service Metadata Data Set Metadata

  8. DT NS Mapping: View => WMS Discovery => CSW Download ~ WFS and more Transformat,~ WCTS OR Coordinate Transf. as WPS Profile + Schema Translation Invoke SD ~tbdService Publish-find-bind pattern Separation between Application layer GeoRM Layer Service Layer Data Layer Network Services • Separation between INSPIRE terms (general, long term,..) and applied specs • Usage of SOAP/ WSDL / … ? Publish Find Bind GeoRM layers Discovery Service Transf. Service ViewService DownloadService InvokeSDService

  9. INSPIRE Network Services Architecture • Provides more detail than the INSPIRE Technical Architecture – Overview document • Follows Services Oriented Architecture principles • Provides the Architecture within which all INSPIRE Services will be implemented – ie the context for INSPIRE Network Services Implementing Rules

  10. INSPIRE Service Types • Discovery, View, Download, Transformation and Invoke Spatial Data Service are mandated by the INSPIRE Directive • Registry Service – an additional service type needed to run an interoperable spatial data infrastructure Application and Geoportals Service Bus GeoRM layers Registry Service Discovery Service Transf. Service ViewService DownloadService InvokeSDService

  11. INSPIRE Service Bus • Proposal is to implement INSPIRE Network Services using SOAP/WSDL based web services • SDICs, LMOs are invited to comment Applications and Geoportals Applications and Geoportals Service Bus INSPIREServices INSPIREServices INSPIREServices INSPIREServices INSPIREServices

  12. Mediator with non-INSPIRE Compatible Services • INSPIRE Network Services can be used to wrap non-INSPIRE compatible services User Geoportal, Applications Provider (e.g. MS, other) Provider (e.g. MS, other) INSPIRE Services INSPIRE Services Interface bridge Interface bridge Undefined interface non INSPIRE compatible Services non INSPIRE compatible Services

  13. Conceptual multi tier architecture of the INSPIRE Geo-portal • The INSPIRE architecture can be structured with multiple tiers, which might be cascaded User User Geoportal, Applications Application,… Provider (e g. EC…) Provider (e.g. MS, other) INSPIRE Services INSPIRE Services Cascades access

  14. eGovernment Integration • Based on European Interoperability Framework (EIF) • It provides standards and guidelines for the implementation national interoperability frameworks • Useful context for Member States when implementing the INSPIRE Directive • INSPIRE Network Services is well aligned with the ongoing work on the new European Interoperability Framework.

  15. Geo Right Management (GeoRM) Application and Geoportals • Annex A describes the possible scenarios how the INSPIRE Services could be invoked using the GeoRM framework Service Bus GeoRM Layers GeoRMServices Identity Price & Order License Registry Service Discovery Service Transf. Service ViewService DownloadService InvokeSDService GeoRM Data

  16. Conclusions • INSPIRE Directive – defines the requirements • INSPIRE Technical Architecture – defines the high-level architecture • INSPIRE Network Services Architecture – defines the architecture for the INSPIRE Network Services Implementing Rules • INSPIRE Network Services IRs – define how Member States implement each of the INSPIRE service types.

More Related