EN ISO 19110:2006/A1:2011

SLOVENSKI STANDARD
01-september-2011
Geografske informacije - Metodologija za objektne kataloge - Dopolnilo 1 (ISO
19110:2005/AMD 1:2011)
Geographic information - Methodology for feature cataloguing - Amendment 1 (ISO
19110:2005/AMD 1:2011)
Geoinformation - Objektartenkataloge - Änderung 1 (ISO 19110:2005/AMD 1:2011)
Information géographique - Méthodologie de catalogage des entités - Amendement 1
(ISO 19110:2005/AMD 1:2011)
Ta slovenski standard je istoveten z: EN ISO 19110:2006/A1:2011
ICS:
07.040 Astronomija. Geodezija. Astronomy. Geodesy.
Geografija Geography
35.240.70 Uporabniške rešitve IT v IT applications in science
znanosti
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN STANDARD
EN ISO 19110:2006/A1
NORME EUROPÉENNE
EUROPÄISCHE NORM
June 2011
ICS 35.240.70
English Version
Geographic information - Methodology for feature cataloguing -
Amendment 1 (ISO 19110:2005/AMD 1:2011)
Information géographique - Méthodologie de catalogage Geoinformation - Objektartenkataloge - Änderung 1 (ISO
des entités - Amendement 1 (ISO 19110:2005/AMD 19110:2005/AMD 1:2011)
1:2011)
This amendment A1 modifies the European Standard EN ISO 19110:2006; it was approved by CEN on 14 June 2011.

CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for inclusion of this
amendment into the relevant national standard without any alteration. Up-to-date lists and bibliographical references concerning such
national standards may be obtained on application to the CEN-CENELEC Management Centre or to any CEN member.

This amendment exists in three official versions (English, French, German). A version in any other language made by translation under the
responsibility of a CEN member into its own language and notified to the CEN-CENELEC Management Centre has the same status as the
official versions.
CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland,
Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and United Kingdom.

EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION

EUROPÄISCHES KOMITEE FÜR NORMUNG

Management Centre: Avenue Marnix 17, B-1000 Brussels
© 2011 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN ISO 19110:2006/A1:2011: E
worldwide for CEN national Members.

Contents Page
Foreword .3

Foreword
This document (EN ISO 19110:2006/A1:2011) has been prepared by Technical Committee ISO/TC 211
"Geographic information/Geomatics" in collaboration with Technical Committee CEN/TC 287 “Geographic
Information” the secretariat of which is held by BSI.
This Amendment to the European Standard EN ISO 19110:2006 shall be given the status of a national
standard, either by publication of an identical text or by endorsement, at the latest by December 2011, and
conflicting national standards shall be withdrawn at the latest by December 2011.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. CEN [and/or CENELEC] shall not be held responsible for identifying any or all such patent rights.
According to the CEN/CENELEC Internal Regulations, the national standards organizations of the following
countries are bound to implement this European Standard: Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech
Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia,
Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain,
Sweden, Switzerland and the United Kingdom.
Endorsement notice
The text of ISO 19110:2005/A1:2011 has been approved by CEN as a EN ISO 19110:2006/A1:2011 without
any modification.
INTERNATIONAL ISO
STANDARD 19110
First edition
2005-02-15
AMENDMENT 1
2011-06-15
Geographic information — Methodology
for feature cataloguing
AMENDMENT 1
Information géographique — Méthodologie de catalogage des entités
AMENDEMENT 1
Reference number
ISO 19110:2005/Amd.1:2011(E)
©
ISO 2011
ISO 19110:2005/Amd.1:2011(E)
©  ISO 2011
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 2011 – All rights reserved

