ISO 19145:2013

Geographic information - Registry of representations of geographic point location

ISO 19145:2013 specifies the process for establishing, maintaining and publishing registers of representation of geographic point location in compliance with ISO 19135. It identifies and describes the information elements and the structure of a register of representations of geographic point location including the elements for the conversion of one representation to another. ISO 19145:2013 also specifies the XML implementation of the required XML extension to ISO/TS 19135-2, for the implementation of a register of geographic point location representations.

Information géographique — Registre de représentations de localisation de point géographique

L'ISO 19145:2013 spécifie les procédures à suivre pour l'établissement, la mise à jour et la publication de registres de représentations de localisation de point géographique conformes à l'ISO 19135. Elle identifie et décrit les éléments d'information et la structure d'un registre de représentations de localisation de point géographique, y compris les éléments de conversion d'une représentation en une autre. L'ISO 19145:2013 spécifie également l'implémentation à l'aide du langage de balisage extensible (XML) de l'extension XML requise de l'ISO/TS 19135‑2, pour l'implémentation d'un registre de représentations de localisation de point géographique.

Geografske informacije - Register predstavitev lokacije geografskih točk

Ta mednarodni standard določa postopke vzpostavljanja, ohranjanja in objavljanja registrov
predstavitev lokacije geografskih točk v skladu s standardom ISO 19135. Določa in opisuje
elemente informacij in strukturo registrov predstavitev lokacije geografskih točk,
vključno z elementi za pretvarjanje iz ene predstavitve v drugo.
Ta mednarodni standard določa tudi implementacijo XML zahtevanih razširitev XML v standardu ISO/TS 19135‑2 za implementacijo registra predstavitev lokacije geografskih točk.
Register predstavitev lokacije geografskih točk se razlikuje od registra koordinatnega referenčnega sistema (CRS),
ker ta ni namenjen opisu parametrov koordinatnega referenčnega sistema, vključno s podatki, projekcijami, merskimi enotami in redom koordinat, ampak obravnava lokacije geografskih točk v skladu s standardom ISO 6709 in je fizično zastopan v zapisu ali njegovem delu.

General Information

• Status: Published
• Publication Date: 19-Feb-2013
• ICS: 35.240.70 - IT applications in science
• Technical Committee: ISO/TC 211 - Geographic information/Geomatics
• Drafting Committee: ISO/TC 211/WG 7 - Information communities
• Current Stage: 9093 - International Standard confirmed
• Start Date: 05-Dec-2023
• Completion Date: 13-Dec-2025
• Ref Project: SIST ISO 19145:2016 - Geographic information - Registry of representations of geographic point location

Overview

ISO 19145:2013 - "Geographic information - Registry of representations of geographic point location" - defines a standard model and XML encoding for registries that describe how geographic point locations (GPLs) are represented in data. The standard specifies the process for establishing, maintaining and publishing registers of geographic point location representations (GPLR) in compliance with ISO 19135 and provides the required XML extension to ISO/TS 19135‑2. ISO 19145 enables clear identification of a GPL format and the conversion services needed to transform one representation to another, supporting syntactic interoperability of geographic point location information.

Key topics and requirements

• Register lifecycle and conformance: Procedures for creating, maintaining and publishing a register of GPLRs; conformance is checked against the abstract test suite (Annex B).
• Register structure (UML + XML): Defines UML classes and elements (e.g., GPLR_Register, GPLR_Item, GPLR_RepresentationType, GPLR_ConversionService, GPLR_Version, GPLR_Compression, GPLR_Method, GPLR_Interface) and specifies an XML implementation (Annex A) as an extension to ISO/TS 19135‑2.
• Representation metadata: Information elements to describe formats (e.g., ISO 6709 variants, KML, GML point profiles, DCMI, etc.) and to document how a point is physically encoded in a record.
• Conversion and services: Identification and description of converters and conversion services (static/offline and dynamic/online) to transform GPLs between representations.
• Separation from CRS registries: ISO 19145 focuses on syntactic representations of point location encodings, not on coordinate reference system parameters (datum, projection, units), which are addressed by CRS registries.
• XML interoperability: Uses XML, XML Schema and related W3C technologies for machine-readable registry implementations.

Applications and who uses it

ISO 19145 is intended for:

• GIS developers and system integrators implementing data import/export and conversion pipelines.
• Data custodians and registry operators who publish authoritative descriptions of point location encodings.
• Metadata specialists who document spatial data formats and ensure interoperable exchange.
• Software vendors offering conversion services or web services that transform GPL encodings in real time (dynamic conversion) or in batch (static conversion).

Practical uses include enabling automatic detection of point encoding formats, discovering available conversion methods, integrating conversion services into GIS workflows, and improving exchange of geospatial data across applications and organizations.

Related standards

• ISO 6709 (geographic point location encoding)
• ISO 19135 and ISO/TS 19135‑2 (item registration and XML schema implementation)
• ISO 19103, ISO 19115, ISO 19118 (conceptual schema, metadata, encoding)
• W3C XML, XML Schema, XLink (XML technologies used for the XML implementation)

By standardizing how point‑location representations and conversion services are registered, ISO 19145 helps ensure consistent, discoverable and automatable handling of geographic point data across systems.

Standards Content (Sample)

SLOVENSKI STANDARD
01-december-2016
*HRJUDIVNHLQIRUPDFLMH5HJLVWHUSUHGVWDYLWHYORNDFLMHJHRJUDIVNLKWRþN
Geographic information - Registry of representations of geographic point location
Information géographique - Registre des représentations de localisation de point
géographique
Ta slovenski standard je istoveten z: ISO 19145:2013
ICS:
07.040 Astronomija. Geodezija. Astronomy. Geodesy.
Geografija Geography
35.240.70 Uporabniške rešitve IT v IT applications in science
znanosti
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

INTERNATIONAL ISO
STANDARD 19145
First edition
2013-02-15
Geographic information — Registry
of representations of geographic
point location
Information géographique — Registre de représentations de
localisation de point géographique
Reference number
©
ISO 2013
© ISO 2013
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form
or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior
written permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of
the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail [e-mail]
Web www.iso.org
Published in Switzerland
ii © ISO 2013 – All rights reserved

Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Conformance . 1
3 Normative references . 1
4 Terms, definitions and abbreviations . 2
4.1 Terms and definitions . 2
4.2 Abbreviations . 4
5 Role of a register of representations of geographic point location .4
5.1 Overview . 4
5.2 User’s environment and registers . 4
5.3 Static and dynamic data conversion . 5
6 Management of registries and registers . 6
7 Schema of the register . 6
7.1 Context . 6
7.2 GPLR_Register . 7
7.3 GPLR_Item . 8
7.4 Geographic Point Location Representation Object .10
7.5 GPLR_CRSSupport .10
7.6 GPLR_ConversionService .11
7.7 GPLR_Interface .13
7.8 GPLR_Method .13
7.9 GPLR_Compression .13
7.10 GPLR_Version .14
7.11 GPLR_RepresentationType .15
7.12 GPLR_ConversionType .15
Annex A (normative) XML extensions required for registry of representations of geographic
point location .16
Annex B (normative) Abstract test suite .23
Annex C (informative) UML notation .25
Bibliography .30
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out
through ISO technical committees. Each member body interested in a subject for which a technical
committee has been established has the right to be represented on that committee. International
organizations, governmental and non-governmental, in liaison with ISO, also take part in the work.
ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of
electrotechnical standardization.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of technical committees is to prepare International Standards. Draft International
Standards adopted by the technical committees are circulated to the member bodies for voting.
Publication as an International Standard requires approval by at least 75 % of the member bodies
casting a vote.
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. ISO shall not be held responsible for identifying any or all such patent rights.
ISO 19145 was prepared by Technical Committee ISO/TC 211, Geographic information/Geomatics.
iv © ISO 2013 – All rights reserved

Introduction
ISO 6709:2008 standardizes the mechanisms for the interoperability of geographic point location
representations. However, the representation of geographic point locations takes various schemes (e.g.
ISO 6709:1983, DCMI Point encoding scheme, KML, GeoVRML, Natural Area Coding System, ISO 8211,
GML Point Profile) depending of the application in which they are used. Accordingly, ISO 6709:2008
recognizes and supports flexibility in the representation of geographic point locations and the
requirement for universal interpretation. In order to support the use of a variety of geographic point
location representations, ISO 6709:2008 introduces the requirement of a registry of geographic point
location representations. A registry of representations of geographic point location gives access to the
description of the format in which a geographic point location is encoded and also identifies conversion
services to transform the representation of the geographic point location to another representation.
As such, knowing in which format a geographic point location is encoded and the format in which it
must be encoded for its use by a specific application, it can be possible to perform the appropriate
transformation of the representation of a geographic point location. However, this requires that
encoding formats and their descriptions need to be made accessible either as part of the geographic
point location representation itself or from a registry of representations of geographic point locations.
As such, the definition of a standard structure for a registry of representations of geographic point
location is required. Such a registry will support the required flexibility identified in ISO 6709:2008 for
efficient syntactic interoperability of geographic point location information.
This International Standard defines a standard structure of a register in Unified Modelling Language
(UML) that supports the description of geographic point location representation (Clause 7). It also
defines the XML implementation of the register’s UML structure by extending ISO/TS 19135-2, Annex A.
Although the structure for the description of geographic point location representation takes its roots
in ISO 19135, it extends that International Standard with specific requirements to an extent that it goes
beyond the definition of a profile of ISO 19135.
INTERNATIONAL STANDARD ISO 19145:2013(E)
Geographic information — Registry of representations of
geographic point location
1 Scope
This International Standard specifies the process for establishing, maintaining and publishing registers
of representation of geographic point location in compliance with ISO 19135. It identifies and describes
the information elements and the structure of a register of representations of geographic point location
including the elements for the conversion of one representation to another.
This International Standard also specifies the XML implementation of the required XML extension to
ISO/TS 19135-2, for the implementation of a register of geographic point location representations.
A registry of geographic point location representations differs from a coordinate reference system (CRS)
registry as it is not intended to describe the parameters of a CRS including datum, projections, units of
measure, and order of coordinates but is concerned by the manner a geographic point location according
to ISO 6709 is physically represented in a record or part of it.
2 Conformance
To conform to this International Standard, a register of geographic point location representations shall
satisfy all of the conditions specified in the abstract test suite (Annex B).
3 Normative references
The following referenced documents are indispensable for the application of this document. For dated
references, only the edition cited applies. For undated references, the latest edition of the referenced
document (including any amendments) applies.
ISO/TS 19103:2005, Geographic information — Conceptual schema language
ISO 19115:2003, Geographic information — Metadata
ISO 19118:2011, Geographic information — Encoding
ISO 19135:2005, Geographic information — Procedures for item registration
ISO/TS 19135-2:2012, Geographic information - Procedures for item registration — Part 2: XML schema
implementation
ISO/TS 19139:2007, Geographic information — Metadata — XML schema implementation
W3C XMLName, Namespaces in XML 1.0 (Second Edition). W3C Recommendation (16 August 2006)
W3C XMLSchema-1, XML Schema Part 1: Structures Second Edition. W3C Recommendation (28 October 2004)
W3C XMLSchema-2, XML Schema Part 2: Datatypes Second Edition. W3C Recommendation (28 October 2004)
W3C XML, Extensible Markup Language (XML) 1.0 (Fourth Edition), W3C Recommendation (16 August 2006)
W3C XLink, XML Linking Language (XLink) Version 1.0. W3C Recommendation (27 June 2001)
4 Terms, definitions and abbreviations
4.1 Terms and definitions
4.1.1
compression
technique used for the reduction of space used by data
4.1.2
compression service
service (4.1.16) that accomplishes compression (4.1.1)
4.1.3
conversion
transformation from one format (4.1.9) to another
4.1.4
conversion service
service (4.1.16) that invokes a converter (4.1.5)
4.1.5
converter
resource that performs conversion (4.1.3)
Note 1 to entry: The resource can be a device or software.
4.1.6
coordinate
one of a sequence of n numbers designating the position of a point in n-dimensional space
Note 1 to entry: In a coordinate reference system, the coordinate numbers are qualified by units.
[SOURCE: ISO 19111:2007, 4.5]
4.1.7
coordinate tuple
tuple (4.1.18) composed of a sequence of coordinates (4.1.6)
Note 1 to entry: In a coordinate reference system, the coordinate numbers are qualified by units.
[SOURCE: ISO 19111:2007, 4.12, modified — Note 1 to entry has been added.]
4.1.8
dynamic conversion
online and real time conversion (4.1.3) of data
4.1.9
format
language construct that specifies the representation, in character form, of data objects in a record, file,
message, storage device, or transmission channel
[SOURCE: ISO/IEC 2382-15:1999, 15.04.35]
4.1.10
geographic information
information concerning phenomena implicitly or explicitly associated with a location relative to the Earth
[SOURCE: ISO 19101:2002, 4.16]
4.1.11
geographic point location
well defined geographic place described by one coordinate tuple (4.1.7)
2 © ISO 2013 – All rights reserved

