6.4.8 Identifier Management

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

All features associated with an Annex I/II theme will in general have a object identifier that is

  • unique within INSPIRE
  • persistent (does not change during the lifetime of the feature)
  • traceable (a mechanism exists to find a feature based on its identifier)
  • feasible (can be created based on an existing identifier, if one exists)

This is achieved by constructing an object identifier from two parts:

  • A namespace to identify the data source. The namespace is owned by the data provider and registered in the INSPIRE External Object Identifier Namespaces Register (which does not exits yet). The namespace will usually start with a country identifier, e.g. "NL" for the Netherlands.
  • A local identifier, assigned by the data provider. The local identifier is unique within the namespace, i.e. no other spatial object carries the same unique identifier.

Both the namespace and the local identifier only use the following set of characters (i.e. only letters from the Latin alphabet, digits, underscore, point, and dash are allowed):

  • "A" …"Z"
  • "a"…"z"
  • "0"…"9"
  • "_"
  • "."
  • "-"

If several versions of the same object are part of a data set, an additional version identifier is used. Within the set of all versions of a spatial object, the version identifier is unique. The version identifier has a maximum length of 25 characters.


← previous Infrastructure for Spatial Information in the European Community (INSPIRE) next →
Retrieved from "http://geostandards.geonovum.nl/index.php/6.4.8_Identifier_Management"
Personal tools