ISO 19110:2005/Amd.1:2011(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.
Amendment 1 to ISO 19110:2005 was prepared by Technical Committee ISO/TC 211, Geographic
information/Geomatics.
ISO 19110:2005/Amd.1:2011(E)
Introduction
This amendment is based on experience in implementing ISO 19110:2005, experience and lessons learned
by the ISO 19126 project team, harmonization with other ISO/TC 211 standards, and in particular
establishment of an eXtensible Mark-up Language (XML) schema encoding for feature catalogues. This
amendment provides XML schemas that are meant to enhance interoperability by providing a common
specification for describing, validating, and exchanging feature catalogue information.
The changes in this amendment aim to:
 facilitate the use of ISO 19110:2005 to create geographic feature catalogues;
 ensure a consistent description of the feature types of an application schema;
 enhance the compliance of ISO 19110:2005 with ISO 19109;
 enable an XML schema implementation, based on ISO/TS 19139 encoding rules, of ISO 19110:2005-
compliant feature catalogues;
 enable the registration of feature catalogues and their feature types.

iv © ISO 2011 – All rights reserved

ISO 19110:2005/Amd.1:2011(E)
Geographic information — Methodology for feature cataloguing
AMENDMENT 1
Page 1, Scope
Replace the entire clause with the following:
This International Standard defines the methodology for cataloguing feature types. This International
Standard specifies how feature types can be 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. Feature catalogues are independent of feature concept dictionaries defined in ISO 19126 and can
be specified without having to use or create a feature concept dictionary.
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 portrayal schemas as specified in ISO 19117.
This International Standard can 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.
Page 1, Conformance
Replace the entire clause with the following:
Because this International Standard specifies a number of options that are not required for all feature
catalogues, this clause specifies five conformance classes. These classes are differentiated on the basis
of the following criteria.
a) Which 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 for defining global feature attributes, feature associations, and feature
operations which may be bound 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 19110:2005/Amd.1:2011(E)
Table 1 — Conformance classes
Attributes, Inheritance
Attributes Attributes and
associations and Global properties relationships Test module
only associations
operations included
 — — — — A.17
—  — — — A.18
— —  — — A.19
— — —  — A.22
 — — —  A.23
—  — —  A.24
— —  —  A.25
NOTE The initial test module numbers are kept, even if some of the test modules are removed. The numbering can
be subject to change on publication of any new edition of this International Standard.
Page 2, Normative references
Update the entries for ISO/TS 19103:— and ISO 19109:—, delete footnote 1), and add ISO 19135:2005 and
ISO/TS 19139:2007:
ISO/TS 19103, Geographic information — Conceptual schema language
ISO 19109:2005, Geographic information — Rules for application schema
ISO 19135:2005, Geographic information — Procedures for item registration
ISO/TS 19139:2007, Geographic information — Metadata — XML schema implementation
Page 3, Terms and definitions
Replace entry 4.4 with the following:
feature catalogue
catalogue containing definitions and descriptions of the feature (4.1) types, feature attributes (4.3), and
feature relationships (4.8) occurring in one or more sets of geographic data, together with any feature
operations (4.5) that may be applied
[ISO 19101:2002, definition 4.13]
Add the following terms and definitions:
4.7
feature inheritance
mechanism by which more specific features (4.1) incorporate structure and behaviour of more general
features related by behaviour
4.8
feature relationship
feature association (4.2) or feature inheritance (4.7)
2 © ISO 2011 – All rights reserved

ISO 19110:2005/Amd.1:2011(E)
Page 3, Abbreviations
Add the following heading under "5 Abbreviations"
5.1 Acronyms
Add the following after the new 5.1:
5.2 Namespace abbreviations
In the list below, the item on the left describes the common namespace prefix used to describe the
elements in the namespace. The second item is an English description of the namespace prefix, and the
item in parenthesis is the URI of the actual namespace. These URIs do not correspond necessarily to an
effective location of the schemas.
This list corresponds to the namespaces used by this International Standard.
gco Geographic Common extensible markup language (http://www.isotc211.org/2005/gco)
gfc Geographic Feature Cataloguing   (http://www.isotc211.org/2005/gfc.)
gmd Geographic MetaData extensible markup language (http://www.isotc211.org/2005/gmd)
gmx Geographic Metadata XML Schema   (http://www.isotc211.org/2005/gmx)
Page 4, 6.1
Replace the text in 6.1 with the following:
A feature catalogue shall present the abstraction of reality represented in one or more sets of geographic
data. The basic level of abstraction 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.
Page 4, 6.2.1
Add the following text at the end of 6.2.1:
Annex E specifies XML encoding for feature catalogue, Annex F specifies concepts that permit the
management of feature catalogue either in a multi-part register or in a hierarchical register containing
multi-part subregisters, in accordance with ISO 19135. Annex G provides an example of XML
implementation of this International Standard.
Page 4, 6.2.2
Replace the first sentence of 6.2.2 with the following:
A template for the representation of feature catalogues is specified in Annex B.
ISO 19110:2005/Amd.1:2011(E)
Page 4, 6.2.3.1
Replace the text in 6.2.3.1 with the following:
All feature types and feature properties (i.e. feature attributes, feature associations, association roles, and
feature operations) included in a feature catalogue shall be identified by a name. The name of a feature
type is unique within that feature catalogue. The name of a feature property (whether the feature property
is a global property bound to the feature type or is local to the feature type) is unique within its feature
type. The name of a global feature property is unique within that feature catalogue.
Page 6, A.1
In the 2nd and 3rd paragraph, replace “Tables B.1 through B.15” with “Tables B.1 through B.16”.
Page 7, A.3
Replace bullet 2) with the following:
2) that all feature types, all feature association and all global feature properties (feature role, feature
attribute or feature operation not directly owned by a feature type) are identified by a name that is
unique within the feature catalogue,
Add the following bullet point after 6):
7) that all carriers of characteristics of a feature type are identified by a name that is unique in the
context of that feature type.
Page 8, A.7
Replace bullet b), with the following [deleting 1) and 2)]:
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;
Page 9, A.10
Replace bullet b) with the following:
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;
Page 10, A.11
Delete bullet 2).
Page 12, A.19
Replace bullet b) with the following [deleting 1), 2) and 3)]:
b) test method: perform test module A.18 and test case A.7 (feature operation);
4 © ISO 2011 – All rights reserved

