EN ISO 19131:2008

SLOVENSKI STANDARD
01-oktober-2008
Geografske informacije - Opredelitev podatkovnih proizvodov (ISO 19131:2007)
Geographic information - Data product specifications (ISO 19131:2007)
Geoinformation - Produktspezifikationen für Geodaten (ISO 19131:2007)
Information géographique - Spécifications de contenu informationnel (ISO 19131:2007)
Ta slovenski standard je istoveten z: EN ISO 19131:2008
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 19131
NORME EUROPÉENNE
EUROPÄISCHE NORM
April 2008
ICS 35.240.70
English Version
Geographic information - Data product specifications (ISO
19131:2007)
Information géographique - Spécifications de contenu Geoinformation - Produktspezifikationen für Geodaten (ISO
informationnel (ISO 19131:2007) 19131:2007)
This European Standard was approved by CEN on 21 March 2008.
CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European
Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references concerning such national
standards may be obtained on application to the CEN Management Centre or to any CEN member.
This European Standard 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 Management Centre has the same status as the
official versions.
CEN members are the national standards bodies of Austria, Belgium, Bulgaria, 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: rue de Stassart, 36  B-1050 Brussels
© 2008 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN ISO 19131:2008: E
worldwide for CEN national Members.

Contents Page
Foreword.3

Foreword
The text of ISO 19131:2007 has been prepared by Technical Committee ISO/TC 211 “Geographic
information/Geomatics” of the International Organization for Standardization (ISO) and has been taken over
as EN ISO 19131:2008 by Technical Committee CEN/TC 287 “Geographic Information” the secretariat of
which is held by NEN.
This European Standard shall be given the status of a national standard, either by publication of an identical
text or by endorsement, at the latest by October 2008, and conflicting national standards shall be withdrawn at
the latest by October 2008.
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, 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 19131:2007 has been approved by CEN as a EN ISO 19131:2008 without any modification.

INTERNATIONAL ISO
STANDARD 19131
First edition
2007-04-15
Geographic information — Data product
specifications
Information géographique — Spécifications de contenu informationnel