4.1.12
geographic point location representation
syntactic description of a geographic point location (4.1.11) in a well known format (4.1.9)
4.1.13
identifier
linguistically independent sequence of characters capable of uniquely and permanently identifying that
with which it is associated
[SOURCE: ISO 19135:2005, 4.1.5]
4.1.14
register
set of files containing identifiers (4.1.13) assigned to items with descriptions of the associated items
[SOURCE: ISO 19135:2005, 4.1.9]
4.1.15
registry
information system on which a register (4.1.14) is maintained
[SOURCE: ISO 19135:2005, 4.1.13]
4.1.16
service
distinct part of the functionality that is provided by an entity through interfaces
[SOURCE: ISO 19119:2005, 4.1]
4.1.17
static conversion
offline process to perform a global conversion (4.1.3) of a large amount of data
4.1.18
tuple
ordered list of values
[SOURCE: ISO 19136:2007, 4.1.63]
4.2 Abbreviations
CRS coordinate reference system
DCMI Dublin Core Metadata Initiative
GeoVRML Geo- Virtual Reality Modelling Language
GIS geographic information system
GML Geography Markup Language
GPL geographic point location
GPLR geographic point location representation
KML Keyhole Markup Language
RFID radio frequency identification
UML Unified Modelling Language
XML eXtensible Markup Language
5 Role of a register of representations of geographic point location
5.1 Overview
The exchange of geographic point locations (GPLs) described by coordinates might use various
representations or formats. To use such information properly in applications, a GPL must be clear about
the representation with which it complies. Then, conversion mechanisms can be applied to transform
exchanged GPLs into systems’ internal representations for their appropriate usage assuming that the
internal representation is also registered and services are available.
Registers give the flexibility to manage geographic point location representations (GPLRs). Registers of
GPLRs made publicly available as a file or web service enhance the interoperability of GPLs by clearly
identifying how one GPL is represented and how it can be converted in another representation.
This clause highlights the role of registers of GPLRs for geographic information interoperability, especially
for the conversion of one GPLR into another through different environments, including static vs. dynamic.
5.2 User’s environment and registers
The role of a register invoked by a user’s environment is depicted in Figure 1. In a user’s environment,
a GIS application typically gets its input data from an external data repository. Usually, that data needs
to be converted into the internal representation of the user’s GIS environment. This is made possible
through a geographic point location converter service, which first searches in a register environment
for possible transformation (i.e. search for specifications) and requests to the register environment the
required information to transform the GPLR into the user’s GIS environment (i.e. request for specification).
To this end, the geographic point location converter service passes the identification of the GPLR from the
external data source to the register’s environment.
In the register’s environment, it is the register service that receives the request. Using the identification
of the GPLR passed by the conversion service, it gets the specification of the representation from the
register (i.e. database of geographic point location representation) including the possible conversions
into other representations and replies to the conversion service. Finally, the conversion service gets
the description information (i.e. geographic point location specifications) of the representation including
4 © ISO 2013 – All rights reserved

known conversions to other representation and the geographic point location converter service will
decide which one bests fit the user’s GIS environment.
Geographic
point location
custodian
Geographic
External point location
Data speci
ications
Request for
speci
ication
Search for
speci
ications
Geographic
point location Register
converter
Geographic
Data base of
point location
GIS
Geographic
speci
ication
point location
representations
User’s
environment
Figure 1 — User’s environment and register
5.3 Static and dynamic data conversion
Two types of data conversion mechanism are recognized: static conversion and dynamic conversion.
Static data conversion consists usually in an offline process to perform a global conversion of a large
amount of data. One such conversion is performed in batch conversion of static geographic data sets such
as digital maps from one format to another. Another consists in the fusion process that integrates multiple
geographic data sets represented by various formats in a common data set under a unique format.
Dynamic data conversion refers to an online and real-time processing mechanism. This means that a
GPL can be imported or exported through a wireless network, converted, and used by a mobile terminal
such as in telematics. For example, the location of moving features can be tracked globally by RFID
sensors passing through the distributed RFID gateways where the various GPL may be managed in and
converted from various coordinate systems and representations.
Consequently, a register of representations of geographic point locations serves in static and dynamic
conversions as a resource to identify the representation format in which a GPL is encoded, to support the
decoding of the GPL by the application (online or offline), and to support the encoding process in another
format representation as required.
6 Management of registries and registers
Several actors are needed in the maintenance of registers, each one playing specific roles. ISO 19135
identifies and describes the following actors:
— Control body;
— Register manager;
— Register owner;
— Registry manager;
— Submitting organization.
The management of registries and registers shall be as specified in ISO 19135.
7 Schema of the register
7.1 Context
Clause 7 specifies the content and structure of the register of GPLR in a UML schema (see Annex C
for a summary of UML notation). The schema includes only one package but refers to classes from
the ISO/TS 19103 Conceptual Schema Language package, the ISO 19115 Metadata package, and the
ISO 19135 Procedures for registration package (Figure 2). It includes information about the register
itself and information about representations of geographic point locations (Figure 3).
ISO 19135:2005 Procedures for Registration
(from ISO 19135-All Procedures for Registration)
ISO 19145 Registry GPL representations
ISO 19115:2003 Metadata
(from ISO 19115-All Metadata)
(from ISO TC211)
ISO 19103:2005 Schema Language
(from ISO 19103 Conceptual Schema Language)
Figure 2 — GPLR package dependencies
6 © ISO 2013 – All rights reserved

ISO 19135:2005 Procedures for
GPLR_Register
Registration::RE_Register
{leaf}
+register 1.*
Content
+containedItem 1.*
+containedItem 1.*
+outFormat
ISO 19135:2005 Procedures for
GPLR_Item GPLR_ConversionService
1.*
+converter
Registration::RE_RegisterItem
{leaf} {root,leaf}
0.*
+crsSupport 1 0.1 +compressionTechnique
GPLR_CRSSuport GPLR_Compression
{root,leaf} {root,leaf}
Figure 3 — Overview of the UML GPLR register’s schema
7.2 GPLR_Register
7.2.1 Semantics
The class GPLR_Register (Figure 4) specifies information about a register of geographic point location
representations. The GPLR_Register class is essentially a subclass of RE_Register from ISO 19135 and as
such inherits all its properties, relations, and behaviours (see ISO 19135:2005, 8.2).
7.2.2 Content
The association Content aggregates GPLR_Items that are parts of the GPLR_Register. This association
is essentially the counterpart of the Content association between RE_Register and RE_RegisterItem
of ISO 19135.
ISO 19135:2005 Procedures for Registration::
RE_Register
+ name :CharacterString
+ contentSummary :CharacterString GPLR_Register
+ uniformResourceIdentiier :CI_OnlineResource [1.*]
{leaf}
+ operatingLanguage :RE_Locale
+ alternativeLanguages :Set constraints
+ version :RE_Version [0.1]
{count(self.version +self.dateOfLastChange) >=1}
+ dateOfLastChange :Date[0.1]
constraints
{count(self.version +self.dateOfLastChange) >=1}
Content
+register 1.*
Content
+containedItem 1.*
+containedItem 1.*
GPLR_Item
{leaf}
ISO 19135:2005 Procedures for
Registration::RE_RegisterItem
constraints
{count(self.legalConstraints.accessConstraints) >=1}
Figure 4 — GPLR_Register
7.3 GPLR_Item
7.3.1 Semantics
The class GPLR_Item (Figure 5) specifies information that describes geographic point location
representations. The GPLR_Item class is essentially a subclass of RE_RegisterItem from ISO 19135 and as
such inherits all its properties, relations, and behaviours (see ISO 19135:2005, 8.8). It adds five attributes
and three association roles: gplrID, specificationName, version, legalConstraints, type, crsSupport,
converter, and compressionTechnique. This information provides the details on how a geographic point
location is rendered, compressed, and can be converted into another representation.
7.3.2 gplrID
The mandatory attribute gplrID consists in a designator that uniquely distinguishes from others a
specific geographic point location representation within the context of the register. It is intended to be
used for information processing. It is represented by a CharacterString (see ISO/TS 19103).
7.3.3 specificationName
The mandatory attribute specificationName designates a specific geographic point location
representation. A specific geographic point location representation is represented by a CI_Citation (see
ISO 19115). In CI_Citation, the attribute title identifies the specific name of the geographic point location
representation and the attribute citedResponsibleParty provides the details of the resources related to
the geographic point location representation. In the context of this International Standard, these two
attributes are mandatory.
7.3.4 version
The mandatory attribute version provides information about the specific release of the geographic point
location representation. It is represented by a GPLR_Version.
8 © ISO 2013 – All rights reserved

ISO 19135:2005 Procedures for Registration::RE_RegisterItem
+ itemIdentiier :Integer
+ name :CharacterString
+ /status :RE_ItemStatus
+ dateAccepted :Date [0.1]
+ dateAmended :Date [0.1]
+ deinition :CharacterString
+ description :CharacterString [0.1] GPLR_Register
+ ieldOfApplication :Set [0.1]
{leaf}
+ alternativeExpressions :Set [0.1]
Content
+containedItem 1.*
GPLR_Item
«CodeList»
GPLR_RepresentationType
{leaf}
+converter
{root,leaf}
GPLR_ConversionService
+ gplrID :CharacterString
+ text
{root,leaf}
+ speciicationName :CI_Citation
0.*
+ binary
+ version :GPLR_Version
+ XML
+ legalConstraints :MD_LegalConstraints [0.*]
+ type :GPLR_RepresentationType = text
+compressionTechnique
GPLR_Compression
constraints
GPLR_Version
{root,leaf}
0.1
{count(self.legalConstraints.accessConstraints) >= 1}
{leaf}
Constraint information::
+crsSupport 1
MD_LegalConstraints
GPLR_CRSSupport
{root,leaf}
«datatype»
Citation and responsible party
information::CI_Citation
«type»
Text::CharacterString
Figure 5 — GPLR_Item
7.3.5 legalConstraints
The optional attribute legalConstraints identifies whether or not the geographic point location
representation can be used only under legal rights, restrictions, and prerequisites. It shall use an
MD_LegalConstraints type as specified in ISO 19115. When a legal constraint is documented, at least
accessConstraints must be documented.
7.3.6 type
The mandatory attribute type provides the encoding type of a geographic point location representation.
It uses the code lists GPLR_RepresentationType. Accordingly, a GPL representation can be encoded as
text, binary, or XML.
7.3.7 compressionTechnique
The optional association role compressionTechnique identifies the mechanism used to reduce the size of
the geographic point location representation. It is described by a GPLR_Compression.
7.3.8 converter
The optional association role converter identifies the conversion tools or services that can transform
this geographic point location representation into another one. It uses a GPLR_ConversionService.
7.3.9 crsSupport
The mandatory association role crsSupport identifies if the geographic point location representation
provides support to coordinate reference systems. It is described by a GPLR_CRSSupport.
7.4 Geographic Point Location Representation Object
A geographic point location register is simple, i.e. it contains a single item class. Accordingly, the
register has one unique containedItem of the type of RE_ItemClass, which is Geographic Point Location
Representation. The GPLR_Register and all containedItems of the GPLR_Item class refer to this Geographic
Point Location Representation. This is illustrated in Figure 6.
ISO 19135 Procedures for
GPLR_Register
Registration::RE_Register
{leaf}
{root}
ContentDescription
ContentDescription
+containedItemClass 1.*
+containedItemClass 1
ISO 19135 Procedures for Registration::
RE_ItemClass
Geographic Point
{root}
Content Content
Location
+ name: CharacterString
Representation
+ technicalStandard: CI_Citation
+ alternativeLanguages: Set
+itemClass 1
+itemClass
Categorization
Categorization
+containedItem 1.*
+containedItem
1.*
ISO 19135 Procedures for
Registration::
GPLR_Item
RE_RegisterItem
{leaf}
{root}
Figure 6 — Geographic Point Location Representation Object
7.5 GPLR_CRSSupport
7.5.1 Semantics
The class GPLR_CRSSupport (Figure 7) specifies information about the support of coordinate reference
systems by the register using two attributes and one association role: supported, fixed, and crs.
7.5.2 supported
The mandatory derived attribute supported identifies whether or not the geographic point location
representation supports at least one coordinate reference system. It shall use a Boolean type as specified
in ISO/TS 19103. If a crs instance is associated with a GPLR_CRSSupport instance, then the attribute
supported is set to true, otherwise it is set to false.
10 © ISO 2013 – All rights reserved