ISO 19110:2005/Amd.1:2011(E)
Page 13, A.22
Replace the text in A.22 with the following:
Information for the test module is as follows:
a) test purpose: verify that feature catalogue supports core representation functionality, comprised
of feature types, and feature properties (i.e. feature attributes, association roles,
and feature operations) either directly owned by a single feature type or globally
defined in the feature catalogue;
b) test method: perform test module A.8, A.16 and A.18;
c) reference: A.8, A.16 and A.18;
d) test type: capability.
Page 16, Annex B
In the first paragraph, replace “Tables B.1 through B.15” with “Tables B.1 through B.16”.
In the second paragraph, replace “Figure B.1” with “Figure B.1 a), b), and c)”.
1)
In the last line, delete “ISO 19109:— ” and insert “ISO 19109:2005”.
Page 17, Annex B
ISO 19110:2005/Amd.1:2011(E)
Replace Table B.1 with the following:
Table B.1 — Feature catalogue
Obligation/ Maximum
No. Name/Role Name Description Type Constraint
a b
Condition Occurrence
1 Class a feature catalogue contains — — — —
FC_FeatureCatalogue the definition of some number
of feature types with other
information necessary for
those definitions
Subtype of see ISO/TS 19139 — — — —
CT_Catalogue
1.1 Attribute name, address, country, and M 1 ISO 19115 Metadata:: —
producer telecommunications address CI_ResponsibleParty
of person or organization
having primary responsibility
for the intellectual content of
this feature catalogue
1.2 Attribute formal functional language in C/Mandatory if 1 CharacterString —
functionalLanguage which the feature operation feature
formal definition occurs in this operation
feature catalogue formal definition
occurs in
feature
catalogue
1.3 Role role that links this feature M N FC_FeatureType Aggregation
featureType catalogue to the feature types
that it contains
1.4 Role role that links this feature O N FC_DefinitionSource Aggregation
definitionSource catalogue to the sources of
definitions of feature types,
property types, and listed
values that it contains
1.5 Role role that links this feature O N FC_InheritanceRelation Aggregation
inheritanceRelation catalogue to the inheritance
relationships that it contains
1.6 Role role that links this feature O N FC_PropertyType Composition
globalProperty catalogue to the global feature
properties, i.e. the feature
properties which may be
bound to many feature types
a
M = mandatory; O = optional; C = conditional.
b
N = repeating occurrences.
6 © ISO 2011 – All rights reserved

ISO 19110:2005/Amd.1:2011(E)
Pages 18 and 19, Annex B
In Table B.2, replace rows 2, 2.9 and 2.11 with the following:
Obligation/ Maximum
No. Name/Role Name Description Type Constraint
a b
Condition Occurrence
2 Class class of real world — — — typeName
FC_FeatureType phenomena with common realizes
properties GF_FeatureType
::typeName;
isAbstract
realizes
GF_FeatureType
::isAbstract;
constrainedBy
realizes
GF_FeatureType
::constrainedBy
2.9 Role role that links this feature type O N FC_CarrierOfChara Composition
carrierOfCharacteristics to the property types that it cteristics
contains
2.11 Role role that links this feature type O 1 FC_DefinitionRefer Aggregation
definitionReference to the source of its definition ence

