6.5.5 Transformation Services
From Geostandards
6 INSPIRE
6.1 Background and Motivation
- 6.1.1 Spatial Data Infrastructures
- 6.1.2 Requirements for a European SDI
- 6.1.3 Existing foundation for a European SDI
- 6.2.1 Background and history
- 6.2.2 The five components of the Directive
- 6.2.3 Implementation, status and schedule
- 6.2.4 Groups and responsibilities within INSPIRE
- 6.2.5 INSPIRE Implementing Rules and INSPIRE Guidance Documents
- 6.2.6 European and Global initiatives in the context of INSPIRE
6.3 Technical Architecture Overview
- 6.3.1 Relationship between the different components, in particular spatial data, metadata, registers, and network services
- 6.3.2 Terminology
6.4 Interoperabilty of spatial data sets / INSPIRE data specifications
- 6.4.1 Requirements of the INSPIRE Directive
- 6.4.2 Interoperability of spatial data
- 6.4.3 INSPIRE data scope
- 6.4.4 Modelling Framework
- 6.4.5 Generic Conceptual Model
- 6.4.6 ISO 19100 series of International Standards
- 6.4.7 Rules for application schemas and feature catalogues
- 6.4.8 Identifier Management
- 6.4.9 Object referencing modelling
- 6.4.10 Coordinate referencing
- 6.4.11 Multi-lingual text and cultural adaptability
- 6.4.12 Data quality
- 6.4.13 Metadata for evaluation and use
- 6.4.14 Multiple representations
- 6.4.15 Consistency between data
- 6.4.16 Portrayal model
- 6.4.17 Conformance
- 6.4.18 Generic Network Model
- 6.4.19 Gazetteers
- 6.4.20 Encoding and data formats
- 6.4.21 INSPIRE registers
- 6.4.22 Annex I data specifications
- 6.4.23 Outlook to Annex II/III data specifications
- 6.4.24 Extensions by countries or communities
The INSPIRE Directive requires, in Article 11(1)(d), Member States to “establish and operate a network of … transformation services, enabling spatial data sets to be transformed with a view to achieving interoperability”. Transformation Service is a special case among the recognized INSPIRE service types, as its function is to help other services in achieving compliance with the relevant INSPIRE specifications. It cannot thus be required at the MS level, if all the existing services already comply with the INSPIRE rules. In many cases the functionality envisaged for a Transformation Service is recommendable to be embedded inside another service type. This can be justified both for performance and service robustness reasons and might be realised, for instance, in the form of a transforming View service or a transforming Download service. When regarded as an individual service instance, the Transformation Service is currently interpreted as a real-time Coordinate Transformation Service, chained with a Download Service for input data. This kind of Transformation Service is seen as a spatial data processing service, capable of transforming the input dataset from a Coordinate Reference System (CRT) into another.
The current recommendation is the usage of an Application Profile of the Web Processing service (WPS) loosly based on the Web Coordinate Transformation Service (WCTS) OGC discussion paper
Reference
Draft INSPIRE Transformation Service Implementing Rule
Draft Technical Guidance Coordinate Transformation Service
| ← previous | Infrastructure for Spatial Information in the European Community (INSPIRE) | next → |