GPLR_Item
{leaf}
constraints
{count(self.legalConstraints.accessConstraints) >= 1}
«enumeration»
Truth::Boolean
{root}
+crsSupport 1
GPLR_CRSSupport
{root.leaf}
+ /supported :Boolean
+ /ix ed :Boolean [0.1]
constraints
{crs ->isEmpty() = false implies supported = true}
{crs -> size() = 1 implies ix ed = true}
+crs 0.*
Reference system information::
MD_ReferenceSystem
Figure 7 — GPLR_CRSSupport
7.5.3 fixed
If coordinate reference system is supported, the optional derived attribute fixed when set to true
identifies that the geographic point location representation supports only one coordinate reference
system, and when set to false identifies that the geographic point location representation supports
multiple coordinate reference systems. It uses a Boolean type (see ISO/TS 19103).
7.5.4 crs
The optional association role crs identifies the coordinate reference systems that are supported by the
geographic point location representation. It uses an MD_ReferenceSystem type (see ISO 19115).
7.6 GPLR_ConversionService
7.6.1 Semantics
The class GPLR_ConversionService (Figure 8) specifies information about converters to transform a
geographic point location representation into another. The class uses four attributes and two association
roles: name, description, uniformResourceIdentifier, conversionType, invocationInterface and outFormat.
7.6.2 name
The mandatory attribute name contains a human readable designator that denotes a conversion tool or
a conversion service. A conversion service name shall be unique within a register. It is represented by a
CharacterString (see ISO/TS 19103).
GPLR_ConversionService
+outFormat
{root.leaf}
GPLR_Item
0.*
+ name :CharacterString
{leaf} 1.*
+converter
+ description :CharacterString [0.1]
+ uniformResourceIdentiier :CI_OnlineResource [0.*]
0.*
0.*
+ conversionType :GPLR_ConversionType
«CodeList»
+invocationInterface 0.1
GPLR_ConversionType
{root.leaf}
GPLR_Interface
+ static
+ dynamic
«type»
+method 1.*
Text::CharacterString
GPLR_Method
«datatype»
+ invocationName :CharacterString
Citation and responsible party
+ parameters :RecordType [0.*]
information::CI_OnlineResource
+ returnValues :RecordType [0.*]
Figure 8 — GPLR_ConversionService
7.6.3 description
The optional attribute description provides a narrative overview or brief explanation of the conversion
tool or conversion service. The description shall inform on the various processes that are involved in the
conversion. It uses a CharacterString (see ISO/TS 19103).
7.6.4 uniformResourceIdentifier
The optional attribute uniformResourceIdentifier provides URLs to online references of resources associated
with the conversion tool or conversion service. It is represented by a CI_OnlineResource (see ISO 19115).
7.6.5 conversionType
The mandatory attribute conversionType identifies whether the conversion is processed online or
offline in batch mode for example. It uses the GPLR_ConversionType code list. Accordingly, a GPLR_
ConversionService can be identified static or dynamic.
7.6.6 invocationInterface
The optional association role invocationInterface describes the interaction mechanism by which the
conversion service can be invocated. An invocation interface is documented by a GPLR_Interface.
7.6.7 outFormat
The mandatory association role outFormat identifies the various geographic point location
representations that the conversion tool or conversion service can generate. Each outFormat instance is
described by a GPLR_Item.
12 © ISO 2013 – All rights reserved

7.7 GPLR_Interface
7.7.1 Semantics
The class GPLR_Interface (Figure 8) specifies the methods that compose the invocation interface of
the conversion.
7.7.2 method
The mandatory association role method identifies the various methods that are included in a GPLR_
Interface. A method is described by a GPLR_Method.
7.8 GPLR_Method
7.8.1 Semantics
The class GPLR_Method (Figure 8) specifies the elements that describe a method of an interface. It has
three attributes: invocationName, parameters, and returnValues.
7.8.2 invocationName
The mandatory attribute invocationName is a human readable designator that denotes the method.
A method name shall be unique within an interface. It is represented by a CharacterString (see
ISO/TS 19103).
7.8.3 parameters
The optional attribute parameters describe the input values involved in the method. Parameters
are represented by a RecordType that specifies names and types of the parameters involved (see
ISO/TS 19103).
7.8.4 returnValues
The optional attribute returnValues describes the output values returned by the method. returnValues
are represented by a RecordType that specifies names and types of the elements returned (see
ISO/TS 19103).
7.9 GPLR_Compression
7.9.1 Semantics
The class GPLR_Compression (Figure 9) specifies information about the compression technique that a
specific geographic point location representation uses. It has four attributes: name, description, version,
and compressionService.
7.9.2 name
The mandatory attribute name designates a specific compression mechanism. It is represented by a CI_
Citation (see ISO 19115). In CI_Citation, the attribute title identifies the specific name of the compression
mechanism and the attribute citedResponsibleParty provides details about resources related to the
compression mechanism.
7.9.3 description
The optional attribute description provides a narrative overview or brief explanation of the compression
technique. It uses a CharacterString (see ISO/TS 19103).
«type» «datatype»
GPLR_Register
Text::CharacterString Citation and responsible party
{leaf}
information::CI_OnlineResource
Content
GPLR_Compression
+containedItem 1.*
{root.leaf}
+compressionTechnique
+ name :CI_Citation
GPLR_Item
+ description :CharacterString [0.1]
{leaf}
0.1
+ version :GPLR_Version [0.1]
+ compressionService :CI_OnlineResource [0.*]
+crsSupport 1
GPLR_CRSSupport
GPLR_Version
{root,leaf} {leaf}
Figure 9 — GPLR_Compression
7.9.4 version
The optional attribute version provides information about the release of the compression technique. It is
represented by a GPLR_Version.
7.9.5 compressionService
The optional attribute compressionService provides URLs to online services or downloadable tools that
perform the compression. Each instance of compressionService is represented by a CI_OnlineResource
(see ISO 19115).
7.10 GPLR_Version
7.10.1 Semantics
The class GPLR_Version (Figure 10) specifies information about the release of a resource. It inherits from
RE_Version (see ISO 19135) and adds to the two RE_Version attributes one additional attribute to include
a possible amendment to a given version. Therefore the class uses three attributes: versionNumber,
versionDate and amendmentNumber.
7.10.2 versionNumber
The mandatory attribute versionNumber contains a constrained CharacterString (see ISO/TS 19103) that
identifies the version and consists of a < first positive integer > < . > < second positive integer > < letters > :
a) < first positive integer > : major version designation
b) < . > : delimiter
c) < second positive integer > : optional minor version designation
d) < letters > : optional minor sub-version designation
EXAMPLE 2.1a
14 © ISO 2013 – All rights reserved

ISO 19135:2005 Procedures for
Registration::RE_Version
{root}
+ versionNumber :CharacterString
+ versionDate :Date
GPLR_Version
{leaf}
+ amendmentNumber :CharacterString [0.1]
Figure 10 — GPLR_Version
7.10.3 versionDate
The mandatory attribute versionDate specifies the date of the release. It is represented by a Date (see
ISO/TS 19103).
7.10.4 amendmentNumber
The optional attribute amendmentNumber contains a CharacterString (see ISO/TS 19103) that denotes a
specific amendment associated with the resource version.
7.11 GPLR_RepresentationType
GPLR_RepresentationType is a code list that specifies the encoding method used for the representation
of the geographic point location.
Table 1 — Encoding method used for the representation of the geographic point location
Value Semantics
text The geographic point location is represented in text format other than XML, but
using a text encoding method such as in ISO/IEC 10646.
binary The geographic point location is represented in binary format, i.e. not using a text
encoding method.
XML The geographic point location is represented in XML format.
7.12 GPLR_ConversionType
GPLR_ConversionType is a code list that specifies the processing mechanism used to convert geographic
point location representations.
Table 2 — Processing mechanism used to convert geographic point location representations
Value Semantics
a
static Offline process to perform a global conversion of a large amount of data.
dynamic Online and real-time processing mechanism.
a
It includes batch conversion of static geographic data sets from one format to another and integration of multiple
geographic data sets from various formats in one common data set in a unique format.
Annex A
(normative)
XML extensions required for registry of representations of
geographic point location
A.1 XML schema implementation
A register of items of representation of geographic point location is described in UML as one specific
package and has dependencies with other packages (see Clause 7). This annex provides an XML
implementation for the encoding of ISO 19145 compliant registers, which extends on the XML
implementation of ISO 19135, defined in ISO/TS 19135-2. The XML schema defined in this annex shall
conform to the rules outlined in ISO 19118 and ISO/TS 19139.
The XML implementation of this International Standard defines the namespace http://www.isotc211.
org/2005/gplr (Figure A.1) where the namespace prefix gplr stands for Geographic Point Location
Representation.
The details of the XML description of all the parts that form an ISO 19145 XML register are provided in B.2.
A.2 XML Schema of the registry of representations of geographic point location
A.2.1 Geographic point location representation item
A.2.1.1 Introduction
A.2.1 documents the XML schema of the classes that are included in the description of the register of
representation of geographic point location.
Figure A.1 shows the namespace used to implement ISO 19145 along with its dependencies on the
namespaces defined in ISO/TS 19135-2 and ISO/TS 19139, used to implement ISO 19135 and ISO 19115
and the related standards, respectively.
16 © ISO 2013 – All rights reserved

«xmlNamespace»
gplr
ISO 19145 Registry GPL representations
«implement»
(from ISO TC211)
«xmlNamespace»
gco
ISO 19103 Schema Language
«import»
«implement»
(from ISO TC211)
«xmlNamespace»
gmd
ISO 19115 Metadata
«import»
«implement»
(from ISO TC211)
«xmlNamespace»
grg
ISO 19135 Procedures for Registration
«import»
«implement»
(from ISO TC211)
Figure A.1 — XML namespaces
For the XML schema element definition hereafter, the following illustrates the typical schema header:

w3.org/1999/xlink”
xmlns:gco=”http://www.isotc211.org/2005/gco” xmlns:gmd=”http://www.isotc211.
org/2005/gmd”
xmlns:grg=”http://www.isotc211.org/2005/grg” xmlns:gplr=”http://www.isotc211.
org/2005/gplr”
targetNamespace=”http://www.isotc211.org/2005/gplr” elementFormDefault=”qualified”
version=”0.1”>

This file was generated from ISO 19145 UML class diagrams xs:documentation>

schemaLocation=”http://standards.iso.org/ittf/
PubliclyAvailableStandards/ISO_19139_Schemas/
gco/gco.xsd”/>
schemaLocation=”http://standards.iso.org/ittf/
PubliclyAvailableStandards/ISO_19139_Schemas/
gmd/gmd.xsd”/>
schemaLocation=”http://standards.iso.org/ittf/
PubliclyAvailableStandards/ISO_19135-
2_Schemas/grg.xsd”/>

A.2.1.2 Namespace organization
The namespace g
...

INTERNATIONAL ISO
STANDARD 19145
First edition
2013-02-15
Geographic information — Registry
of representations of geographic
point location
Information géographique — Registre de représentations de
localisation de point géographique
Reference number
©
ISO 2013
© ISO 2013
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form
or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior
written permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of
the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail [e-mail]
Web www.iso.org
Published in Switzerland
ii © ISO 2013 – All rights reserved

Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Conformance . 1
3 Normative references . 1
4 Terms, definitions and abbreviations . 2
4.1 Terms and definitions . 2
4.2 Abbreviations . 4
5 Role of a register of representations of geographic point location .4
5.1 Overview . 4
5.2 User’s environment and registers . 4
5.3 Static and dynamic data conversion . 5
6 Management of registries and registers . 6
7 Schema of the register . 6
7.1 Context . 6
7.2 GPLR_Register . 7
7.3 GPLR_Item . 8
7.4 Geographic Point Location Representation Object .10
7.5 GPLR_CRSSupport .10
7.6 GPLR_ConversionService .11
7.7 GPLR_Interface .13
7.8 GPLR_Method .13
7.9 GPLR_Compression .13
7.10 GPLR_Version .14
7.11 GPLR_RepresentationType .15
7.12 GPLR_ConversionType .15
Annex A (normative) XML extensions required for registry of representations of geographic
point location .16
Annex B (normative) Abstract test suite .23
Annex C (informative) UML notation .25
Bibliography .30
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out
through ISO technical committees. Each member body interested in a subject for which a technical
committee has been established has the right to be represented on that committee. International
organizations, governmental and non-governmental, in liaison with ISO, also take part in the work.
ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of
electrotechnical standardization.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of technical committees is to prepare International Standards. Draft International
Standards adopted by the technical committees are circulated to the member bodies for voting.
Publication as an International Standard requires approval by at least 75 % of the member bodies
casting a vote.
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. ISO shall not be held responsible for identifying any or all such patent rights.
ISO 19145 was prepared by Technical Committee ISO/TC 211, Geographic information/Geomatics.
iv © ISO 2013 – All rights reserved