Page 19, Annex B
In Table B.3, replace row 3.1 with the following:
Obligation/ Maximum
No. Name/Role Name Description Type Constraint
Condition Occurrence
3.1 Attribute text string that uniquely O 1 CharacterString —
name identifies this inheritance
relation within the feature
catalogue that contains this
inheritance relation
Page 20, Annex B
Add the following Table B.4a before Table B.4.
Table B.4a — Carrier of characteristics
Obligation/ Maximum
No. Name/Role Name Description Type Constraint
a b
Condition Occurrence
4bis Class abstract class for local feature — — — —
FC_CarrierOfCharact properties and bound global
eristics properties of a feature type
4bis. Role role that links the local and C/Mandatory 1 FC_FeatureType —
1 featureType bound properties with the for local
feature type that contains properties
them
4bis. Role role that links a carrier of O N FC_Constraint Aggregation
2 constrainedBy characteristics to the
constraints placed upon it
a
O = optional; C = conditional.
b
N = repeating occurrences.
ISO 19110:2005/Amd.1:2011(E)
Page 20, Annex B
Update and extend Table B.4 with the following:
Table B.4 — Property type
Obligation/ Maximum
No. Name/Role Name Description Type Constraint
a
Condition Occurrence
4 Class abstract class for local and — — — —
FC_PropertyType global feature properties
Subtype of Table B.4a — — — —
FC_CarrierOfCharact
eristics
4.1 Attribute member name that locates M 1 LocalName —
memberName this member within a feature
type for a local property or
within the feature catalogue
for a global property
4.2 Attribute definition of the member in a C/Mandatory if 1 CharacterString —
definition natural language: This attribute not provided by
is required if the definition is definition source
not provided by
FC_FeatureCatalogue::definiti
onSource. If not provided, the
definitionReference should
specify a citation where the
definition may be found, and
any additional information as to
which definition is to be used
4.3 Attribute cardinality of the member in M 1 Multiplicity Initial value 1
cardinality the feature class. If this is an
attribute or operation, the
default cardinality is 1. If this
is an association role, then
the default cardinality is 0.*.
For operations, this is the
number of return values
possible.
This is an elaboration of the
GFM to allow for complete
specifications for various
programming and data
definition languages
4.6 Role role that links this instance to O 1 FC_DefinitionReferen Aggregation
definitionReference the source of its definition ce
4.7 Role feature catalogue to which a C/Mandatory 1 FC_FeatureCatalogue —
featureCatalogue global property pertains for a global
property
a
M = mandatory; O = optional; C = conditional.

8 © ISO 2011 – All rights reserved

ISO 19110:2005/Amd.1:2011(E)
Page 21, Annex B
In Table B.5, replace rows 5.3, 5.4 and 5.5 with the following:
Obligation/ Maximum
No. Name/Role Name Description Type Constraint
a b
Condition Occurrence
5.3 Role specifies attribute which may O N FC_Carrier Shall be instantiated as
triggeredByValues trigger an operation OfCharact FC_FeatureAttribute,
Of eristics FC_BoundFeatureAttribute or one
of their derived classes.
5.4 Role specifies attribute that may be O N FC_Carrier Shall be instantiated as
observesValuesOf used as input to perform an OfCharact FC_FeatureAttribute,
operation eristics FC_BoundFeatureAttribute or one
of their derived classes.
5.5 Role specifies attribute that will be O N FC_Carrier Shall be instantiated as
affectsValuesOf affected by an operation OfCharact FC_FeatureAttribute,
eristics FC_BoundFeatureAttribute or one
of their derived classes.
Page 21, Annex B
Replace Table B.6 with the following:
Name/Role Obligation/ Maximum
No. Description Type Constraint
a
Name Condition Occurrence
6 Class class that is used to describe the specifics of — — — —
FC_Binding how a property type is bound to a particular
feature type
Subtype of Table B.4a — — — —
FC_CarrierOfCh
aracteristics
6.1 Attribute description of how a property type is bound to O 1 CharacterString —
description a particular feature type
6.2 Role role that links to the bound global property M 1 FC_PropertyType —
globalProperty
a
M = mandatory; O = optional.
Page 22, Annex B
In Table B.8, replace rows 8.3 and 8.4 with the following:
Obligation/ Maximum
No. Name/Role Name Description Type Constraint
a b
Condition Occurrence
8.3 Attribute if present, it defines the permissible O 1 FC_ListedValue —
listedValue values of this feature attribute as a
restriction of the attribute valueType. If
not present, there is no restriction on
the valueType.
8.4 Attribute type of the value of this feature C/Mandatory 1 TypeName —
valueType attribute; a name from some for local feature
namespace attribute
ISO 19110:2005/Amd.1:2011(E)
Page 23, Annex B
In Table B.9, replace row 9.6 with the following:
Obligation/
Maximum
No. Name/Role Name Description Type Constraint
a
Occurrence
Condition
9.6 Role type of the target value of this C/Mandator 1 FC_Feature —
rolePlayer association role y for a local Type
association
role
Page 24, Annex B
In Table B.11, replace row 11.4 with the following:
Obligation/ Maximum
No. Name/Role Name Description Type Constraint
a
Condition Occurrence
11.4 Role role that links this instance to the O 1 FC_DefinitionReference Aggregation
definitionReference source of its definition

