ISO 19110:2005
(Main)Geographic information — Methodology for feature cataloguing
Geographic information — Methodology for feature cataloguing
ISO 19110:2005 defines the methodology for cataloguing feature types and specifies how the classification of feature types is organized into a feature catalogue and presented to the users of a set of geographic data. ISO 19110:2005 is applicable to creating catalogues of feature types in previously uncatalogued domains and to revising existing feature catalogues to comply with standard practice. ISO 19110:2005 applies to the cataloguing of feature types that are represented in digital form. Its principles can be extended to the cataloguing of other forms of geographic data. ISO 19110:2005 is applicable to the definition of geographic features at the type level. ISO 19110:2005 is not applicable to the representation of individual instances of each type and excludes spatial, temporal, and portrayal schemas as specified in ISO 19107, ISO 19108, and the future ISO 19117, respectively. It also excludes collection criteria for feature instances. ISO 19910:2005 may be used as a basis for defining the universe of discourse being modelled in a particular application, or to standardize general aspects of real world features being modelled in more than one application.
Information géographique — Méthodologie de catalogage des entités
L'ISO 19110:2005 définit la méthodologie de catalogage des types d'entités. Elle spécifie comment la classification des types d'entités est organisée dans un catalogue d'entités et présentée aux utilisateurs d'un jeu de données géographiques. L'ISO 19110:2005 s'applique à la création de catalogues de types d'entités dans des domaines jusqu'ici non catalogués et à la révision des catalogues d'entités existants pour qu'ils soient conformes aux pratiques normalisées. Elle s'applique au catalogage des types d'entités qui sont représentés sous forme numérique. Ses principes peuvent être élargis au catalogage d'autres formes de données géographiques. L'ISO 19110:2005 s'applique à la définition d'entités géographiques au niveau du type d'entité. Elle ne s'applique pas à la représentation des instances individuelles de chaque type. Elle exclut les schémas spatiaux, temporels et de présentation tels que spécifiés, respectivement dans l'ISO 19107, l'ISO 19108 et l'ISO 19117. Elle exclut également les critères de collecte pour les instances d'entités. L'ISO 19110:2005 peut être utilisée comme base permettant de définir l'univers du discours modélisé dans une application particulière ou pour normaliser les aspects généraux d'entités du monde réel modélisés dans plusieurs applications.
Geografske informacije – Metodologija za objektne kataloge
General Information
Relations
Buy Standard
Standards Content (Sample)
INTERNATIONAL ISO
STANDARD 19110
First edition
2005-02-15
Geographic information — Methodology
for feature cataloguing
Information géographique — Méthodologie de catalogage des entités
Reference number
ISO 19110:2005(E)
©
ISO 2005
---------------------- Page: 1 ----------------------
ISO 19110:2005(E)
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.
© ISO 2005
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing 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 copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO 2005 – All rights reserved
---------------------- Page: 2 ----------------------
ISO 19110:2005(E)
Contents Page
Foreword. iv
Introduction . v
1 Scope. 1
2 Conformance . 1
3 Normative references . 2
4 Terms and definitions. 2
5 Abbreviations . 3
6 Principal requirements . 4
6.1 Feature catalogue . 4
6.2 Information elements. 4
Annex A (normative) Abstract test suite. 6
Annex B (normative) Feature catalogue template. 16
Annex C (informative) Feature cataloguing examples. 31
Annex D (informative) Feature cataloguing concepts . 46
Bibliography . 55
© ISO 2005 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO 19110:2005(E)
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 19110 was prepared by Technical Committee ISO/TC 211, Geographic information/Geomatics.
iv © ISO 2005 – All rights reserved
---------------------- Page: 4 ----------------------
ISO 19110:2005(E)
Introduction
Geographic features are real world phenomena associated with a location relative to the Earth, about which
data are collected, maintained, and disseminated. Feature catalogues defining the types of features, their
operations, attributes, and associations represented in geographic data are indispensable to turning the data
into usable information. Such feature catalogues promote the dissemination, sharing, and use of geographic
data through providing a better understanding of the content and meaning of the data. Unless suppliers and
users of geographic data have a shared understanding of the kinds of real world phenomena represented by
the data, users will be unable to judge whether the data supplied are fit for their purpose.
The availability of standard feature catalogues that can be used multiple times will reduce costs of data
acquisition and simplify the process of product specification for geographic datasets.
This International Standard provides a standard framework for organizing and reporting the classification of
real world phenomena in a set of geographic data. Any set of geographic data is a greatly simplified and
reduced abstraction of a complex and diverse world. A catalogue of feature types can never capture the
richness of geographic reality. However, such a feature catalogue should present the particular abstraction
represented in a given dataset clearly, precisely, and in a form readily understandable and accessible to users
of the data.
Geographic features occur at two levels: instances and types. At the instance level, a geographic feature is
represented as a discrete phenomenon that is associated with its geographic and temporal coordinates and
may be portrayed by a particular graphic symbol. These individual feature instances are grouped into classes
with common characteristics: feature types. It is recognized that geographic information is subjectively
perceived and that its content depends upon the needs of particular applications. The needs of particular
applications determine the way instances are grouped into types within a particular classification scheme.
ISO 19109, Geographic information ― Rules for application schema specifies how data shall be organized to
reflect the particular needs of applications with similar data requirements.
NOTE The full description of the contents and structure of a geographic dataset is given by the application schema
developed in compliance with ISO 19109. The feature catalogue defines the meaning of the feature types and their
associated feature attributes, feature operations and feature associations contained in the application schema.
The collection criteria used to identify individual real world phenomena and to represent them as feature
instances in a dataset are not specified in this International Standard. Because they are not included in the
standards, collection criteria should be included separately in the product specification for each dataset.
A standard way of organizing feature catalogue information will not automatically result in harmonization or
interoperability between applications. In situations where classifications of features differ, this International
Standard may at least serve to clarify the differences and thereby help to avoid the errors that would result
from ignoring them. It may also be used as a standard framework within which to harmonize existing feature
catalogues that have overlapping domains.
© ISO 2005 – All rights reserved v
---------------------- Page: 5 ----------------------
INTERNATIONAL STANDARD ISO 19110:2005(E)
Geographic information — Methodology for feature cataloguing
1 Scope
This International Standard defines the methodology for cataloguing feature types. This International Standard
specifies how the classification of feature types is organized into a feature catalogue and presented to the
users of a set of geographic data. This International Standard is applicable to creating catalogues of feature
types in previously uncatalogued domains and to revising existing feature catalogues to comply with standard
practice. This International Standard applies to the cataloguing of feature types that are represented in digital
form. Its principles can be extended to the cataloguing of other forms of geographic data.
This International Standard is applicable to the definition of geographic features at the type level. This
International Standard is not applicable to the representation of individual instances of each type. This
International Standard excludes spatial, temporal, and portrayal schemas as specified in ISO 19107,
ISO 19108, and ISO 19117, respectively. It also excludes collection criteria for feature instances.
This International Standard may be used as a basis for defining the universe of discourse being modelled in a
particular application, or to standardize general aspects of real world features being modelled in more than
one application.
2 Conformance
Because this International Standard specifies a number of options that are not required for all feature
catalogues, this clause specifies 12 conformance classes. These classes are differentiated on the basis of
three criteria:
a) What elements of a feature type are required in a catalogue:
1) feature attributes only?
2) feature attributes and feature associations?
3) feature attributes, feature associations, and feature operations?
b) Is there a requirement to link feature attributes, feature associations, and feature operations to only one
feature type or may they be linked to multiple feature types?
c) Is there a requirement to include inheritance relationships in the feature catalogue?
Annex A specifies a test module for each of the conformance classes, as shown in Table 1.
© ISO 2005 – All rights reserved 1
---------------------- Page: 6 ----------------------
ISO 19110:2005(E)
Table 1 — Conformance classes
Attributes, Properties Inheritance
Attributes Attributes and
associations and associated with relationships Test module
only associations
operations multiple features included
X — — — — A.17
— X — — — A.18
— — X — — A.19
X — — X — A.20
— X — X — A.21
— — X X — A.22
X — — — X A.23
— X — — X A.24
— — X — X A.25
X — — X X A.26
— X — X X A.27
— — X X X A.28
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.
1)
ISO/TS 19103:— , Geographic information — Conceptual schema language
1)
ISO 19109:— , Geographic information — Rules for application schema
ISO 19115:2003, Geographic information — Metadata
4 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
4.1
feature
abstraction of real world phenomena
[ISO 19101]
EXAMPLE The phenomenon named ‘Eiffel Tower’ may be classified with other similar phenomena into a feature
type ‘tower’.
NOTE A feature may occur as a type or an instance. Feature type or feature instance should be used when only one
is meant.
1) To be published.
2 © ISO 2005 – All rights reserved
---------------------- Page: 7 ----------------------
ISO 19110:2005(E)
4.2
feature association
relationship that links instances of one feature (4.1) type with instances of the same or a different feature type
4.3
feature attribute
characteristic of a feature (4.1)
[ISO 19101]
EXAMPLE 1 A feature attribute named ‘colour’ may have an attribute value ‘green’ which belongs to the data type
‘text’.
EXAMPLE 2 A feature attribute named ‘length’ may have an attribute value ’82,4’ which belongs to the data type ‘real’.
NOTE A feature attribute has a name, a data type, and a value domain associated to it. A feature attribute for a
feature instance also has an attribute value taken from the value domain.
4.4
feature catalogue
catalogue containing definitions and descriptions of the feature (4.1) types, feature attributes (4.3), and
feature associations (4.2) occurring in one or more sets of geographic data, together with any feature
operations that may be applied
4.5
feature operation
operation that every instance of a feature (4.1) type may perform
EXAMPLE A feature operation upon a ‘dam’ is to raise the dam. The results of this operation are to raise the height
of the ‘dam’ and the level of water in a ‘reservoir’.
NOTE Sometimes feature operations provide a basis for feature type definition.
4.6
functional language
language in which feature operations are formally specified
NOTE In a functional language, feature types may be represented as abstract data types.
5 Abbreviations
DIGEST Digital Geographic Information Exchange Standard
FACC Feature and Attribute Coding Catalogue
GFM General Feature Model
HTTP Hyper Text Transfer Protocol
IHO International Hydrographic Organization
TS Technical Specification
UML Unified Modeling Language
URI Uniform Resource Identifier
XML eXtensible Markup Language
© ISO 2005 – All rights reserved 3
---------------------- Page: 8 ----------------------
ISO 19110:2005(E)
6 Principal requirements
6.1 Feature catalogue
A feature catalogue shall present the abstraction of reality represented in one or more sets of geographic data
as a defined classification of phenomena. The basic level of classification in a feature catalogue shall be the
feature type. A feature catalogue shall be available in electronic form for any set of geographic data that
contains features. A feature catalogue may also comply with the specifications of this International Standard
independently of any existing set of geographic data.
6.2 Information elements
6.2.1 Introduction
The following clauses specify general and specific requirements for feature catalogue information elements.
Annex B specifies detailed requirements. Annex C illustrates the application of these requirements. Annex D
discusses the application of feature operations as the conceptual basis for determining feature types in a
feature catalogue.
6.2.2 Completeness
A template for the representation of feature classification information is specified in Annex B. A feature
catalogue prepared according to this template shall document all of the feature types found in a given set of
geographic data. The feature catalogue shall include identification information as specified in Annex B. The
feature catalogue shall include definitions and descriptions of all feature types contained in the data, including
any feature attributes and feature associations contained in the data that are associated with each feature
type, and optionally including feature operations that are supported by the data. To ensure predictability and
comparability of feature catalogue content across different applications, it is recommended that the feature
catalogue should include only the elements specified in Annex B. To maximize the usefulness of a feature
catalogue across different applications, the use of a conceptual schema language to model feature catalogue
information is recommended.
NOTE Natural-language definitions, feature-type aliases, criteria for the birth and death of feature instances, and
other semantic elements of the feature catalogue may be included in a conceptual schema as structured comments or as
attributes.
6.2.3 General requirements
6.2.3.1 Form of names
All feature types, feature attributes, feature associations, association roles, and feature operations included in
a feature catalogue shall be identified by a name that is unique within that feature catalogue. If the name of a
feature type, feature attribute, feature association, association role, or feature operation appears more than
once in that feature catalogue, the definition shall be the same for all occurrences.
6.2.3.2 Form of definitions
Definitions of feature types, feature attributes, feature attribute listed values, feature associations, association
roles, and feature operations shall be given in a natural language. These definitions shall be included in the
catalogue, unless the catalogue specifies a separate definition source. If the same term appears in both the
definition source and the feature catalogue, the definition in the feature catalogue shall apply.
6.2.4 Requirements for feature types
Each feature type shall be identified by a name and defined in a natural language. Each feature type may also
be identified by an alphanumeric code that is unique within the catalogue and it may have a set of aliases. The
feature catalogue shall also include, for each feature type, its feature operations and associated feature
4 © ISO 2005 – All rights reserved
---------------------- Page: 9 ----------------------
ISO 19110:2005(E)
attributes, feature associations and association roles, if any. The use of functional language specifications to
help define feature types is recommended.
6.2.5 Requirements for feature operations
Feature operations, if any, shall be identified and defined for each feature type. Feature attributes involved in
each feature operation shall be specified well as any feature types affected by the operation. The definition
shall include a natural language definition and may be formally specified in a functional language.
6.2.6 Requirements for feature attributes
Feature attributes, if any, shall be identified and defined for each feature type. The definition shall include a
natural language definition and a specified data type for values of the attribute. Each feature attribute may
also be identified by an alphanumeric code that is unique within the catalogue.
6.2.7 Requirements for feature attribute listed values
Feature-attribute listed values, if any, shall be labelled for each feature attribute. The label shall be unique
within the feature attribute of which it is a listed value. Each listed value may also be identified by an
alphanumeric code that is unique within the feature attribute of which it is a listed value.
6.2.8 Requirements for feature associations
Feature associations, if any, shall be named and defined. Each feature association may also be identified by
an alphanumeric code that is unique within the catalogue. The names and roles of the feature types that
participate in the association shall be specified.
6.2.9 Requirements for association roles
Association roles, if any, shall be named and defined. The name of the feature type that holds the role and the
association in which it participates shall be specified.
© ISO 2005 – All rights reserved 5
---------------------- Page: 10 ----------------------
ISO 19110:2005(E)
Annex A
(normative)
Abstract test suite
A.1 Introduction
This normative annex presents the abstract test suite for evaluating conformance to this International
Standard. This abstract test suite contains fifteen test cases and twelve test modules: a test case for the
existence and form of feature catalogue information (A.2); a test case for general feature catalogue
requirements (A.3); test cases for each principal feature catalogue information class (A.4 through A.16); and
test modules for specific subsets of the functionality of a feature catalogue (A.17 through A.28).
Test cases are based on each principal-feature catalogue information class specified in Annex B, Tables B.1
through B.15. Each class-based test case consists of examining each class element (attribute or role) and
verifying that:
the obligation/condition specification for the presence of the element is met;
the maximum number of occurrences of the element is not exceeded;
the type of the value of the element is correct;
NOTE Unless otherwise stated, e.g., by specifying a type in a well-known package or ISO standard, the type
specifications as will be given in ISO/TS 19103 may be applied.
the value of the element is in accordance with the element description;
any specified constraint on the element is met.
Tests on the class as a whole are specified as class-constraints as specified in Annex B, Tables B.1 through
B.15, and/or in test modules.
Test modules are based on useful subsets of the functionality of the feature catalogue template specified in
Annex B. Subsets are organized starting with core functionality capable of representing feature types and
feature attributes that are unique to a feature type (see A.17). The core representation functionality is
extended by supporting one or more of the following
additional feature property types (for association roles, see A.18; for both association roles and feature
operations, see A.19);
additional relationships among feature catalogue information elements (for multiple-use feature attributes,
see A.20; for inheritance, see A.23; for both multiple-use feature attributes and inheritance, see A.26);
both additional feature property types and additional relationships among feature catalogue information
elements (see A.21, A.22, A.24, A.25, A.27 and A.28).
Test modules are specified by the test cases that apply. Test modules A.18 through A.28 extend the core
representation functionality specified by test module A.17. These extensions are summarized in Table 1.
To check that a feature catalogue conforms to this International Standard, verify that all of the requirements in
at least one test module are satisfied.
6 © ISO 2005 – All rights reserved
---------------------- Page: 11 ----------------------
ISO 19110:2005(E)
A.2 Test case for existence and form of feature catalogue information
Information for the test case is as follows:
a) test purpose: verify the existence and form of a feature catalogue;
b) test method: check whether the feature catalogue exists and can be obtained in electronic form, by
obtaining a copy of the feature catalogue such as on a computer disk or through a file
transfer;
c) reference: 6.1;
d) test type: basic.
A.3 Test case for general feature catalogue requirements
Information for the test case is as follows:
a) test purpose: verify that general feature catalogue requirements are met;
b) test method: check
1) if the feature catalogue is specified as applying to a given set of geographic data, then the feature
catalogue documents all of the feature types found in that set of geographic data,
2) whether all feature types, feature attributes, feature associations, association roles, and feature
operations are identified by a name that is unique within the feature catalogue,
3) whether all feature attribute listed values are identified by a label that is unique within the feature
attribute of which it is a listed value,
4) whether all feature types, feature attributes, feature associations, association roles, and feature
operations are either defined or reference a definition from another source,
5) if any feature type, feature attribute, or feature association is identified by an alphanumeric code, that
alphanumeric code is unique within the feature catalogue,
6) if any feature attribute listed value is identified by an alphanumeric code, that alphanumeric code is
unique within the feature attribute of which it is a listed value;
c) reference: 6.2;
d) test type: capability.
A.4 Test case for the feature catalogue class
Information for the test case is as follows:
a) test purpose: verify that the required information is included in objects of class feature catalogue;
b) test method: test each attribute and role listed in Table B.1 by verifying that for each the specified
description, obligation/condition, maximum occurrence, type, and constraint are satisfied;
c) reference: Annex B, Table B.1;
d) test type: capability.
© ISO 2005 – All rights reserved 7
---------------------- Page: 12 ----------------------
ISO 19110:2005(E)
A.5 Test case for the feature type class
Information for the test case is as follows:
a) test purpose: verify that the required information is included in objects of class feature type;
b) test method: test each attribute and role listed in Table B.2 by verifying that for each the specified
description, obligation/condition, maximum occurrence, type, and constraint are satisfied;
c) reference: Annex B, Table B.2;
d) test type: capability.
A.6 Test case for the inheritance relation class
Information for the test case is as follows:
a) test purpose: verify that the required information is included in objects of class inheritance relation;
b) test method: test each attribute and role listed in Table B.3 by verifying that for each the specified
description, obligation/condition, maximum occurrence, type, and constraint are satisfied;
c) reference: Annex B, Table B.3;
d) test type: capability.
A.7 Test case for the feature operation class
Information for the test case is as follows:
a) test purpose: verify that the required information is included in objects of class feature operation;
b) test method: test each attribute and role listed in Table B.5 (and Table B.4) by verifying that for each
the specified description, obligation/condition, maximum occurrence, type, and constraint
are satisfied. In addition:
1) If feature attributes are unique to a feature type (test modules A.19 and A.25), the type of the
following roles shall be FC_FeatureAttribute rather than FC_BoundFeatureAttribute:
i) FC_FeatureOperation::triggeredByValuesOf (Table B.5, line 5.3),
ii) FC_FeatureOperation::observesValuesOf (Table B.5, line 5.4),
iii) FC_FeatureOperation::affectsValuesOf (Table B.5, line 5.5);
2) If the role FC_FeatureOperation::featureType (Table B.4, line 4.4) exists more than once, the
association class FC_Binding for each shall satisfy test case A.8. This condition occurs in test
modules A.22 and A.28;
c) reference: Annex B, Tables B.4 and B.5;
d) test type: capability.
8 © ISO 2005 – All rights reserved
---------------------- Page: 13 ----------------------
ISO 19110:2005(E)
A.8 Test case for the binding class
Information for the test case is as follows:
a) test purpose: verify that the required information is included in objects of class binding;
b) test method: test each attribute listed in Table B.6 by verifying that for each the specified description,
obligation/condition, maximum occurrence, type, and constraint are satisfied;
c) reference: Annex B, Table B.6;
d) test type: capability.
A.9 Test case for the constraint class
Information for the test case is as follows:
a) test purpose: verify that the required information is included in objects of class constraint;
b) test method: test each attribute listed in Table B.7 by verifying that for each the specified description,
obligation/condition, maximum occurrence, type, and constraint are satisfied;
c) reference: Annex B, Table B.7;
d) test type: capability.
A.10 Test case for the feature attribute class
Information for the test case is as follows:
a) test purpose: verify that the required information is included in objects of class feature attribute;
b) test method: test each attribute and role listed in Table B.8 (and Table B.4) by verifying that for each
the specified description, obligation/condition, maximum occurrence, type, and constraint
are satisfied. In addition:
If the role FC_FeatureAttribute::featureType (Table B.4, line 4.4) exists more than once,
the association class FC_Binding for each shall satisfy test case A.8. This condition
occurs in test modules A.20, A.21, A.22, A.26, A.27 and A.28;
c) reference: Annex B, Tables B.4 and B.8;
d) test type: capability.
A.11 Test case for the association role class
Information for the test case is as follows:
a) test purpose: verify that the required information is included in objects of class association role;
b) test method: test each attribute and role listed in Table B.9 (and Table B.4) by verifying that for each
the specified description, obligation/condition, maximum occurrence, type, and constraint
are satisfied. In addition:
1) Verify that the value of attribute type (Table B.
...
INTERNATIONAL ISO
STANDARD 19110
First edition
2005-02-15
Geographic information — Methodology
for feature cataloguing
Information géographique — Méthodologie de catalogage des entités
Reference number
ISO 19110:2005(E)
©
ISO 2005
---------------------- Page: 1 ----------------------
ISO 19110:2005(E)
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.
© ISO 2005
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing 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 copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO 2005 – All rights reserved
---------------------- Page: 2 ----------------------
ISO 19110:2005(E)
Contents Page
Foreword. iv
Introduction . v
1 Scope. 1
2 Conformance . 1
3 Normative references . 2
4 Terms and definitions. 2
5 Abbreviations . 3
6 Principal requirements . 4
6.1 Feature catalogue . 4
6.2 Information elements. 4
Annex A (normative) Abstract test suite. 6
Annex B (normative) Feature catalogue template. 16
Annex C (informative) Feature cataloguing examples. 31
Annex D (informative) Feature cataloguing concepts . 46
Bibliography . 55
© ISO 2005 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO 19110:2005(E)
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 19110 was prepared by Technical Committee ISO/TC 211, Geographic information/Geomatics.
iv © ISO 2005 – All rights reserved
---------------------- Page: 4 ----------------------
ISO 19110:2005(E)
Introduction
Geographic features are real world phenomena associated with a location relative to the Earth, about which
data are collected, maintained, and disseminated. Feature catalogues defining the types of features, their
operations, attributes, and associations represented in geographic data are indispensable to turning the data
into usable information. Such feature catalogues promote the dissemination, sharing, and use of geographic
data through providing a better understanding of the content and meaning of the data. Unless suppliers and
users of geographic data have a shared understanding of the kinds of real world phenomena represented by
the data, users will be unable to judge whether the data supplied are fit for their purpose.
The availability of standard feature catalogues that can be used multiple times will reduce costs of data
acquisition and simplify the process of product specification for geographic datasets.
This International Standard provides a standard framework for organizing and reporting the classification of
real world phenomena in a set of geographic data. Any set of geographic data is a greatly simplified and
reduced abstraction of a complex and diverse world. A catalogue of feature types can never capture the
richness of geographic reality. However, such a feature catalogue should present the particular abstraction
represented in a given dataset clearly, precisely, and in a form readily understandable and accessible to users
of the data.
Geographic features occur at two levels: instances and types. At the instance level, a geographic feature is
represented as a discrete phenomenon that is associated with its geographic and temporal coordinates and
may be portrayed by a particular graphic symbol. These individual feature instances are grouped into classes
with common characteristics: feature types. It is recognized that geographic information is subjectively
perceived and that its content depends upon the needs of particular applications. The needs of particular
applications determine the way instances are grouped into types within a particular classification scheme.
ISO 19109, Geographic information ― Rules for application schema specifies how data shall be organized to
reflect the particular needs of applications with similar data requirements.
NOTE The full description of the contents and structure of a geographic dataset is given by the application schema
developed in compliance with ISO 19109. The feature catalogue defines the meaning of the feature types and their
associated feature attributes, feature operations and feature associations contained in the application schema.
The collection criteria used to identify individual real world phenomena and to represent them as feature
instances in a dataset are not specified in this International Standard. Because they are not included in the
standards, collection criteria should be included separately in the product specification for each dataset.
A standard way of organizing feature catalogue information will not automatically result in harmonization or
interoperability between applications. In situations where classifications of features differ, this International
Standard may at least serve to clarify the differences and thereby help to avoid the errors that would result
from ignoring them. It may also be used as a standard framework within which to harmonize existing feature
catalogues that have overlapping domains.
© ISO 2005 – All rights reserved v
---------------------- Page: 5 ----------------------
INTERNATIONAL STANDARD ISO 19110:2005(E)
Geographic information — Methodology for feature cataloguing
1 Scope
This International Standard defines the methodology for cataloguing feature types. This International Standard
specifies how the classification of feature types is organized into a feature catalogue and presented to the
users of a set of geographic data. This International Standard is applicable to creating catalogues of feature
types in previously uncatalogued domains and to revising existing feature catalogues to comply with standard
practice. This International Standard applies to the cataloguing of feature types that are represented in digital
form. Its principles can be extended to the cataloguing of other forms of geographic data.
This International Standard is applicable to the definition of geographic features at the type level. This
International Standard is not applicable to the representation of individual instances of each type. This
International Standard excludes spatial, temporal, and portrayal schemas as specified in ISO 19107,
ISO 19108, and ISO 19117, respectively. It also excludes collection criteria for feature instances.
This International Standard may be used as a basis for defining the universe of discourse being modelled in a
particular application, or to standardize general aspects of real world features being modelled in more than
one application.
2 Conformance
Because this International Standard specifies a number of options that are not required for all feature
catalogues, this clause specifies 12 conformance classes. These classes are differentiated on the basis of
three criteria:
a) What elements of a feature type are required in a catalogue:
1) feature attributes only?
2) feature attributes and feature associations?
3) feature attributes, feature associations, and feature operations?
b) Is there a requirement to link feature attributes, feature associations, and feature operations to only one
feature type or may they be linked to multiple feature types?
c) Is there a requirement to include inheritance relationships in the feature catalogue?
Annex A specifies a test module for each of the conformance classes, as shown in Table 1.
© ISO 2005 – All rights reserved 1
---------------------- Page: 6 ----------------------
ISO 19110:2005(E)
Table 1 — Conformance classes
Attributes, Properties Inheritance
Attributes Attributes and
associations and associated with relationships Test module
only associations
operations multiple features included
X — — — — A.17
— X — — — A.18
— — X — — A.19
X — — X — A.20
— X — X — A.21
— — X X — A.22
X — — — X A.23
— X — — X A.24
— — X — X A.25
X — — X X A.26
— X — X X A.27
— — X X X A.28
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.
1)
ISO/TS 19103:— , Geographic information — Conceptual schema language
1)
ISO 19109:— , Geographic information — Rules for application schema
ISO 19115:2003, Geographic information — Metadata
4 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
4.1
feature
abstraction of real world phenomena
[ISO 19101]
EXAMPLE The phenomenon named ‘Eiffel Tower’ may be classified with other similar phenomena into a feature
type ‘tower’.
NOTE A feature may occur as a type or an instance. Feature type or feature instance should be used when only one
is meant.
1) To be published.
2 © ISO 2005 – All rights reserved
---------------------- Page: 7 ----------------------
ISO 19110:2005(E)
4.2
feature association
relationship that links instances of one feature (4.1) type with instances of the same or a different feature type
4.3
feature attribute
characteristic of a feature (4.1)
[ISO 19101]
EXAMPLE 1 A feature attribute named ‘colour’ may have an attribute value ‘green’ which belongs to the data type
‘text’.
EXAMPLE 2 A feature attribute named ‘length’ may have an attribute value ’82,4’ which belongs to the data type ‘real’.
NOTE A feature attribute has a name, a data type, and a value domain associated to it. A feature attribute for a
feature instance also has an attribute value taken from the value domain.
4.4
feature catalogue
catalogue containing definitions and descriptions of the feature (4.1) types, feature attributes (4.3), and
feature associations (4.2) occurring in one or more sets of geographic data, together with any feature
operations that may be applied
4.5
feature operation
operation that every instance of a feature (4.1) type may perform
EXAMPLE A feature operation upon a ‘dam’ is to raise the dam. The results of this operation are to raise the height
of the ‘dam’ and the level of water in a ‘reservoir’.
NOTE Sometimes feature operations provide a basis for feature type definition.
4.6
functional language
language in which feature operations are formally specified
NOTE In a functional language, feature types may be represented as abstract data types.
5 Abbreviations
DIGEST Digital Geographic Information Exchange Standard
FACC Feature and Attribute Coding Catalogue
GFM General Feature Model
HTTP Hyper Text Transfer Protocol
IHO International Hydrographic Organization
TS Technical Specification
UML Unified Modeling Language
URI Uniform Resource Identifier
XML eXtensible Markup Language
© ISO 2005 – All rights reserved 3
---------------------- Page: 8 ----------------------
ISO 19110:2005(E)
6 Principal requirements
6.1 Feature catalogue
A feature catalogue shall present the abstraction of reality represented in one or more sets of geographic data
as a defined classification of phenomena. The basic level of classification in a feature catalogue shall be the
feature type. A feature catalogue shall be available in electronic form for any set of geographic data that
contains features. A feature catalogue may also comply with the specifications of this International Standard
independently of any existing set of geographic data.
6.2 Information elements
6.2.1 Introduction
The following clauses specify general and specific requirements for feature catalogue information elements.
Annex B specifies detailed requirements. Annex C illustrates the application of these requirements. Annex D
discusses the application of feature operations as the conceptual basis for determining feature types in a
feature catalogue.
6.2.2 Completeness
A template for the representation of feature classification information is specified in Annex B. A feature
catalogue prepared according to this template shall document all of the feature types found in a given set of
geographic data. The feature catalogue shall include identification information as specified in Annex B. The
feature catalogue shall include definitions and descriptions of all feature types contained in the data, including
any feature attributes and feature associations contained in the data that are associated with each feature
type, and optionally including feature operations that are supported by the data. To ensure predictability and
comparability of feature catalogue content across different applications, it is recommended that the feature
catalogue should include only the elements specified in Annex B. To maximize the usefulness of a feature
catalogue across different applications, the use of a conceptual schema language to model feature catalogue
information is recommended.
NOTE Natural-language definitions, feature-type aliases, criteria for the birth and death of feature instances, and
other semantic elements of the feature catalogue may be included in a conceptual schema as structured comments or as
attributes.
6.2.3 General requirements
6.2.3.1 Form of names
All feature types, feature attributes, feature associations, association roles, and feature operations included in
a feature catalogue shall be identified by a name that is unique within that feature catalogue. If the name of a
feature type, feature attribute, feature association, association role, or feature operation appears more than
once in that feature catalogue, the definition shall be the same for all occurrences.
6.2.3.2 Form of definitions
Definitions of feature types, feature attributes, feature attribute listed values, feature associations, association
roles, and feature operations shall be given in a natural language. These definitions shall be included in the
catalogue, unless the catalogue specifies a separate definition source. If the same term appears in both the
definition source and the feature catalogue, the definition in the feature catalogue shall apply.
6.2.4 Requirements for feature types
Each feature type shall be identified by a name and defined in a natural language. Each feature type may also
be identified by an alphanumeric code that is unique within the catalogue and it may have a set of aliases. The
feature catalogue shall also include, for each feature type, its feature operations and associated feature
4 © ISO 2005 – All rights reserved
---------------------- Page: 9 ----------------------
ISO 19110:2005(E)
attributes, feature associations and association roles, if any. The use of functional language specifications to
help define feature types is recommended.
6.2.5 Requirements for feature operations
Feature operations, if any, shall be identified and defined for each feature type. Feature attributes involved in
each feature operation shall be specified well as any feature types affected by the operation. The definition
shall include a natural language definition and may be formally specified in a functional language.
6.2.6 Requirements for feature attributes
Feature attributes, if any, shall be identified and defined for each feature type. The definition shall include a
natural language definition and a specified data type for values of the attribute. Each feature attribute may
also be identified by an alphanumeric code that is unique within the catalogue.
6.2.7 Requirements for feature attribute listed values
Feature-attribute listed values, if any, shall be labelled for each feature attribute. The label shall be unique
within the feature attribute of which it is a listed value. Each listed value may also be identified by an
alphanumeric code that is unique within the feature attribute of which it is a listed value.
6.2.8 Requirements for feature associations
Feature associations, if any, shall be named and defined. Each feature association may also be identified by
an alphanumeric code that is unique within the catalogue. The names and roles of the feature types that
participate in the association shall be specified.
6.2.9 Requirements for association roles
Association roles, if any, shall be named and defined. The name of the feature type that holds the role and the
association in which it participates shall be specified.
© ISO 2005 – All rights reserved 5
---------------------- Page: 10 ----------------------
ISO 19110:2005(E)
Annex A
(normative)
Abstract test suite
A.1 Introduction
This normative annex presents the abstract test suite for evaluating conformance to this International
Standard. This abstract test suite contains fifteen test cases and twelve test modules: a test case for the
existence and form of feature catalogue information (A.2); a test case for general feature catalogue
requirements (A.3); test cases for each principal feature catalogue information class (A.4 through A.16); and
test modules for specific subsets of the functionality of a feature catalogue (A.17 through A.28).
Test cases are based on each principal-feature catalogue information class specified in Annex B, Tables B.1
through B.15. Each class-based test case consists of examining each class element (attribute or role) and
verifying that:
the obligation/condition specification for the presence of the element is met;
the maximum number of occurrences of the element is not exceeded;
the type of the value of the element is correct;
NOTE Unless otherwise stated, e.g., by specifying a type in a well-known package or ISO standard, the type
specifications as will be given in ISO/TS 19103 may be applied.
the value of the element is in accordance with the element description;
any specified constraint on the element is met.
Tests on the class as a whole are specified as class-constraints as specified in Annex B, Tables B.1 through
B.15, and/or in test modules.
Test modules are based on useful subsets of the functionality of the feature catalogue template specified in
Annex B. Subsets are organized starting with core functionality capable of representing feature types and
feature attributes that are unique to a feature type (see A.17). The core representation functionality is
extended by supporting one or more of the following
additional feature property types (for association roles, see A.18; for both association roles and feature
operations, see A.19);
additional relationships among feature catalogue information elements (for multiple-use feature attributes,
see A.20; for inheritance, see A.23; for both multiple-use feature attributes and inheritance, see A.26);
both additional feature property types and additional relationships among feature catalogue information
elements (see A.21, A.22, A.24, A.25, A.27 and A.28).
Test modules are specified by the test cases that apply. Test modules A.18 through A.28 extend the core
representation functionality specified by test module A.17. These extensions are summarized in Table 1.
To check that a feature catalogue conforms to this International Standard, verify that all of the requirements in
at least one test module are satisfied.
6 © ISO 2005 – All rights reserved
---------------------- Page: 11 ----------------------
ISO 19110:2005(E)
A.2 Test case for existence and form of feature catalogue information
Information for the test case is as follows:
a) test purpose: verify the existence and form of a feature catalogue;
b) test method: check whether the feature catalogue exists and can be obtained in electronic form, by
obtaining a copy of the feature catalogue such as on a computer disk or through a file
transfer;
c) reference: 6.1;
d) test type: basic.
A.3 Test case for general feature catalogue requirements
Information for the test case is as follows:
a) test purpose: verify that general feature catalogue requirements are met;
b) test method: check
1) if the feature catalogue is specified as applying to a given set of geographic data, then the feature
catalogue documents all of the feature types found in that set of geographic data,
2) whether all feature types, feature attributes, feature associations, association roles, and feature
operations are identified by a name that is unique within the feature catalogue,
3) whether all feature attribute listed values are identified by a label that is unique within the feature
attribute of which it is a listed value,
4) whether all feature types, feature attributes, feature associations, association roles, and feature
operations are either defined or reference a definition from another source,
5) if any feature type, feature attribute, or feature association is identified by an alphanumeric code, that
alphanumeric code is unique within the feature catalogue,
6) if any feature attribute listed value is identified by an alphanumeric code, that alphanumeric code is
unique within the feature attribute of which it is a listed value;
c) reference: 6.2;
d) test type: capability.
A.4 Test case for the feature catalogue class
Information for the test case is as follows:
a) test purpose: verify that the required information is included in objects of class feature catalogue;
b) test method: test each attribute and role listed in Table B.1 by verifying that for each the specified
description, obligation/condition, maximum occurrence, type, and constraint are satisfied;
c) reference: Annex B, Table B.1;
d) test type: capability.
© ISO 2005 – All rights reserved 7
---------------------- Page: 12 ----------------------
ISO 19110:2005(E)
A.5 Test case for the feature type class
Information for the test case is as follows:
a) test purpose: verify that the required information is included in objects of class feature type;
b) test method: test each attribute and role listed in Table B.2 by verifying that for each the specified
description, obligation/condition, maximum occurrence, type, and constraint are satisfied;
c) reference: Annex B, Table B.2;
d) test type: capability.
A.6 Test case for the inheritance relation class
Information for the test case is as follows:
a) test purpose: verify that the required information is included in objects of class inheritance relation;
b) test method: test each attribute and role listed in Table B.3 by verifying that for each the specified
description, obligation/condition, maximum occurrence, type, and constraint are satisfied;
c) reference: Annex B, Table B.3;
d) test type: capability.
A.7 Test case for the feature operation class
Information for the test case is as follows:
a) test purpose: verify that the required information is included in objects of class feature operation;
b) test method: test each attribute and role listed in Table B.5 (and Table B.4) by verifying that for each
the specified description, obligation/condition, maximum occurrence, type, and constraint
are satisfied. In addition:
1) If feature attributes are unique to a feature type (test modules A.19 and A.25), the type of the
following roles shall be FC_FeatureAttribute rather than FC_BoundFeatureAttribute:
i) FC_FeatureOperation::triggeredByValuesOf (Table B.5, line 5.3),
ii) FC_FeatureOperation::observesValuesOf (Table B.5, line 5.4),
iii) FC_FeatureOperation::affectsValuesOf (Table B.5, line 5.5);
2) If the role FC_FeatureOperation::featureType (Table B.4, line 4.4) exists more than once, the
association class FC_Binding for each shall satisfy test case A.8. This condition occurs in test
modules A.22 and A.28;
c) reference: Annex B, Tables B.4 and B.5;
d) test type: capability.
8 © ISO 2005 – All rights reserved
---------------------- Page: 13 ----------------------
ISO 19110:2005(E)
A.8 Test case for the binding class
Information for the test case is as follows:
a) test purpose: verify that the required information is included in objects of class binding;
b) test method: test each attribute listed in Table B.6 by verifying that for each the specified description,
obligation/condition, maximum occurrence, type, and constraint are satisfied;
c) reference: Annex B, Table B.6;
d) test type: capability.
A.9 Test case for the constraint class
Information for the test case is as follows:
a) test purpose: verify that the required information is included in objects of class constraint;
b) test method: test each attribute listed in Table B.7 by verifying that for each the specified description,
obligation/condition, maximum occurrence, type, and constraint are satisfied;
c) reference: Annex B, Table B.7;
d) test type: capability.
A.10 Test case for the feature attribute class
Information for the test case is as follows:
a) test purpose: verify that the required information is included in objects of class feature attribute;
b) test method: test each attribute and role listed in Table B.8 (and Table B.4) by verifying that for each
the specified description, obligation/condition, maximum occurrence, type, and constraint
are satisfied. In addition:
If the role FC_FeatureAttribute::featureType (Table B.4, line 4.4) exists more than once,
the association class FC_Binding for each shall satisfy test case A.8. This condition
occurs in test modules A.20, A.21, A.22, A.26, A.27 and A.28;
c) reference: Annex B, Tables B.4 and B.8;
d) test type: capability.
A.11 Test case for the association role class
Information for the test case is as follows:
a) test purpose: verify that the required information is included in objects of class association role;
b) test method: test each attribute and role listed in Table B.9 (and Table B.4) by verifying that for each
the specified description, obligation/condition, maximum occurrence, type, and constraint
are satisfied. In addition:
1) Verify that the value o
...
SLOVENSKI STANDARD
SIST ISO 19110:2005
01-december-2005
Geografske informacije – Metodologija za objektne kataloge
Geographic information -- Methodology for feature cataloguing
Information géographique -- Méthodologie de catalogage des entités
Ta slovenski standard je istoveten z: ISO 19110:2005
ICS:
07.040 Astronomija. Geodezija. Astronomy. Geodesy.
Geografija Geography
35.240.70 Uporabniške rešitve IT v IT applications in science
znanosti
SIST ISO 19110:2005 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
SIST ISO 19110:2005
---------------------- Page: 2 ----------------------
SIST ISO 19110:2005
INTERNATIONAL ISO
STANDARD 19110
First edition
2005-02-15
Geographic information — Methodology
for feature cataloguing
Information géographique — Méthodologie de catalogage des entités
Reference number
ISO 19110:2005(E)
©
ISO 2005
---------------------- Page: 3 ----------------------
SIST ISO 19110:2005
ISO 19110:2005(E)
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.
© ISO 2005
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing 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 copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO 2005 – All rights reserved
---------------------- Page: 4 ----------------------
SIST ISO 19110:2005
ISO 19110:2005(E)
Contents Page
Foreword. iv
Introduction . v
1 Scope. 1
2 Conformance . 1
3 Normative references . 2
4 Terms and definitions. 2
5 Abbreviations . 3
6 Principal requirements . 4
6.1 Feature catalogue . 4
6.2 Information elements. 4
Annex A (normative) Abstract test suite. 6
Annex B (normative) Feature catalogue template. 16
Annex C (informative) Feature cataloguing examples. 31
Annex D (informative) Feature cataloguing concepts . 46
Bibliography . 55
© ISO 2005 – All rights reserved iii
---------------------- Page: 5 ----------------------
SIST ISO 19110:2005
ISO 19110:2005(E)
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 19110 was prepared by Technical Committee ISO/TC 211, Geographic information/Geomatics.
iv © ISO 2005 – All rights reserved
---------------------- Page: 6 ----------------------
SIST ISO 19110:2005
ISO 19110:2005(E)
Introduction
Geographic features are real world phenomena associated with a location relative to the Earth, about which
data are collected, maintained, and disseminated. Feature catalogues defining the types of features, their
operations, attributes, and associations represented in geographic data are indispensable to turning the data
into usable information. Such feature catalogues promote the dissemination, sharing, and use of geographic
data through providing a better understanding of the content and meaning of the data. Unless suppliers and
users of geographic data have a shared understanding of the kinds of real world phenomena represented by
the data, users will be unable to judge whether the data supplied are fit for their purpose.
The availability of standard feature catalogues that can be used multiple times will reduce costs of data
acquisition and simplify the process of product specification for geographic datasets.
This International Standard provides a standard framework for organizing and reporting the classification of
real world phenomena in a set of geographic data. Any set of geographic data is a greatly simplified and
reduced abstraction of a complex and diverse world. A catalogue of feature types can never capture the
richness of geographic reality. However, such a feature catalogue should present the particular abstraction
represented in a given dataset clearly, precisely, and in a form readily understandable and accessible to users
of the data.
Geographic features occur at two levels: instances and types. At the instance level, a geographic feature is
represented as a discrete phenomenon that is associated with its geographic and temporal coordinates and
may be portrayed by a particular graphic symbol. These individual feature instances are grouped into classes
with common characteristics: feature types. It is recognized that geographic information is subjectively
perceived and that its content depends upon the needs of particular applications. The needs of particular
applications determine the way instances are grouped into types within a particular classification scheme.
ISO 19109, Geographic information ― Rules for application schema specifies how data shall be organized to
reflect the particular needs of applications with similar data requirements.
NOTE The full description of the contents and structure of a geographic dataset is given by the application schema
developed in compliance with ISO 19109. The feature catalogue defines the meaning of the feature types and their
associated feature attributes, feature operations and feature associations contained in the application schema.
The collection criteria used to identify individual real world phenomena and to represent them as feature
instances in a dataset are not specified in this International Standard. Because they are not included in the
standards, collection criteria should be included separately in the product specification for each dataset.
A standard way of organizing feature catalogue information will not automatically result in harmonization or
interoperability between applications. In situations where classifications of features differ, this International
Standard may at least serve to clarify the differences and thereby help to avoid the errors that would result
from ignoring them. It may also be used as a standard framework within which to harmonize existing feature
catalogues that have overlapping domains.
© ISO 2005 – All rights reserved v
---------------------- Page: 7 ----------------------
SIST ISO 19110:2005
---------------------- Page: 8 ----------------------
SIST ISO 19110:2005
INTERNATIONAL STANDARD ISO 19110:2005(E)
Geographic information — Methodology for feature cataloguing
1 Scope
This International Standard defines the methodology for cataloguing feature types. This International Standard
specifies how the classification of feature types is organized into a feature catalogue and presented to the
users of a set of geographic data. This International Standard is applicable to creating catalogues of feature
types in previously uncatalogued domains and to revising existing feature catalogues to comply with standard
practice. This International Standard applies to the cataloguing of feature types that are represented in digital
form. Its principles can be extended to the cataloguing of other forms of geographic data.
This International Standard is applicable to the definition of geographic features at the type level. This
International Standard is not applicable to the representation of individual instances of each type. This
International Standard excludes spatial, temporal, and portrayal schemas as specified in ISO 19107,
ISO 19108, and ISO 19117, respectively. It also excludes collection criteria for feature instances.
This International Standard may be used as a basis for defining the universe of discourse being modelled in a
particular application, or to standardize general aspects of real world features being modelled in more than
one application.
2 Conformance
Because this International Standard specifies a number of options that are not required for all feature
catalogues, this clause specifies 12 conformance classes. These classes are differentiated on the basis of
three criteria:
a) What elements of a feature type are required in a catalogue:
1) feature attributes only?
2) feature attributes and feature associations?
3) feature attributes, feature associations, and feature operations?
b) Is there a requirement to link feature attributes, feature associations, and feature operations to only one
feature type or may they be linked to multiple feature types?
c) Is there a requirement to include inheritance relationships in the feature catalogue?
Annex A specifies a test module for each of the conformance classes, as shown in Table 1.
© ISO 2005 – All rights reserved 1
---------------------- Page: 9 ----------------------
SIST ISO 19110:2005
ISO 19110:2005(E)
Table 1 — Conformance classes
Attributes, Properties Inheritance
Attributes Attributes and
associations and associated with relationships Test module
only associations
operations multiple features included
X — — — — A.17
— X — — — A.18
— — X — — A.19
X — — X — A.20
— X — X — A.21
— — X X — A.22
X — — — X A.23
— X — — X A.24
— — X — X A.25
X — — X X A.26
— X — X X A.27
— — X X X A.28
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.
1)
ISO/TS 19103:— , Geographic information — Conceptual schema language
1)
ISO 19109:— , Geographic information — Rules for application schema
ISO 19115:2003, Geographic information — Metadata
4 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
4.1
feature
abstraction of real world phenomena
[ISO 19101]
EXAMPLE The phenomenon named ‘Eiffel Tower’ may be classified with other similar phenomena into a feature
type ‘tower’.
NOTE A feature may occur as a type or an instance. Feature type or feature instance should be used when only one
is meant.
1) To be published.
2 © ISO 2005 – All rights reserved
---------------------- Page: 10 ----------------------
SIST ISO 19110:2005
ISO 19110:2005(E)
4.2
feature association
relationship that links instances of one feature (4.1) type with instances of the same or a different feature type
4.3
feature attribute
characteristic of a feature (4.1)
[ISO 19101]
EXAMPLE 1 A feature attribute named ‘colour’ may have an attribute value ‘green’ which belongs to the data type
‘text’.
EXAMPLE 2 A feature attribute named ‘length’ may have an attribute value ’82,4’ which belongs to the data type ‘real’.
NOTE A feature attribute has a name, a data type, and a value domain associated to it. A feature attribute for a
feature instance also has an attribute value taken from the value domain.
4.4
feature catalogue
catalogue containing definitions and descriptions of the feature (4.1) types, feature attributes (4.3), and
feature associations (4.2) occurring in one or more sets of geographic data, together with any feature
operations that may be applied
4.5
feature operation
operation that every instance of a feature (4.1) type may perform
EXAMPLE A feature operation upon a ‘dam’ is to raise the dam. The results of this operation are to raise the height
of the ‘dam’ and the level of water in a ‘reservoir’.
NOTE Sometimes feature operations provide a basis for feature type definition.
4.6
functional language
language in which feature operations are formally specified
NOTE In a functional language, feature types may be represented as abstract data types.
5 Abbreviations
DIGEST Digital Geographic Information Exchange Standard
FACC Feature and Attribute Coding Catalogue
GFM General Feature Model
HTTP Hyper Text Transfer Protocol
IHO International Hydrographic Organization
TS Technical Specification
UML Unified Modeling Language
URI Uniform Resource Identifier
XML eXtensible Markup Language
© ISO 2005 – All rights reserved 3
---------------------- Page: 11 ----------------------
SIST ISO 19110:2005
ISO 19110:2005(E)
6 Principal requirements
6.1 Feature catalogue
A feature catalogue shall present the abstraction of reality represented in one or more sets of geographic data
as a defined classification of phenomena. The basic level of classification in a feature catalogue shall be the
feature type. A feature catalogue shall be available in electronic form for any set of geographic data that
contains features. A feature catalogue may also comply with the specifications of this International Standard
independently of any existing set of geographic data.
6.2 Information elements
6.2.1 Introduction
The following clauses specify general and specific requirements for feature catalogue information elements.
Annex B specifies detailed requirements. Annex C illustrates the application of these requirements. Annex D
discusses the application of feature operations as the conceptual basis for determining feature types in a
feature catalogue.
6.2.2 Completeness
A template for the representation of feature classification information is specified in Annex B. A feature
catalogue prepared according to this template shall document all of the feature types found in a given set of
geographic data. The feature catalogue shall include identification information as specified in Annex B. The
feature catalogue shall include definitions and descriptions of all feature types contained in the data, including
any feature attributes and feature associations contained in the data that are associated with each feature
type, and optionally including feature operations that are supported by the data. To ensure predictability and
comparability of feature catalogue content across different applications, it is recommended that the feature
catalogue should include only the elements specified in Annex B. To maximize the usefulness of a feature
catalogue across different applications, the use of a conceptual schema language to model feature catalogue
information is recommended.
NOTE Natural-language definitions, feature-type aliases, criteria for the birth and death of feature instances, and
other semantic elements of the feature catalogue may be included in a conceptual schema as structured comments or as
attributes.
6.2.3 General requirements
6.2.3.1 Form of names
All feature types, feature attributes, feature associations, association roles, and feature operations included in
a feature catalogue shall be identified by a name that is unique within that feature catalogue. If the name of a
feature type, feature attribute, feature association, association role, or feature operation appears more than
once in that feature catalogue, the definition shall be the same for all occurrences.
6.2.3.2 Form of definitions
Definitions of feature types, feature attributes, feature attribute listed values, feature associations, association
roles, and feature operations shall be given in a natural language. These definitions shall be included in the
catalogue, unless the catalogue specifies a separate definition source. If the same term appears in both the
definition source and the feature catalogue, the definition in the feature catalogue shall apply.
6.2.4 Requirements for feature types
Each feature type shall be identified by a name and defined in a natural language. Each feature type may also
be identified by an alphanumeric code that is unique within the catalogue and it may have a set of aliases. The
feature catalogue shall also include, for each feature type, its feature operations and associated feature
4 © ISO 2005 – All rights reserved
---------------------- Page: 12 ----------------------
SIST ISO 19110:2005
ISO 19110:2005(E)
attributes, feature associations and association roles, if any. The use of functional language specifications to
help define feature types is recommended.
6.2.5 Requirements for feature operations
Feature operations, if any, shall be identified and defined for each feature type. Feature attributes involved in
each feature operation shall be specified well as any feature types affected by the operation. The definition
shall include a natural language definition and may be formally specified in a functional language.
6.2.6 Requirements for feature attributes
Feature attributes, if any, shall be identified and defined for each feature type. The definition shall include a
natural language definition and a specified data type for values of the attribute. Each feature attribute may
also be identified by an alphanumeric code that is unique within the catalogue.
6.2.7 Requirements for feature attribute listed values
Feature-attribute listed values, if any, shall be labelled for each feature attribute. The label shall be unique
within the feature attribute of which it is a listed value. Each listed value may also be identified by an
alphanumeric code that is unique within the feature attribute of which it is a listed value.
6.2.8 Requirements for feature associations
Feature associations, if any, shall be named and defined. Each feature association may also be identified by
an alphanumeric code that is unique within the catalogue. The names and roles of the feature types that
participate in the association shall be specified.
6.2.9 Requirements for association roles
Association roles, if any, shall be named and defined. The name of the feature type that holds the role and the
association in which it participates shall be specified.
© ISO 2005 – All rights reserved 5
---------------------- Page: 13 ----------------------
SIST ISO 19110:2005
ISO 19110:2005(E)
Annex A
(normative)
Abstract test suite
A.1 Introduction
This normative annex presents the abstract test suite for evaluating conformance to this International
Standard. This abstract test suite contains fifteen test cases and twelve test modules: a test case for the
existence and form of feature catalogue information (A.2); a test case for general feature catalogue
requirements (A.3); test cases for each principal feature catalogue information class (A.4 through A.16); and
test modules for specific subsets of the functionality of a feature catalogue (A.17 through A.28).
Test cases are based on each principal-feature catalogue information class specified in Annex B, Tables B.1
through B.15. Each class-based test case consists of examining each class element (attribute or role) and
verifying that:
the obligation/condition specification for the presence of the element is met;
the maximum number of occurrences of the element is not exceeded;
the type of the value of the element is correct;
NOTE Unless otherwise stated, e.g., by specifying a type in a well-known package or ISO standard, the type
specifications as will be given in ISO/TS 19103 may be applied.
the value of the element is in accordance with the element description;
any specified constraint on the element is met.
Tests on the class as a whole are specified as class-constraints as specified in Annex B, Tables B.1 through
B.15, and/or in test modules.
Test modules are based on useful subsets of the functionality of the feature catalogue template specified in
Annex B. Subsets are organized starting with core functionality capable of representing feature types and
feature attributes that are unique to a feature type (see A.17). The core representation functionality is
extended by supporting one or more of the following
additional feature property types (for association roles, see A.18; for both association roles and feature
operations, see A.19);
additional relationships among feature catalogue information elements (for multiple-use feature attributes,
see A.20; for inheritance, see A.23; for both multiple-use feature attributes and inheritance, see A.26);
both additional feature property types and additional relationships among feature catalogue information
elements (see A.21, A.22, A.24, A.25, A.27 and A.28).
Test modules are specified by the test cases that apply. Test modules A.18 through A.28 extend the core
representation functionality specified by test module A.17. These extensions are summarized in Table 1.
To check that a feature catalogue conforms to this International Standard, verify that all of the requirements in
at least one test module are satisfied.
6 © ISO 2005 – All rights reserved
---------------------- Page: 14 ----------------------
SIST ISO 19110:2005
ISO 19110:2005(E)
A.2 Test case for existence and form of feature catalogue information
Information for the test case is as follows:
a) test purpose: verify the existence and form of a feature catalogue;
b) test method: check whether the feature catalogue exists and can be obtained in electronic form, by
obtaining a copy of the feature catalogue such as on a computer disk or through a file
transfer;
c) reference: 6.1;
d) test type: basic.
A.3 Test case for general feature catalogue requirements
Information for the test case is as follows:
a) test purpose: verify that general feature catalogue requirements are met;
b) test method: check
1) if the feature catalogue is specified as applying to a given set of geographic data, then the feature
catalogue documents all of the feature types found in that set of geographic data,
2) whether all feature types, feature attributes, feature associations, association roles, and feature
operations are identified by a name that is unique within the feature catalogue,
3) whether all feature attribute listed values are identified by a label that is unique within the feature
attribute of which it is a listed value,
4) whether all feature types, feature attributes, feature associations, association roles, and feature
operations are either defined or reference a definition from another source,
5) if any feature type, feature attribute, or feature association is identified by an alphanumeric code, that
alphanumeric code is unique within the feature catalogue,
6) if any feature attribute listed value is identified by an alphanumeric code, that alphanumeric code is
unique within the feature attribute of which it is a listed value;
c) reference: 6.2;
d) test type: capability.
A.4 Test case for the feature catalogue class
Information for the test case is as follows:
a) test purpose: verify that the required information is included in objects of class feature catalogue;
b) test method: test each attribute and role listed in Table B.1 by verifying that for each the specified
description, obligation/condition, maximum occurrence, type, and constraint are satisfied;
c) reference: Annex B, Table B.1;
d) test type: capability.
© ISO 2005 – All rights reserved 7
---------------------- Page: 15 ----------------------
SIST ISO 19110:2005
ISO 19110:2005(E)
A.5 Test case for the feature type class
Information for the test case is as follows:
a) test purpose: verify that the required information is included in objects of class feature type;
b) test method: test each attribute and role listed in Table B.2 by verifying that for each the specified
description, obligation/condition, maximum occurrence, type, and constraint are satisfied;
c) reference: Annex B, Table B.2;
d) test type: capability.
A.6 Test case for the inheritance relation class
Information for the test case is as follows:
a) test purpose: verify that the required information is included in objects of class inheritance relation;
b) test method: test each attribute and role listed in Table B.3 by verifying that for each the specified
description, obligation/condition, maximum occurrence, type, and constraint are satisfied;
c) reference: Annex B, Table B.3;
d) test type: capability.
A.7 Test case for the feature operation class
Information for the test case is as follows:
a) test purpose: verify that the required information is included in objects of class feature operation;
b) test method: test each attribute and role listed in Table B.5 (and Table B.4) by verifying that for each
the specified description, obligation/condition, maximum occurrence, type, and constraint
are satisfied. In addition:
1) If feature attributes are unique to a feature type (test modules A.19 and A.25), the type of the
following roles shall be FC_FeatureAttribute rather than FC_BoundFeatureAttribute:
i) FC_FeatureOperation::triggeredByValuesOf (Table B.5, line 5.3),
ii) FC_FeatureOperation::observesValuesOf (Table B.5, line 5.4),
iii) FC_FeatureOperation::affectsValuesOf (Table B.5, line 5.5);
2) If the role FC_FeatureOperation::featureType (Table B.4, line 4.4) exists more than once, the
association class FC_Binding for each shall satisfy test case A.8. This condition occurs in test
modules A.22 and A.28;
c) reference: Annex B, Tables B.4 and B.5;
d) test type: capability.
8 © ISO 2005 – All rights reserved
---------------------- Page: 16 ----------------------
SIST ISO 19110:2005
ISO 19110:2005(E)
A.8 Test case for the binding class
Information for the test case is as follows:
a) test purpose: verify that the required information is included in objects of class binding;
b) test method: test each attribute listed in Table B.6 by verifying that for each the specified description,
obligation/condition, maximum occurrence, type, and constraint are satisfied;
c) reference: Annex B, Table B.6;
d) test type: capability.
A.9 Test case for the constraint class
Information for the test case is as follows:
a) test purpose: verify that the required information is included in objects of class constraint;
b) test method: test each attribute listed in Table B.7 by verifying that for each the specified description,
obligation/condition, maximum occurrence, type, and constraint are satisfied;
c) reference: Annex B, Table B.7;
d) test type: capability.
A.10 Test case for the feature attribute class
Information for the test case is as follows:
a) test purpose:
...
NORME ISO
INTERNATIONALE 19110
Première édition
2005-02-15
Information géographique —
Méthodologie de catalogage des entités
Geographic information — Methodology for feature cataloguing
Numéro de référence
ISO 19110:2005(F)
©
ISO 2005
---------------------- Page: 1 ----------------------
ISO 19110:2005(F)
DOCUMENT PROTÉGÉ PAR COPYRIGHT
© ISO 2005
Droits de reproduction réservés. Sauf prescription différente, 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 et les microfilms, sans l'accord écrit
de l'ISO à l'adresse ci-après ou du 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 copyright@iso.org
Web www.iso.org
Version française parue en 2011
Publié en Suisse
ii © ISO 2005 – Tous droits réservés
---------------------- Page: 2 ----------------------
ISO 19110:2005(F)
Sommaire Page
Avant-propos . iv
Introduction . iv
1 Domaine d'application . 1
2 Conformité . 1
3 Références normatives . 2
4 Termes et définitions . 2
5 Abréviations . 3
6 Exigences principales . 4
6.1 Catalogue d’entités . 4
6.2 Éléments d’information . 4
Annexe A (normative) Suite d’essais abstraits. 6
Annexe B (normative) Modèle de catalogue d'entités . 17
Annexe C (informative) Exemples de catalogage des entités . 32
Annexe D (informative) Concepts de catalogage des entités . 47
Bibliographie . 56
© ISO 2005 – Tous droits réservés iii
---------------------- Page: 3 ----------------------
ISO 19110:2005(F)
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 19110 a été élaborée par le comité technique ISO/TC 211, Information géographique/Géomatique.
iv © ISO 2005 – Tous droits réservés
---------------------- Page: 4 ----------------------
ISO 19110:2005(F)
Introduction
Les entités géographiques sont des phénomènes du monde réel associés à un lieu sur la Terre, au sujet
desquels des données sont recueillies, tenues à jour et diffusées. Les catalogues d’entités qui définissent les
types d'entités, leurs opérations, leurs attributs et leurs associations représentés sous forme de données
géographiques sont indispensables pour transformer les données en informations exploitables. De tels
catalogues d’entités favorisent la diffusion, le partage et l’utilisation des données géographiques en facilitant
la compréhension du contenu et de la signification des données. À moins que les fournisseurs et les
utilisateurs de données géographiques ne partagent la même compréhension des types de phénomènes du
monde réel représentés par les données, les utilisateurs ne pourront pas juger si les données fournies
conviennent à leurs besoins.
La disponibilité de catalogues d’entités normalisés pouvant être utilisés à de multiples reprises réduira les
coûts d’acquisition des données et simplifiera le processus de spécification de produit pour les jeux de
données géographiques.
La présente Norme internationale fournit un cadre normalisé d’organisation et de présentation de la
classification des phénomènes du monde réel dans un jeu de données géographiques. Tout jeu de données
géographiques constitue une abstraction grandement simplifiée et réduite d’un monde complexe et divers. Un
catalogue de types d'entités ne peut jamais saisir la richesse de la réalité géographique. Il convient toutefois
qu’il présente l’abstraction particulière représentée dans un jeu de données d’une façon claire et précise et
sous une forme facilement compréhensible et accessible aux utilisateurs des données.
Il existe deux niveaux d’entités géographiques: les instances et les types. Au niveau de l’instance, une entité
géographique est représentée comme un phénomène discret qui est associé à des coordonnées
géographiques et temporelles et peut être caractérisé par un symbole graphique particulier. Ces instances
d’entités individuelles sont regroupées en classes ayant des caractéristiques communes: les types d'entités. Il
est reconnu que l’information géographique est perçue de manière subjective et que son contenu dépend des
besoins particuliers des applications. Les besoins particuliers des applications déterminent la manière dont les
instances d’entités sont regroupées en types d'entités à l’intérieur d’un système de classification particulier.
L’ISO 19109, Information géographique — Règles de schéma d’application, spécifie comment les données
doivent être organisées afin de refléter les besoins particuliers des applications présentant des exigences
similaires en matière de données.
NOTE La description complète du contenu et de la structure d’un jeu de données géographiques est donnée par le
schéma d’application développé conformément à l’ISO 19109. Le catalogue d’entités définit la signification des types
d'entités et des attributs, opérations et associations d’entités associés contenus dans le schéma d’application.
Les critères de collecte servant à identifier les phénomènes individuels du monde réel et à les représenter
sous forme d’instances d’entités dans un jeu de données ne sont pas spécifiés dans la présente Norme
internationale. Parce qu’ils ne sont pas inclus dans les normes, il convient d’inclure ces critères de collecte
séparément dans la spécification de produit de chaque jeu de données.
L’organisation normalisée des informations d’un catalogue d’entités n’aboutira pas automatiquement à une
harmonisation des applications ou à leur interopérabilité. Dans les situations où les classifications des entités
sont différentes, la présente Norme internationale peut au moins servir à clarifier les différences et, de cette
façon, aider à éviter les erreurs qui résulteraient de leur non-prise en compte. La norme peut également être
utilisée comme cadre standard d’harmonisation des catalogues d’entités existants dont les domaines se
chevauchent.
© ISO 2005 – Tous droits réservés v
---------------------- Page: 5 ----------------------
NORME INTERNATIONALE ISO 19110:2005(F)
Information géographique — Méthodologie de catalogage des
entités
1 Domaine d'application
La présente Norme internationale définit la méthodologie de catalogage des types d'entités. Elle spécifie
comment la classification des types d'entités est organisée dans un catalogue d’entités et présentée aux
utilisateurs d’un jeu de données géographiques. La présente Norme internationale s’applique à la création de
catalogues de types d'entités dans des domaines jusqu’ici non catalogués et à la révision des catalogues
d’entités existants pour qu'ils soient conformes aux pratiques normalisées. Elle s’applique au catalogage des
types d'entités qui sont représentés sous forme numérique. Ses principes peuvent être élargis au catalogage
d’autres formes de données géographiques.
La présente Norme internationale s’applique à la définition d’entités géographiques au niveau du type d’entité.
Elle ne s’applique pas à la représentation des instances individuelles de chaque type. Elle exclut les schémas
spatiaux, temporels et de présentation tels que spécifiés, respectivement dans l’ISO 19107, l’ISO 19108 et
l’ISO 19117. Elle exclut également les critères de collecte pour les instances d’entités.
La présente Norme internationale peut être utilisée comme base permettant de définir l’univers du discours
modélisé dans une application particulière ou pour normaliser les aspects généraux d’entités du monde réel
modélisés dans plusieurs applications.
2 Conformité
Parce que la présente Norme internationale stipule un certain nombre d’options qui ne sont pas exigées pour
tous les catalogues d’entités, cet article précise 12 classes de conformité. Ces classes se différencient sur la
base de trois critères:
a) Quels sont les éléments d’un type d’entité qui sont nécessaires à un catalogue?
1) Uniquement les attributs d'entité?
2) Les attributs d'entité et des associations d’entités?
3) Les attributs d'entité, des associations d’entités et des opérations d'entité?
b) Y a-t-il une obligation de lier les attributs, les associations et les opérations d'entités à un seul type
d'entité ou peuvent-ils être liés à de multiples types d'entités?
c) Y a-t-il une obligation d'inclure les relations d'héritage dans le catalogue d’entités?
L’Annexe A indique un module d’essai pour chacune des classes de conformité présentées dans le Tableau 1.
© ISO 2005 – Tous droits réservés 1
---------------------- Page: 6 ----------------------
ISO 19110:2005(F)
Tableau 1 — Classes de conformité
Attributs, Propriétés associées Relations
Attributs Attributs et Module
associations et à de multiples d’héritage
seulement associations d’essai
opérations entités incluses
X — — — — A.17
— X — — — A.18
— — X — — A.19
X — — X — A.20
— X — X — A.21
— — X X — A.22
X — — — X A.23
— X — — X A.24
— — X — X A.25
X — — X X A.26
— X — X X A.27
— — X X X A.28
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 sapplique (y compris les éventuels amendements).
1)
ISO/TS 19103:— , Information géographique — Langage de schéma conceptuel
1)
ISO 19109:— , Information géographique — Règles de schéma d'application
ISO 19115:2003, Information géographique — Métadonnées
4 Termes et définitions
Pour les besoins du présent document, les termes et définitions suivants s'appliquent.
4.1
entité
abstraction de phénomènes du monde réel
[ISO 19101]
EXEMPLE Le phénomène nommé «Tour Eiffel» peut être classé avec d'autres phénomènes similaires dans un type
d'entité «tour».
NOTE Une entité peut se présenter sous la forme d’un type ou d’une instance. Il convient de n’utiliser type d’entité ou
instance d’entité que lorsque l’un d’eux seulement est impliqué.
1) À publier.
2 © ISO 2005 – Tous droits réservés
---------------------- Page: 7 ----------------------
ISO 19110:2005(F)
4.2
association d’entités
relation qui relie les instances d’un type d’entité (4.1) à des instances du même type d'entité ou d'un type
d'entité différent
4.3
attribut d’entité
caractéristique d’une entité (4.1)
[ISO 19101]
EXEMPLE 1 Un attribut d’entité nommé «couleur» peut avoir une valeur d’attribut «vert» qui appartient au type de
donnée «texte».
EXEMPLE 2 Un attribut d’entité nommé «longueur» peut avoir une valeur d’attribut «82,4» qui appartient au type de
donnée «réel».
NOTE Un attribut d’entité possède un nom, un type de donnée et un domaine de valeur qui lui sont associés. Un
attribut d’entité pour une instance d’entité possède également une valeur d’attribut émanant du domaine de valeur.
4.4
catalogue d’entités
catalogue contenant des définitions et des descriptions de types d'entités (4.1), d’attributs d'entité (4.3) et
d’associations d’entités (4,2) apparaissant dans un ou plusieurs jeux de données géographiques, en même
temps que toutes les opérations d'entité (4.5) pouvant s’appliquer.
4.5
opération d’entité
fonction que chaque instance d’un type d’entité (4.1) peut accomplir
EXEMPLE Une opération d’entité sur un «barrage» est de rehausser le barrage. Les résultats de cette opération
sont d’augmenter la hauteur du «barrage» et le niveau de l’eau dans un «réservoir».
NOTE Il arrive que les opérations d'entité fournissent une base pour la définition du type d’entité.
4.6
langage fonctionnel
langage dans lequel les opérations d'entité sont formellement définies
NOTE Dans un langage fonctionnel, les types d'entités peuvent être représentés sous forme de types de données
abstraites.
5 Abréviations
DIGEST Digital Geographic Information Exchange Standard (Norme d’échange d’informations
géographiques numériques)
FACC Feature and Attribute Coding Catalogue (Catalogue de codage des entités et des attributs)
GFM General Feature Model (Modèle général des entités géographiques)
HTTP Hyper Text Transfer Protocol (Protocole de transfert hypertexte)
OHI Organisation hydrographique internationale (IHO International Hydrographic Organization)
TS Technical Specification (Spécification technique)
UML Unified Modeling Language (Langage de modélisation unifié)
© ISO 2005 – Tous droits réservés 3
---------------------- Page: 8 ----------------------
ISO 19110:2005(F)
URI Uniform Resource Identifier (Identificateur de ressource uniforme)
XML eXtensible Markup Language (Langage de balisage extensible)
6 Exigences principales
6.1 Catalogue d’entités
Un catalogue d’entités doit présenter l’abstraction d’une réalité représentée par un ou plusieurs jeux de
données géographiques sous forme d’une classification de phénomènes définie. Le niveau de base de la
classification, dans un catalogue d’entités, doit être le type d’entité. Un catalogue d’entités doit être disponible
sous format électronique pour tout jeu de données géographiques contenant des entités. Un catalogue
d’entités peut également se conformer aux spécifications de la présente Norme internationale,
indépendamment de tout jeu de données géographiques existant.
6.2 Éléments d’information
6.2.1 Introduction
Les paragraphes suivants indiquent les exigences générales et spécifiques relatives aux éléments
d'information du catalogue d'entités. L'Annexe B spécifie les exigences détaillées. L'Annexe C illustre
l'application de ces exigences. L'Annexe D traite de l'application des opérations d'entité comme base
conceptuelle de détermination des types d'entités dans un catalogue d'entités.
6.2.2 Exhaustivité
Un modèle de représentation des informations de classification d'entités figure dans l’Annexe B. Un catalogue
d'entités préparé selon ce modèle doit documenter tous les types d'entités se trouvant dans un ensemble
déterminé de données géographiques. Le catalogue d'entités doit comporter les informations d'identification
comme indiqué à l'Annexe B. Le catalogue d’entités doit comporter la définition et la description de tous les
types d'entités figurant dans les données, y compris tous attributs d'entité et toutes associations d’entités
figurant dans les données associées à chaque type d’entité, y compris également, mais de manière facultative,
les opérations d'entité supportées par les données. Pour assurer la prédictibilité et la comparabilité du
contenu du catalogue d'entités dans différentes applications, il est recommandé que le catalogue d'entités ne
comporte que les éléments indiqués dans l'Annexe B. Pour optimiser au maximum l'utilité d'un catalogue
d'entités dans différentes applications, il est recommandé d'utiliser un langage de schéma conceptuel pour
modéliser les informations du catalogue d'entités.
NOTE Les définitions de langage naturel, les alias de type d'entité, les critères de cycle de vie des instances d'entités
et les autres éléments sémantiques du catalogue d'entités peuvent être inclus dans un schéma conceptuel sous forme de
commentaires structurés ou d'attributs.
6.2.3 Exigences générales
6.2.3.1 Formes des noms
Tous les types, attributs, associations d’entités, rôles d’association et opérations d'entité compris dans un
catalogue d’entités doivent être identifiés par un nom qui leur est propre au sein même de ce catalogue
d’entités. Si le nom d’un type d’entité, d’un attribut, d’une association, d'un rôle d'association ou d'une
opération d'entité apparaît plus d'une fois dans le catalogue d'entités, la définition doit être la même pour
toutes les occurrences.
4 © ISO 2005 – Tous droits réservés
---------------------- Page: 9 ----------------------
ISO 19110:2005(F)
6.2.3.2 Forme des définitions
Les définitions des types d'entités, des attributs, des valeurs listées des attributs, des associations, des rôles
d’association et des opérations d'entité doivent être données dans un langage naturel. Ces définitions doivent
figurer au catalogue, à moins que le catalogue ne renvoie à une source de définition séparée. Si le même
terme apparaît à la fois dans la source de définition et dans le catalogue d'entités, c'est la définition du
catalogue d'entités qui doit s'appliquer.
6.2.4 Exigences relatives aux types d'entités
Chaque type d'entité doit être identifié par un nom et défini dans un langage naturel. Chaque type d'entité
peut être aussi identifié par un code alphanumérique qui lui est propre au sein même du catalogue et peut
posséder un ensemble d'alias. Le catalogue d’entités doit comporter également, pour chaque type d’entité,
ses opérations et les attributs associés, les associations et les rôles d'association le cas échéant. Il est
recommandé d'utiliser les spécifications d’un langage fonctionnel pour faciliter la définition des types d'entités.
6.2.5 Exigences relatives aux opérations d’entité
Le cas échéant, les opérations d'entité doivent être identifiées et définies pour chaque type d'entité. Les
attributs d'entité impliqués dans chaque opération d'entité doivent être indiqués, ainsi que les types d'entités
concernés par l’opération. La définition doit comporter une définition en langage naturel et peut être spécifiée,
de façon formelle, dans un langage fonctionnel.
6.2.6 Exigences relatives aux attributs d’entité
Le cas échéant, les attributs d'entité doivent être identifiés et définis pour chaque type d'entité. La définition
doit comporter une définition en langage naturel et un type de données spécifié pour les valeurs de l’attribut.
Chaque type d’attribut peut être également identifié par un code alphanumérique qui lui est propre au sein du
catalogue.
6.2.7 Exigences relatives aux valeurs listées des attributs d'entité
Le cas échéant, les valeurs listées des attributs d’entité doivent être libellées pour chaque attribut d’entité. Le
libellé doit être unique au sein même de l'attribut d'entité dont elle est une valeur listée. Chaque valeur listée
peut être également identifiée par un code alphanumérique qui lui est propre au sein de l’attribut d’entité dont
elle est une valeur listée.
6.2.8 Exigences relatives aux associations d’entités
Le cas échéant, les associations d’entités doivent être nommées et définies. Chaque association d’entités
peut être également identifiée par un code alphanumérique qui lui est propre au sein du catalogue. Les noms
et les rôles des types d'entités qui participent à l'association doivent être spécifiés.
6.2.9 Exigences relatives aux rôles d'association
Le cas échéant, les rôles d'association doivent être nommés et définis. Le nom du type d'entité qui détient le
rôle et l'association à laquelle il participe doivent être spécifiés.
© ISO 2005 – Tous droits réservés 5
---------------------- Page: 10 ----------------------
ISO 19110:2005(F)
Annexe A
(normative)
Suite d’essais abstraits
A.1 Introduction
La présente annexe normative expose la suite d’essais abstraits destinée à évaluer la conformité à la
présente Norme internationale. Cette suite d’essais abstraits comporte quinze cas d’essai et douze modules
d’essai: un cas d’essai pour l'existence et la forme des informations du catalogue d'entités (A.2); un cas
d’essai pour les exigences générales du catalogue d'entités (A.3); des cas d’essai pour chaque classe
d'information principale du catalogue d'entités (de A.4 à A.16) et des modules d’essai pour des sous-
ensembles particuliers de fonctionnalité d'un catalogue d’entités (de A.17 à A.28).
Ces cas d’essais se fondent sur chacune des classes d’information principales du catalogue d'entités
spécifiées dans les Tableaux B.1 à B.15. Chaque cas d’essai fondé sur une classe implique l’examen de
chaque élément de la classe (attribut ou rôle) et la vérification des points suivants:
les spécifications d'obligation/condition de la présence de l'élément sont respectées;
le nombre maximal d'occurrences de l'élément n'est pas dépassé;
le type de la valeur de l'élément est correct;
NOTE Sauf indication contraire, donnée par exemple en précisant un type d'un paquetage bien connu ou d'une
norme ISO, il est possible d'appliquer les spécifications de type telles qu'elles seront données dans l'ISO/TS 19103.
la valeur de l’élément est conforme à la description de l'élément;
il est répondu à toute contrainte énoncée sur l'élément.
Les essais portant sur la classe dans sa globalité sont définis comme des contraintes de classe, tel qu'indiqué
dans les Tableaux B.1 à B.15, et/ou dans les modules d’essais.
Les modules d’essai s'appuient sur des sous-ensembles utiles de la fonctionnalité du modèle de catalogue
d'entités spécifié dans l'Annexe B. Les sous-ensembles sont organisés en commençant par une fonctionnalité
de base capable de représenter les types d'entités et les attributs d'entité qui appartiennent en propre à un
type d'entité (voir A.17). La fonctionnalité de représentation de base s'élargit en supportant au moins un des
éléments suivants:
des types de propriétés d’entité supplémentaires (pour les rôles d’association, voir A.18; pour les rôles
d’association et les opérations d’entité, voir A.19);
des relations supplémentaires entre les éléments d'information du catalogue d'entités (pour les attributs
d'entité à utilisation multiple, voir A.20; pour les héritages, voir A.23; pour les attributs d'entité à utilisation
multiple et les héritages, voir A.26);
des types de propriétés d’entité supplémentaires et des relations supplémentaires entre les éléments
d’information du catalogue d’entités (voir A.21, A.22, A.24, A.25, A.27 et A.28).
6 © ISO 2005 – Tous droits réservés
---------------------- Page: 11 ----------------------
ISO 19110:2005(F)
Les modules d’essais sont spécifiés par les cas d’essai qui s’appliquent. Les modules d’essais de A.18 à A.28
étendent la fonctionnalité de représentation de base spécifiée par le module d’essai A.17. Ces extensions
sont résumées dans le Tableau 1.
Pour établir la conformité d'un catalogue d'entités à la présente Norme internationale, vérifier que toutes les
exigences d’au moins un module d’essai sont satisfaites.
A.2 Cas d’essai pour l'existence et la forme de l'information du catalogue d'entités
Les informations concernant le cas d’essai sont les suivantes:
a) finalité de l’essai: vérifier l’existence et la forme d’un catalogue d’entités;
b) méthode d’essai: contrôler si le catalogue d'entités existe et peut être obtenu au format électronique, en
obtenant une copie du catalogue d'entités, par exemple sur un disque informatique ou
par transfert de fichier;
c) référence: 6.1;
d) type d’essai: essai de base.
A.3 Cas d’essai pour les exigences générales du catalogue d'entités
Les informations concernant le cas d’essai sont les suivantes:
a) finalité de l’essai: vérifier que les exigences générales du catalogue d’entités sont respectées;
b) méthode d’essai: contrôler
1) que, s’il est spécifié que le catalogue d’entités s’applique à un jeu déterminé de données
géographiques, le catalogue d'entités documente alors tous les types d'entités figurant dans ce jeu
de données géographiques,
2) que tous les types, les attributs, les associations d’entités, les rôles d’association et les opérations
d'entité sont identifiés par un nom qui leur est propre au sein de ce catalogue d’entités,
3) que chacune des valeurs listées d’attribut d’entité est identifiée par un libellé qui lui est propre au
sein de l’attribut d’entité dont elle est une valeur listée,
4) que tous les types, les attributs, les associations d’entités, les rôles d’association et les opérations
d'entité sont définis, ou alors qu'ils font référence à une définition provenant d'une autre source,
5) que, si un type, un attribut ou une association quelconque d’entité est identifié par un code
alphanumérique, ce code alphanumérique lui est propre au sein du catalogue d’entités,
6) que, si une quelconque valeur listée d’attribut d’entité est identifiée par un code alphanumérique, ce
code alphanumérique lui est propre au sein de l’attribut d’entité dont elle est une valeur listée;
c) référence: 6.2;
d) type d’essai: capacité.
© ISO 2005 – Tous droits réservés 7
---------------------- Page: 12 ----------------------
ISO 19110:2005(F)
A.4 Cas d’essai pour la classe Feature Catalogue (Catalogue d'entités)
Les informations concernant le cas d’essai sont les suivantes:
a) finalité de l’essai: vérifier que l'information requise est incluse dans les objets de la classe Feature
Catalogue (Catalogue d'entités);
b) méthode d’essai: soumettre à essai chaque attribut et rôle listés dans le Tableau B.1 en vérifiant que
chacun répond aux spécifications de description, d'obligation/condition, d'occurrence
maximale, de type et de contrainte;
c) référence: Tableau B.1;
d) type d’essai: capacité.
A.5 Cas d’essai pour la classe Feature Type (Type d'entité)
Les informations concernant le cas d’essai sont les suivantes:
a) finalité de l’essai: vérifier que l'information requise est incluse dans les objets de la classe FeatureType
(Type d'entité);
b) méthode d’essai: soumettre à essai chaque attribut et rôle listés dans le Tableau B.2 en vérifiant que
chacun répond aux spécifications de description, d'obligation/condition, d'occurrence
maximale, de type et de contrainte;
c) référence: Tableau B.2;
d) type d’essai: capacité.
A.6 Cas d’essai pour la classe Inheritance Relation (Relation d'héritage)
Les informations concernant le cas d’essai sont les suivantes:
a) finalité de l’essai: vérifier que l'information requise est incluse dans les objets de la classe Inheritance
Relation (Relation d'héritage);
b) méthode d’essai: soumettre à essai chaque attribut et rôle listés dans le Tableau B.3 en vérifiant que
chacun répond aux spécifications de description, d'obligation/condition, d'occurrence
maximale, de type et de contrainte;
c) référence: Tableau B.3;
d) type d’essai: capacité.
8 © ISO 2005 – Tous droits réservés
---------------------- Page: 13 ----------------------
ISO 19110:2005(F)
A.7 Cas d’essai pour la classe Feature Operation (Opération d'entité)
Les informations concernant le cas d’essai sont les suivantes:
a) finalité de l’essai: vérifier que l'information requise est incluse dans les objets de la classe Feature
Operation (Opération d’entité);
b) méthode d’essai: soumettre à essai chaque attribut et rôle listés dans le Tableau B.5 (et le Tableau B.4)
en vérifiant que chacun répond aux spécifications de description, d'obligation/condition,
d'occurrence maximale, de type et de contrainte. En outre:
1) Si les attributs d'entité sont propres à un type d'entité (modules d’essai A.19 et A.25), le type d
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.