Introduction
ISO 6709:2008 standardizes the mechanisms for the interoperability of geographic point location
representations. However, the representation of geographic point locations takes various schemes (e.g.
ISO 6709:1983, DCMI Point encoding scheme, KML, GeoVRML, Natural Area Coding System, ISO 8211,
GML Point Profile) depending of the application in which they are used. Accordingly, ISO 6709:2008
recognizes and supports flexibility in the representation of geographic point locations and the
requirement for universal interpretation. In order to support the use of a variety of geographic point
location representations, ISO 6709:2008 introduces the requirement of a registry of geographic point
location representations. A registry of representations of geographic point location gives access to the
description of the format in which a geographic point location is encoded and also identifies conversion
services to transform the representation of the geographic point location to another representation.
As such, knowing in which format a geographic point location is encoded and the format in which it
must be encoded for its use by a specific application, it can be possible to perform the appropriate
transformation of the representation of a geographic point location. However, this requires that
encoding formats and their descriptions need to be made accessible either as part of the geographic
point location representation itself or from a registry of representations of geographic point locations.
As such, the definition of a standard structure for a registry of representations of geographic point
location is required. Such a registry will support the required flexibility identified in ISO 6709:2008 for
efficient syntactic interoperability of geographic point location information.
This International Standard defines a standard structure of a register in Unified Modelling Language
(UML) that supports the description of geographic point location representation (Clause 7). It also
defines the XML implementation of the register’s UML structure by extending ISO/TS 19135-2, Annex A.
Although the structure for the description of geographic point location representation takes its roots
in ISO 19135, it extends that International Standard with specific requirements to an extent that it goes
beyond the definition of a profile of ISO 19135.
INTERNATIONAL STANDARD ISO 19145:2013(E)
Geographic information — Registry of representations of
geographic point location
1 Scope
This International Standard specifies the process for establishing, maintaining and publishing registers
of representation of geographic point location in compliance with ISO 19135. It identifies and describes
the information elements and the structure of a register of representations of geographic point location
including the elements for the conversion of one representation to another.
This International Standard also specifies the XML implementation of the required XML extension to
ISO/TS 19135-2, for the implementation of a register of geographic point location representations.
A registry of geographic point location representations differs from a coordinate reference system (CRS)
registry as it is not intended to describe the parameters of a CRS including datum, projections, units of
measure, and order of coordinates but is concerned by the manner a geographic point location according
to ISO 6709 is physically represented in a record or part of it.
2 Conformance
To conform to this International Standard, a register of geographic point location representations shall
satisfy all of the conditions specified in the abstract test suite (Annex B).
3 Normative references
The following referenced documents are indispensable for the application of this document. For dated
references, only the edition cited applies. For undated references, the latest edition of the referenced
document (including any amendments) applies.
ISO/TS 19103:2005, Geographic information — Conceptual schema language
ISO 19115:2003, Geographic information — Metadata
ISO 19118:2011, Geographic information — Encoding
ISO 19135:2005, Geographic information — Procedures for item registration
ISO/TS 19135-2:2012, Geographic information - Procedures for item registration — Part 2: XML schema
implementation
ISO/TS 19139:2007, Geographic information — Metadata — XML schema implementation
W3C XMLName, Namespaces in XML 1.0 (Second Edition). W3C Recommendation (16 August 2006)
W3C XMLSchema-1, XML Schema Part 1: Structures Second Edition. W3C Recommendation (28 October 2004)
W3C XMLSchema-2, XML Schema Part 2: Datatypes Second Edition. W3C Recommendation (28 October 2004)
W3C XML, Extensible Markup Language (XML) 1.0 (Fourth Edition), W3C Recommendation (16 August 2006)
W3C XLink, XML Linking Language (XLink) Version 1.0. W3C Recommendation (27 June 2001)
4 Terms, definitions and abbreviations
4.1 Terms and definitions
4.1.1
compression
technique used for the reduction of space used by data
4.1.2
compression service
service (4.1.16) that accomplishes compression (4.1.1)
4.1.3
conversion
transformation from one format (4.1.9) to another
4.1.4
conversion service
service (4.1.16) that invokes a converter (4.1.5)
4.1.5
converter
resource that performs conversion (4.1.3)
Note 1 to entry: The resource can be a device or software.
4.1.6
coordinate
one of a sequence of n numbers designating the position of a point in n-dimensional space
Note 1 to entry: In a coordinate reference system, the coordinate numbers are qualified by units.
[SOURCE: ISO 19111:2007, 4.5]
4.1.7
coordinate tuple
tuple (4.1.18) composed of a sequence of coordinates (4.1.6)
Note 1 to entry: In a coordinate reference system, the coordinate numbers are qualified by units.
[SOURCE: ISO 19111:2007, 4.12, modified — Note 1 to entry has been added.]
4.1.8
dynamic conversion
online and real time conversion (4.1.3) of data
4.1.9
format
language construct that specifies the representation, in character form, of data objects in a record, file,
message, storage device, or transmission channel
[SOURCE: ISO/IEC 2382-15:1999, 15.04.35]
4.1.10
geographic information
information concerning phenomena implicitly or explicitly associated with a location relative to the Earth
[SOURCE: ISO 19101:2002, 4.16]
4.1.11
geographic point location
well defined geographic place described by one coordinate tuple (4.1.7)
2 © ISO 2013 – All rights reserved

4.1.12
geographic point location representation
syntactic description of a geographic point location (4.1.11) in a well known format (4.1.9)
4.1.13
identifier
linguistically independent sequence of characters capable of uniquely and permanently identifying that
with which it is associated
[SOURCE: ISO 19135:2005, 4.1.5]
4.1.14
register
set of files containing identifiers (4.1.13) assigned to items with descriptions of the associated items
[SOURCE: ISO 19135:2005, 4.1.9]
4.1.15
registry
information system on which a register (4.1.14) is maintained
[SOURCE: ISO 19135:2005, 4.1.13]
4.1.16
service
distinct part of the functionality that is provided by an entity through interfaces
[SOURCE: ISO 19119:2005, 4.1]
4.1.17
static conversion
offline process to perform a global conversion (4.1.3) of a large amount of data
4.1.18
tuple
ordered list of values
[SOURCE: ISO 19136:2007, 4.1.63]
4.2 Abbreviations
CRS coordinate reference system
DCMI Dublin Core Metadata Initiative
GeoVRML Geo- Virtual Reality Modelling Language
GIS geographic information system
GML Geography Markup Language
GPL geographic point location
GPLR geographic point location representation
KML Keyhole Markup Language
RFID radio frequency identification
UML Unified Modelling Language
XML eXtensible Markup Language
5 Role of a register of representations of geographic point location
5.1 Overview
The exchange of geographic point locations (GPLs) described by coordinates might use various
representations or formats. To use such information properly in applications, a GPL must be clear about
the representation with which it complies. Then, conversion mechanisms can be applied to transform
exchanged GPLs into systems’ internal representations for their appropriate usage assuming that the
internal representation is also registered and services are available.
Registers give the flexibility to manage geographic point location representations (GPLRs). Registers of
GPLRs made publicly available as a file or web service enhance the interoperability of GPLs by clearly
identifying how one GPL is represented and how it can be converted in another representation.
This clause highlights the role of registers of GPLRs for geographic information interoperability, especially
for the conversion of one GPLR into another through different environments, including static vs. dynamic.
5.2 User’s environment and registers
The role of a register invoked by a user’s environment is depicted in Figure 1. In a user’s environment,
a GIS application typically gets its input data from an external data repository. Usually, that data needs
to be converted into the internal representation of the user’s GIS environment. This is made possible
through a geographic point location converter service, which first searches in a register environment
for possible transformation (i.e. search for specifications) and requests to the register environment the
required information to transform the GPLR into the user’s GIS environment (i.e. request for specification).
To this end, the geographic point location converter service passes the identification of the GPLR from the
external data source to the register’s environment.
In the register’s environment, it is the register service that receives the request. Using the identification
of the GPLR passed by the conversion service, it gets the specification of the representation from the
register (i.e. database of geographic point location representation) including the possible conversions
into other representations and replies to the conversion service. Finally, the conversion service gets
the description information (i.e. geographic point location specifications) of the representation including
4 © ISO 2013 – All rights reserved

known conversions to other representation and the geographic point location converter service will
decide which one bests fit the user’s GIS environment.
Geographic
point location
custodian
Geographic
External point location
Data speci
ications
Request for
speci
ication
Search for
speci
ications
Geographic
point location Register
converter
Geographic
Data base of
point location
GIS
Geographic
speci
ication
point location
representations
User’s
environment
Figure 1 — User’s environment and register
5.3 Static and dynamic data conversion
Two types of data conversion mechanism are recognized: static conversion and dynamic conversion.
Static data conversion consists usually in an offline process to perform a global conversion of a large
amount of data. One such conversion is performed in batch conversion of static geographic data sets such
as digital maps from one format to another. Another consists in the fusion process that integrates multiple
geographic data sets represented by various formats in a common data set under a unique format.
Dynamic data conversion refers to an online and real-time processing mechanism. This means that a
GPL can be imported or exported through a wireless network, converted, and used by a mobile terminal
such as in telematics. For example, the location of moving features can be tracked globally by RFID
sensors passing through the distributed RFID gateways where the various GPL may be managed in and
converted from various coordinate systems and representations.
Consequently, a register of representations of geographic point locations serves in static and dynamic
conversions as a resource to identify the representation format in which a GPL is encoded, to support the
decoding of the GPL by the application (online or offline), and to support the encoding process in another
format representation as required.
6 Management of registries and registers
Several actors are needed in the maintenance of registers, each one playing specific roles. ISO 19135
identifies and describes the following actors:
— Control body;
— Register manager;
— Register owner;
— Registry manager;
— Submitting organization.
The management of registries and registers shall be as specified in ISO 19135.
7 Schema of the register
7.1 Context
Clause 7 specifies the content and structure of the register of GPLR in a UML schema (see Annex C
for a summary of UML notation). The schema includes only one package but refers to classes from
the ISO/TS 19103 Conceptual Schema Language package, the ISO 19115 Metadata package, and the
ISO 19135 Procedures for registration package (Figure 2). It includes information about the register
itself and information about representations of geographic point locations (Figure 3).
ISO 19135:2005 Procedures for Registration
(from ISO 19135-All Procedures for Registration)
ISO 19145 Registry GPL representations
ISO 19115:2003 Metadata
(from ISO 19115-All Metadata)
(from ISO TC211)
ISO 19103:2005 Schema Language
(from ISO 19103 Conceptual Schema Language)
Figure 2 — GPLR package dependencies
6 © ISO 2013 – All rights reserved

ISO 19135:2005 Procedures for
GPLR_Register
Registration::RE_Register
{leaf}
+register 1.*
Content
+containedItem 1.*
+containedItem 1.*
+outFormat
ISO 19135:2005 Procedures for
GPLR_Item GPLR_ConversionService
1.*
+converter
Registration::RE_RegisterItem
{leaf} {root,leaf}
0.*
+crsSupport 1 0.1 +compressionTechnique
GPLR_CRSSuport GPLR_Compression
{root,leaf} {root,leaf}
Figure 3 — Overview of the UML GPLR register’s schema
7.2 GPLR_Register
7.2.1 Semantics
The class GPLR_Register (Figure 4) specifies information about a register of geographic point location
representations. The GPLR_Register class is essentially a subclass of RE_Register from ISO 19135 and as
such inherits all its properties, relations, and behaviours (see ISO 19135:2005, 8.2).
7.2.2 Content
The association Content aggregates GPLR_Items that are parts of the GPLR_Register. This association
is essentially the counterpart of the Content association between RE_Register and RE_RegisterItem
of ISO 19135.
ISO 19135:2005 Procedures for Registration::
RE_Register
+ name :CharacterString
+ contentSummary :CharacterString GPLR_Register
+ uniformResourceIdentiier :CI_OnlineResource [1.*]
{leaf}
+ operatingLanguage :RE_Locale
+ alternativeLanguages :Set constraints
+ version :RE_Version [0.1]
{count(self.version +self.dateOfLastChange) >=1}
+ dateOfLastChange :Date[0.1]
constraints
{count(self.version +self.dateOfLastChange) >=1}
Content
+register 1.*
Content
+containedItem 1.*
+containedItem 1.*
GPLR_Item
{leaf}
ISO 19135:2005 Procedures for
Registration::RE_RegisterItem
constraints
{count(self.legalConstraints.accessConstraints) >=1}
Figure 4 — GPLR_Register
7.3 GPLR_Item
7.3.1 Semantics
The class GPLR_Item (Figure 5) specifies information that describes geographic point location
representations. The GPLR_Item class is essentially a subclass of RE_RegisterItem from ISO 19135 and as
such inherits all its properties, relations, and behaviours (see ISO 19135:2005, 8.8). It adds five attributes
and three association roles: gplrID, specificationName, version, legalConstraints, type, crsSupport,
converter, and compressionTechnique. This information provides the details on how a geographic point
location is rendered, compressed, and can be converted into another representation.
7.3.2 gplrID
The mandatory attribute gplrID consists in a designator that uniquely distinguishes from others a
specific geographic point location representation within the context of the register. It is intended to be
used for information processing. It is represented by a CharacterString (see ISO/TS 19103).
7.3.3 specificationName
The mandatory attribute specificationName designates a specific geographic point location
representation. A specific geographic point location representation is represented by a CI_Citation (see
ISO 19115). In CI_Citation, the attribute title identifies the specific name of the geographic point location
representation and the attribute citedResponsibleParty provides the details of the resources related to
the geographic point location representation. In the context of this International Standard, these two
attributes are mandatory.
7.3.4 version
The mandatory attribute version provides information about the specific release of the geographic point
location representation. It is represented by a GPLR_Version.
8 © ISO 2013 – All rights reserved