Page 24, Annex B
In Table B.12, replace row 12.1 with the following:
Obligation/ Maximum
Name/Role Name Description Type Constraint
a b
Condition Occurrence
12.1 Role roles that are a part of this M N FC_AssociationRole Composition
roleName association (minimum
occurrence:
2)
10 © ISO 2011 – All rights reserved

ISO 19110:2005/Amd.1:2011(E)
Page 25, Annex B
Replace Table B.15 with the following:
Table B.15 — Bound feature attribute
Obligation/ Maximum
No. Name/Role Name Description Type Constraint
a
Condition Occurrence
15 Class class that is used to describe — — — —
FC_BoundFeatureAttribute the specifics of how a global
feature attribute is bound to a
particular feature type
Subtype of FC_Binding Table B.6 — — — —
15.1 Attribute type of the value of this C/Mandatory 1 TypeName —
valueType feature attribute; a name from if the value
some namespace type of the
feature
attribute is not
defined
globally
a
C = conditional.
Page 25, Annex B
Insert Table B.16 after Table B.15:
Table B.16 — Bound association role
Obligation/ Maximum
No. Name/Role Name Description Type Constraint
a
Condition Occurrence
16 Class class that is used to describe — — — —
FC_BoundAssociationRole the specifics of how a global
association role is bound to a
particular feature type
Subtype of FC_Binding Table B.6 — — — —
16.1 Role target feature type of this C/Mandatory if 1 FC_FeatureType —
rolePlayer association role the target
feature type
of this
association
role is not
defined
globally
a
C = conditional.
ISO 19110:2005/Amd.1:2011(E)
Pages 26 to 30, Annex B
Replace Figures B.1 to B.5 with the following.
<>
CT_Catalogue
(from Catalogues)
+ name : CharacterString
+ scope[1.*] : CharacterString
+ fieldOfApplication[0.*] : CharacterString
+inheritanceRelation
<>
+ versionNumber : CharacterString
FC_InheritanceRelation
+ versionDate : Date 0.*
+ language[0.1] : CharacterString
+ name[0.1] : CharacterString
+inheritsFrom
+ characterSet[0.1] : MD_CharacterSetCode = “utf8”
+ description : CharacterString
+ locale[0.*] : PT_Locale 0.*
+ uniqueInstance : Boolean
+inheritsTo 0.*
Specialization
<>
FC_FeatureCatalogue
+ producer : CI_ResponsibleParty Generalization
1 +subtype
+ functionalLanguage[0.1] : CharacterString
<>
+featureCatalogue 1 +featureType
FC_FeatureType
+supertype
1.*
ConsistsOf
+ typeName : LocalName
<>
+ definition[0.1] : CharacterString
FC_CarrierOfCharacteristics
+rolePlayer
+carrierOfCharacteristics 0.1
+ code[0.1] : CharacterString
0.* +featureType + isAbstract : Boolean = FALSE
0.1
Member Of
+ aliases[0.*] : LocalName
<>
FC_PropertyType
<>
FC_FeatureAssociation
+ memberName : LocalName
+ definition[0.1] : CharacterString
+ cardinality : Multiplicity = 1
+relation
Role
<>
2.*
FC_AssociationRole
+roleName
+ isOrdered : Boolean = FALSE
+ isNavigable : Boolean = TRUE
<>
<>
FC_FeatureAttribute
FC_RoleType
if count(featureType)=1 then
+ code[0.1] : CharacterString
+ ordinary
rolePlayer is mandatory
+ valueMeasurementUnit[0.1] : UnitOfMeasure
+ aggregation
+ valueType[0.1] : TypeName
+ composition
0.* <>
FC_ListedValue
<>
+listedValue
FC_FeatureOperation
+ label : CharacterString
+ code[0.1] : CharacterString
+ signature : CharacterString if count(featureType)=1 then
+ definition[0.1] : CharacterString
+ formalDefinition[0.1] : CharacterString valueType is mandatory

a)  Conceptual model
Figure B.1 (continued)
12 © ISO 2011 – All rights reserved