Reference number
ISO 19131:2007(E)
©
ISO 2007
ISO 19131:2007(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 2007
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 2007 – All rights reserved

ISO 19131:2007(E)
Contents Page
1 Scope . 1
2 Conformance. 1
3 Normative references . 1
4 Terms and definitions. 2
5 Symbols and abbreviated terms . 4
5.1 Abbreviations . 4
5.2 UML notation. 4
5.3 UML model relationships . 5
5.4 UML model stereotypes . 6
5.5 Package abbreviations. 6
6 General structure and content of a data product specification. 6
7 Overview . 7
8 Specification scopes . 8
9 Data product identification . 8
10 Data content and structure . 9
10.1 Feature-based data. 9
10.2 Coverage-based and imagery data . 10
11 Reference systems . 10
12 Data quality. 11
13 Data capture . 11
14 Data maintenance . 11
15 Portrayal . 11
16 Data product delivery . 12
17 Additional information. 12
18 Metadata . 12
Annex A (normative) Abstract test suite. 13
Annex B (informative) Relationship between data product specification and metadata. 14
Annex C (informative) UML packages . 15
Annex D (normative) Data product specification scopes . 16
Annex E (normative) Data product specification contents. 18
Annex F (informative) Example of a data product specification . 29

ISO 19131:2007(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 19131 was prepared by Technical Committee ISO/TC 211, Geographic information/Geomatics.
iv © ISO 2007 – All rights reserved

ISO 19131:2007(E)
Introduction
A data product specification is a detailed description of a dataset or dataset series together with additional
information that will enable it to be created, supplied to and used by another party. It is a precise technical
description of the data product in terms of the requirements that it will or may fulfil. However, the data product
specification only defines how the dataset should be. For various reasons, compromises may need to be
made in the implementation. The metadata associated with the product dataset should reflect how the product
dataset actually is.
A data product specification may be created and used on different occasions, by different parties and for
different reasons. It may, for example, be used for the original process of collecting data as well as for
products derived from already existing data. It may be created by producers to specify their product or by
users to state their requirements.
The purpose of this International Standard is to provide practical help in the creation of data product
specifications, in conformance with other existing standards for geographic information. An aim is to produce a
complete list of the items used to specify a data product.
This International Standard makes references to parts of existing standards. Some of the items used to
specify the data in a data product can also be used as metadata for a resulting dataset with the same data
product.
It is not necessary for a data product specification to specify the production process, but only the resulting
data product. Nevertheless, it may include production and maintenance aspects if judged necessary to
describe the data product.
This International Standard describes the content and structure of a data product specification. An example of
a data product specification is presented in Annex F.
When an item for a data product specification is already defined in another standard of the ISO 19100 series,
a reference to that document is explicitly made.
This International Standard is intended for use by producers, providers and potential users of data products.

INTERNATIONAL STANDARD ISO 19131:2007(E)

Geographic information — Data product specifications
1 Scope
This International Standard describes requirements for the specification of geographic data products, based
upon the concepts of other ISO 19100 International Standards. It also provides help in the creation of data
product specifications, so that they are easily understood and fit for their intended purpose.
2 Conformance
Any data product specification claiming conformance with this International Standard shall pass all the
requirements described in the abstract test suites in Annex A.
3 Normative references
The following referenced documents are indispensable for the application of this document. For dated
references, only the edition cited applies. For undated references, the latest edition of the referenced
document (including any amendments) applies.
ISO 639-2, Code for the representation of names of languages — Part 2: Alpha-3 code
ISO/TS 19103, Geographic information — Conceptual schema language
ISO 19107, Geographic information — Spatial schema
ISO 19108, Geographic information — Temporal schema
ISO 19109:2005, Geographic information — Rules for application schema
ISO 19110, Geographic information — Methodology for feature cataloguing
ISO 19111, Geographic information — Spatial referencing by coordinates
ISO 19112, Geographic information — Spatial referencing by geographic identifiers
ISO 19113, Geographic information — Quality principles
ISO 19115, Geographic information — Metadata
ISO 19117, Geographic information — Portrayal
ISO 19123, Geographic information — Schema for coverage geometry and functions
ISO/TS 19138, Geographic information — Data quality measures
ISO 19131:2007(E)
4 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
4.1
application
manipulation and processing of data in support of user requirements
[ISO 19101]
4.2
application schema
conceptual schema for data required by one or more applications
[ISO 19101]
4.3
conceptual model
model that defines concepts of a universe of discourse
[ISO 19101]
4.4
conceptual schema
formal description of a conceptual model
[ISO 19101]
4.5
coverage
feature that acts as a function to return values from its range for any direct position within its spatial, temporal
or spatiotemporal domain
[ISO 19123]
EXAMPLES Raster image, polygon overlay, digital elevation matrix.
4.6
data product
dataset or dataset series that conforms to a data product specification
4.7
data product specification
detailed description of a dataset or dataset series together with additional information that will enable it to be
created, supplied to and used by another party
NOTE A data product specification provides a description of the universe of discourse and a specification for
mapping the universe of discourse to a dataset. It may be used for production, sales, end-use or other purposes.
4.8
dataset
identifiable collection of data
[ISO 19115]
NOTE A dataset may be a smaller grouping of data which, though limited by some constraint such as spatial extent
or feature type, is located physically within a larger dataset. Theoretically, a dataset may be as small as a single feature or
feature attribute contained within a larger dataset. A hardcopy map or chart may be considered a dataset.
2 © ISO 2007 – All rights reserved

ISO 19131:2007(E)
4.9
dataset series
collection of datasets sharing the same product specification
[ISO 19115]
4.10
domain
well-defined set
[ISO/TS 19103]
NOTE “Well-defined” means that the definition is both necessary and sufficient, as everything that satisfies the
definition is in the set and everything that does not satisfy the definition is necessarily outside the set.
4.11
feature
abstraction of real-world phenomena
[ISO 19101]
NOTE A feature may occur as a type or an instance. Feature type or feature instance shall be used when only one is
meant.
4.12
feature association
relationship that links instances of one feature type with instances of the same or a different feature type
[ISO 19110]
NOTE 1 A feature association may occur as a type or an instance. Feature association type or feature association
instance is used when only one is meant.
NOTE 2 Feature associations include aggregation of features.
4.13
feature attribute
characteristic of a feature
[ISO 19101]
NOTE 1 A feature attribute may occur as a type or an instance. Feature attribute type or feature attribute instance is
used when only one is meant.
NOTE 2 A feature attribute type has a name, a data type and a domain associated with it. A feature attribute for a
feature instance has an attribute value taken from the domain.
4.14
geographic data
data with implicit or explicit reference to a location relative to the Earth
[ISO 19109]
NOTE Geographic information is also used as a term for information concerning phenomena implicitly or explicitly
associated with a location relative to the Earth.
ISO 19131:2007(E)
4.15
metadata
data about data
[ISO 19115]
4.16
model
abstraction of some aspects of reality
[ISO 19109]
4.17
portrayal
presentation of information to humans
[ISO 19117]
4.18
quality
totality of characteristics of a product that bear on its ability to satisfy stated and implied needs
[ISO 19101]
4.19
universe of discourse
view of the real or hypothetical world that includes everything of interest
[ISO 19101]
5 Symbols and abbreviated terms
5.1 Abbreviations
This International Standard adopts the following convention for presentation purposes:
UML Unified Modeling Language.
5.2 UML notation
The diagrams that appear in this International Standard are presented using the Unified Modeling Language
(UML) static structure diagram with the basic type definitions from ISO/TS 19103. The UML notations used in
this International Standard are described in the Figures 1 and 2.
4 © ISO 2007 – All rights reserved

ISO 19131:2007(E)
Figure 1 — UML notation
5.3 UML model relationships
If an association is navigable in a particular direction, the model has a “role name” that is appropriate for the
role of the target object in relation to the source object. Thus, in a two-way association, two role names will be
supplied. Figure 2 represents how role names and cardinalities are expressed in UML diagrams.

NOTE Where cardinality is not explicitly stated in a diagram, it is assumed to be “exactly one”.
Figure 2 — UML roles
ISO 19131:2007(E)
5.4 UML model stereotypes
A UML stereotype is an extension mechanism for existing UML concepts. It is a model element that is used to
classify (or mark) other UML elements so that they behave in some respect as if they were instances of new
virtual or pseudo metamodel classes whose form is based on existing base metamodel classes. Stereotypes
augment the classification mechanisms on the basis of the built-in UML metamodel class hierarchy. Below are
brief descriptions of the stereotypes used in this International Standard. For more detailed descriptions consult
ISO/TS 19103.
In this International Standard the following stereotype is used:
⎯ <> package that contains definitions, without any sub-packages.
5.5 Package abbreviations
Abbreviations are used to denote the package that contains a class. Those abbreviations precede class
names, connected by a “_”. The International Standard in which those classes are located is indicated in
parentheses. A list of those abbreviations follows.
CI Citation (ISO 19115)
CV Coverages (ISO 19123)
DPS Data product specification (this International Standard)
DQ Data quality (ISO 19115)
EX Extent (ISO 19115)
FC Feature catalogue (ISO 19110)
GM Geometry (ISO 19107)
MD Metadata (ISO 19115)
TM Temporal (ISO 19108)
6 General structure and content of a data product specification
A data product specification defines the requirements for a data product. It forms the basis for producing or
acquiring data. It may also help potential users to evaluate the data product to determine its fitness for use by
them. The information contained in a data product specification is different from that contained in metadata,
which provides information about a particular physical dataset. Information from the data product specification
may be used in the creation of metadata for a particular dataset that is created in conformance with that data
product specification. Thus, metadata describes how a dataset actually is, whilst a data product specification
describes how it should be. The requirements for metadata are described in ISO 19115. The relationship
between a data product specification and metadata is described more fully in Annex B.
A data product specification shall contain major sections covering the following aspects of the data product:
⎯ Overview — see Clause 7;
⎯ Specification scopes — see Clause 8;
⎯ Data product identification — see Clause 9;
⎯ Data content and structure — see Clause 10;
6 © ISO 2007 – All rights reserved

ISO 19131:2007(E)
⎯ Reference systems — see Clause 11;
⎯ Data quality — see Clause 12;
⎯ Data product delivery — see Clause 16;
⎯ Metadata — see Clause 18.
A data product specification may also contain sections covering the following aspects of the data product:
⎯ Data capture — see Clause 13;
⎯ Data maintenance — see Clause 14;
⎯ Portrayal — see Clause 15;
⎯ Additional information — see Clause 17.
Each of these sections of the data product specification is described in the following clauses. Each section,
except for the overview (see Clause 7), which is human-readable free text, corresponds to a UML package.
These packages are shown in Annex C.
The minimum description of a data product shall contain the mandatory elements within each section (see
UML model and corresponding tables in Annexes D and E).
7 Overview
The overview shall include the following parts:
⎯ information about the creation of the data product specification;
NOTE This may include the title, a reference date, the responsible party, the language and the topic category.
⎯ terms and definitions;
NOTE This may take the form of a reference to a terminology repository.
⎯ abbreviations;
⎯ the name and any acronyms of the data product;
⎯ an informal description of the data product.
The informal description of the data product shall contain general information about the data product which
may include the following aspects:
⎯ the content of the dataset;
⎯ the extent (both spatial and temporal) of the data;
⎯ the specific purpose for which the data shall be or has been collected;
⎯ the data sources and data production processes;
⎯ the maintenance of the data.
NOTE An informal description is intended to give a short introduction to the data product specification and allow a
human reader a better understanding of the specification.
ISO 19131:2007(E)
8 Specification scopes
The specification of a data product shall include a description of its scope, which may be restricted in terms of
spatial or temporal extent, feature types and properties included, spatial representation, or position within a
product hierarchy. The data product specification may specify a partitioning of the data content of the product
on the basis of one or more criteria. Such partitioning may be different for different parts of the data product
specification. Each such part of the data content shall be described by a specification scope that may inherit
or override the general specification scope.
Criteria that might be used as the basis for partitioning include, but are not limited to
⎯ spatial or temporal extent,
⎯ feature type,
⎯ property type,
⎯ property value,
⎯ spatial representation,
⎯ product hierarchy.
EXAMPLE Data products to support navigation often contain two sets of feature types: those that provide navigation
information that changes rapidly and is essential for safety of navigation, and those that provide background reference
information. Maintenance and delivery information would be partitioned on the basis of these groupings; reference system
information would not.
The information describing the specification scope shall include scope identification and items from the
following as required to describe the scope:
⎯ level — a code identifying the hierarchical level of the data;
⎯ level name — the name of the hierarchical level of the data;
⎯ level description — a detailed description of the level of the data;
⎯ extent — the spatial, vertical and temporal extent of the data;
⎯ coverage — the coverages to which the information applies.
A formal definition for specification scope information is given in Annex D which provides a UML model and
the corresponding data definitions. The specification scope shall be identified by a Scope ID in the statement
of that part of the specification.
9 Data product identification
The information identifying the data product shall include the following items:
⎯ title — the title of the data product;
⎯ abstract — a brief narrative summary of the content of the data product;
⎯ topic category — the main theme(s) of the data product;
⎯ geographic description — the extent of the geographic area covered by the data product.
8 © ISO 2007 – All rights reserved

ISO 19131:2007(E)
The following optional items may be included where appropriate:
⎯ alternate title — short name or other name by which the data product is known;
⎯ purpose — summary of the intentions with which the data product is developed;
⎯ spatial representation type — the form of the spatial representation (e.g. vector data);
⎯ spatial resolution — a factor which provides a general understanding of the density of spatial data in the
data product;
⎯ supplemental information — any other descriptive information about the data product.
A formal definition for identification information is given in E.1 which provides a UML model and the
corresponding data definitions.
10 Data content and structure
10.1 Feature-based data
The content information of a feature-based data product is described in terms of an application schema and a
feature catalogue, and references to these and a narrative description shall be included in the specification.
An application schema provides the formal description of the data structure and content of the data product. It
is a conceptual model described using a conceptual schema language such as UML. It shall include the
representation of feature types, property types including attribute types, feature operations and feature
associations, inheritance relations and constraints. Attribute types cover descriptive, geometric and temporal
properties. Associations include spatial and temporal relationships such as topological relations as well as
non-spatial relationships (e.g. ownership) that occur between feature types.
The elaboration of the application schema shall be in accordance with ISO 19109:2005, more specifically
applying the rules in Clauses 7 and 8, and in particular those in the following subclauses of ISO 19109:2005:
⎯ 8.3 when the application schema is created in UML;
⎯ 8.5 when metadata has to be added on feature instances, feature attributes or associations between
features (e.g. quality information);
⎯ 8.6, Temporal rules, when describing temporal feature type properties;
⎯ 8.7, Spatial rules, when describing spatial feature type properties with spatial data types;
⎯ 8.9, Spatial referencing using geographic identifiers, when describing spatial feature type properties with
geographic identifiers.
A feature catalogue is a repository which provides the semantics of all feature types, together with their
attributes and attribute value domains, association types between feature types, and feature operations
contained in the application schema. All the feature types, their attributes and attribute value domains, the
association types between feature types, and feature operations expressed in the application schema shall be
described in a feature catalogue.
The feature catalogue shall be realized according to ISO 19110. It may be included in the data product
specification or may be externally referenced by the name of the feature catalogue. The data product
specification shall include a description of each of the features in the data product. This shall include a
reference to, or a description of, a feature and attribute catalogue as described in ISO 19110.
A formal definition for content and structure of feature-based data is given in E.2 which provides a UML model
and the corresponding data definitions.
ISO 19131:2007(E)
10.2 Coverage-based and imagery data
A coverage is considered a subtype of a feature. It behaves like a function which returns one or more feature
attribute values from a direct position within a spatiotemporal domain. It can be derived from a collection of
features that have common attributes. It associates a “range” to a “spatiotemporal domain.” A “range” of a
coverage is a set of attribute values which is associated with the elements of the spatiotemporal domain of
that coverage. A spatiotemporal domain is a set of geometric objects described in terms of direct positions
(spatial and/or temporal coordinates) within a bounded space and may be extended to all of the direct
positions within the convex hull of that set of geometric objects. The spatiotemporal domain corresponds to
the extent of the coverage. Coverage includes raster images (e.g. Landsat images), digital models for
elevation, temperature, or precipitation, and polygon overlays (e.g. land use polygons, forest stand inventories,
crop measurements). For example, an entire satellite image could be considered as the representation of a
feature, that is, the “abstraction of real-world phenomena” as viewed by the sensor that produced the image.
The image itself is usually represented as a simple grid consisting of a set of rows and columns providing
organization to a set of pixels. Each pixel contains attribution data such the intensity — represented by a
colour schema (e.g. RGB, HIS) within a colour space — seen at that point. Also, each pixel may contain an
additional attribute that indicates the feature identifier associated with the pixel, so that the pixels
corresponding to the image of a building are marked as the feature “building”, and those corresponding to a
road are marked as “road”.
A data product specification shall identify each coverage and each image that is included within the
specification and shall provide a narrative description for each. The content information for each coverage or
image shall be described according to ISO 19123. Accordingly, the following components shall be identified to
describe a coverage or an image:
⎯ coverage/imagery identifier;
⎯ coverage/imagery description;
⎯ the coverage type;
⎯ the specification of additional coverage information.
NOTE The coverage type specifies the type of geometry used for this particular coverage and may be either a
discrete coverage or a continuous coverage. Further information regarding the coverage may be specified as defined in
ISO 19123.
A formal definition of data content and structure for coverage-based and imagery data is given in E.2, which
provides a UML model and the corresponding data definitions.
11 Reference systems
The data product specification shall include information that defines the reference systems used in the data
product. This shall include the following:
⎯ the spatial reference system;
⎯ the temporal reference system.
The spatial reference system used may be either a coordinate reference system, as defined in ISO 19111, or
a spatial reference system using geographic identifiers, as defined in ISO 19112. The temporal reference
system shall be as defined in ISO 19108. In either case, the reference system shall be identified by a
reference system identifier.
A formal definition for reference system information is given in E.3, which provides a UML model and the
corresponding data definitions.
10 © ISO 2007 – All rights reserved

ISO 19131:2007(E)
12 Data quality
The data product specification shall identify the data quality requirements for the data product in accordance
with ISO 19113. This shall include a statement on acceptable conformance quality levels and corresponding
data quality measures as defined in ISO/TS 19138. This statement shall cover all the data quality elements
and data quality sub-elements defined in ISO 19113, even if only to state that a specific data quality element
or data quality sub-element is not applicable. It shall also include any additional data quality elements and
sub-elements.
A formal definition of data quality information is given in E.4, which provides a UML model and the
corresponding data definitions. It shall be repeated as many times as the number of different specification
scopes in the data product and shall be recorded as described in ISO 19115.
When establishing the conformance quality levels in a data product specification, it should be taken into
consideration that
⎯ different quality evaluation methods may be applied to different parts of the dataset (different data quality
scopes),
⎯ for the same data quality element, different results with different confidence intervals can be achieved
with different quality evaluation measures,
⎯ conformance quality levels can be different for different features in the dataset, e.g. the required
positional accuracy for features with fuzzy boundaries is usually much lower than for linear and well-
defined features.
13 Data capture
The data product specification may provide information on how the data is captured. Where this section of the
data product specification is included, it shall contain a data capture statement which shall be a general
description of the sources and the processes to be used. It may allow freedom of choice for the data capture
process or may specify one particular data capture process. Conformance quality levels may need to be given
for intermediate data which may be required for the production of the data. A formal definition for data capture
information is given in E.5, which provides a UML model and the corresponding data definitions.
14 Data maintenance
The data product specification may provide information on how the data is maintained. Where this section of
the data product specification is included, it shall describe the principles and criteria applied in the
maintenance of the data once it has been captured. This shall include the maintenance and update frequency
which shall describe the frequency with which changes and additions are made to the data product. A formal
definition for data maintenance information is given in E.6, which provides a UML model and the
corresponding data definitions.
15 Portrayal
The data product specification may provide information on how the data held within the dataset is to be
presented as graphic output, as a plot or as an image. Where included, this shall take the form of a reference
to a set of portrayal rules and a set of portrayal specifications. A formal definition of portrayal information is
given in E.7, which provides a UML model and the corresponding data definitions.
The portrayal catalogue shall be defined in accordance with ISO 19117.
ISO 19131:2007(E)
16 Data product delivery
The data product specification shall identify any requirements for the data product delivery. These shall
include delivery format information and delivery medium information, where applicable.
Delivery format information may include the following items:
⎯ name of the data format;
⎯ version of the format (date, number, etc);
⎯ the name of the subset, profile or product specification of the format;
⎯ structure of the delivery file;
⎯ language(s) used within the dataset;
⎯ the full name of the character-coding standard used.
Delivery medium information may include the following items:
⎯ description of the units of delivery (e.g. tiles, layer, geographic areas);
⎯ estimated size of a unit in the specified format, expressed in Mbytes;
⎯ name of the data medium;
⎯ other delivery information.
A formal definition for data product delivery information is given in E.8, which provides a UML model and the
corresponding data definitions.
17 Additional information
This section of the data product specification may include any other aspects of the data product not provided
elsewhere in this International Standard. A formal definition for additional information is given in E.9, which
provides a UML model and the corresponding data definitions. This might include constraint information (for
access and use). If this information only applies to part of the product, then the scope for this must be clearly
identified.
18 Metadata
The core metadata elements as defined in ISO 19115 shall be included with the data product. Any additional
metadata items that need to be supplied shall be stated in the data product specification. The format and
encoding of the metadata shall be stated in the data product specification.
12 © ISO 2007 – All rights reserved

ISO 19131:2007(E)
Annex A
(normative)
Abstract test suite
A.1 Data product specification sections
a) Test purpose: Verify that all the mandatory sections are included in the data product specification.
b) Test method: Inspect all sections in the data product specification to verify that they are included.
c) Reference: Clause 6.
d) Test type: Basic.
A.2 Mandatory items
a) Test purpose: Verify that for each section of the data product specification, all the mandatory items of the
standard are included in the data product specification.
b) Test method: Inspect each section of the data product specification to verify that all the mandatory items
are present.
c) Reference: Clauses 7-18.
d) Test type: Basic.
A.3 Item details
a) Test purpose: Verify that each item is in the correct form.
b) Test method: Inspect all items in the data product specification to verify that they are in the correct form.
c) Reference: Annexes D and E.
d) Test type: Basic.
ISO 19131:2007(E)
Annex B
(informative)
Relationship between data product specification and metadata
ISO 19115 provides a structure for describing digital geographic data. It defines metadata elements, provides
a schema and establishes a common set of metadata terminology, definitions and extension procedures. This
International Standard uses part of the same schema.
To ensure the smooth transition of information elements from the data product specification to metadata, the
mapping of the concepts is vital. Whilst metadata documents how data really is, the data product specification
documents how the data should be, focusing on the requirements. These requirements are the basis for
producing data, but also for some users to evaluate if the product is suitable for their requirements. The data
product specification may be created before the data product. Many of the elements of the data product
specification will be used to document the metadata of the resulting dataset. Figure B.1 explains this
relationship, showing how the data product specification specifies the data product which is implemented as a
dataset which in turn is described by metadata.

Figure B.1 — Relationship between data product specification and metadata
NOTE Figure B.1 is illustrative and does not form part of the UML specification for a data product specification.
14 © ISO 2007 – All rights reserved

ISO 19131:2007(E)
Annex C
(informative)
UML packages
The model for a data product specification (DPS) is described as a set of packages. Each package contains
one or more entities (UML classes) which can be specified (subclassed) or generalized (superclassed).
Entities contain elements (UML class attributes) which identify the discrete units applicable to describing a
data product specification. Figure C.1 illustrates the layout of the packages. A data product is fully specified in
the UML model diagrams and partially specified in the data dictionary for each package which can be found in
Annexes D and E.
Figure C.1 — Data product specification packages

ISO 19131:2007(E)
Annex D
(normative)
Data product specification scop
...