ISO 19135:2005 Procedures for Registration::RE_RegisterItem
+ itemIdentiier :Integer
+ name :CharacterString
+ /status :RE_ItemStatus
+ dateAccepted :Date [0.1]
+ dateAmended :Date [0.1]
+ deinition :CharacterString
+ description :CharacterString [0.1] GPLR_Register
+ ieldOfApplication :Set [0.1]
{leaf}
+ alternativeExpressions :Set [0.1]
Content
+containedItem 1.*
GPLR_Item
«CodeList»
GPLR_RepresentationType
{leaf}
+converter
{root,leaf}
GPLR_ConversionService
+ gplrID :CharacterString
+ text
{root,leaf}
+ speciicationName :CI_Citation
0.*
+ binary
+ version :GPLR_Version
+ XML
+ legalConstraints :MD_LegalConstraints [0.*]
+ type :GPLR_RepresentationType = text
+compressionTechnique
GPLR_Compression
constraints
GPLR_Version
{root,leaf}
0.1
{count(self.legalConstraints.accessConstraints) >= 1}
{leaf}
Constraint information::
+crsSupport 1
MD_LegalConstraints
GPLR_CRSSupport
{root,leaf}
«datatype»
Citation and responsible party
information::CI_Citation
«type»
Text::CharacterString
Figure 5 — GPLR_Item
7.3.5 legalConstraints
The optional attribute legalConstraints identifies whether or not the geographic point location
representation can be used only under legal rights, restrictions, and prerequisites. It shall use an
MD_LegalConstraints type as specified in ISO 19115. When a legal constraint is documented, at least
accessConstraints must be documented.
7.3.6 type
The mandatory attribute type provides the encoding type of a geographic point location representation.
It uses the code lists GPLR_RepresentationType. Accordingly, a GPL representation can be encoded as
text, binary, or XML.
7.3.7 compressionTechnique
The optional association role compressionTechnique identifies the mechanism used to reduce the size of
the geographic point location representation. It is described by a GPLR_Compression.
7.3.8 converter
The optional association role converter identifies the conversion tools or services that can transform
this geographic point location representation into another one. It uses a GPLR_ConversionService.
7.3.9 crsSupport
The mandatory association role crsSupport identifies if the geographic point location representation
provides support to coordinate reference systems. It is described by a GPLR_CRSSupport.
7.4 Geographic Point Location Representation Object
A geographic point location register is simple, i.e. it contains a single item class. Accordingly, the
register has one unique containedItem of the type of RE_ItemClass, which is Geographic Point Location
Representation. The GPLR_Register and all containedItems of the GPLR_Item class refer to this Geographic
Point Location Representation. This is illustrated in Figure 6.
ISO 19135 Procedures for
GPLR_Register
Registration::RE_Register
{leaf}
{root}
ContentDescription
ContentDescription
+containedItemClass 1.*
+containedItemClass 1
ISO 19135 Procedures for Registration::
RE_ItemClass
Geographic Point
{root}
Content Content
Location
+ name: CharacterString
Representation
+ technicalStandard: CI_Citation
+ alternativeLanguages: Set
+itemClass 1
+itemClass
Categorization
Categorization
+containedItem 1.*
+containedItem
1.*
ISO 19135 Procedures for
Registration::
GPLR_Item
RE_RegisterItem
{leaf}
{root}
Figure 6 — Geographic Point Location Representation Object
7.5 GPLR_CRSSupport
7.5.1 Semantics
The class GPLR_CRSSupport (Figure 7) specifies information about the support of coordinate reference
systems by the register using two attributes and one association role: supported, fixed, and crs.
7.5.2 supported
The mandatory derived attribute supported identifies whether or not the geographic point location
representation supports at least one coordinate reference system. It shall use a Boolean type as specified
in ISO/TS 19103. If a crs instance is associated with a GPLR_CRSSupport instance, then the attribute
supported is set to true, otherwise it is set to false.
10 © ISO 2013 – All rights reserved

GPLR_Item
{leaf}
constraints
{count(self.legalConstraints.accessConstraints) >= 1}
«enumeration»
Truth::Boolean
{root}
+crsSupport 1
GPLR_CRSSupport
{root.leaf}
+ /supported :Boolean
+ /ix ed :Boolean [0.1]
constraints
{crs ->isEmpty() = false implies supported = true}
{crs -> size() = 1 implies ix ed = true}
+crs 0.*
Reference system information::
MD_ReferenceSystem
Figure 7 — GPLR_CRSSupport
7.5.3 fixed
If coordinate reference system is supported, the optional derived attribute fixed when set to true
identifies that the geographic point location representation supports only one coordinate reference
system, and when set to false identifies that the geographic point location representation supports
multiple coordinate reference systems. It uses a Boolean type (see ISO/TS 19103).
7.5.4 crs
The optional association role crs identifies the coordinate reference systems that are supported by the
geographic point location representation. It uses an MD_ReferenceSystem type (see ISO 19115).
7.6 GPLR_ConversionService
7.6.1 Semantics
The class GPLR_ConversionService (Figure 8) specifies information about converters to transform a
geographic point location representation into another. The class uses four attributes and two association
roles: name, description, uniformResourceIdentifier, conversionType, invocationInterface and outFormat.
7.6.2 name
The mandatory attribute name contains a human readable designator that denotes a conversion tool or
a conversion service. A conversion service name shall be unique within a register. It is represented by a
CharacterString (see ISO/TS 19103).
GPLR_ConversionService
+outFormat
{root.leaf}
GPLR_Item
0.*
+ name :CharacterString
{leaf} 1.*
+converter
+ description :CharacterString [0.1]
+ uniformResourceIdentiier :CI_OnlineResource [0.*]
0.*
0.*
+ conversionType :GPLR_ConversionType
«CodeList»
+invocationInterface 0.1
GPLR_ConversionType
{root.leaf}
GPLR_Interface
+ static
+ dynamic
«type»
+method 1.*
Text::CharacterString
GPLR_Method
«datatype»
+ invocationName :CharacterString
Citation and responsible party
+ parameters :RecordType [0.*]
information::CI_OnlineResource
+ returnValues :RecordType [0.*]
Figure 8 — GPLR_ConversionService
7.6.3 description
The optional attribute description provides a narrative overview or brief explanation of the conversion
tool or conversion service. The description shall inform on the various processes that are involved in the
conversion. It uses a CharacterString (see ISO/TS 19103).
7.6.4 uniformResourceIdentifier
The optional attribute uniformResourceIdentifier provides URLs to online references of resources associated
with the conversion tool or conversion service. It is represented by a CI_OnlineResource (see ISO 19115).
7.6.5 conversionType
The mandatory attribute conversionType identifies whether the conversion is processed online or
offline in batch mode for example. It uses the GPLR_ConversionType code list. Accordingly, a GPLR_
ConversionService can be identified static or dynamic.
7.6.6 invocationInterface
The optional association role invocationInterface describes the interaction mechanism by which the
conversion service can be invocated. An invocation interface is documented by a GPLR_Interface.
7.6.7 outFormat
The mandatory association role outFormat identifies the various geographic point location
representations that the conversion tool or conversion service can generate. Each outFormat instance is
described by a GPLR_Item.
12 © ISO 2013 – All rights reserved

7.7 GPLR_Interface
7.7.1 Semantics
The class GPLR_Interface (Figure 8) specifies the methods that compose the invocation interface of
the conversion.
7.7.2 method
The mandatory association role method identifies the various methods that are included in a GPLR_
Interface. A method is described by a GPLR_Method.
7.8 GPLR_Method
7.8.1 Semantics
The class GPLR_Method (Figure 8) specifies the elements that describe a method of an interface. It has
three attributes: invocationName, parameters, and returnValues.
7.8.2 invocationName
The mandatory attribute invocationName is a human readable designator that denotes the method.
A method name shall be unique within an interface. It is represented by a CharacterString (see
ISO/TS 19103).
7.8.3 parameters
The optional attribute parameters describe the input values involved in the method. Parameters
are represented by a RecordType that specifies names and types of the parameters involved (see
ISO/TS 19103).
7.8.4 returnValues
The optional attribute returnValues describes the output values returned by the method. returnValues
are represented by a RecordType that specifies names and types of the elements returned (see
ISO/TS 19103).
7.9 GPLR_Compression
7.9.1 Semantics
The class GPLR_Compression (Figure 9) specifies information about the compression technique that a
specific geographic point location representation uses. It has four attributes: name, description, version,
and compressionService.
7.9.2 name
The mandatory attribute name designates a specific compression mechanism. It is represented by a CI_
Citation (see ISO 19115). In CI_Citation, the attribute title identifies the specific name of the compression
mechanism and the attribute citedResponsibleParty provides details about resources related to the
compression mechanism.
7.9.3 description
The optional attribute description provides a narrative overview or brief explanation of the compression
technique. It uses a CharacterString (see ISO/TS 19103).
«type» «datatype»
GPLR_Register
Text::CharacterString Citation and responsible party
{leaf}
information::CI_OnlineResource
Content
GPLR_Compression
+containedItem 1.*
{root.leaf}
+compressionTechnique
+ name :CI_Citation
GPLR_Item
+ description :CharacterString [0.1]
{leaf}
0.1
+ version :GPLR_Version [0.1]
+ compressionService :CI_OnlineResource [0.*]
+crsSupport 1
GPLR_CRSSupport
GPLR_Version
{root,leaf} {leaf}
Figure 9 — GPLR_Compression
7.9.4 version
The optional attribute version provides information about the release of the compression technique. It is
represented by a GPLR_Version.
7.9.5 compressionService
The optional attribute compressionService provides URLs to online services or downloadable tools that
perform the compression. Each instance of compressionService is represented by a CI_OnlineResource
(see ISO 19115).
7.10 GPLR_Version
7.10.1 Semantics
The class GPLR_Version (Figure 10) specifies information about the release of a resource. It inherits from
RE_Version (see ISO 19135) and adds to the two RE_Version attributes one additional attribute to include
a possible amendment to a given version. Therefore the class uses three attributes: versionNumber,
versionDate and amendmentNumber.
7.10.2 versionNumber
The mandatory attribute versionNumber contains a constrained CharacterString (see ISO/TS 19103) that
identifies the version and consists of a < first positive integer > < . > < second positive integer > < letters > :
a) < first positive integer > : major version designation
b) < . > : delimiter
c) < second positive integer > : optional minor version designation
d) < letters > : optional minor sub-version designation
EXAMPLE 2.1a
14 © ISO 2013 – All rights reserved

ISO 19135:2005 Procedures for
Registration::RE_Version
{root}
+ versionNumber :CharacterString
+ versionDate :Date
GPLR_Version
{leaf}
+ amendmentNumber :CharacterString [0.1]
Figure 10 — GPLR_Version
7.10.3 versionDate
The mandatory attribute versionDate specifies the date of the release. It is represented by a Date (see
ISO/TS 19103).
7.10.4 amendmentNumber
The optional attribute amendmentNumber contains a CharacterString (see ISO/TS 19103) that denotes a
specific amendment associated with the resource version.
7.11 GPLR_RepresentationType
GPLR_RepresentationType is a code list that specifies the encoding method used for the representation
of the geographic point location.
Table 1 — Encoding method used for the representation of the geographic point location
Value Semantics
text The geographic point location is represented in text format other than XML, but
using a text encoding method such as in ISO/IEC 10646.
binary The geographic point location is represented in binary format, i.e. not using a text
encoding method.
XML The geographic point location is represented in XML format.
7.12 GPLR_ConversionType
GPLR_ConversionType is a code list that specifies the processing mechanism used to convert geographic
point location representations.
Table 2 — Processing mechanism used to convert geographic point location representations
Value Semantics
a
static Offline process to perform a global conversion of a large amount of data.
dynamic Online and real-time processing mechanism.
a
It includes batch conversion of static geographic data sets from one format to another and integration of multiple
geographic data sets from various formats in one common data set in a unique format.
Annex A
(normative)
XML extensions required for registry of representations of
geographic point location
A.1 XML schema implementation
A register of items of representation of geographic point location is described in UML as one specific
package and has dependencies with other packages (see Clause 7). This annex provides an XML
implementation for the encoding of ISO 19145 compliant registers, which extends on the XML
implementation of ISO 19135, defined in ISO/TS 19135-2. The XML schema defined in this annex shall
conform to the rules outlined in ISO 19118 and ISO/TS 19139.
The XML implementation of this International Standard defines the namespace http://www.isotc211.
org/2005/gplr (Figure A.1) where the namespace prefix gplr stands for Geographic Point Location
Representation.
The details of the XML description of all the parts that form an ISO 19145 XML register are provided in B.2.
A.2 XML Schema of the registry of representations of geographic point location
A.2.1 Geographic point location representation item
A.2.1.1 Introduction
A.2.1 documents the XML schema of the classes that are included in the description of the register of
representation of geographic point location.
Figure A.1 shows the namespace used to implement ISO 19145 along with its dependencies on the
namespaces defined in ISO/TS 19135-2 and ISO/TS 19139, used to implement ISO 19135 and ISO 19115
and the related standards, respectively.
16 © ISO 2013 – All rights reserved