ISO 19110:2005/Amd.1:2011(E)
<>
<>
FC_DefinitionSource
+definitionSource
FC_FeatureCatalogue
+ source : CI_Citation
0.*
+ featureCatalogue
1 +definitionSource
ConsistsOf
1.* +featureType
<>
<>
0.1
FC_DefinitionReference
FC_FeatureType
+definitionReference
+ sourceIdentifier[0.1] : CharacterString
0.1 +featureType
+definitionReference 0.1 0.1 +definitionReference
Member Of
+carrierOfCharacteristics
0.* <>
FC_CarrierOfCharacteristics
<>
<>
FC_ListedValue
FC_PropertyType
0.*
b)  Definition source and reference
<>
<>
FC_FeatureCatalogue
FC_FeatureType
+featureType ConsistsOf 1
+ producer : CI_ResponsibleParty
+ typeName : LocalName
1.* +featureCatalogue
+rolePlayer
+ functionalLanguage[0.1] : CharacterString
+ definition[0.1] : CharacterString
+featureType Member Of
+ code[0.1] : CharacterString
0.1
+featureCatalogue 0.1
+ isAbstract : Boolean = FALSE
0.1
+ aliases[0.*] : LocalName
0.* +carrierOfCharacteristics
<>
count(globalProperty.FC_PropertyType).
FC_CarrierOfCharacteristics
featureType)=0 and count(featureType)=1
0.*
<> <>
0.* +globalProperty
FC_Binding FC_PropertyType
+globalProperty
+ description[0.1] : CharacterString
count(featureCatalogue) +
count(featureType) = 1
<> <>
FC_BoundAssociationRole FC_BoundFeatureAttribute
+ valueType [0.1] : TypeName
type(globalProperty)=FC_AssociationRole and
count(rolePlayer)+count(globalProperty.FC_AssociationRole.rolePlayer) = 1
type(globalProperty)=FC_FeatureAttribute and
count(valueType)+count(globalProperty.FC_FeatureAttribute.valueType)= 1

c)  Global properties
Figure B.1 — Feature catalogue
ISO 19110:2005/Amd.1:2011(E)
Generalization 0.*
<>
GF_InheritanceRelation
FC_InheritanceRelation
(from General Feature Model)
0.*
Specialization
<>
+supertype 1 1 +subtype
GF_AssociationType
(from General Feature Model)
<>
GF_FeatureType
(from General Feature Model)
<>
FC_FeatureAssociation
<>
FC_FeatureType
<>
0.1 +featureType Member Of 0.*
FC_CarrierOfCharacteristics
+carrierOfCharacteristics
0.* +carrierOfCharacteristics
<>
<>
GF_PropertyType
(from General Feature Model) FC_PropertyType
<>
<>
GF_AssociationRole
FC_AssociationRole
(from General Feature Model)
<>
<>
GF_AttributeType
FC_FeatureAttribute
(from General Feature Model)
<>
<>
GF_Operation
FC_FeatureOperation
(from General Feature Model)
Figure B.2 — Feature cataloguing classes as realizations of general feature model metaclasses
14 © ISO 2011 – All rights reserved

ISO 19110:2005/Amd.1:2011(E)
<>
+featureCatalogue ConsistsOf
FC_FeatureCatalogue
+featureType
1.*
<>
+includes
<>
GF_FeatureType
FC_FeatureType
1.*
(from General Feature Model)
+featureType 0.1
Member Of
<> <>
0.*
FC_FeatureAssociation GF_AssociationType
(from General Feature Model)
+linkBetween
0.* +carrierOfCharacteristics
<>
+relation
FC_CarrierOfCharacteristics
+carrierOfCharacteristics 0.*
<>
<>
GF_ProperyType
FC_PropertyType
(from General Feature Model)
Role
Role
<>
<>
GF_Operation
FC_FeatureOperation
(from General Feature Model)
<>
<>
GF_AttributeType
FC_FeatureAttribute
(from General Feature Model)
1.* +roleName
+roleName 2.*
<>
<>
GF_AssociationRole
FC_AssociationRole
(from General Feature Model)
Figure B.3 — Derivation FC_FeatureType, FC_FeatureAttribute, FC_FeatureAssociation, and
FC_AssociationRole from general feature model metaclasses
ISO 19110:2005/Amd.1:2011(E)
+observesValuesOf
<>
0.*
<>
FC_FeatureType
+triggeredByValuesOf
FC_CarrierOfCharacteristics
0.1
+carrierOfCharacteristics
0.*
+ typeName : LocalName
0.*
+ definition[0.1] : CharacterString Member Of 0.*
+featureType
+ code[0.1] : CharacterString
+affectsValuesOf
+ isAbstract : Boolean = FALSE
+ aliases[0.*] : LocalName
<> <> <>
+globalProperty
FC_BoundFeatureAttribute FC_Binding FC_PropertyType
0.*
+ memberName : LocalName
+ valueType [0.1] : TypeName + description[0.1] : CharacterString
+ definition[0.1] : CharacterString
+ cardinality : Multiplicity = 1
<> <>
FC_FeatureOperation
FC_FeatureAttribute
+ signature : CharacterString
+ code[0.1] : CharacterString
+ formalDefinition[0.1] : CharacterString
+ valueMeasurementUnit[0.1] : UnitOfMeasure
+ valueType[0.1] : TypeName
0.*
<> <>
+characterize
+triggeredByValuesOf
GF_AttributeType GF_Operation
0.*
0.1
(from General Feature Model) (from General Feature Model)
+observesValuesOf
0.*
+ valueType : TypeName + signature : CharacterString
+ valueDomain : CharacterString
+affectsValuesOf
+ cardinality : Multiplicity
( type(affectsValueOf)=FC_BoundFeatureAttribute or
type(affectsValueOf)=FC_FeatureAttribute ) and
+characterizeBy 0.*
( type(triggeredByValuesOf)=FC_BoundFeatureAttribute or
type(triggeredByValuesOf)=FC_FeatureAttribute ) and
AttributeOfAttribute
( type(observesValueOf)=FC_BoundFeatureAttribute or
type(observesValueOf)=FC_FeatureAttribute )
<>
GF_PropertyType
(from General Feature Model)
+ memberName : LocalName
+ definition: CharacterString
Figure B.4 — Derivation of FC_FeatureOperation from the GF_Operation metaclass
16 © ISO 2011 – All rights reserved

