6.4.20 Encoding and data formats

From Geostandards

Jump to: navigation, search

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 Overview and Context

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.22.1 Coordinate reference systems
6.4.22.2 Geographical grid systems
6.4.22.3 Geographical names
6.4.22.4 Administrative units
6.4.22.5 Addresses
6.4.22.6 Cadastral parcels
6.4.22.7 Transport networks
6.4.22.8 Hydrography
6.4.22.9 Protected sites
6.4.23 Outlook to Annex II/III data specifications
6.4.24 Extensions by countries or communities

6.5 Network Services

6.5.1 Network Service Architecture
6.5.2 View Services
6.5.3 Discovery Services
6.5.4 Download Services
6.5.5 Transformation Services
6.5.6 Invoke spatial data service services

6.6 Metadata

6.6.1 Requirements of the INSPIRE Directive
6.6.2 INSPIRE Metadata scope
6.6.3 INSPIRE Metadata elements
6.6.4 Metadata guidelines
6.6.4.1 Implementation according to ISO 19000 series
6.6.4.2 Implementation according to Dublin Core
6.6.4 Relationship to INSPIRE Discovery Services

Spatial data will be accessible via download and view services.

The approach to the encoding of spatial data in INSPIRE can be summarised as follows:

  • Conformant spatial data in INSPIRE conforms to the INSPIRE data specifications.
  • The encoding of the spatial data in INSPIRE depends on the encoding rule chosen for the data.
  • All valid encoding rules conform to EN ISO 19118.
  • A default EN ISO 19136 and CEN ISO/TS 19139-based encoding is specified. Additional or alternative encoding rules may be specified for each application schema.

The encoding rules and application-schema-specific data structure schemas used within INSPIRE are published in guidance documents.

The current version of the GML application schemas is available here.

The following XML instance is an example from the INSPIRE Annex I testing based on version 2.0 of the data specifications (showing a watercourse in Norway). The example follows the general GML encoding rules, the following aspects should be highlighted:

  • the encoding of a geographical name (GN:GeographicalName)
  • the encoding of an INSPIRE identifier (base:Identifier)
  • the encoding of localised text (gmd:LocalisedCharacterString)
  • the encoding of void values (elements with xsi:nil="true")
<HY:Watercourse gml:id="Watercourse.001006033"
   xmlns:GN="urn:x-inspire:specification:gmlas:GeographicalNames:2.0" 
   xmlns:HY="urn:x-inspire:specification:gmlas:Hydrography:2.0" 
   xmlns:base="urn:x-inspire:specification:gmlas:BaseTypes:3.1" 
   xmlns:gmd="http://www.isotc211.org/2005/gmd" 
   xmlns:gml="http://www.opengis.net/gml/3.2" 
   xmlns:xlink="http://www.w3.org/1999/xlink" 
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <gml:identifier codeSpace="http://inspire.jrc.ec.europa.eu/">urn:x-inspire:object:id:NONVEHY:001.FZ</gml:identifier>
  <HY:pointOfInterest nilReason="other:unpopulated" xsi:nil="true"/>
  <HY:neighbour nilReason="unknown" xsi:nil="true"/>
  <HY:hasEmbankment nilReason="other:unpopulated" xsi:nil="true"/>
  <HY:drainsCatchment xlink:href="urn:x-inspire:object:id:NONVEHY:Basin.602"/>
  <HY:shoreline nilReason="other:unpopulated" xsi:nil="true"/>
  <HY:theHydroFacility nilReason="other:unpopulated" xsi:nil="true"/>
  <HY:hasConstruction nilReason="other:unpopulated" xsi:nil="true"/>
  <HY:beginLifespanVersion>1993-07-01T12:00:00 </HY:beginLifespanVersion>
  <HY:endLifespanVersion nilReason="unknown" xsi:nil="true"/>
  <HY:geographicalName>
    <GN:GeographicalName>
      <GN:spelling>
        <GN:SpellingOfName>
          <GN:text>MJERMA/HALDENVASSDRAGET</GN:text>
        </GN:SpellingOfName>
      </GN:spelling>
    </GN:GeographicalName>
  </HY:geographicalName>
  <HY:geometry>
    <gml:LineString gml:id="Watercourse.001006033.Geom_0">
      <gml:posList>59.9415606105 11.6855411646 59.9408389910 11.6834773297</gml:posList>
    </gml:LineString>
  </HY:geometry>
  <HY:hydroId nilReason="other:unpopulated" xsi:nil="true"/>
  <HY:id>
    <base:Identifier>
      <base:localId>001.FZ</base:localId>
      <base:namespace>NONVEHY</base:namespace>
    </base:Identifier>
  </HY:id>
  <HY:localType>
    <gmd:LocalisedCharacterString locale="urn:x-inspire:def:locale:INSPIRE:no">ElvBekk</gmd:LocalisedCharacterString>
  </HY:localType>
  <HY:origin nilReason="other:unpopulated" xsi:nil="true"/>
  <HY:persistence nilReason="other:unpopulated" xsi:nil="true"/>
  <HY:isWfdRiver nilReason="unknown" xsi:nil="true"/>
  <HY:theWfdTransitionalWater nilReason="unknown" xsi:nil="true"/>
  <HY:hasNetworkSegment nilReason="unknown" xsi:nil="true"/>
  <HY:hasGlacier nilReason="other:unpopulated" xsi:nil="true"/>
  <HY:riverbank nilReason="other:unpopulated" xsi:nil="true"/>
  <HY:foreshore nilReason="other:unpopulated" xsi:nil="true"/>
  <HY:theCrossing nilReason="other:unpopulated" xsi:nil="true"/>
  <HY:asNetworkAggregate nilReason="unknown" xsi:nil="true"/>
  <HY:hasManMadeObject nilReason="other:unpopulated" xsi:nil="true"/>
  <HY:isAdminBoundary nilReason="other:unpopulated"/>
  <HY:condition nilReason="other:unpopulated" xsi:nil="true"/>
  <HY:fictitious nilReason="other:unpopulated" xsi:nil="true"/>
  <HY:length uom="m">153.106654548 </HY:length>
  <HY:level nilReason="other:unpopulated" xsi:nil="true"/>
  <HY:tidal nilReason="other:unpopulated" xsi:nil="true"/>
  <HY:waterCourseHierarchy nilReason="other:unpopulated" xsi:nil="true"/>
  <HY:width nilReason="other:unpopulated" xsi:nil="true"/>
</HY:Watercourse>
previous Infrastructure for Spatial Information in the European Community (INSPIRE) next
Personal tools