«xmlNamespace»
gplr
ISO 19145 Registry GPL representations
«implement»
(from ISO TC211)
«xmlNamespace»
gco
ISO 19103 Schema Language
«import»
«implement»
(from ISO TC211)
«xmlNamespace»
gmd
ISO 19115 Metadata
«import»
«implement»
(from ISO TC211)
«xmlNamespace»
grg
ISO 19135 Procedures for Registration
«import»
«implement»
(from ISO TC211)
Figure A.1 — XML namespaces
For the XML schema element definition hereafter, the following illustrates the typical schema header:

w3.org/1999/xlink”
xmlns:gco=”http://www.isotc211.org/2005/gco” xmlns:gmd=”http://www.isotc211.
org/2005/gmd”
xmlns:grg=”http://www.isotc211.org/2005/grg” xmlns:gplr=”http://www.isotc211.
org/2005/gplr”
targetNamespace=”http://www.isotc211.org/2005/gplr” elementFormDefault=”qualified”
version=”0.1”>

This file was generated from ISO 19145 UML class diagrams xs:documentation>

schemaLocation=”http://standards.iso.org/ittf/
PubliclyAvailableStandards/ISO_19139_Schemas/
gco/gco.xsd”/>
schemaLocation=”http://standards.iso.org/ittf/
PubliclyAvailableStandards/ISO_19139_Schemas/
gmd/gmd.xsd”/>
schemaLocation=”http://standards.iso.org/ittf/
PubliclyAvailableStandards/ISO_19135-
2_Schemas/grg.xsd”/>

A.2.1.2 Namespace organization
The namespace gplr contains the implementation of the schema of the register of representations of
geographic point location. The root of this namespace is gplr.xsd. Figure A.2 shows the organization of the
gplr namespace. gplrRegister shall include the element definitions described in A.2.1.3 to A.2.1.11 and A.2.2.
«xmlSchema» «xmlSchema»
gplr.xsd gplrRegister.xsd
«include»
Figure A.2 — gplr namespace
A.2.1.3 GPLR_Item
The following XML schema defines the GPLR_Item_Type complex type, the GPLR_Item element and
the GPLR_Item_PropertyType complex type. These definitions correspond to the GPLR_Item class of
the UML model.


Element of information recorded in the register







minOccurs=”0”
maxOccurs=”unbounded”/>

...

NORME ISO
INTERNATIONALE 19145
Première édition
2013-02-15
Information géographique — Registre
de représentations de localisation de
point géographique
Geographic information — Registry of representations of geographic
point location
Numéro de référence
©
ISO 2013
DOCUMENT PROTÉGÉ PAR COPYRIGHT
© ISO 2013
Droits de reproduction réservés. Sauf indication contraire, aucune partie de cette publication ne peut être reproduite ni utilisée
sous quelque forme que ce soit et par aucun procédé, électronique ou mécanique, y compris la photocopie, l’affichage sur
l’internet ou sur un Intranet, sans autorisation écrite préalable. Les demandes d’autorisation peuvent être adressées à l’ISO à
l’adresse ci-après ou au comité membre de l’ISO dans le pays du demandeur.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail [e-mail]
Web www.iso.org
Publié en Suisse
ii © ISO 2013 – Tous droits réservés

Sommaire Page
Avant-propos .iv
Introduction .v
1 Domaine d’application . 1
2 Conformité . 1
3 Références normatives . 1
4 Termes, définitions et termes abrégés . 2
4.1 Termes et définitions . 2
4.2 Termes abrégés . 4
5 Rôle d’un registre de représentations de localisation de point géographique .4
5.1 Présentation . 4
5.2 Environnement utilisateur et registres . 4
5.3 Conversion de données statique et dynamique . 5
6 Gestion des registres et des systèmes de registres . 6
7 Schéma du registre . 6
7.1 Contexte . 6
7.2 GPLR_Register (Registre_GPLR) . 7
7.3 GPLR_Item . 8
7.4 Objet de représentation de localisation de point géographique .10
7.5 GPLR_CRSSupport .10
7.6 GPLR_ConversionService .11
7.7 GPLR_Interface .13
7.8 GPLR_Method .13
7.9 GPLR_Compression .13
7.10 GPLR_Version .14
7.11 GPLR_RepresentationType .15
7.12 GPLR_ConversionType .15
Annexe A (normative) Extensions XML requises pour l’enregistrement des
représentationsde localisation de point géographique .17
Annexe B (normative) Suite d’essais abstraits .24
Annexe C (informative) Notation UML .26
Bibliographie .31
Avant-propos
L’ISO (Organisation internationale de normalisation) est une fédération mondiale d’organismes
nationaux de normalisation (comités membres de l’ISO). L’élaboration des Normes internationales est
en général confiée aux comités techniques de l’ISO. Chaque comité membre intéressé par une étude
a le droit de faire partie du comité technique créé à cet effet. Les organisations internationales,
gouvernementales et non gouvernementales, en liaison avec l’ISO participent également aux travaux.
L’ISO collabore étroitement avec la Commission électrotechnique internationale (CEI) en ce qui concerne
la normalisation électrotechnique.
Les Normes internationales sont rédigées conformément aux règles données dans les Directives
ISO/CEI, Partie 2.
La tâche principale des comités techniques est d’élaborer les Normes internationales. Les projets de
Normes internationales adoptés par les comités techniques sont soumis aux comités membres pour vote.
Leur publication comme Normes internationales requiert l’approbation de 75 % au moins des comités
membres votants.
L’attention est appelée sur le fait que certains des éléments du présent document peuvent faire l’objet de
droits de propriété intellectuelle ou de droits analogues. L’ISO ne saurait être tenue pour responsable de
ne pas avoir identifié de tels droits de propriété et averti de leur existence.
L’ISO 19145 a été élaborée par le comité technique ISO/TC 211, Information géographique/Géomatique.
iv © ISO 2013 – Tous droits réservés

Introduction
L’ISO 6709:2008 normalise les mécanismes relatifs à l’interopérabilité des représentations de
localisation de point géographique. Cependant, la représentation des localisations de point géographique
se présente sous divers schémas (par exemple ISO 6709:1983, DCMI Point encoding scheme, KML,
GeoVRML, Natural Area Coding System, ISO/CEI 8211, GML Point Profile) selon l’application dans
laquelle elles sont utilisées. En conséquence, l’ISO 6709:2008 reconnaît et contribue à la flexibilité
de la représentation des localisations de point géographique et à l’exigence d’une interprétation
universelle. Afin de prendre en charge l’utilisation d’une variété de représentations de localisation de
point géographique, l’ISO 6709:2008 spécifie l’exigence d’un registre de représentations de localisation
de point géographique. Le registre de représentations de localisation de point géographique permet
d’accéder à la description du format dans lequel une localisation de point géographique est codée et
d’identifier également les services de conversion pour transformer la représentation de localisation
de point géographique en une autre représentation. À ce titre, en connaissant le format dans lequel
une localisation de point géographique est codée et le format dans lequel elle doit être codée pour son
utilisation par une application spécifique, il peut être possible de réaliser la transformation appropriée
de la représentation d’une localisation de point géographique. Toutefois, cela nécessite que les formats
de codage et leurs descriptions soient accessibles soit comme partie intégrante de la représentation elle-
même soit à partir d’un registre de représentations de localisation de point géographique. À cet effet, il
est donc nécessaire de définir une structure normalisée du registre de représentations de localisation de
point géographique. Un tel registre contribue à la flexibilité requise identifiée dans l’ISO 6709:2008 pour
assurer une interopérabilité syntaxique efficace des informations de localisation de point géographique.
La présente Norme internationale définit une structure normalisée de registre en langage de modélisation
unifié (UML) destinée à décrire la représentation de localisation de point géographique (Article 7). Elle
définit également l’implémentation par XML (langage de balisage extensible) de la structure UML du
registre par extension de l’ISO/TS 19135-2:2012, Annexe A. Bien que la structure de description de
la représentation de localisation de point géographique soit issue de l’ISO 19135, la présente Norme
internationale élargit ce modèle avec des exigences spécifiques qui vont au-delà de la définition d’un
profil de l’ISO 19135.
NORME INTERNATIONALE ISO 19145:2013(F)
Information géographique — Registre de représentations
de localisation de point géographique
1 Domaine d’application
La présente Norme internationale spécifie les procédures à suivre pour l’établissement, la mise à jour
et la publication de registres de représentations de localisation de point géographique conformes
à l’ISO 19135. Elle identifie et décrit les éléments d’information et la structure d’un registre de
représentations de localisation de point géographique, y compris les éléments de conversion d’une
représentation en une autre.
La présente Norme internationale spécifie également l’implémentation à l’aide du langage de balisage
extensible (XML) de l’extension XML requise de l’ISO/TS 19135-2, pour l’implémentation d’un registre
de représentations de localisation de point géographique.
Un registre de représentations de localisation de point géographique diffère d’un registre CRS (système
de coordonnées de référence) dans la mesure où il n’est pas destiné à décrire les paramètres d’un CRS
comprenant les données, les projections, les unités de mesure et l’ordre des coordonnées, mais s’intéresse
plutôt à la manière dont une localisation de point géographique conforme à l’ISO 6709 est physiquement
représentée dans un enregistrement ou une partie de ce dernier.
2 Conformité
Pour être conforme à la présente Norme internationale, un registre de représentations de localisation
de point géographique doit satisfaire à toutes les conditions spécifiées dans la Suite d’Essais Abstraits
(Annexe B).
3 Références normatives
Les documents de référence suivants sont indispensables pour l’application du présent document. Pour
les références datées, seule l’édition citée s’applique. Pour les références non datées, la dernière édition
du document de référence s’applique (y compris les éventuels amendements).
ISO/TS 19103:2005, Information géographique — Langage de schéma conceptuel
ISO 19115:2003, Information géographique — Métadonnées
ISO 19118:2011, Information géographique — Codage
ISO 19135:2005, Information géographique — Procédures pour l’enregistrement d’éléments
ISO/TS 19135-2:2012, Information géographique — Procédures pour l’enregistrement d’éléments —
Partie 2: Implémentation des schémas XML
ISO/TS 19139:2007, Information géographique — Métadonnées — Implémentation de schémas XML
W3C XMLName, Namespaces in XML 1.0 (Second Edition). W3C Recommendation (16 August 2006)
W3C XMLSchema-1, XML Schema Part 1: Structures Second Edition.W3C Recommendation
(28 October 2004)
W3C XMLSchema-2, XML Schema Part 2: Datatypes Second Edition. W3C Recommendation
(28 October 2004)
W3C XML, Extensible Markup Language (XML) 1.0 (Fourth Edition), W3C Recommendation (16 August 2006)
W3C XLink, XML Linking Language (XLink) Version 1.0. W3C Recommendation (27 June 2001)
4 Termes, définitions et termes abrégés
4.1 Termes et définitions
Pour les besoins du présent document, les termes et définitions suivants s’appliquent.
4.1.1
compression
technique utilisée pour la réduction de l’espace utilisé par les données
4.1.2
service de compression
service (4.1.16) qui accomplit la compression (4.1.1)
4.1.3
conversion
transformation d’un format (4.1.9) en un autre
4.1.4
service de conversion
service (4.1.16) qui fait appel à un convertisseur (4.1.5)
4.1.5
convertisseur
ressource qui accomplit la conversion (4.1.3)
Note 1 à l’article: Cette ressource peut être un appareil ou un logiciel.
4.1.6
coordonnée
une des séquences de n nombres désignant la position d’un point dans un espace à n dimensions
Note 1 à l’article: Dans un système de coordonnées de référence, les coordonnées sont établies par unités.
[SOURCE: ISO 19111:2007, 4.5]
4.1.7
uplet de coordonnées
uplet (4.1.18) composé d’une séquence de coordonnées (4.1.6)
Note 1 à l’article: Dans un système de coordonnées de référence, les coordonnées sont établies par unités.
[SOURCE: ISO 19111:2007, 4.12, modifiée — ajout d’une Note à l’article.]
4.1.8
conversion dynamique
conversion (4.1.3) de données en ligne et en temps réel
4.1.9
format
élément de langage qui spécifie la représentation, sous forme de caractères, d’objets de données dans un
enregistrement, un fichier, un message, en mémoire ou dans une voie de transmission
[SOURCE: ISO/CEI 2382-15:1999, 15.04.35]
2 © ISO 2013 – Tous droits réservés