ISO 19110:2005/Amd.1:2011(E)
<> <>
GF_FeatureType FC_FeatureType
(from General Feature Model)
+ typeName : LocalName
+ typeName : LocalName
+ definition[0.1] : CharacterString
+ definition : CharacterString +featureType
+ code[0.1] : CharacterString
+ isAbstract : Boolean = false
+ isAbstract : Boolean = FALSE
0.1
+ aliases[0.*] : LocalName
Member Of
0.* +constrainedBy
+constrainedBy 0.*
<>
GF_Constraint
<>
(from General Feature Model)
FC_Constraint
+ description : CharacterString
+ description : CharacterString
+constrainedBy 0.*
0.* +constrainedBy
<>
FC_Binding
+ description[0.1] : CharacterString
0.*
+carrierOfCharacteristics 0.*
+globalProperty
0.*
<>
GF_PropertyType
<>
(from General Feature Model)
FC_PropertyType
+ memberName : LocalName
+ memberName : LocalName
+ definition: CharacterString
+ definition[0.1] : CharacterString
+ cardinality : Multiplicity = 1
<>
FC_CarrierOfCharacteristics
0.*
+carrierOfCharacteristics
Figure B.5 — Derivation of FC_Constraint from the GF_Constraint metaclass
Page 31, C.1
Delete the second and third paragraphs.
Page 31, C.2
Replace the two first paragraphs with the following.
A feature catalogue contains its identification and contact information, and definition of some number of
feature types with other information necessary for those definitions. Table C.1 illustrates a populated
FC_FeatureCatalogue (Table B.1). Only one of the contained feature types is illustrated; in addition, there
is one feature association (see C.4) in this sample feature catalogue.
Table C.2 illustrates a populated FC_DefinitionSource (Table B.13) for this sample feature catalogue.
ISO 19110:2005/Amd.1:2011(E)
Page 32, C.2
In Table C.1:
delete “Digital Geographic Information Exchange Standard (DIGEST) Feature and Attribute Coding Catalogue
(FACC)”, insert “A sample feature catalogue” in column 2, row 2;
delete row 8.
Page 33, C.3.1
In Table C.3, delete “FC_Binding (identity = 6)” from column 2, row 9.
Page 34, C.3.1
In Table C.4, delete “FC_Binding (identity = 6)” from column 2, row 6.
Delete the text immediately after Table C.5 and delete Table C.6.
Page 34, C.3.2
Change the heading as follows:
C.3.2 The abstract representation of a 'berthing structure'
Page 35, C.3.2
In Table C.7, delete “FC_Binding (identity = 19)” from column 2, last row.
In Table C.8, delete “FC_Binding (identity = 19)” from column 2, row 6.
Page 37, C.3.2
Delete the text immediately after Table C.18 and delete Table C.19.
Page 38, C.4
In Table C.20, delete “FC_FeatureAssociationRole”, insert “FC_AssociationRole” in column 2, row 7.
Delete “FC_Binding (unspecified in this example)” from column 2, last row.
In Table C.21, delete “FC_Binding (unspecified in this example)” from column 2, row 8.
Delete the footnote.
In Table C.22, delete “FC_FeatureAssociation.role”, insert “FC_FeatureAssociation.roleName” in column 1,
rows 7 and 8.
18 © ISO 2011 – All rights reserved