4.1.10
information géographique
information concernant des phénomènes associés implicitement ou explicitement à un emplacement sur
Terre
[SOURCE: ISO 19101:2002, 4.16]
4.1.11
localisation de point géographique
lieu géographique bien défini décrit par un uplet de coordonnées (4.1.7)
4.1.12
représentation de localisation de point géographique
description syntaxique d’une localisation de point géographique (4.1.11) sous un format (4.1.9) bien connu
4.1.13
identifiant
séquence de caractères linguistiquement indépendante, capable d’identifier de manière exclusive et
continue ce à quoi elle est associée
[SOURCE: ISO 19135:2005, 4.1.5]
4.1.14
registre
ensemble de fichiers comportant les identifiants (4.1.13) attribués aux items et des descriptions qui leur
sont associées
[SOURCE: ISO 19135:2005, 4.1.9]
4.1.15
système de registre
système d’information dans lequel un registre (4.1.14) est mis à jour
[SOURCE: ISO 19135:2005, 4.1.13]
4.1.16
service
partie distincte de la fonctionnalité qui est fournie par une entité par des interfaces
[SOURCE: ISO 19119:2005, 4.1]
4.1.17
conversion statique
processus hors ligne permettant de réaliser une conversion (4.1.3) globale d’une grande quantité de données
4.1.18
uplet
liste ordonnée de valeurs
[SOURCE: ISO 19136:2007, 4.1.63]
4.2 Termes abrégés
CRS coordinate reference system (système de coordonnées de référence)
DCMI Dublin Core Metadata Initiative
GeoVRML Geo-Virtual Reality Modelling Language
GIS geographic information system (système d’information géographique)
GML Geography Markup Language (langage de balisage en géographie)
GPL geographic point location (localisation de point géographique)
GPLR geographic point location representation (représentation de localisation de point géogra-
phique)
KML Keyhole Markup Language
RFID radio frequency identification (identification par radiofréquence)
UML Unified Modelling Language (langage de modélisation unifié)
XML eXtensible Markup Language (langage de balisage extensible)
5 Rôle d’un registre de représentations de localisation de point géographique
5.1 Présentation
L’échange de localisations de point géographique (GPL) décrit par des coordonnées peut utiliser diverses
représentations ou formats. Pour utiliser convenablement de telles informations dans les applications,
une localisation de point géographique (GPL) doit être claire au sujet de la représentation avec laquelle
elle s’accorde. Les mécanismes de conversion peuvent alors être appliqués pour transformer les GPL
échangées en représentations internes des systèmes pour leur usage approprié en supposant que la
représentation interne est aussi enregistrée et que les services sont disponibles.
Les registres rendent flexible la gestion des représentations de localisation de point géographique
(GPLR). Les registres de GPLR accessibles au public sous la forme d’un fichier ou de services web
améliorent l’interopérabilité des GPL en identifiant clairement la manière dont une GPL est représentée
et la manière dont elle peut être convertie en une autre représentation.
Le présent article souligne le rôle des registres de GPLR pour l’interopérabilité de l’information
géographique, notamment pour la conversion d’une GPLR en une autre dans différents environnements,
y compris la conversion statique par rapport à la conversion dynamique.
5.2 Environnement utilisateur et registres
Le rôle d’un registre auquel fait appel un environnement utilisateur est décrit à la Figure 1. Dans
un environnement utilisateur, une application GIS (système d’information géographique) obtient
généralement ses données d’entrée à partir d’un identificateur de données externes. En règle générale, ces
données doivent être converties en une représentation interne de l’environnement GIS de l’utilisateur.
Cela est possible grâce au service de convertisseur de localisation de point géographique, qui recherche
tout d’abord dans l’environnement d’un registre la possibilité d’une transformation (c’est-à-dire recherche
de spécifications) et demande à l’environnement du registre les informations requises pour transformer
la GPLR dans l’environnement GIS de l’utilisateur (c’est-à-dire demande de spécification). À cette fin, le
service de convertisseur de localisation de point géographique transmet à l’environnement du registre
l’identification de la GPLR à partir de la source des données externes.
4 © ISO 2013 – Tous droits réservés

Dans l’environnement du registre, c’est le service de registre qui reçoit la demande. En utilisant
l’identification de la GPLR transmise par le service de conversion, il obtient la spécification de la
représentation à partir du registre (c’est-à-dire la base de données de représentation de localisation de
point géographique), y compris les conversions possibles en d’autres représentations, et répond au service
de conversion. Enfin, le service de conversion obtient les informations de description (c’est-à-dire les
spécifications de localisation de point géographique) de la représentation comprenant les conversions, déjà
connues, en d’autres représentations, et le service de convertisseur de localisation de point géographique
décide de l’information qui correspond le mieux à l’environnement GIS de l’utilisateur.
Responsable de
localisation de point
géographique
Spéci ications de
Données
localisation de
externes
Demande de
point géographique
spéci ication
Recherche de
spéci ications
Convertisseur
de localisation
Registre
de point
géographique
Base de données
de représentations
GIS
Convertisseur de
de localisation de
localisation de
point géographique
point
géographique
Environnement
utilisateur
Figure 1 — Environnement et registre utilisateur
5.3 Conversion de données statique et dynamique
Deux types de mécanisme de conversion de données sont reconnus: la conversion statique et la
conversion dynamique.
La conversion de données statique est habituellement un processus hors ligne permettant de réaliser une
conversion globale d’une grande quantité de données. Une telle conversion est réalisée par conversion
par lots d’ensembles de données géographiques statiques, comme la conversion de cartes numériques
d’un format en un autre. Une autre méthode consiste à réaliser un processus de fusion qui intègre des
ensembles de données géographiques multiples représentés par divers formats dans un ensemble
commun de données sous un format unique.
La conversion de données dynamique fait référence à un mécanisme de traitement en ligne et en temps
réel. Cela signifie qu’une GPL (localisation de point géographique) peut être importée ou exportée via
un réseau sans fil, convertie et utilisée par un terminal mobile de la même manière que dans le cadre
de la télématique. Par exemple, la localisation d’entités mobiles peut être suivie au niveau mondial par
des détecteurs RFID via les passerelles RFID réparties permettant de gérer les diverses GPL et de les
convertir à partir de divers systèmes et représentations par coordonnées.
Par conséquent, dans le cadre des conversions statiques et dynamiques, un registre de représentations
de localisation de point géographique sert de ressource pour identifier le format de représentation dans
lequel une GPL est codée, contribuer au décodage de la GPL par l’application (en ligne ou hors ligne) et
favoriser le processus de codage dans un autre format de représentation requis.
6 Gestion des registres et des systèmes de registres
La tenue des registres nécessite plusieurs acteurs, chacun d’eux jouant un rôle spécifique. L’ISO 19135
identifie et décrit les acteurs suivants:
— organisme de contrôle;
— responsable de registre;
— propriétaire de registre;
— responsable du système de registre;
— organisme de soumission.
La gestion des systèmes de registres et des registres doit être telle que spécifiée dans l’ISO 19135.
7 Schéma du registre
7.1 Contexte
L’Article 7 spécifie le contenu et la structure du registre de GPLR dans un schéma UML (voir l’Annexe C
pour un résumé de la notation UML). Le schéma comprend un seul module mais fait référence aux
classes du module «Conceptual Schema Language» (langage de schéma conceptuel) de l’ISO/TS 19103,
du module «Metadata» (Métadonnées) de l’ISO 19115 et des Procédures de l’ISO 19135 pour le module
d’enregistrement (Figure 2). Il contient des informations sur le registre lui-même et des informations
sur les représentations de localisations de point géographique (Figure 3).
ISO 19135:2005 Procédures pour l’enregistrement d’éléments
ISO 19145 Registre des représentations
(de l’ISO 19135 Toutes procédures pour l’enregistrement)
de localisation de point géographique
ISO 19115:2005 Métadonnées
(de l’ISO 19115 Métadonnées)
(de l’ISO TC 211)
ISO 19103:2005 Langage de schéma conceptuel
(de l’ISO 19103 Langage de schéma Conceptuel)
Figure 2 — Dépendances du module GPLR
6 © ISO 2013 – Tous droits réservés

ISO 19135 Procédures
pour l’enregistrement
GPLR_Register
d’éléments::RE_Register
{leaf}
+register 1.*
Content
0.*
+containedItem
+containedItem 1.*
+outFormat
ISO 19135 Procédures
GPLR_ConversionService
GPLR_item 1.*
pour l’enregistrement
+converter
{leaf}
{root,leaf}
d’éléments::RE_Registerltem
0.*
+crsSupport 1 0.1 +compressionTechnique
GPLR_CRSupport
GPLR_Compression
{root,leaf}
{root,leaf}
Figure 3 — Présentation du schéma UML du registre de GPLR
7.2 GPLR_Register (Registre_GPLR)
7.2.1 Sémantique
La classe GPLR_Register (Figure 4) spécifie les informations concernant un registre de représentations
de localisation de point géographique. La classe GPLR_Register est par essence une sous-classe de RE_
Register de l’ISO 19135 et hérite à ce titre de toutes ses propriétés, relations et comportements (voir
l’ISO 19135:2005, 8.2).
7.2.2 Content (Contenu)
L’association Content regroupe les GPLR_Items qui font partie de GPLR_Register. Cette association est
par essence l’équivalent de l’association Content entre RE_Register et RE_RegisterItem de l’ISO 19135.
ISO 19135:2005 Procédures pour l’enregistrement
d’éléments::RE_Register
+ name :CharacterString
GPLR_Register
+ contentSummary :CharacterString
+ uniformResourceIdentiier :CI_OnlineResource [1.*]
{leaf}
+ operatingLanguage :RE_Locale
+ alternativeLanguages :Set
constraints
+ version :RE_Version [0.1]
{count(self.version +self.dateOfLastChange) >=1}
+ dateOfLastChange :Date[0.1]
constraints
{count(self.version +self.dateOfLastChange) >=1}
Content
+register 1.*
Content
+containedItem 1.*
+containedItem 1.*
GPLR_Item
{leaf}
ISO 19135:2005 Procédures pour
l’enregistrement d’éléments::RE_RegisterItem
constraints
{count(self.legalConstraints.accessConstraints) >=1}
Figure 4 — GPLR_Register
7.3 GPLR_Item
7.3.1 Sémantique
La classe GPLR_Item (Figure 5) spécifie les informations qui décrivent les représentations de localisation
de point géographique. La classe GPLR_Item est par essence une sous-classe de RE_RegisterItem de
l’ISO 19135 et à ce titre hérite de toutes ses propriétés, relations et comportements (voir l’ISO 19135:2005,
8.8). Elle ajoute cinq attributs et trois rôles d’association: gplrID, specificationName, version,
legalConstraints, type, crsSupport, converter et compressionTechnique. Ces informations fournissent des
détails sur la manière dont une localisation de point géographique est rendue, compressée et peut être
convertie en une autre représentation.
7.3.2 gplrID
L’attribut obligatoire gplrID est un identificateur qui distingue de façon unique parmi d’autres une
représentation spécifique de localisation de point géographique dans le cadre du registre. Il est
destiné à être utilisé pour le traitement de l’information. Il est représenté par une chaîne de caractères
«CharacterString» (voir l’ISO/TS 19103).
7.3.3 specificationName
L’attribut obligatoire specificationName désigne une représentation spécifique de localisation de point
géographique. Une représentation spécifique de localisation de point géographique est représentée par
une CI_Citation (voir l’ISO 19115). Dans la CI_Citation, le titre de l’attribut identifie le nom spécifique de
la représentation de la localisation de point géographique et l’attribut citedResponsibleParty fournit les
détails des ressources relatives à la représentation de localisation de point géographique. Dans le cadre
de la présente Norme internationale, ces deux attributs sont obligatoires.
7.3.4 version
L’attribut obligatoire version fournit des informations concernant la version spécifique de la
représentation de localisation de point géographique. Il est représenté par une GPLR_Version.
8 © ISO 2013 – Tous droits réservés