ISO 19110:2005/Amd.1:2011(E)
Page 39, C.4
In Tables C.23 and C.24, delete “FC_AssociationRole.valueType”, insert “FC_AssociationRole.rolePlayer” in
columns 1, last rows.
Page 40, C.5
In Table C.25 and C.26, delete “FC_FeatureInheritanceRelation”, insert “FC_InheritanceRelation”, in
columns 2, penultimate rows.
Replace the paragraph after Table C.26 with the following:
An instance of a “lighthouse” feature type is also an instance of a “building” feature type; feature
properties that apply to the “building” feature type in the sample feature catalogue also apply to the
“lighthouse” feature type. Table C.27 illustrates the representation of the “is a” inheritance relation using
FC_InheritanceRelation (Table B.3).
Page 41, C.6
In Table C.28, delete “FC_Binding (unspecified in this example)” from column 2, rows 10, 12, and 14.
In Table C.29, delete “FC_Binding (unspecified in this example)” from column 2, row 6.
Page 42, C.6
In Table C.30, delete “FC_Binding (unspecified in this example)” from column 2, row 6.
In Table C.31, delete “FC_Binding s” from column 2, last row.
In Table C.32, delete “FC_Binding (unspecified in this example)” from column 2, row 6.
Page 43, C.6
In Table C.33, delete “FC_Binding (unspecified in this example)” from column 2, row 13 and the last row.
In Table C.34, delete “FC_Binding (unspecified in this example)” from column 2, row 6.
In Table C.35, delete “FC_Binding (unspecified in this example)” from column 2, row 6.
Page 44, C.6
In C.6, replace the sixth paragraph (second paragraph on this page) with the following:
The feature operation definition describes the semantics of “raise dam” while the feature operation
signature specifies that given a real-valued newHeight and a Dam feature, that feature is accordingly
revised.
In Table C.36, delete row 7.
Page 44, C.6
Delete the last paragraph.
ISO 19110:2005/Amd.1:2011(E)
Page 45, C.6
Delete Tables C.37, C.38, and C.39.
Page 46, D.1
Replace the first paragraph with the following:
A feature catalogue forms a repository for a set of definitions to classify real-world phenomena of
significance to a particular universe of discourse. The catalogue provides a means for organizing the
abstract representation of the data that represent these phenomena, so that the resulting information is
as unambiguous, comprehensible, and useful as possible.
Replace the third paragraph with the following:
Although, for the purposes of this International Standard, feature operations are presented as a fourth
major aspect of feature abstraction, they represent a difference in point of view as much as they do a
difference in kind. In a functional specification, an operation is triggered by, returns or affects a value (i.e.
a feature attribute value) for a given type of geographic feature. If values are observed or affected for
more than one feature, the operation also specifies a functional relationship between them. By including
feature operations as an additional dimension of feature abstract representation, this International
Standard seeks to support the anticipated transition from current practice to a future, more rigorously
functional, approach; see Reference [8].
Pages 48 to 54, Annex D
Delete D.6.
Page 55, Bibliography
Update entry [4] as follows and delete footnote 2):
[4] ISO 19117, Geographic information — Portrayal
Add entry [9]:
[9] ISO 19126, Geographic information — Feature concept dictionaries and registers
Page 55
Insert Annexes E, F, and G before the Bibliography (see following pages).
20 © ISO 2011 – All rights reserved

ISO 19110:2005/Amd.1:2011(E)
Annex E
(normative)
Encoding description
E.1 Introduction
The XML schema implementation of this International Standard follows the encoding rules stated in
ISO/TS 19139:2007, Clause 8.
The namespace of the XML implementation of this International Standard is http://www.isotc211.org/2005/gfc.
This namespace is abbreviated to gfc, which stands for Geographic Feature Cataloguing.
E.2 XML namespaces
Figure E.1 shows the different namespaces used to implement this International Standard (grey boxes) along
with the relationships between these namespaces and the ISO 19100 series packages (white boxes).
<>
ISO 19110 Feature <>
Cataloguing gfc
<> <>
<>
<> <> <>
gco gmd gmx
<> <> <>
ISO/TS 19103 Conceptual ISO 19115 ISO 19139 XML
Schema Language Metadata schema

Figure E.1 — XML packaging
ISO 19110:2005/Amd.1:2011(E)
E.3 gfc namespace
E.3.1 Organization of the gfc namespace
This namespace contains the implementation of ISO 19110:2005 as defined in this amendment. As shown in
Figure E.2, the gfc namespace contains only one XML schema: gfc.xsd.
<>
<>
<>
Feature Cataloguing
gfc.xsd
Figure E.2 — Organization of the gfc namespace
E.3.2 gfc.xsd
This XML schema implements all the UML classes defined in ISO 19110:2005: FC_FeatureCatalogue,
FC_FeatureTyp
...