ISO 19135:2005 Procédures pour l’enregistrement
d’éléments::RE_RegisterItem
+ itemIdentiier :Integer
+ name :CharacterString
+ /status :RE_ItemStatus
+ dateAccepted :Date [0.1]
+ dateAmended :Date [0.1]
+ deinition :CharacterString
+ description :CharacterString [0.1]
GPLR_Register
+ ieldOfApplication :Set [0.1] {leaf}
+ alternativeExpressions :Set [0.1]
Content
+containedItem 1.*
GPLR_Item
«CodeList»
GPLR_RepresentationType
{leaf}
+converter
{root,leaf}
GPLR_ConversionService
+ gplrID :CharacterString
+ text {root,leaf}
+ speciicationName :CI_Citation
0.*
+ binary
+ version :GPLR_Version
+ XML
+ legalConstraints :MD_LegalConstraints [0.*]
+ type :GPLR_RepresentationType = text
+compressionTechnique
GPLR_Compression
constraints
GPLR_Version
{root,leaf}
0.1
{count(self.legalConstraints.accessConstraints) >= 1}
{leaf}
Constraint information::
+crsSupport 1
MD_LegalConstraints
GPLR_CRSSupport
{root,leaf}
«datatype»
Citation and responsible party
information::CI_Citation
«type»
Text::CharacterString
Figure 5 — GPLR_Item
7.3.5 legalConstraints
L’attribut facultatif legalConstraints identifie si oui ou non la représentation de localisation de point
géographique ne peut être utilisée qu’en vertu de droits, restrictions et conditions préalables légaux. Il
doit utiliser un type MD_LegalConstraints tel que spécifié dans l’ISO 19115. Lorsqu’une contrainte légale
est documentée, les contraintes minimales d’accès (accessConstraints) doivent être documentées.
7.3.6 type
L’attribut obligatoire type fournit le type de codage d’une représentation de localisation de point
géographique. Il utilise les listes de codes GPLR_RepresentationType. En conséquence, une représentation
GPL peut être codée sous forme textuelle, binaire ou XML.
7.3.7 compressionTechnique
Le rôle d’association facultatif compressionTechnique identifie le mécanisme utilisé pour réduire la taille
de la représentation de localisation de point géographique. Il est décrit par une GPLR_Compression.
7.3.8 converter
Le rôle d’association facultatif converter identifie les outils ou services de conversion qui peuvent
transformer cette représentation de localisation de point géographique en une autre. Il utilise une
GPLR_ConversionService.
7.3.9 crsSupport
Le rôle d’association obligatoire crsSupport identifie si la représentation de localisation de point géographique
fournit un support aux systèmes de coordonnées de référence. Il est décrit par une GPLR_CRSSupport.
7.4 Objet de représentation de localisation de point géographique
Un registre de localisation de point géographique est simple, c’est-à-dire qu’il contient une seule classe
d’item. En conséquence, le registre a un containedItem unique de type RE_ItemClass, lequel est une
Représentation de Localisation de Point Géographique. Le GPLR_Register et tous les containedItems de
la classe GPLR_Item font référence à cette Représentation de Localisation de Point Géographique. Il est
illustré à la Figure 6.
ISO 19135 Procédures
GPLR_Register
pour l’enregistrement
d’éléments::RE_Register
{leaf}
{root}
ContentDescription
ContentDescription
+containedItemClass 1.*
+containedItemClass 1
ISO 19135 Procédures pour
l’enregistrement d’éléments::
Geographic Point
{root}
RE_ItemClass
Content Content
Location
+ name: CharacterString
Representation
+ technicalStandard: CI_Citation
+ alternativeLanguages: Set
+itemClass 1
+itemClass
Categorization
Categorization
+containedItem 1.*
1.* +containedItem
ISO 19135 Procédures
pour l’enregistrement
GPLR_Item
d’éléments::RE_RegisterItem
{leaf}
{root}
Figure 6 — Objet de Représentation de Localisation de Point Géographique
7.5 GPLR_CRSSupport
7.5.1 Sémantique
La classe GPLR_CRSSupport (Figure 7) spécifie les informations concernant la prise en charge des
systèmes de coordonnées de référence par le registre en utilisant deux attributs et un rôle d’association:
supported, fixed et crs.
7.5.2 supported
L’attribut dérivé obligatoire supported identifie si oui ou non la représentation de localisation de point
géographique prend en charge au moins un système de coordonnées de référence. Il doit utiliser un
type booléen tel que spécifié dans l’ISO/TS 19103. Si une instance crs est associée à une instance GPLR_
CRSSupport, l’attribut supported est alors mis à true (vrai), sinon il est mis à false (faux).
10 © ISO 2013 – Tous droits réservés

GPLR_Item
{leaf}
constraints
{count(self.legalConstraints.accessConstraints) >= 1}
«enumeration»
Truth::Boolean
{root}
+crsSupport 1
GPLR_CRSSupport
{root.leaf}
+ /supported :Boolean
+ /ix ed :Boolean [0.1]
constraints
{crs ->isEmpty() = false implies supported = true}
{crs -> size() = 1 implies ix ed = true}
+crs 0.*
Reference system information::
MD_ReferenceSystem
Figure 7 — GPLR_CRSSupport
7.5.3 fixed
Si un système de coordonnées de référence est pris en charge, l’attribut dérivé facultatif fixed, lorsqu’il
est mis à true (vrai), identifie que la représentation de localisation de point géographique ne prend en
charge qu’un seul système de coordonnées de référence, et, lorsqu’il est mis à false (faux), il identifie
que la représentation de localisation de point géographique prend en charge plusieurs systèmes de
coordonnées de référence. Il utilise un type booléen (voir l’ISO/TS 19103).
7.5.4 crs
Le rôle d’association facultatif crs identifie les systèmes de coordonnées de référence pris en charge par
la représentation de localisation de point géographique. Il utilise un type MD_ReferenceSystem (voir
l’ISO 19115).
7.6 GPLR_ConversionService
7.6.1 Sémantique
La classe GPLR_ConversionService (Figure 8) spécifie les informations concernant les convertisseurs
permettant de transformer une représentation de localisation de point géographique en une autre. La
classe utilise quatre attributs et deux rôles d’association: name, description, uniformResourceIdentifier,
conversionType, invocationInterface et outFormat.
7.6.2 name
L’attribut obligatoire name contient un identificateur interprétable par l’homme qui désigne un outil de
conversion ou un service de conversion. Un nom de service de conversion doit être unique au sein du
registre. Il est représenté par une CharacterString (voir l’ISO/TS 19103).
GPLR_ConversionService
+outFormat
{root.leaf}
GPLR_Item
0.*
+ name :CharacterString
{leaf} 1.*
+converter
+ description :CharacterString [0.1]
+ uniformResourceIdentiier :CI_OnlineResource [0.*]
0.*
0.*
+ conversionType :GPLR_ConversionType
«CodeList»
+invocationInterface 0.1
GPLR_ConversionType
{root.leaf}
GPLR_Interface
+ static
+ dynamic
«type»
+method 1.*
Text::CharacterString
GPLR_Method
«datatype»
+ invocationName :CharacterString
Citation and responsible party
+ parameters :RecordType [0.*]
information::CI_OnlineResource
+ returnValues :RecordType [0.*]
Figure 8 — GPLR_ConversionService
7.6.3 description
L’attribut facultatif description fournit une présentation narrative ou une explication succincte de l’outil
de conversion ou du service de conversion. La description doit renseigner sur les divers processus
impliqués pour la conversion. Il utilise une CharacterString (voir l’ISO/TS 19103).
7.6.4 uniformResourceIdentifier
L’attribut facultatif uniformResourceIdentifier fournit des URL aux références en ligne des ressources
associées à l’outil de conversion ou service de conversion. Il est représenté par une CI_OnlineResource
(voir l’ISO 19115).
7.6.5 conversionType
L’attribut obligatoire conversionType identifie si la conversion est traitée en ligne ou hors ligne en mode
par lots par exemple. Il utilise la liste de codes GPLR_ConversionType. En conséquence, un GPLR_
ConversionService peut être identifié comme statique ou dynamique.
7.6.6 invocationInterface
Le rôle d’association facultatif invocationInterface décrit le mécanisme d’interaction par lequel le service
de conversion peut être invoqué. Une interface d’invocation est documentée par une GPLR_Interface.
7.6.7 outFormat
Le rôle d’association obligatoire outFormat identifie les diverses représentations de localisation de
point géographique que l’outil de conversion ou le service de conversion peut générer. Chaque instance
OutFormat est décrite par un GPLR_Item.
12 © ISO 2013 – Tous droits réservés

7.7 GPLR_Interface
7.7.1 Sémantique
La classe GPLR_Interface (Figure 8) spécifie les méthodes qui composent l’interface d’invocation de
la conversion.
7.7.2 method
Le rôle d’association obligatoire method identifie les diverses méthodes contenues dans une GPLR_
Interface. Une méthode est décrite par une GPLR_Method.
7.8 GPLR_Method
7.8.1 Sémantique
La classe GPLR_Method (Figure 8) spécifie les éléments qui décrivent une méthode d’une interface. Il a
trois attributs: invocationName, parameters et returnValues.
7.8.2 invocationName
L’attribut obligatoire invocationName est un identificateur interprétable par l’homme qui désigne
la méthode. Un nom de méthode doit être unique au sein d’une interface. Il est représenté par une
CharacterString (voir l’ISO/TS 19103).
7.8.3 parameters
L’attribut facultatif parameters décrit les valeurs d’entrée impliquées dans la méthode. Les paramètres
sont représentés par un RecordType qui spécifie les noms et les types des paramètres concernés (voir
l’ISO/TS 19103).
7.8.4 returnValues
L’attribut facultatif returnValues décrit les valeurs de sortie renvoyées par la méthode. Les returnValues
sont représentées par un RecordType qui spécifie les noms et les types des éléments renvoyés (voir
l’ISO/TS 19103).
7.9 GPLR_Compression
7.9.1 Sémantique
La classe GPLR_Compression (Figure 9) spécifie les informations concernant la technique de compression
qu’une représentation spécifique de localisation de point géographique utilise. Il a quatre attributs:
name, description, version et compressionService.
7.9.2 name
L’attribut obligatoire name désigne un mécanisme de compression spécifique. Il est représenté par une
CI_Citation (voir l’ISO 19115). Dans la CI_Citation, l’attribut titre identifie le nom spécifique du mécanisme
de compression et l’attribut citedResponsibleParty fournit des détails sur les ressources relatives au
mécanisme de compression.
7.9.3 description
L’attribut facultatif description fournit une présentation narrative ou une explication succincte de la
technique de compression. Il utilise une CharacterString (voir l’ISO/TS 19103).
«type» «datatype»
GPLR_Register
Text::CharacterString Citation and responsible party
{leaf}
information::CI_OnlineResource
Content
GPLR_Compression
+containedItem 1.*
{root.leaf}
+compressionTechnique
+ name :CI_Citation
GPLR_Item
+ description :CharacterString [0.1]
{leaf}
0.1
+ version :GPLR_Version [0.1]
+ compressionService :CI_OnlineResource [0.*]
+crsSupport 1
GPLR_CRSSupport
GPLR_Version
{root,leaf} {leaf}
Figure 9 — GPLR_Compression
7.9.4 version
L’attribut facultatif version fournit des informations concernant la version de la technique de compression.
Il est représenté par une GPLR_Version.
7.9.5 compressionService
L’attribut facultatif compressionService fournit des URL aux services en ligne ou aux outils téléchargeables
qui réalisent la compression. Chaque instance de compressionService est représentée par une CI_
OnlineResource (voir l’ISO 19115).
7.10 GPLR_Version
7.10.1 Sémantique
La classe GPLR_Version (Figure 10) spécifie les informations concernant la version d’une ressource.
Elle hérite de RE_Version (voir l’ISO 19135) et ajoute aux deux attributs de RE_Version un attribut
supplémentaire pour prendre en compte un éventuel amendement d’une version donnée. Par conséquent,
la classe utilise trois attributs: versionNumber, versionDate et amendmentNumber.
7.10.2 versionNumber
L’attribut obligatoire versionNumber contient une CharacterString contrainte (voir l’ISO/TS 19103)
qui identifie la version et qui comprend un < first positive integer > < . > < second positive integer >
< letters >, où:
a) < first positive integer >: désignation de la version principale
b) < . >: délimiteur
c) < second positive integer >: désignation facultative de la version secondaire
d) < letters >: désignation facultative de la sous-version secondaire
EXEMPLE 2.1a
14 © ISO 2013 – Tous droits réservés

ISO 19135:2005 Procédure pour
l’enregistrement
d’éléments::RE_Version {root}
+ versionNumber :CharacterString
+ versionDate :Date
GPLR_Version
{leaf}
+ amendmentNumber :CharacterString [0.1]
Figure 10 — GPLR_Version
7.10.3 versionDate
L’attribut obligatoire versionDate spécifie la date de la version. Il est représenté par une Date (voir
l’ISO/TS 19103).
7.10.4 amendmentNumber
L’attribut facultatif amendmentNumber contient une CharacterString (voir l’ISO/TS 19103) qui désigne
un amendement spécifique associé à la version de la ressource.
7.11 GPLR_RepresentationType
GPLR_RepresentationType est une liste de codes qui spécifie la méthode de codage utilisée pour la
représentation de la localisation de point géographique.
Tableau 1 — Méthode de codage utilisée pour la représentation
de la localisation de point géographique
Valeur Signification
text (texte) La localisation du point géographique est représentée en format texte autre que XML,
mais utilisant une méthode d’encodage de texte telle que l’ISO/CEI 10646.
binary (binaire) La localisation du point géographique est représentée en format binaire, c’est-à-dire
n’utilisant pas de méthode d’encodage de texte.
XML La localisation du point géographique est représentée en format XML.
7.12 GPLR_ConversionType
GPLR_ConversionType est une liste de codes qui spécifie le mécanisme de traitement utilisé pour convertir
les représentations de localisation de point géographique.
Tableau 2 — Mécanisme de traitement utilisé pour convertir les représentations
de localisation de point géographique
Valeur Signification
static (statique) Traitement hors ligne permettant de réaliser une conversion globale d’une grande
a
quantité de données
dynamic (dynamique) Mécanisme de traitement en ligne et en temps réel.
a
Cela comprend la conversion par lots d’ensembles de données géographiques statiques d’un format en un autre et
l’intégration de plusieurs ensembles de données géographiques ayant divers formats dans un ensemble commun de données
sous un format unique.
16 © ISO 2013 – Tous droits réservés

Annexe A
(normative)
Extensions XML requises pour l’enregistrement des
représentationsde localisation de point géographique
A.1 Implémentation du schéma XML
Un registre d’items relatifs à la représentation de localisation de point géographique est décrit en UML
sous la forme d’un module spécifique et a des dépendances avec d’autres modules (voir Article 7). La
présente annexe fournit une implémentation XML pour le codage des registres conformes à l’ISO 19145,
qui s’étend à l’implémentation XML de l’ISO 19135 définie dans l’ISO/TS 19135-2. Le schéma XML
...