Reference number ISO 19115:2003(E) © ISO 2003 INTERNATIONAL STANDARD ISO 19115 First edition 2003-05-01 Geographic information — Metadata Information géographique — Métadonnées ISO 19115:2003(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 2003 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 2003 — All rights reserved ISO 19115:2003(E) © ISO 2003 — All rights reserved iii Contents Page Foreword .......................................................................................................................................................... vii Introduction..................................................................................................................................................... viii 1 Scope......................................................................................................................................................1 2 Conformance .........................................................................................................................................1 2.1 Conformance requirements .................................................................................................................1 2.2 Metadata Profiles...................................................................................................................................1 2.3 Obligation and condition ......................................................................................................................2 3 Normative references............................................................................................................................2 4 Terms and definitions ...........................................................................................................................3 5 Symbols and abbreviated terms..........................................................................................................4 5.1 Abbreviations.........................................................................................................................................4 5.2 UML notations........................................................................................................................................4 5.3 UML model relationships......................................................................................................................5 5.3.1 Associations ..........................................................................................................................................5 5.3.2 Generalization........................................................................................................................................5 5.3.3 Instantiation/Dependency.....................................................................................................................5 5.3.4 Roles.......................................................................................................................................................5 5.4 UML model stereotypes........................................................................................................................6 5.5 Package abbreviations..........................................................................................................................7 5.6 UML model/data dictionary relationships...........................................................................................8 6 Requirements.........................................................................................................................................8 6.1 Metadata for geographic data requirement ........................................................................................8 6.2 Metadata application information........................................................................................................8 6.3 Metadata packages................................................................................................................................9 6.3.1 Metadata package and entity relationship..........................................................................................9 6.3.2 Package descriptions..........................................................................................................................11 6.4 Metadata datatypes .............................................................................................................................14 6.4.1 Extent information (EX_Extent) .........................................................................................................14 6.4.2 Citation and responsible party information (CI_Citation and CI_ResponsibleParty) ..................15 6.5 Core metadata for geographic datasets............................................................................................15 6.6 Unified Modelling Language (UML) diagrams ..................................................................................16 6.7 Data dictionary.....................................................................................................................................16 6.8 Metadata extensions and profiles......................................................................................................17 6.9 Abstract test suite ...............................................................................................................................17 6.10 Comprehensive dataset metadata application profile.....................................................................17 6.11 Metadata extension methodology .....................................................................................................17 6.12 Metadata implementation ...................................................................................................................17 6.13 Hierarchical levels of metadata..........................................................................................................17 6.14 Implementation examples ..................................................................................................................17 6.15 Multilingual support for free text fields.............................................................................................17 Annex A (normative) Metadata schemas........................................................................................................18 A.1 Metadata UML models.........................................................................................................................18 A.2 Metadata package UML diagrams......................................................................................................19 A.2.1 Metadata entity set information .........................................................................................................19 A.2.2 Identification information ...................................................................................................................19 A.2.3 Constraint information........................................................................................................................21 A.2.4 Data quality information .....................................................................................................................22 A.2.5 Maintenance information....................................................................................................................25 A.2.6 Spatial representation information....................................................................................................26 ISO 19115:2003(E) iv © ISO 2003 — All rights reserved A.2.7 Reference system information .......................................................................................................... 27 A.2.8 Content information............................................................................................................................ 28 A.2.9 Portrayal catalogue information........................................................................................................ 29 A.2.10 Distribution information..................................................................................................................... 30 A.2.11 Metadata extension information........................................................................................................ 31 A.2.12 Application schema information....................................................................................................... 32 A.3 Metadata data types ........................................................................................................................... 33 A.3.1 Extent information .............................................................................................................................. 33 A.3.2 Citation and responsible party information..................................................................................... 34 Annex B (normative) Data dictionary for geographic metadata.................................................................. 35 B.1 Data dictionary overview ................................................................................................................... 35 B.1.1 Introduction......................................................................................................................................... 35 B.1.2 Name/role name .................................................................................................................................. 35 B.1.3 Short name and domain code ........................................................................................................... 35 B.1.4 Definition ............................................................................................................................................. 35 B.1.5 Obligation/Condition .......................................................................................................................... 36 B.1.6 Maximum occurrence......................................................................................................................... 36 B.1.7 Data type.............................................................................................................................................. 36 B.1.8 Domain................................................................................................................................................. 36 B.2 Metadata package data dictionaries ................................................................................................. 38 B.2.1 Metadata entity set information......................................................................................................... 38 B.2.2 Identification information (includes data and service identification)............................................ 40 B.2.3 Constraint information (includes legal and security) ..................................................................... 46 B.2.4 Data quality information..................................................................................................................... 48 B.2.5 Maintenance information ................................................................................................................... 57 B.2.6 Spatial representation information (includes grid and vector representation)............................ 59 B.2.7 Reference system information (includes temporal, coordinate and geographic identifiers)..... 63 B.2.8 Content information (includes Feature catalogue and Coverage descriptions).......................... 68 B.2.9 Portrayal catalogue information........................................................................................................ 73 B.2.10 Distribution information..................................................................................................................... 73 B.2.11 Metadata extension information........................................................................................................ 78 B.2.12 Application schema information....................................................................................................... 80 B.3 Data type information......................................................................................................................... 81 B.3.1 Extent information .............................................................................................................................. 81 B.3.2 Citation and responsible party information..................................................................................... 85 B.4 Externally referenced entities............................................................................................................ 91 B.4.1 Introduction......................................................................................................................................... 91 B.4.2 Date and DateTime information......................................................................................................... 91 B.4.3 Distance, angle, measure, number, record, recordType, scale and UomLength information.... 91 B.4.4 Feature type, property type, and attribute type information.......................................................... 91 B.4.5 PeriodDuration and temporal primitive information ....................................................................... 91 B.4.6 Point and Object information ............................................................................................................ 92 B.4.7 Set and Sequence information.......................................................................................................... 92 B.4.8 Type name information ...................................................................................................................... 92 B.4.9 Vertical datum information ................................................................................................................ 92 B.5 CodeLists and enumerations ............................................................................................................ 92 B.5.1 Introduction......................................................................................................................................... 92 B.5.2 CI_DateTypeCode <> ...................................................................................................... 92 B.5.3 CI_OnLineFunctionCode <>........................................................................................... 93 B.5.4 CI_PresentationFormCode <> ....................................................................................... 93 B.5.5 CI_RoleCode <>............................................................................................................... 93 B.5.6 DQ_EvaluationMethodTypeCode <>............................................................................. 94 B.5.7 DS_AssociationTypeCode <>........................................................................................ 94 B.5.8 DS_InitiativeTypeCode <>.............................................................................................. 94 B.5.9 MD_CellGeometryCode <>............................................................................................. 95 B.5.10 MD_CharacterSetCode <>.............................................................................................. 95 B.5.11 MD_ClassificationCode <>............................................................................................. 96 B.5.12 MD_CoverageContentTypeCode <>.............................................................................. 96 B.5.13 MD_DatatypeCode <> ..................................................................................................... 97 ISO 19115:2003(E) © ISO 2003 — All rights reserved v B.5.14 MD_DimensionNameTypeCode <> ................................................................................97 B.5.15 MD_GeometricObjectTypeCode <> ...............................................................................97 B.5.16 MD_ImagingConditionCode <> ......................................................................................98 B.5.17 MD_KeywordTypeCode <> .............................................................................................98 B.5.18 MD_MaintenanceFrequencyCode <>.............................................................................99 B.5.19 MD_MediumFormatCode <> ...........................................................................................99 B.5.20 MD_MediumNameCode <>..............................................................................................99 B.5.21 MD_ObligationCode <>...........................................................................................100 B.5.22 MD_PixelOrientationCode <>.................................................................................100 B.5.23 MD_ProgressCode <> ...................................................................................................100 B.5.24 MD_RestrictionCode <> ................................................................................................101 B.5.25 MD_ScopeCode <> ........................................................................................................101 B.5.26 MD_SpatialRepresentationTypeCode <> ....................................................................102 B.5.27 MD_TopicCategoryCode << Enumeration>> ..................................................................................102 B.5.28 MD_TopologyLevelCode <>..........................................................................................104 Annex C (normative) Metadata extensions and profiles.............................................................................105 C.1 Background........................................................................................................................................105 C.2 Types of extensions..........................................................................................................................105 C.3 Creating an extension.......................................................................................................................105 C.4 Rules for creating an extension.......................................................................................................105 C.5 Community profile.............................................................................................................................106 C.6 Rules for creating a profile...............................................................................................................107 Annex D (normative) Abstract test suite ......................................................................................................108 D.1 Abstract test suite .............................................................................................................................108 D.2 Metadata test suite ............................................................................................................................108 D.2.1 Test case identifier: Completeness test..........................................................................................108 D.2.2 Test case identifier: Maximum occurrence test .............................................................................108 D.2.3 Test case identifier: Short name test ..............................................................................................108 D.2.4 Test case identifier: Data type test..................................................................................................109 D.2.5 Test case identifier: Domain test.....................................................................................................109 D.2.6 Test case identifier: Schema test ....................................................................................................109 D.3 User-defined extension metadata test suite...................................................................................109 D.3.1 Test case identifier: Exclusiveness test .........................................................................................109 D.3.2 Test case identifier: Definition test..................................................................................................110 D.3.3 Test case identifier: Standard metadata test..................................................................................110 D.4 Metadata profiles...............................................................................................................................110 D.4.1 Test case identifier: Metadata profiles............................................................................................110 Annex E (normative) Comprehensive dataset metadata application profile............................................111 E.1 Comprehensive dataset metadata application schema ................................................................111 E.2 Comprehensive dataset metadata profile – UML model ...............................................................112 Annex F (informative) Metadata extension methodology...........................................................................113 F.1 Metadata extensions methodology .................................................................................................113 F.2 Review of existing metadata elements (Stage 1) ...........................................................................113 F.3 Definition of a new metadata section (Stage 2)..............................................................................114 F.4 Definition of a new metadata codelist (Stage 3).............................................................................114 F.5 Definition of a new metadata codelist element (Stage 4)..............................................................114 F.6 Definition of a new metadata element (Stage 5).............................................................................115 F.7 Definition of a new metadata entity (Stage 6).................................................................................115 F.8 Definition of a more stringent metadata obligation (Stage 7).......................................................116 F.9 Definition of more restrictive metadata codelist (Stage 8)............................................................116 F.10 Documentation of metadata extensions (Stage 9).........................................................................117 Annex G (informative) Metadata implementation ........................................................................................119 G.1 Background........................................................................................................................................119 G.1.1 Problem statement ............................................................................................................................119 G.1.2 Scope and objectives........................................................................................................................119 G.1.3 Granularity of spatial data supported .............................................................................................119 G.2 Metadata hierarchy levels.................................................................................................................120 ISO 19115:2003(E) vi © ISO 2003 — All rights reserved G.2.1 Dataset series metadata (optional) ................................................................................................. 120 G.2.2 Dataset metadata .............................................................................................................................. 120 G.2.3 Feature type metadata (optional) .................................................................................................... 121 G.2.4 Feature instance metadata (optional)............................................................................................. 121 G.2.5 Attribute type metadata (optional) .................................................................................................. 121 G.2.6 Attribute instance metadata (optional)........................................................................................... 121 Annex H (informative) Hierarchical levels of metadata .............................................................................. 122 H.1 Levels of metadata ........................................................................................................................... 122 H.2 Example ............................................................................................................................................. 122 Annex I (informative) Implementation examples......................................................................................... 126 I.1 Metadata examples........................................................................................................................... 126 I.2 Example 1 – Exploration Licences for Minerals ............................................................................ 126 I.3 Example 2 – Example of extended metadata................................................................................. 129 I.4 Data dictionary for the extended elements.................................................................................... 130 I.5 MD_KeywordType (Modified) .......................................................................................................... 136 Annex J (informative) Multilingual support for free text metadata element............................................. 137 J.1 Free text metadata elements ........................................................................................................... 137 J.2 Data structure for handling multi-languages support in free text metadata elements ............. 138 J.3 Example of multi-languages free text in a metadata element...................................................... 139 Bibliography................................................................................................................................................... 140 ISO 19115:2003(E) © ISO 2003 — All rights reserved vii 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 19115 was prepared by Technical Committee ISO/TC 211, Geographic information/Geomatics. ISO 19115:2003(E) viii © ISO 2003 — All rights reserved Introduction A revival in the awareness of the importance of geography and how things relate spatially, combined with the advancement of electronic technology, have caused an expansion in the use of digital geographic information and geographic information systems worldwide. Increasingly, individuals from a wide range of disciplines outside of the geographic sciences and information technologies are capable of producing, enhancing, and modifying digital geographic information. As the number, complexity, and diversity of geographic datasets grow, a method for providing an understanding of all aspects of this data grows in importance. Digital geographic data is an attempt to model and describe the real world for use in computer analysis and graphic display of information. Any description of reality is always an abstraction, always partial, and always just one of many possible "views". This "view" or model of the real world is not an exact duplication; some things are approximated, others are simplified, and some things are ignored. There is seldom perfect, complete, and correct data. To ensure that data is not misused, the assumptions and limitations affecting the creation of data must be fully documented. Metadata allows a producer to describe a dataset fully so that users can understand the assumptions and limitations and evaluate the dataset's applicability for their intended use. Typically, geographic data is used by many people other than the producer. It is often produced by one individual or organization and used by another. Proper documentation will provide those unfamiliar with the data with a better understanding, and enable them to use it properly. As geographic data producers and users handle more and more data, proper documentation will provide them with a keener knowledge of their holdings and will allow them to better manage data production, storage, updating, and reuse. The objective of this International Standard is to provide a structure for describing digital geographic data. This International Standard is intended to be used by information system analysts, program planners, and developers of geographic information systems, as well as others in order to understand the basic principles and the overall requirements for standardization of geographic information. This International Standard defines metadata elements, provides a schema and establishes a common set of metadata terminology, definitions, and extension procedures. When implemented by a data producer, this International Standard will: 1) Provide data producers with appropriate information to characterize their geographic data properly. 2) Facilitate the organization and management of metadata for geographic data. 3) Enable users to apply geographic data in the most efficient way by knowing its basic characteristics. 4) Facilitate data discovery, retrieval and reuse. Users will be better able to locate, access, evaluate, purchase and utilize geographic data. 5) Enable users to determine whether geographic data in a holding will be of use to them. This International Standard defines general-purpose metadata, in the field of geographic information. More detailed metadata for geographic datatypes and geographic services are defined in other ISO 19100 series standards and user extensions. INTERNATIONAL STANDARD ISO 19115:2003(E) © ISO 2003 — All rights reserved 1 1 Scope This International Standard defines the schema required for describing geographic information and services. It provides information about the identification, the extent, the quality, the spatial and temporal schema, spatial reference, and distribution of digital geographic data. This International Standard is applicable to:  the cataloguing of datasets, clearinghouse activities, and the full description of datasets;  geographic datasets, dataset series, and individual geographic features and feature properties. This International Standard defines:  mandatory and conditional metadata sections, metadata entities, and metadata elements;  the minimum set of metadata required to serve the full range of metadata applications (data discovery, determining data fitness for use, data access, data transfer, and use of digital data);  optional metadata elements – to allow for a more extensive standard description of geographic data, if required;  a method for extending metadata to fit specialized needs. Though this International Standard is applicable to digital data, its principles can be extended to many other forms of geographic data such as maps, charts, and textual documents as well as non-geographic data. NOTE Certain mandatory metadata elements may not apply to these other forms of data. 2 Conformance 2.1 Conformance requirements Metadata shall be provided as specified in Clause 6 and Annexes A and B. User-defined metadata shall be defined and provided as specified in Annex C. Any metadata claiming conformance with this International Standard shall pass the requirements described in the abstract test suite presented in Annex D. 2.2 Metadata Profiles Any profile conforming to this International Standard shall conform to the rules in Annex C, Clause C.6. Geographic information — Metadata ISO 19115:2003(E) 2 © ISO 2003 — All rights reserved 2.3 Obligation and condition For the purposes of conformance testing using the abstract test suite in Annex D, metadata entities and elements shall be considered to be mandatory, conditional or optional as specified in the applicable profile. 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 (all parts), Code for the representation of names of languages ISO 3166 (all parts), Codes for the representation of names of countries and their subdivisions ISO 4217:2001, Codes for the representation of currencies and funds ISO 8859 (parts 1 to 16), Information technology ― 8-bit single-byte coded graphic character sets ISO 8879, Information processing ― Text and office systems ― Standard Generalized Markup Language (SGML) ISO/IEC 10646-1, Information technology ― Universal Multiple-Octet Coded Character Set (UCS) ― Part 1: Architecture and Basic Multilingual Plane ISO/IEC 11179 (all parts), Information technology ― Specification and standardization of data elements ISO 19106:―1) , Geographic information ― Profiles ISO 19107:―1), Geographic information ― Spatial schema ISO 19108:2002, Geographic information ― Temporal schema ISO 19109:―1), Geographic information ― Rules for application schema ISO 19110:―1), Geographic information ― Methodology for feature cataloguing ISO 19111:2003, Geographic information ― Spatial referencing by coordinates ISO 19112:―1), Geographic information ― Spatial referencing by geographic identifiers ISO 19113:2002, Geographic information ― Quality principles ISO 19114:―1), Geographic information ― Quality evaluation procedures ISO 19117:―1), Geographic information ― Portrayal ISO 19118:―1), Geographic information ― Encoding 1) To be published. ISO 19115:2003(E) © ISO 2003 — All rights reserved 3 4 Terms and definitions For the purposes of this document, the following terms and definitions apply. NOTE The terms and definitions used in conjunction with the UML models are addressed in Clause 5. 4.1 data type specification of a value domain with operations allowed on values in this domain [ISO 19103] EXAMPLE Integer, Real, Boolean, String, Date, and GM_Point. NOTE A data type is identified by a term, e.g. Integer. 4.2 dataset identifiable collection of data 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. 4.3 dataset series collection of datasets sharing the same product specification 4.4 grid network composed of two or more sets of curves in which the member of each set intersect the members of the other sets in an algorithmic way [ISO 19123] 4.5 metadata data about data 4.6 metadata element discrete unit of metadata NOTE 1 Metadata elements are unique within a metadata entity. NOTE 2 Equivalent to an attribute in UML terminology. 4.7 metadata entity set of metadata elements describing the same aspect of data NOTE 1 May contain one or more metadata entities. NOTE 2 Equivalent to a class in UML terminology. 4.8 metadata section subset of metadata which consists of a collection of related metadata entities and metadata elements NOTE Equivalent to a package in UML terminology. 4.9 model abstraction of some aspects of a universe of discourse [ISO 19109] ISO 19115:2003(E) 4 © ISO 2003 — All rights reserved 4.10 resource asset or means that fulfils a requirement EXAMPLE Dataset, service, document, person or organization. 4.11 temporal reference system reference system against which time is measured [ISO 19108] 5 Symbols and abbreviated terms 5.1 Abbreviations DTD Document Type Definition IDL Interface Definition Language OCL Object Constraint Language SGML Standard Generalized Markup Language UML Unified Modelling Language XML Extensible Markup Language 5.2 UML notations The diagrams that appear in this International Standard are presented using the Unified Modelling Language (UML) static structure diagram with the ISO Interface Definition Language (IDL) basic type definitions and the UML Object Constraint Language (OCL) as the conceptual schema language. The UML notations used in this International Standard are described in the Figure 1. Association Aggregation Composition Generalization Dependency Figure 1 — UML notation ISO 19115:2003(E) © ISO 2003 — All rights reserved 5 5.3 UML model relationships 5.3.1 Associations An association is used to describe a relationship between two or more classes. UML defines three different types of relationships, called association, aggregation and composition. The three types have different semantics. An ordinary association shall be used to represent a general relationship between two classes. The aggregation and composition associations shall be used to create part-whole relationships between two classes. The direction of an association must be specified. If the direction is not specified, it is assumed to be a two-way association. If one-way associations are intended, the direction of the association can be marked by an arrow at the end of the line. An aggregation association is a relationship between two classes in which one of the classes plays the role of container and the other plays the role of a containee. A composition association is a strong aggregation. In a composition association, if a container object is deleted, then all of its containee objects are deleted as well. The composition association shall be used when the objects representing the parts of a container object cannot exist without the container object. 5.3.2 Generalization A generalization is a relationship between a superclass and the subclasses that may be substituted for it. The superclass is the generalized class, while the subclasses are specified classes. 5.3.3 Instantiation/Dependency A dependency relationship shows that the client class depends on the supplier class/interface to provide certain services, such as:  Client class accesses a value (constant or variable) defined in the supplier class/interface;  Operations of the client class invoke operations of the supplier class/interface;  Operations of the client class have signatures whose return class or arguments are instances of the supplier class/interface. An instantiated relationship represents the act of substituting actual values for the parameters of a parameterized class or parameterized class utility to create a specialized version of the more general item. 5.3.4 Roles If an association is navigable in a particular direction, the model shall supply 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. ISO 19115:2003(E) 6 © ISO 2003 — All rights reserved Association name n ……...... ……....... Association between classes Association cardinality Exactly one Zero or more Optional (zero or one) Aggregation between classes One or more Specific number role-1 role-2 0..* 0..1 1..* Class Inheritance (subtyping of classes) Class #1 Class #2 Class Class Class Class Class Aggregate class Superclass Component class #1 Component class #2 Component class #n Subclass #1 Subclass #2 Subclass #n 1 Figure 2 — UML roles 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 in some respect behave 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 stereotypes are used: a) <> class used for specification of a domain of instances (objects), together with the operations applicable to the objects. A type may have attributes and associations. b) <> data type whose instances form a list of named literal values. Both the enumeration name and its literal values are declared. Enumeration means a short list of well-understood potential values within a class. c) <> a descriptor of a set of values that lack identity and whose operations do not have side effects. Datatypes include primitive pre-defined types and user-definable types. Pre-defined types include numbers, string, and time. User-definable types include enumerations. d) <> used to describe a more open enumeration. <> is a flexible enumeration. Code lists are useful for expressing a long list of potential values. If the elements of the list are completely known, an enumeration should be used; if the only likely values of the elements are known, a code list should be used. ISO 19115:2003(E) © ISO 2003 — All rights reserved 7 e) <> describes a selection of one of the specified types. This is useful to specify a set of alternative classes/types that can be used, without the need to create a common super-type/class. f) <> class (or other classifier) that cannot be directly instantiated. UML notation for this to show the name in italics. g) <> class whose instances are classes. Metaclasses are typically used in the construction of metamodels. A metaclass is an object class whose primary purpose is to hold metadata about another class. h) <> named set of operations that characterize the behaviour of an element. i) <> cluster of logically related components, containing sub-packages. j) <> package that contains definitions, without any sub-packages. 5.5 Package abbreviations Two letter abbreviations are used to denote the package that contains a class. Those abbreviations precede class names, connected by a “_”. The standard that those classes are located in is indicated in parentheses. A list of those abbreviations follows. CC Changing Coordinates (ISO 19111) CI Citation (ISO 19115) CV Coverages (ISO 19123) DQ Data quality (ISO 19115) DS Dataset (ISO 19115) EX Extent (ISO 19115) FC Feature Catalogue (ISO 19110) FE Feature (ISO 19109) FT Feature Topology (ISO 19107) GF General Feature (ISO 19109) GM Geometry (ISO 19107) GR Graph (ISO 19107) LI Lineage (ISO 19115) MD Metadata (ISO 19115) PF Feature Portrayal (ISO 19117) PS Positioning Services (ISO 19116) RS Reference System (ISO 19115) SC Spatial Coordinates (ISO 19111) ISO 19115:2003(E) 8 © ISO 2003 — All rights reserved SI Spatial Identification (ISO 19112) SV Services (ISO 19119) TM Temporal (ISO 19108) TP Topology (ISO 19107) TS Simple Topology (ISO 19107) 5.6 UML model/data dictionary relationships Table 1 illustrates the relationship between the terminology of the UML models and the data dictionary. Table 1 — Relationship between UML model and data dictionary UML Model Data Dictionary Package Section Generalized Class Entity Specified Class Entity Class Entity Attribute Element Association Element 6 Requirements 6.1 Metadata for geographic data requirement This International Standard identifies the metadata required to describe digital geographic data. Metadata is applicable to independent datasets, aggregations of datasets, individual geographic features, and the various classes of objects that compose a feature. Metadata shall be provided for geographic datasets and may, optionally, be provided for aggregations of datasets, features, and attributes of features. Metadata is composed of one or more Metadata Sections (UML Packages) containing one or more Metadata Entities (UML classes). 6.2 Metadata application information Figure 3 is a UML class diagram defining the classes of geographic information to which metadata applies. It specifies that a dataset (DS_DataSet) must have one or more related Metadata entity sets (MD_Metadata). Metadata may optionally relate to a Feature, Feature Attribute, Feature Type, Feature Property Type (a Metaclass instantiated by Feature association role, Feature attribute type, and Feature operation), and aggregations of datasets (DS_Aggregate). Dataset aggregations may be specified (subclassed) as a general association (DS_OtherAggregate), a dataset series (DS_Series), or a special activity (DS_Initiative). MD_Metadata also applies to other classes of information and services not shown in this diagram (see MD_ScopeCode, B.5.25). ISO 19115:2003(E) © ISO 2003 — All rights reserved 9 <> GF_FeatureType (from General Feature Model) <> GF_AttributeType +featureType +featureAttribute MD_Metadata (from Metadata entity set information) <> GF_PropertyType (from General Feature Model) 0..* 0..* 0..* 0..* 0..* 0..* 0..* +propertyType 0..* +propertyTypeMetadata +featureTypeMetadata +featureAttributeMetadata +series +partOf <> DS_Aggregate DS_DataSet +describes +seriesMetadata 1..* 0..* +composedOf 1..*0..* 0..*+superset +subset MultipleAggregation DS_OtherAggregate DS_Series DS_Initiative DS_StereoMate DS_Platform DS_Sensor DS_ProductionSeries 1..* +has Figure 3 — Metadata application 6.3 Metadata packages 6.3.1 Metadata package and entity relationship In this International Standard, metadata for geographic data is presented in UML 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 of metadata. Entities may be related to one or more other entities. Entities can be aggregated and repeated as necessary to meet: (1) the mandatory requirements stated in this International Standard; (2) additional user requirements. Figure 4 illustrates the layout of the packages. The metadata is fully specified in the UML model diagrams and data dictionary for each package, which can be found in Annexes A and B respectively. If a discrepancy between the two annexes exists, Annex A shall be considered authoritative. ISO 19115:2003(E) 10 © ISO 2003 — All rights reserved <> Metadata entity set information <> Constraint information <> Spatial representation information <> Application schema information <> Portrayal catalogue information <> Citation and responsible party information <> Content information <> Distribution information <> Maintenance information <> Metadata extension information <> Identification information<> Data quality information <> Reference system information <> Extent information <> Units of Measure (from Derived) Figure 4 — Metadata packages The relationship between packages of metadata and metadata entities is shown in Table 2. The packages of metadata are listed in the Package column and the aggregate entity of metadata contained within the corresponding package is listed in the Entity column. The entities contained within the packages are further defined in 6.3.2 through 6.4.2. Each package has a corresponding subclause, which is listed in the Subclause Number column. ISO 19115:2003(E) © ISO 2003 — All rights reserved 11 Table 2 — Relationship between packages of metadata and metadata entities Subclause Number Package Entity UML Diagram Data Dictionary 6.3.2.1 Metadata entity set information MD_Metadata A.2.1 B.2.1 6.3.2.2 Identification information MD_Identification A.2.2 B.2.2 6.3.2.3 Constraint information MD_Constraints A.2.3 B.2.3 6.3.2.4 Data quality information DQ_DataQuality A.2.4.1 A.2.4.2 A.2.4.3 B.2.4.1 B.2.4.2 B.2.4.3 6.3.2.5 Maintenance information MD_MaintenanceInformation A.2.5 B.2.5 6.3.2.6 Spatial representation information MD_SpatialRepresentation A.2.6 B.2.6 6.3.2.7 Reference system information MD_ReferenceSystem A.2.7 B.2.7 6.3.2.8 Content information MD_ContentInformation A.2.8 B.2.8 6.3.2.9 Portrayal catalogue information MD_PortrayalCatalogueReference A.2.9 B.2.9 6.3.2.10 Distribution information MD_Distribution A.2.10 B.2.10 6.3.2.11 Metadata extension information MD_MetadataExtensionInformation A.2.11 B.2.11 6.3.2.12 Application schema information MD_ApplicationSchemaInformation A.2.12 B.2.12 6.4.1 Extent information EX_Extent A.3.1 B.3.1 6.4.2 Citation and responsible party information CI_Citation CI_ResponsibleParty A.3.2 B.3.2 6.3.2 Package descriptions 6.3.2.1 Metadata entity set information (MD_Metadata) Metadata entity set information consists of the entity (UML class) MD_Metadata, which is mandatory. The MD_Metadata entity contains both mandatory and optional metadata elements (UML attributes). The MD_Metadata entity is an aggregate of the following entities (which are further explained in the following subclauses): • MD_Identification • MD_Constraints • DQ_DataQuality • MD_MaintenanceInformation • MD_SpatialRepresentation • MD_ReferenceSystem • MD_ContentInformation • MD_PortrayalCatalogueReference • MD_Distribution • MD_MetadataExtensionInformation • MD_ApplicationSchemaInformation ISO 19115:2003(E) 12 © ISO 2003 — All rights reserved 6.3.2.2 Identification information (MD_Identification) Identification information contains information to uniquely identify the data. Identification information includes information about the citation for the resource, an abstract, the purpose, credit, the status and points of contact. The MD_Identification entity is mandatory. It contains mandatory, conditional, and optional elements. The MD_Identification entity may be specified (subclassed) as MD_DataIdentification when used to identify data and as MD_ServiceIdentification when used to identify a service. MD_ServiceIdentification provides a high level description of a service, for further information see ISO 19119. MD_Identification is an aggregate of the following entities: • MD_Format, format of the data • MD_BrowseGraphic, graphic overview of the data • MD_Usage, specific uses of the data • MD_Constraints, constraints placed on the resource • MD_Keywords, keywords describing the resource • MD_MaintenanceInformation, how often the data is scheduled to be updated and the scope of the update • MD_AggregateInformation, information about datasets that are aggregate parts of the dataset that the metadata describes The extent element of MD_DataIdentification is conditional; either the EX_GeographicBoundingBox or the EX_GeographicDescription subclass of extent’s geographicElement Role shall be included if the dataset is spatially referenced. If necessary both may be used. The characterSet element of MD_DateIdentification is conditional; it is documented if ISO/IEC 10646-1 is not used. 6.3.2.3 Constraint information (MD_Constraints) This package contains information concerning the restrictions placed on data. The MD_Constraints entity is optional and may be specified as MD_LegalConstraints and/or MD_SecurityConstraints. The otherConstraint element of MD_LegalConstraints shall be non-zero (used) only if accessConstraints and/or useConstraints elements have a value of “otherRestrictions”, which is found in the MD_RestrictionCode codelist. 6.3.2.4 Data quality information (DQ_DataQuality) This package contains a general assessment of the quality of the dataset. The DQ_DataQuality entity is optional and contains the scope of the quality assessment. DQ_DataQuality is an aggregate of LI_Lineage and DQ_Element. DQ_Element can be specified as DQ_Completeness, DQ_LogicalConsistency, DQ_PositionalAccuracy, DQ_ThematicAccuracy and DQ_TemporalAccuracy. Those five entities represent Elements of data quality and can be further subclassed to the sub-Elements of data quality. Users may add additional elements and sub-elements of data quality by sub-classing DQ_Element or the appropriate sub- element. This package also contains information about the sources and production processes used in producing a dataset. The LI_Lineage entity is optional and contains a statement about the lineage. LI_Lineage is an aggregate of LI_ProcessStep and LI_Source. Either the “report” or “lineage” roles of DQ_DataQuality must be present if DQ_DataQuality.scope.DQ_Scope.level has a value of “dataset”. ISO 19115:2003(E) © ISO 2003 — All rights reserved 13 The “levelDescription” element of DQ_Scope is mandatory if the “level” element of DQ_Scope does not have a value of “dataset” or “series”. The “statement” element of LI_Lineage is mandatory if DQ_DataQuality.scope.DQ_Scope.level has a value of “dataset” or “series” and the LI_Lineage roles of “source” and “processStep” are not documented. The “source” role of LI_Lineage is mandatory if the “statement” element and the “processStep” role of LI_Lineage are not documented. The “processStep” role of LI_Lineage is mandatory if the “statement” element and the “source” role of LI_Lineage are not documented. Either the “description” or “sourceExtent” element of LI_Source must be documented. 6.3.2.5 Maintenance information (MD_MaintenanceInformation) This package contains information about the scope and frequency of updating data. The MD_MaintenanceInformation entity is optional and contains mandatory and optional metadata elements. 6.3.2.6 Spatial representation information (MD_SpatialRepresentation) This package contains information concerning the mechanisms used to represent spatial information in a dataset. The MD_SpatialRepresentation entity is optional and can be specified as MD_GridSpatialRepresentation and MD_VectorSpatialRepresentation. Each of the specified entities contains mandatory and optional metadata elements. When further description is necessary, MD_GridSpatialRepresentation may be specified as MD_Georectified and/or MD_Georeferenceable. Metadata for Spatial data representation are derived from ISO 19107. 6.3.2.7 Reference system information (MD_ReferenceSystem) This package contains the description of the spatial and temporal reference system(s) used in a dataset. MD_ReferenceSystem contains an element to identify the reference system used. MD_ReferenceSystem may be subclassed as MD_CRS, which is an aggregate of MD_ProjectionParameters and MD_EllipsoidParameters. MD_ProjectionParameters is an aggregate of MD_ObliqueLineAzimuth and MD_ObliqueLinePoint. 6.3.2.8 Content information (MD_ContentInformation) This package contains information identifying the feature catalogue used (MD_FeatureCatalogueDescription) and/or information describing the content of a coverage dataset (MD_CoverageDescription). Both description entities are subclasses of the MD_ContentInformation entity. MD_CoverageDescription may be subclassed as MD_ImageDescription, and has an aggregate of MD_RangeDimension. MD_RangeDimension may additionally be subclassed as MD_Band. 6.3.2.9 Portrayal catalogue information (MD_PortrayalCatalogueReference) This package contains information identifying the portrayal catalogue used. It consists of the optional entity MD_PortrayalCatalogueReference. This entity contains the mandatory element used to specify which portrayal catalogue is used by the dataset. 6.3.2.10 Distribution information (MD_Distribution) This package contains information about the distributor of, and options for obtaining, a resource. It contains the optional MD_Distribution entity. MD_Distribution is an aggregate of the options for the digital distribution of a dataset (MD_DigitalTransferOptions), identification of the distributor (MD_Distributor) and the format of the distribution (MD_Format), which contains mandatory and optional elements. MD_DigitalTransferOptions contains the medium used for the distribution (MD_Medium) of a dataset, and is an aggregate of ISO 19115:2003(E) 14 © ISO 2003 — All rights reserved MD_Distributor. MD_Distributor’s other aggregate is the process for ordering a distribution (MD_StandardOrderProcess). The “distributionFormat” role of MD_Distribution is mandatory if the “distributorFormat” role of MD_Distributor is not documented. The “distributorFormat” role of MD_Distributor is mandatory if the “distributionFormat” role of MD_Distribution is not documented. 6.3.2.11 Metadata extension information (MD_MetadataExtensionInformation) This package contains information about user specified extensions. It contains the optional MD_MetadataExtensionInformation entity. MD_MetadataExtensionInformation is an aggregate of information describing the extended metadata elements (MD_ExtendedElementInformation). If the “dataType” element of MD_ExtendedElementInformation does not have a value of ‘codelist’, ‘enumeration’ or ‘codelistElement’; then the “obligation”, “maximumOccurence” and “domainValue” elements are mandatory. If the “dataType” element of MD_ExtendedElementInformation has a value of ‘codelistElement’, then the “domainCode” element is mandatory. If the “dataType” element of MD_ExtendedElementInformation does not have a value of ‘codelistElement’, then the “shortName” element is mandatory. If the “obligation” element of MD_ExtendedElementInformation has a value of ‘conditional’, then the “condition” element is mandatory. 6.3.2.12 Application schema information (MD_ApplicationSchemaInformation) This package contains information about the application schema used to build a dataset. It contains the optional entity MD_ApplicationSchemaInformation. The entity contains mandatory and optional elements. 6.4 Metadata datatypes 6.4.1 Extent information (EX_Extent) The datatype in this package is an aggregate of the metadata elements that describe the spatial and temporal extent of the referring entity. The EX_Extent entity contains information about the geographic (EX_GeographicExtent), temporal (EX_TemporalExtent) and the vertical (EX_VerticalExtent) extent of the referring entity. EX_GeographicExtent can be subclassed as EX_BoundingPolygon, EX_GeographicBoundingBox and EX_GeographicDescription. The combined spatial and temporal extent (EX_SpatialTemporalExtent) is an aggregate of EX_GeographicExtent. EX_SpatialTemporalExtent is a subclass of EX_TemporalExtent. The EX_Extent entity has three optional roles named “geographicElement”, “temporalElement”, and “verticalElement” and an element called “description”. At least one of the four shall be used. The entity stereotype “DataType” is defined in 5.4. ISO 19115:2003(E) © ISO 2003 — All rights reserved 15 6.4.2 Citation and responsible party information (CI_Citation and CI_ResponsibleParty) This package of datatypes provides a standardized method (CI_Citation) for citing a resource (dataset, feature, source, publication, etc.), as well as information about the party responsible (CI_ResponsibleParty) for a resource. The CI_ResponsibleParty datatype contains the identity of person(s), and/or position, and/or organization(s) associated with the resource. The location (CI_Address) of the responsible person or organization is also defined here. The entity stereotype “DataType” is defined in 5.4. 6.5 Core metadata for geographic datasets This International Standard defines an extensive set of metadata elements; typically only a subset of the full number of elements is used. However, it is essential that a basic minimum number of metadata elements be maintained for a dataset. Listed are the core metadata elements required to identify a dataset, typically for catalogue purposes. This list contains metadata elements answering the following questions: “Does a dataset on a specific topic exist (‘what’)?”, “For a specific place (‘where’)?”, “For a specific date or period (‘when’)?” and “A point of contact to learn more about or order the dataset (‘who’)?”. Using the recommended optional elements in addition to the mandatory elements will increase interoperability, allowing users to understand without ambiguity the geographic data and the related metadata provided by either the producer or the distributor. Dataset metadata profiles of this International Standard shall include this core. Listed below (see Table 3) are the core metadata elements (mandatory and recommended optional) required for describing a dataset. An “M” indicates that the element is mandatory. An “O” indicates that the element is optional. A “C” indicates that the element is mandatory under certain conditions. ISO 19115:2003(E) 16 © ISO 2003 — All rights reserved Table 3 — Core metadata for geographic datasets Dataset title (M) (MD_Metadata > MD_DataIdentification.citation > CI_Citation.title) Spatial representation type (O) (MD_Metadata > MD_DataIdentification.spatialRepresentationType) Dataset reference date (M) (MD_Metadata > MD_DataIdentification.citation > CI_Citation.date) Reference system (O) (MD_Metadata > MD_ReferenceSystem) Dataset responsible party (O) (MD_Metadata > MD_DataIdentification.pointOfContact > CI_ResponsibleParty) Lineage (O) (MD_Metadata > DQ_DataQuality.lineage > LI_Lineage) Geographic location of the dataset (by four coordinates or by geographic identifier) (C) (MD_Metadata > MD_DataIdentification.extent > EX_Extent > EX_GeographicExtent > EX_GeographicBoundingBox or EX_GeographicDescription) On-line resource (O) (MD_Metadata > MD_Distribution > MD_DigitalTransferOption.onLine > CI_OnlineResource) Dataset language (M) (MD_Metadata > MD_DataIdentification.language) Metadata file identifier (O) (MD_Metadata.fileIdentifier) Dataset character set (C) (MD_Metadata > MD_DataIdentification.characterSet) Metadata standard name (O) (MD_Metadata.metadataStandardName) Dataset topic category (M) (MD_Metadata > MD_DataIdentification.topicCategory) Metadata standard version (O) (MD_Metadata.metadataStandardVersion) Spatial resolution of the dataset (O) (MD_Metadata > MD_DataIdentification.spatialResolution > MD_Resolution.equivalentScale or MD_Resolution.distance) Metadata language (C) (MD_Metadata.language) Abstract describing the dataset (M) (MD_Metadata > MD_DataIdentification.abstract) Metadata character set (C) (MD_Metadata.characterSet) Distribution format (O) (MD_Metadata > MD_Distribution > MD_Format.name and MD_Format.version) Metadata point of contact (M) (MD_Metadata.contact > CI_ResponsibleParty) Additional extent information for the dataset (vertical and temporal) (O) (MD_Metadata > MD_DataIdentification.extent > EX_Extent > EX_TemporalExtent or EX_VerticalExtent) Metadata date stamp (M) (MD_Metadata.dateStamp) 6.6 Unified Modelling Language (UML) diagrams Annex A provides the metadata schemas in the form of Unified Modelling Language (UML) diagrams. These diagrams, in conjunction with the data dictionary presented in Annex B, serve to fully define the total abstract model for metadata. 6.7 Data dictionary Annex B contains the element and entity definitions for the metadata schemas. This dictionary, in conjunction with the diagrams presented in Annex A, serve to fully define the total abstract model for metadata. Codelists and their values provided in this International Standard (B.5 and A.2) are normative. User extensions to codelists shall follow the rules as described in Annex C and ISO/IEC 11179-6. ISO/IEC 11179-6 defines the information to be specified, conditions to be fulfilled and procedure(s) to be followed for registering data elements. ISO 19115:2003(E) © ISO 2003 — All rights reserved 17 6.8 Metadata extensions and profiles Annex C provides the rules for defining and applying additional metadata to better serve special user needs. 6.9 Abstract test suite Annex D defines the tests that must be passed to claim conformance with this International Standard. 6.10 Comprehensive dataset metadata application profile Annex E defines a comprehensive metadata application schema, which provides an implementable metadata profile. It incorporates the mandatory and optional metadata required to document a geographic data resource completely (independent dataset, dataset series, or individual geographic features). This schema fully defines the complete range of metadata required to identify, evaluate, extract, employ, and manage geographic information. Data producers typically provide comprehensive metadata. This schema is provided as a UML model. 6.11 Metadata extension methodology Annex F provides guidance on extending metadata. Additional metadata elements shall be defined according to the rules described in Annex C. 6.12 Metadata implementation Annex G provides an overview of methods and ideas for the implementation and management of metadata for the purposes of search and retrieval, metadata exchange, and presentation. 6.13 Hierarchical levels of metadata Annex H provides methods for efficiently handling metadata for datasets with metadata requirements at different levels. 6.14 Implementation examples Annex I provides an example of the use of this International Standard, utilizing the core components of the comprehensive profile, for a geographic dataset. An example of extended metadata elements, as may be developed by a specific information community, is provided (I.3). 6.15 Multilingual support for free text fields Annex J provides a structure to implement the free text fields of this International Standard in multiple languages. ISO 19115:2003(E) 18 © ISO 2003 — All rights reserved Annex A (normative) Metadata schemas A.1 Metadata UML models Metadata for describing geographic data is defined using an abstract object model in the Unified Modelling Language (UML). The diagrams in the following subclauses provide “views,” which are portions of the total abstract model for metadata. Each diagram defines a metadata section (UML package) of related entities, elements, data types, and code lists. Related entities, which are defined in another diagram, are shown with elements suppressed and the defining package specified under the entity name in parenthesis. Throughout the following models, entities may have mandatory and/or optional elements and associations. In some cases, optional entities may have mandatory elements; those elements become mandatory only if the optional element is used. ISO 19115:2003(E) © ISO 2003 — All rights reserved 19 A.2 Metadata package UML diagrams A.2.1 Metadata entity set information Figure A.1 defines the class “MD_Metadata” and shows containment relationships with the other metadata classes which, in aggregate, define metadata for geographic data. The other metadata class diagrams can be found on the following pages. The data dictionary for this diagram is located in B.2.1. Conditional statements: language: documented if not defined by the encoding standard characterSet: documented if ISO 10646-1 not used and not defined by the encoding standard <> MD_SpatialRepresentation (from Spatial representation information) MD_ApplicationSchemaInformation (from Application schema information) MD_PortrayalCatalogueReference (from Portrayal catalogue information) MD_MetadataExtensionInformation (from Metadata extension information) <> MD_ContentInformation (from Content information) MD_ReferenceSystem (from Reference system information) DQ_DataQuality (from Data quality information) MD_Distribution (from Distribution information) MD_MaintenanceInformation (from Maintenance information) MD_Metadata + fileIdentifier [0..1] : CharacterString + language [0..1] : CharacterString + characterSet [0..1] : MD_CharacterSetCode = "utf8" + parentIdentifier [0..1] : CharacterString + hierarchyLevel [0..*] : MD_ScopeCode = "dataset" + hierarchyLevelName [0..*] : CharacterString + contact [1..*] : CI_ResponsibleParty + dateStamp : Date + metadataStandardName [0..1] : CharacterString + metadataStandardVersion [0..1] : CharacterString + dataSetURI [0..1] : CharacterString +spatialRepresentationInfo +applicationSchemaInfo +portrayalCatalogueInfo +metadataMaintenance +metadataExtensionInfo +contentInfo +referenceSystemInfo +dataQualityInfo +distributionInfo MD_Constraints (from Constraint information) +metadataConstraints <> MD_Identification (from Identification information) +resourceMaintenance +identificationInfo +resourceConstraints 0..* 0..* 0..* 0..1 0..* 0..* 0..1 0..* 1..* 0..* 0..* 0..* 0..* hierarchyLevel: documented if hierarchyLevel not = "dataset" hierarchyLevelName: documented if hierarchyLevel not = "dataset" Figure A.1 — Metadata entity set information A.2.2 Identification information Figure A.2 defines the metadata classes required to identify a resource. It also defines separate specialization sub-classes for identifying data and services. The data dictionary for this diagram is located in B.2.2. ISO 19115:2003(E) 20 © ISO 2003 — All rights reserved MD_Usage + specificUsage : CharacterString + usageDateTime [0..1] : DateTime + userDeterminedLimitations [0..1] : CharacterString + userContactInfo [1..*] : CI_ResponsibleParty MD_Metadata (from Metadata entity set information) MD_Constraints (from Constraint information) MD_BrowseGraphic + fileName : CharacterString + fileDescription [0..1] : CharacterString + fileType [0..1] : CharacterString <> MD_Identification + citation : CI_Citation + abstract : CharacterString + purpose [0..1] : CharacterString + credit [0..*] : CharacterString + status [0..*] : MD_ProgressCode + poinOfContact [0..*] : CI_ResponsibleParty MD_Format (from Distribution information) <> MD_KeywordTypeCode + dicipline + place + stratum + temporal + theme {MD_Metadata.hierarchyLevel = "dataset" implies count (extent.geographicElement.EX_GeographicBoundingBox) + count (extent.geographicElement.EX_GeographicDescription) >=1} MD_DataIdentification + spatialRepresentationType [0..*] : MD_SpatialRepresentationTypeCode + spatialResolution [0..*] : MD_Resolution + language [1..*] : CharacterString + characterSet [0..*] : MD_CharacterSetCode = "utf8" + topicCategory [0..*] : MD_TopicCategoryCode + environmentDescription [0..1] : CharacterString + extent [0..*] : EX_Extent + supplementalInformation [0..1] : CharacterString <> MD_Resolution + equivalentScale : MD_RepresentativeFraction + distance : Distance <> MD_InitiativeTypeCode + campaign + collection + exercise + experiment + investigation + mission + sensor + operation + platform + process + program + project + study + task + trial <> DS_AssociationTypeCode + crossReference + largerWorkCitation + partOfSeamlessDatabase + source + stereoMate <> MD_TopicCategoryCode + farming + biota + boundaries + climatologyMeteorologyAtmosphere + economy + elevation + environment + geoscientificInformation + health + imageryBaseMapsEarthCover + intelligenceMilitary + inlandWaters + location + oceans + planningCadastre + society + structure + transportation + utilitiesCommunication <> MD_SpatialRepresentationTypeCode + vector + grid + textTable + tin + stereoModel + video <> MD_CharacterSetCode + ucs2 + ucs4 + utf7 + utf8 + utf16 + 8859part1 + 8859part2 + 8859part3 + 8859part4 + 8859part5 + 8859part6 + 8859part7 + 8859part8 + 8859part9 + 8859part10 + 8859part11 + (reserved for future use) + 8859part13 + 8859part14 + 8859part15 + 8859part16 + jis + shiftJIS + eucJP + usAscii + ebcdic + eucKR + big5 + GB2312 Either "aggregateDataSetName" or "aggregateDataSetIdentifier" must be documented <> MD_AggregateInformation + aggregateDataSetName [0..1] : CI_Citation + aggregateDataSetIdentifier [0..1] : MD_Identifier + associationType : DS_AssociationTypeCode + initiativeType [0..1] : DS_InitiativeTypeCode MD_Keywords + keyword [1..*] : CharacterString + type [0..1] : MD_KeywordTypeCode + thesaurusName [0..1] : CI_Citation MD_MaintenanceInformation (from Maintenance information) MD_ServiceIdentification <> MD_ProgressCode + completed + historicalArchive + obsolete + onGoing + planned + required + underDevelopment <> MD_RepresentativeFraction + denominator : Integer +resourceSpecificUsage 0..* +identificationInfo 1..* +graphicOverview 0..* 0..* +resourceFormat 0..* 0..* 0..* 0..* +resourceMaintenance aggregationInfo +descriptiveKeywords +resourceConstraints characterSet: documented if ISO 10646-1 is not used {MD_Metadata.hierarchyLevel notEqual "dataset" implies topicCategory is not mandatory} Figure A.2 — Identification information ISO 19115:2003(E) © ISO 2003 — All rights reserved 21 A.2.3 Constraint information Figure A.3 defines the metadata required for managing rights to information including restrictions on access and use. The data dictionary for this diagram is located in B.2.3. <> MD_Identification (from Identification information) MD_Metadata (from Metadata entity set information) MD_Constraints +resourceConstraints 0..* + useLimitation [0..*] : CharacterString + unclassified + restricted + confidential + secret + topSecret <> MD_ClassificationCode +metadataConstraints 0..* MD_LegalConstraints + accessConstraints [0..*] : MD_RestrictionCode + useConstraints [0..*] : MD_RestrictionCode + otherConstraints [0..*] : CharacterString MD_SecurityConstraints + classification : MD_ClassificationCode + userNote [0..1] : CharacterString + classificationSystem [0..1] : CharacterString + handlingDescription [0..1] : CharacterString + copyright + patent + patentPending + trademark + license + intellectualPropertyRights + restricted + otherRestrictions <> MD_RestrictionCode otherConstraints: documented if accessConstraints or useConstraints = "otherRestrictions" Figure A.3 — Constraint information ISO 19115:2003(E) 22 © ISO 2003 — All rights reserved A.2.4 Data quality information A.2.4.1 General Figure A.4 defines the metadata required to give a general assessment of the quality of a resource. The data dictionary for this diagram is located in B.2.4. MD_Metadata (from Metadata entity set information) DQ_DataQuality +dataQualityInfo 0..* + scope : DQ_Scope + directInternal + directExternal + indirect <> MD_EvaluationMethodTypeCode +report 0..* <> DQ_Element + nameOfMeasure [0..*] : CharacterString + measureIdentification [0..1] : MD_Identifier + measureDescription [0..1] : CharacterString + evaluationMethodType [0..1] : DQ_EvaluationMethodTypeCode + evaluationMethodDescription [0..1] : CharacterString + evaluationProcedure [0..1] : CI_Citation + dateTime [0..*] : DateTime + result [1..2] : DQ_Result DQ_QuantitativeResult + valueType [0..1] : RecordType + valueUnit : UnitOfMeasure + errorStatistic [0..1] : CharacterString + value [1..*] : Record "report" or "linage" role is mandatory if scope.DQ_Scope.level = 'dataset' LI_Linage +linage0..1 + level : MD_ScopeCode + extent [0..1] : EX_Extent + levelDescription [0..*] : MD_ScopeDescription <> DQ_Scope DQ_ConformanceResult + specification : CI_Citation + explanation : CharacterString + pass : Boolean <> DQ_Result "levelDescription" is mandatoryif "level" notEqual 'dataset' or 'series' Figure A.4 — Data quality information ISO 19115:2003(E) © ISO 2003 — All rights reserved 23 A.2.4.2 Lineage information Figure A.5 defines metadata required to describe the sources and production processes used in producing a dataset. The data dictionary for this diagram is located in B.2.4.2. LI_Lineage +linage 0..1 + statement [0..1] : CharacterString +source 0..* LI_Source + description [0..1] : CharacterString + scaleDenominator [0..1] : MD_RepresentativeFraction + sourceReferenceSystem [0..1] : MD_ReferenceSystem + sourceCitation [0..1] : CI_Citation + sourceExtent [0..*] : EX_Extent LI_ProcessStep + description : CharacterString + rationale [0..1] : CharacterString + dateTime [0..1] : DateTime + processor [0..*] : CI_ResponsibleParty DQ_DataQuality + scope : DQ_Scope If(count(source) + count(processStep) =0) and (DQ_DataQuality.cope.level = 'dataset' or 'series') then statement is mandatory "source" role is mandatory if LI_Lineage.statement and "processStep" role are not documented "processStep" role is mandatory if LI_Lineage.statement and "source" role are not documented "description" is mandatory if "soruceExtent" is not documented "sourceExtent" is mandatory if "description" is not documented +source 0..* 0..* +sourceStep 0..* +processStep Figure A.5 — Lineage information ISO 19115:2003(E) 24 © ISO 2003 — All rights reserved A.2.4.3 Data quality classes and subclasses Figure A.6 defines the classes and subclasses of data quality used in the data quality diagram. The data dictionary for this diagram is located in B.2.4.3. +lineage 0..1 0..* DQ_DataQuality + scope : DQ_Scope +report LI_Lineage <> DQ_Element <> DQ_Completeness <> DQ_LogicalConsistency <> DQ_PositionalAccuracy DQ_CompletenessCommission DQ_CompletenessOmission DQ_AbsoluteExternalPositionalAccuracyDQ_ConceptualConsistency DQ_DomainConsistency DQ_FormatConsistency DQ_TopologicalConsistency DQ_GriddedDataPositionalAccuracy DQ_RelativeInternalPositionalAccuracy <> DQ_ThematicAccuracy <> DQ_TemporalAccuracy DQ_ThematicClassificationCorrectness DQ_NonQuantitativeAttributeAccuracy DQ_QuantitativeAttributeAccuracy DQ_TemporalValidity DQ_TemporalConsistency DQ_AccuracyOfATimeMeasurement Figure A.6 — Data quality classes and subclasses ISO 19115:2003(E) © ISO 2003 — All rights reserved 25 A.2.5 Maintenance information Figure A.7 defines the metadata required to describe the maintenance and update practices for information. The data dictionary for this diagram is located in B.2.5. MD_Metadata (from Metadata entity set information) MD_MaintenanceInformation + maintenanceAndUpdateFrequency : MD_MaintenanceFrequencyCode + dateOfNextUpdate [0..1] : Date + userDefinedMaintenanceFrequency [0..1] : TM_PeriodDuration + updateScope [0..*] : MD_ScopeCode + updateScopeDescription [0..*] : MD_ScopeDescription + maintenanceNote [0..*] : CharacterString + contact [0..*] : CI_ResponsibleParty +metadataMaintenance 0..1 + attribute + attributeType + collectionHardware + collectionSession + dataset + series + nonGeographicDataset + dimensionGroup + feature + featureType + propertyType + fieldSession + software + service + model + tile <> MD_ScopeCode + attributes : Set + features : Set + featureInstances : Set + attributeInstances : Set + dataset : CharacterString + other : CharacterString <> MD_ScopeDescription + continual + daily + weekly + forthnightly + monthly + quarterly + biannually + annually + asNeeded + irregular + notPlanned + unknown <> MD_MaintenanceFrequencyCode Figure A.7 — Maintenance information ISO 19115:2003(E) 26 © ISO 2003 — All rights reserved A.2.6 Spatial representation information Figure A.8 defines metadata required to describe the mechanism used to represent spatial information. The data dictionary for this diagram is located in B.2.6. MD_Metadata (from Metadata entity set information) MD_GridSpatialRepresentation +spatialRepresentationInfo 0..* <> MD_SpatialRepresentation + numberOfDimensions : Integer + axisDimensionProperties : Sequence + cellGeometry : MD_CellGeometryCode + transformationParameterAvailability : Boolean MD_VectorSpatialRepresentation + topologyLevel [0..1] : MD_TopologyLevelCode + geometricObjects [0..*] : MD_GeometricObjects MD_Georeferenceable + controlPointAvailability: Boolean + orientationParameterAvailability : Boolean + orientationParameterDescription [0..1] : CharacterString + georeferencedParameters : Record + parameterCitation [0..*] : CI_Citation MD_Georectified + checkPointAvailability: Boolean + checkPointDescription [0..1] : CharacterString + cornerPoints : Sequence + centerPoint [0..1] : GM_Point + pointInPixel : MD_PixelOrientationCode + transformationDimensionDescription [0..1] : CharacterString + transformationDimensionMapping [0..2] : CharacterString "checkPointDescription" is mandatory if "checkPointAvaliability" = 1 <> MD_Dimension + dimensionName : MD_DimensionNameTypeCode + dimensionSize : Integer + resolution [0..1] : Measure <> MD_GeometricObjectTypeCode + complex + composite + curve + point + solid + surface <> MD_DimensionTypeCode + row + column + vertical + track + crossTrack + line + sample + time <> MD_GeometricObjects + geometricObjectType : MD_GeometricObjectTypeCode + geometricObjectCount [0..1] : Integer <> MD_CellGeometryCode + point + area <> MD_TopologyLevelCode + geometryOnly + topology1D + planarGraph + fullPlanarGraph + surfaceGraph + fullSurfaceGraph + topology3D + fullTopology3D + abstract <> MD_PixelOrientationCode + center + lowerLeft + lowerRight + upperRight + upperLeft Figure A.8 — Spatial representation information ISO 19115:2003(E) © ISO 2003 — All rights reserved 27 A.2.7 Reference system information Figure A.9 defines metadata required to describe the spatial and temporal reference system used. The data dictionary for this diagram is located in B.2.7. MD_Metadata (from Metadata entity set information) MD_ReferenceSystem +referenceSystemInfo 0..* + referenceSystemIdentifier [0..1] : RS:Identifier RS_Identifier + codeSpace [0..1] : CharacterString + version [0..1] : CharacterString "referenceSystemIdentifier" is mandatory if MD_CRS.projection, MD_CRS.ellipsoid and MD_CRS.datum are not documented <> MD_Identifier + authority [0..1] : CI_Citation + code : CharacterString MD_CRS + projection [0..1] : RS_Identifier + ellipsoid [0..1] : RS_Identifier + datum [0..1] : RS_Identifier <> RS_ReferenceSystem + name : RS_Identifier + domainOfValidity [0..*] : EX_Extent MD_EllipsoidParameters + semiMajorAxis : Real + axisUnits : UomLength + denominatorOfFlatteningRatio [0..1] : Real "denominatorOfFlatteningRatio" is mandatory if not a spheroid MD_ObliqueLineAzimuth + azimuthAngle : Real + azimuthMeasurePointLongitude : Real MD_ObliqueLinePoint + azimuthLineLatitude : Real + azimuthLIneLongitude : Real MD_ProjectionParameters + zone [0..1] : Integer + standardParallel [0..2] : Real + longitudeOfCentralMeridian [0..1] : Real + latitudeOfProjectionOrigin [0..1] : Real + falseEasting [0..1] : Real + falseNorthing [0..1] : Real + falseEastingNorthingUnits [0..1] : UomLength + scaleFactorAtEquator [0..1] : Real + heightOfProspectivePointAboveSurface [0..1] : Real + longitudeOfProjectionCenter [0..1] : Real + latitudeOfProjectionCenter [0..1] : Real + scaleFactorAtCenterLine [0..1] : Real + straightVerticalLongitudeFromPole [0..1] : Real + scaleFactorAtProjectionOrigin [0..1] : Real +obliqueLinePointParameter 0,2 +obliqueLineAzimuthParameter 0..1 0..1 +projectionParameters 0..1 +ellipsoidParameters Figure A.9 — Reference system information ISO 19115:2003(E) 28 © ISO 2003 — All rights reserved A.2.8 Content information Figure A.10 defines metadata about the content of a coverage and the feature catalogue(s) used to define features. The data dictionary for this diagram is located in B.2.8. MD_Metadata (from Metadata entity set information) MD_CoverageDescription +contentInfo 0..* <> MD_ContentInformation + attributeDescription : RecordType + contentType : MD_CoverageContentTypeCode MD_FeatureCatalogueDescription + complianceCode [0..1] : Boolean + language [0..*] : CharacterString + includeWithDataset : Boolean + featureTypes [0..*] : GenericName + featureCatalogueCitation [1..*] : CI_Citation MD_ImageDescription + illuminationElevationAngel [0..1] : Real + illuminationAzimuthAngel [0..1] : Real + imagingCondition [0..1] : MD_ImagingConditionCode + imageQualityCode [0..1] : MD_Identifier + cloudCoverPercentage [0..1] : Real + processingLevelCode [0..1] : MD_Identifer + compressionGenerationQuantity [0..1] : Integer + triangulationIndicator [0..1] : Boolean + radiometricCalibrationDataAvailability [0..1] : Boolean + cameraCalibrationInformationAvailability [0..1] : Boolean + filmDistortionInformationAvailability [0..1] : Boolean + lensDistortionInformationAvailability [0..1] : Boolean "units" is mandatory if "maxValue" or "minValue" are provided <> MD_CoverageContentTypeCode + image + thematicClassification + physicalMeasurement MD_RangeDimension + sequenceIdentifier [0..1] : MemberName + descriptor [0..1] : CharacterString <> MD_ImagingConditionCode + blurredImage + cloud + degradingObliquity + fog + heavySmokeOrDust + night + rain + seminDarkness + shadow + snow + terrainMasking MD_Band + maxValue [0..1] : Real + minValue [0..1] : Real + units [0..1] : UomLength + peakResponse [0..1] : Real + bitsPerValue [0..1] : Integer + toneGradation [0..1] : Integer + scaleFactor [0..1] : Real + offset [0..1] : Real +dimension 0..* Figure A.10 — Content information ISO 19115:2003(E) © ISO 2003 — All rights reserved 29 A.2.9 Portrayal catalogue information Figure A.11 defines metadata about the portrayal catalogue(s) used to display data. The data dictionary for this diagram is located in B.2.9. MD_Metadata (from Metadata entity set information) MD_PortrayalCatalogueReference + portrayalCatalogueCitation [1..*] : CI_Citation 0..*+portrayalCatalogueInfo Figure A.11 — Portrayal catalogue information ISO 19115:2003(E) 30 © ISO 2003 — All rights reserved A.2.10 Distribution information Figure A.12 defines metadata required for accessing a resource. The data dictionary for this diagram is located in B.2.10. MD_Metadata (from Metadata entity set information) MD_DigitalTransferOptions +distributionInfo 0..1 MD_Distribution + unitsOfDistribution [0..1] : CharacterString + transferSize [0..1] : Real + onLine [0..*] : CI_OnlineResource + offLine [0..1] : MD_Medium MD_Format + name : CharacterString + version : CharacterString + amendmentNumber [0..1] : CharacterString + specification [0..1] : CharacterString + fileDecompressionTechnique [0..1] : CharacterString "densityUnits" is mandatory if "density" is provided <> MD_Medium +transferOptions 0..* count (distributionFormat + distributorFormat) > 0 +distributionFormat 0..* <> MD_MediumFormatCode + cpio + tar + highSierra + iso9660 + iso9660RockRidge + iso9660AppleHFS <> MD_MediumNameCode + cdRom + dvd + dvdRom + 3halfInchFloppy + 5quarterInchFloppy + 7trackTape + 9trackTape + 3480Cartridge + 3490Cartridge + 3580Cartridge + 4mmCartridgeTape + 8mmCartridgeTape + 1quarterInchCartridgeTape + digitalLinearTape + onLine + satellite + telephoneLink + hardcopy MD_Distributor + distributorContact : CI_ResponsibleParty + name [0..1] : MD_MediumNameCode + density [0..*] : Real + densityUnits [0..1] : CharacterString + volumes [0..1] : Integer + mediumFormat [0..*] : MD_MediumFormatCode + mediumName [0..1] : CharacterString MD_StandardOrderProcess + fees [0..1] : CharacterString + plannedAvailableDateTime [0..1] : DateTime + orderingInstructions [0..1] : CharacterString + turnaround [0..1] : CharacterString +distributorFormat 0..* 0..* +FormatDistributor +distributor 0..* +distributorTransferOptions 0..* +distributionOrderProcess 0..* Figure A.12 — Distribution information ISO 19115:2003(E) © ISO 2003 — All rights reserved 31 A.2.11 Metadata extension information Figure A.13 defines the extended metadata elements. The data dictionary for this diagram is located in B.2.11. MD_Metadata (from Metadata entity set information) MD_ExtendedElementInformation + name : CharacterString + shortName [0..1] : CharacterString + domainCode [0..1] : Integer + definition : CharacterString + obligation [0..1] : MD_ObligationCode + condition [0..1] : CharacterString + dataType : MD_DatatypeCode + maximumOccurence [0..1] : CharacterString + domainValue [0..1] : CharacterString + parentEntity [1..*] : CharacterString + rule : CharacterString + rationale [0..*] : CharacterString + source [1..*] : CI_ResponsibleParty if "dataType" = 'codelistElement' then "domainCode" is mandatory 0..* +metadataExtentionInfo0..* <> MD_ObligationCode + mandatory + optional + conditional <> MD_DatatypeCode + class + codelist + enumeration + codelistElement + abstractClass + aggregateClass + specifiedClass + datatypeClass + interfaceClass + unionClass + metaClass + typeClass + characterString + integer + association MD_MetadataExtensionInformation + extensionOnLineResource [0..1] : CI_OnlineResource +extendedElementInformation if "dataType" notEqual 'codelistElement' then "shortName" is mandatory if "dataType" notEqual 'codelist', 'enumeration' or 'codelistElement' then "obligation", "maximumOccurence" and "domainValue" are mandatory if "obligation" = 'conditional' then "condition" is mandatory Figure A.13 — Metadata extension information ISO 19115:2003(E) 32 © ISO 2003 — All rights reserved A.2.12 Application schema information Figure A.14 defines the application schema used. The data dictionary for this diagram is located in B.2.12. MD_Metadata (from Metadata entity set information) +applicationSchemaInfo 0..* MD_ApplicationSchemaInformation + name : CI_Citation + schemaLanguage : CharacterString + constraintLanguage : CharacterString + schemaAscii [0..1] : CharacterString + graphicsFile [0..1] : Binary + softwareDevelopmentFile [0..1] : Binary + softwareDevelopmentFileFormat [0..1] : CharacterString Figure A.14 — Application schema information ISO 19115:2003(E) © ISO 2003 — All rights reserved 33 A.3 Metadata data types A.3.1 Extent information Figure A.15 defines metadata describing the spatial and temporal extent covered by a resource. The data dictionary for this diagram is located in B.3.1. SC_VerticalDatum (from Spatial Referencing by Coordinates) EX_GeographicBoundingBox EX_SpatialTemporalExtent+ westBoundLongitude : Angle + eastBoundLongitude : Angle + southBoundLatitude : Angle + northBoundLatitude : Angle <> EX_GeographicExtent +temporalElement 0..* EX_TemporalExtent + extent : TM_Primitive + extentTypeCode [0..1] : Boolean = "1" EX_VerticalExtent + minimumValue : Real + maximumValue : Real + unitOfMeasure : UomLength 0..* <> EX_Extent + description [0..1] : CharacterString count(description + geographicElement + temporalElement + verticalElement) > 0 +geographicElement +spatialExtent 1..* 1 +verticalDatum EX_GeographicDescription + geographicIdentifier : MD_Identifier EX_BoundingPolygon + polygon [1..*] : GM_Object +verticalElement 0..* Figure A.15 — Extent information ISO 19115:2003(E) 34 © ISO 2003 — All rights reserved A.3.2 Citation and responsible party information Figure A.16 defines metadata describing authoritative reference information, including responsible party and contact information. The data dictionary for this diagram is located in B.3.2. <> CI_PresentationFormCode + documentDigital + documentHardcopy + imageDigital + imageHardcopy + mapDigial + mapHardcopy + modelDigital + modelHardcopy + profileDigital + profileHardcopy + tableDigital + tableHardcopy + videoDigital + videoHardcopy <> CI_Citation + title : CharacterString + alternateTitle [0..*] : CharacterString + date [1..*] : CI_Date + edition [0..1] : CharacterString + editionDate [0..1] : Date + identifier [0..*] : MD_Identifier + citedResponsibleParty [0..*] : CI_ResponsibleParty + presentationForm [0..*] : CI_PresentationFormCode + series [0..1] : CI_Series + otherCitationDetails [0..1] : CharacterString + collectiveTitle [0..1] : CharacterString + ISBN [0..1] : CharacterString + ISSN [0..1] : CharacterString <> CI_ResponsibleParty + individualName [0..1] : CharacterString + organisationName [0..1] : CharacterString + positionName [0..1] : CharacterString + contactInfo [0..1] : CI_Contact + role : CI_RoleCode count of (individualName + organisationName + positionName) > 0 <> CI_Contact + phone [0..1] : CI_Telephone + address [0..1] : Address + onlineResource [0..1] : CI_OnlineResource + hoursOfService [0..1] : CharacterString + contactInstructions [0..1] : CharacterString <> CI_OnlineResource + linkage : URL + protocol [0..1] : CharacterString + applicationProfile [0..1] : CharacterString + name [0..1] : CharacterString + description [0..1] : CharacterString + function [0..1] : CI_OnLineFunctionCode <> CI_Address + deliveryPoint [0..*] : CharacterString + city [0..1] : CharacterString + adminitrativeArea [0..1] : CharacterString + postalCode [0..1] : CharacterString + country [0..1] : CharacterString + electronicMailAddress [0..*] : CharacterString <> CI_RoleCode + resourceProvider + custodian + owner + user + distributor + originator + pointOfContact + principalInvestigator + processor + publisher + author <> CI_Telephone + voice [0..*] : CharacterString + facsimile [0..*] : CharacterString <> CI_OnLineFunctionCode + download + information + offlineAccess + order + search <> CI_DateTypeCode + creation + publication + revision <> CI_Date + date : Date + dateType : CI_DateTypeCode URL <> CI_Series + name [0..1] : CharacterString + issueIdentification [0..1] : CharacterString + page [0..1] : CharacterString Figure A.16 — Citation and responsible party information ISO 19115:2003(E) © ISO 2003 — All rights reserved 35 Annex B (normative) Data dictionary for geographic metadata B.1 Data dictionary overview B.1.1 Introduction This data dictionary describes the characteristics of the metadata defined in Clause 6 and Annex A. The dictionary is specified in a hierarchy to establish relationships and an organization for the information. The dictionary is categorised into sections by UML model package diagram: Metadata Entity Set, Identification, Resource Constraints, Data Quality, Maintenance, Spatial Representation, Reference System, Content, Portrayal Catalogue, Distribution, Metadata Extension, Application Schema, Extent, Citation and Responsible Party and Metadata Application. The clause titles of several of the tables have been expanded to reflect class specification within the respective diagram. Each model diagram from Annex A has a section within the data dictionary. Each UML model class equates to a data dictionary entity. Each UML model class attribute equates to a data dictionary element. The shaded rows define entities. The entities and elements within the data dictionary are defined by seven attributes (those attributes are listed below and are based on those specified in ISO/IEC 11179-3 for the description of data element concepts, i.e. data elements without representation). The term “dataset” when used as part of a definition is synonymous with all types of geographic data resources (aggregations of datasets, individual features and the various classes that compose a feature). B.1.2 Name/role name A label assigned to a metadata entity or to a metadata element. Metadata entity names start with an upper case letter. Spaces do not appear in a metadata entity name. Instead, multiple words are concatenated, with each new subword starting with a capital letter (example: XnnnYmmm). Metadata entity names are unique within the entire data dictionary of this International Standard. Metadata element names are unique within a metadata entity, not the entire data dictionary of this International Standard. Metadata element names are made unique, within an application, by the combination of the metadata entity and metadata element names (example: MD_Metadata.characterSet). Role names are used to identify metadata abstract model associations and are preceded by “Role name:” to distinguish them from other metadata elements. Names and role names may be in a language other than that used in this International Standard. B.1.3 Short name and domain code Those classes that are not CodeList or Enumeration stereotypes are provided with a Short Name for each element. These short names are unique within this International Standard and may be used with the Extensible MarkUp Language (XML) and ISO 8879 (SGML) or other similar implementation techniques. A naming convention similar to that used to create the longer entity and element names was used to create the short names. NOTE Implementation using SGML and XML is not mandatory; other implementation methods may be accommodated. For CodeList and Enumeration stereotypes, a code is provided for each possible selection. These domain codes are numerical, unique within the codelist and 3 digits long. Row one of each CodeList and Enumeration contains an alphabetic short name, described above, as row one is the name of the CodeList or Enumeration. B.1.4 Definition The metadata entity/element description. ISO 19115:2003(E) 36 © ISO 2003 — All rights reserved B.1.5 Obligation/Condition B.1.5.1 General This is a descriptor indicating whether a metadata entity or metadata element shall always be documented in the metadata or sometimes be documented (i.e. contains value(s)). This descriptor may have the following values: M (mandatory), C (conditional), or O (optional). B.1.5.2 Mandatory (M): The metadata entity or metadata element shall be documented. B.1.5.3 Conditional (C): Specifies an electronically manageable condition under which at least one metadata entity or a metadata element is mandatory. ‘Conditional’ is used for one of the three following possibilities:  Expressing a choice between two or more options. At least one option is mandatory and must be documented.  Documenting a metadata entity or a metadata element if another element has been documented.  Documenting a metadata element if a specific value for another metadata element has been documented. To facilitate reading by humans, the specific value is used in plain text (ex. table in Clause B.2, row 3 "C/not defined by encoding?”). However, the code shall be used to verify the condition in an electronical user interface. If the answer to the condition is positive, then the metadata entity or the metadata element shall be mandatory. B.1.5.4 Optional (O): The metadata entity or the metadata element may be documented or may not be documented. Optional metadata entities and optional metadata elements have been defined to provide a guide to those looking to fully document their data. (Use of this common set of defined elements will help promote interoperability among geographic data users and producers world-wide.) If an optional entity is not used, the elements contained within that entity (including mandatory elements) will also not be used. Optional entities may have mandatory elements; those elements only become mandatory if the optional entity is used. B.1.6 Maximum occurrence Specifies the maximum number of instances the metadata entity or the metadata element may have. Single occurrences are shown by “1”; repeating occurrences are represented by “N”. Fixed number occurrences other than one are allowed, and will be represented by the corresponding number (i.e. “2”, “3”…etc). B.1.7 Data type Specifies a set of distinct values for representing the metadata elements; for example, integer, real, string, DateTime, and Boolean. The data type attribute is also used to define metadata entities, stereotypes, and metadata associations. NOTE Data types are defined in ISO/TS 19103, 6.5.2. B.1.8 Domain For an entity, the domain indicates the line numbers covered by that entity. ISO 19115:2003(E) © ISO 2003 — All rights reserved 37 For a metadata element, the domain specifies the values allowed or the use of free text. “Free text” indicates that no restrictions are placed on the content of the field. Integer-based codes shall be used to represent values for domains containing codelists. ISO 19115:2003(E) 38 B.2Metadatapackagedatadictionaries B.2.1Metadataentitysetinformation •UMLmodelshowninFigureA.1. Name/RolenameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 1MD_MetadataMetadatarootentitywhichdefinesmetadata aboutaresourceorresources M1ClassLines2-22 2fileIdentifiermdFileIDuniqueidentifierforthismetadata file O1CharacterStringFreetext 3languagemdLanglanguageusedfordocumenting metadata C/notdefinedby encoding? 1CharacterStringISO639-2,otherpartsmaybe used 4characterSetmdCharfullnameofthecharactercoding standardusedforthemetadataset C/ISO/IEC10646-1 notusedandnot definedbyencoding? 1ClassMD_CharacterSetCode <>(B.5.10) 5parentIdentifiermdParentIDfileidentifierofthemetadatato whichthismetadataisasubset (child) C/hierarchyLevelis notequalto "dataset"? 1CharacterStringFreetext 6hierarchyLevelmdHrLvscopetowhichthemetadata applies(seeAnnexHformore informationaboutmetadata hierarchylevels) C/hierarchyLevelis notequalto "dataset"? NClassMD_ScopeCode <>(B.5.25) 7hierarchyLevelNamemdHrLvNamenameofthehierarchylevelsfor whichthemetadataisprovided C/hierarchyLevelis notequalto "dataset"? NCharacterStringFreetext 8contactmdContactpartyresponsibleforthemetadata information MNClassCI_ResponsibleParty(B.3.2) <> 9dateStampmdDateStdatethatthemetadatawas created M1ClassDate(B.4.2) 10metadataStandardNamemdStanNamenameofthemetadatastandard (includingprofilename)used O1CharacterStringFreetext 11metadataStandardVersionmdStanVerversion(profile)ofthemetadata standardused O1CharacterStringFreetext © ISO 2003 — All rights reserved Name/RolenameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 11.1dataSetURIdataSetURIUniformedResourceIdentifier (URI)ofthedatasettowhichthe metadataapplies O1CharacterStringFreetext 12Rolename: spatialRepresentationInfo spatRepInfodigitalrepresentationofspatial informationinthedataset ONAssociationMD_SpatialRepresentation <>(B.2.6) 13Rolename: referenceSystemInfo refSysInfodescriptionofthespatialand temporalreferencesystemsused inthedataset ONAssociationMD_ReferenceSystem(B.2.7) 14Rolename: metadataExtensionInfo mdExtInfoinformationdescribingmetadata extensions ONAssociationMD_MetadataExtension Information(B.2.11) 15Rolename: identificationInfo dataIdInfobasicinformationaboutthe resource(s)towhichthemetadata applies MNAssociationMD_Identification <>(B.2.2) 16Rolename: contentInfo contInfoprovidesinformationaboutthe featurecatalogueanddescribes thecoverageandimagedata characteristics ONAssociationMD_ContentInformation <>(B.2.8) 17Rolename: distributionInfo distInfoprovidesinformationaboutthe distributorofandoptionsfor obtainingtheresource(s) O1AssociationMD_Distribution(B.2.10) 18Rolename: dataQualityInfo dqInfoprovidesoverallassessmentof qualityofaresource(s) ONAssociationDQ_DataQuality(B.2.4) 19Rolename: portrayalCatalogueInfo porCatInfoprovidesinformationaboutthe catalogueofrulesdefinedforthe portrayalofaresource(s) ONAssociationMD_PortrayalCatalogue Reference(B.2.9) 20Rolename: metadataConstraints mdConstprovidesrestrictionsontheaccess anduseofmetadata ONAssociationMD_Constraints(B.2.3) 21Rolename: applicationSchemaInfo appSchInfoprovidesinformationaboutthe conceptualschemaofadataset ONAssociationMD_ApplicationSchema Information(B.2.12) 22Rolename: metadataMaintenance mdMaintprovidesinformationaboutthe frequencyofmetadataupdates, andthescopeofthoseupdates O1AssociationMD_MaintenanceInformation (B.2.5) ISO 19115:2003(E) © ISO 2003 — All rights reserved 39 B.2.2Identificationinformation(includesdataandserviceidentification) B.2.2.1General •UMLmodelshowninFigureA.2 Name/RolenameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 23.MD_IdentificationIdentbasicinformationrequiredto uniquelyidentifyaresourceor resources Useobligationfrom referencingobject Use maximum occurrence from referencing object AggregatedClass (MD_Metadata) <> Lines24-35.1 24.citationidCitationcitationdatafortheresource(s)M1ClassCI_Citation(B.3.2) <> 25.abstractidAbsbriefnarrativesummaryofthe contentoftheresource(s) M1CharacterStringFreetext 26.purposeidPurpsummaryoftheintentionswith whichtheresource(s)was developed O1CharacterStringFreetext 27.creditidCreditrecognitionofthosewho contributedtotheresource(s) ONCharacterStringFreetext 28.statusidStatusstatusoftheresource(s)ONClassMD_ProgressCode <>(B.5.23) 29.pointOfContactidPoCidentificationof,andmeansof communicationwith,person(s)and organization(s)associatedwiththe resource(s) ONClassCI_ResponsibleParty(B.3.2) <> 30.Rolename: resourceMaintenance resMaintprovidesinformationaboutthe frequencyofresourceupdates, andthescopeofthoseupdates ONAssociationMD_MaintenanceInformation (B.2.5) 31.Rolename: graphicOverview graphOverprovidesagraphicthatillustrates theresource(s)(shouldincludea legendforthegraphic) ONAssociationMD_BrowseGraphic(B.2.2.2) 32.Rolename: resourceFormat dsFormatprovidesadescriptionofthe formatoftheresource(s) ONAssociationMD_Format(B.2.10.4) ISO 19115:2003(E) 40 © ISO 2003 — All rights reserved Name/RolenameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 33.Rolename: descriptiveKeywords descKeysprovidescategorykeywords,their type,andreferencesource ONAssociationMD_Keywords(B.2.2.3) 34.Rolename: resourceSpecificUsage idSpecUseprovidesbasicinformationabout specificapplication(s)forwhichthe resource(s)has/havebeenoris beingusedbydifferentusers ONAssociationMD_Usage(B.2.2.6) 35.Rolename: resourceConstraints resConstprovidesinformationabout constraintswhichapplytothe resource(s) ONAssociationMD_Constraints(B.2.3) 35.1Rolename: aggregationInfo aggrInfoprovidesaggregatedataset information ONAssociationMD_AggregateInformation (B.2.2.7) 36.MD_DataIdentificationDataIdentinformationrequiredtoidentifya dataset Useobligationfrom referencingobject Use maximum occurrence from referencing object SpecifiedClass (MD_Identification) Lines37-46and24-35.1 37.spatialRepresentationTypespatRpTypemethodusedtospatiallyrepresent geographicinformation ONClassMD_SpatialRepresentation TypeCode <>(B.5.26) 38.spatialResolutiondataScalefactorwhichprovidesageneral understandingofthedensityof spatialdatainthedataset ONClassMD_Resolution <>(B.2.2.5) 39.languagedataLanglanguage(s)usedwithinthe dataset MNCharacterStringISO639-2,otherpartsmaybe used 40.characterSetdataCharfullnameofthecharactercoding standardusedforthedataset C/ISO/IEC10646-1 notused? NClassMD_CharacterSetCode <>(B.5.10) 41.topicCategorytpCatmaintheme(s)ofthedatasetC/ifhierarchyLevel equals“dataset”? NClassMD_TopicCategoryCode <>(B.5.27) 42.intentionallyleftblank 43.intentionallyleftblank ISO 19115:2003(E) © ISO 2003 — All rights reserved 41 Name/RolenameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 44.environmentDescriptionenvirDescdescriptionofthedatasetinthe producer’sprocessing environment,includingitemssuch asthesoftware,thecomputer operatingsystem,filename,and thedatasetsize O1CharacterStringFreetext 45.extentdataExtextentinformationincludingthe boundingbox,boundingpolygon, vertical,andtemporalextentofthe dataset C/ifhierarchyLevel equals“dataset”? either extent.geographic Element.EX_ GeographicBounding Boxor extent.geographic Element.EX_ Geographic Descriptionis required NClassEX_Extent <>(B.3.1) 46.supplementalInformationsuppInfoanyotherdescriptiveinformation aboutthedataset O1CharacterStringFreetext 47.MD_ServiceIdentificationSerIdentidentificationofcapabilitieswhicha serviceprovidermakesavailable toaserviceuserthroughasetof interfacesthatdefineabehaviour- SeeISO19119forfurther information Useobligationfrom referencingobject Use maximum occurrence from referencing object SpecifiedClass (MD_Identification) Lines24-35.1 B.2.2.2Browsegraphicinformation Name/RolenameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 48.MD_BrowseGraphicBrowGraphgraphicthatprovidesanillustration ofthedataset(shouldincludea legendforthegraphic) Useobligationfrom referencingobject Use maximum occurrence from referencing object AggregatedClass (MD_Identification) Lines49-51 ISO 19115:2003(E) 42 © ISO 2003 — All rights reserved Name/RolenameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 49.fileNamebgFileNamenameofthefilethatcontainsa graphicthatprovidesanillustration ofthedataset M1CharacterStringFreetext 50.fileDescriptionbgFileDesctextdescriptionoftheillustrationO1CharacterStringFreetext 51.fileTypebgFileTypeformatinwhichtheillustrationis encodedExamples:CGM,EPS, GIF,JPEG,PBM,PS,TIFF,XWD O1CharacterStringFreetext B.2.2.3Keywordinformation Name/RolenameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 52.MD_KeywordsKeywordskeywords,theirtypeandreference source Useobligationfrom referencingobject Use maximum occurrence from referencing object AggregatedClass (MD_Identification) Lines53-55 53.keywordkeywordcommonlyusedword(s)or formalisedword(s)orphrase(s) usedtodescribethesubject MNCharacterStringFreetext 54.TypekeyTypsubjectmatterusedtogroup similarkeywords O1ClassMD_KeywordTypeCode <>(B.5.17) 55.ThesaurusNamethesaNamenameoftheformallyregistered thesaurusorasimilarauthoritative sourceofkeywords O1ClassCI_Citation(B.3.2) <> ISO 19115:2003(E) © ISO 2003 — All rights reserved 43 B.2.2.4Representativefractioninformation Name/RolenameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 56.MD_RepresentativeFractionRepFractderivedfromISO19103Scale whereMD_Representative Fraction.denominator=1/Scale. measureAndScale.targetUnits= Scale.sourceUnits Useobligationfrom referencingobject Use maximum occurrence from referencing object Class <> Line57 57.denominatorrfDenomthenumberbelowthelineina vulgarfraction M1IntegerInteger>0 58.intentionallyleftblank B.2.2.5Resolutioninformation Name/RolenameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 59.MD_ResolutionResollevelofdetailexpressedasascale factororagrounddistance Useobligationfrom referencingobject Use maximum occurrence from referencing object Class <> Lines60-61 60.equivalentScaleequScalelevelofdetailexpressedasthe scaleofacomparablehardcopy maporchart C/distancenot documented? 1ClassMD_RepresentativeFraction <>(B.2.2.4) 61.distancescaleDistgroundsampledistanceC/equivalentScale notdocumented? 1ClassDistance(B.4.3) ISO 19115:2003(E) 44 © ISO 2003 — All rights reserved B.2.2.6Usageinformation Name/RolenameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 62.MD_UsageUsagebriefdescriptionofwaysinwhich theresource(s)is/arecurrentlyor hasbeenused Useobligationfrom referencingobject Use maximum occurrence from referencing object AggregatedClass (MD_Identification) Lines63-66 63.specificUsagespecUsagebriefdescriptionoftheresource and/orresourceseriesusage M1CharacterStringFreetext 64.usageDateTimeusageDatedateandtimeofthefirstuseor rangeofusesoftheresource and/orresourceseries O1ClassDateTime(B.4.2) 65.userDeterminedLimitationsusrDetLimapplications,determinedbythe userforwhichtheresourceand/or resourceseriesisnotsuitable O1CharacterStringFreetext 66.userContactInfousrCntInfoidentificationofandmeansof communicatingwithperson(s)and organization(s)usingthe resource(s) MNClassCI_ResponsibleParty <>(B.3.2) B.2.2.7Aggregationinformation Name/RolenameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 66.1MD_AggregateInformationAggregateInfoaggregatedatasetinformationUseobligationfrom referencingobject Use maximum occurrence from referencing object AggregatedClass (MD_Identification) Lines66.2-66.5 66.2aggregateDataSetNameaggrDSNamecitationinformationaboutthe aggregatedataset C/if aggregateDataSet Identifiernot documented? 1ClassCI_Citation(B.3.2) <> ISO 19115:2003(E) © ISO 2003 — All rights reserved 45 Name/RolenameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 66.3aggregateDataSetIdentifieraggrDSIdentidentificationinformationabout aggregatedataset C/if aggregateDataSet Namenot documented? 1ClassMD_Identifier(B.2.7.3) <> 66.4associationTypeassocTypeassociationtypeoftheaggregate dataset M1ClassDS_AssociationTypeCode (B.5.7) <> 66.5initiativeTypeinitTypetypeofinitiativeunderwhichthe aggregatedatasetwasproduced O1ClassDS_InitiativeTypeCode (B.5.8) <> B.2.3Constraintinformation(includeslegalandsecurity) •UMLmodelshowninFigureA.3 Name/RolenameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 67.MD_ConstraintsConstsrestrictionsontheaccessanduse ofaresourceormetadata Useobligationfrom referencingobject Use maximum occurrence from referencing object AggregatedClass (MD_Metadataand MD_Identification) Line68 68.useLimitationuseLimitlimitationaffectingthefitnessfor useoftheresourceormetadata. Example,“nottobeusedfor navigation” ONCharacterStringFreetext 69.MD_LegalConstraintsLegConstsrestrictionsandlegalprerequisites foraccessingandusingthe resourceormetadata Useobligationfrom referencingobject NSpecifiedClass (MD_Constraints) Lines70-72and68 70.accessConstraintsaccessConstsaccessconstraintsappliedto assuretheprotectionofprivacyor intellectualproperty,andany specialrestrictionsorlimitationson obtainingtheresourceormetadata ONClassMD_RestrictionCode <>(B.5.24) ISO 19115:2003(E) 46 © ISO 2003 — All rights reserved Name/RolenameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 71.useConstraintsuseConstsconstraintsappliedtoassurethe protectionofprivacyorintellectual property,andanyspecial restrictionsorlimitationsor warningsonusingtheresourceor metadata ONClassMD_RestrictionCode <>(B.5.24) 72.otherConstraintsothConstsotherrestrictionsandlegal prerequisitesforaccessingand usingtheresourceormetadata C/accessConstraints oruseConstraints equal “otherRestrictions”? NCharacterStringFreetext 73.MD_SecurityConstraintsSecConstshandlingrestrictionsimposedon theresourceormetadatafor nationalsecurityorsimilarsecurity concerns Useobligationfrom referencingobject Use maximum occurrence from referencing object SpecifiedClass (MD_Constraints) Lines74-77and68 74.classificationclassnameofthehandlingrestrictions ontheresourceormetadata M1ClassMD_ClassificationCode <>(B.5.11) 75.userNoteuserNoteexplanationoftheapplicationof thelegalconstraintsorother restrictionsandlegalprerequisites forobtainingandusingthe resourceormetadata O1CharacterStringFreetext 76.classificationSystemclassSysnameoftheclassificationsystemO1CharacterStringFreetext 77.handlingDescriptionhandDescadditionalinformationaboutthe restrictionsonhandlingthe resourceormetadata O1CharacterStringFreetext ISO 19115:2003(E) © ISO 2003 — All rights reserved 47 B.2.4Dataqualityinformation B.2.4.1General •UMLmodelshowninFiguresA.4,A.5(Lineage)andA.6(Dataqualityclassesandsubclasses) Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 78.DQ_DataQualityDataQualqualityinformationforthedata specifiedbyadataqualityscope Useobligationfrom referencingobject Use maximum occurrence from referencing object AggregatedClass (MD_Metadata) Lines79-81 79.scopedqScopethespecificdatatowhichthedata qualityinformationapplies M1ClassDQ_Scope <>(B.2.4.5) 80.Rolename: report dqReportquantitativequalityinformationfor thedataspecifiedbythescope C/ lineagenotprovided? NAssociationDQ_Element <>(B.2.4.3) 81.Rolename: lineage dataLineagenon-quantitativequalityinformation aboutthelineageofthedata specifiedbythescope C/ reportnotprovided? 1AssociationLI_Lineage(B.2.4.2) B.2.4.2Lineageinformation B.2.4.2.1General Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 82.LI_LineageLineageinformationabouttheeventsor sourcedatausedinconstructing thedataspecifiedbythescopeor lackofknowledgeaboutlineage Useobligationfrom referencingobject Use maximum occurrence from referencing object AggregatedClass (DQ_DataQuality) Lines83-85 ISO 19115:2003(E) 48 © ISO 2003 — All rights reserved Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 83.statementstatementgeneralexplanationofthedata producer’sknowledgeaboutthe lineageofadataset C/ (DQ_DataQuality.sco pe.DQ_Scope.level= “dataset”or“series”)? 1CharacterStringFreetext 84.Rolename: processStep prcStepinformationabouteventsinthelife ofadatasetspecifiedbythescope C/ mandatoryif statementandsource notprovided? NAssociationLI_ProcessStep(B.2.4.2.2) 85.Rolename: source dataSourceinformationaboutthesourcedata usedincreatingthedataspecified bythescope C/ mandatoryif statementand processStepnot provided? NAssociationLI_Source(B.2.4.2.3) B.2.4.2.2Processstepinformation Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 86.LI_ProcessStepPrcessStepinformationaboutaneventor transformationinthelifeofa datasetincludingtheprocessused tomaintainthedataset Useobligationfrom referencingobject Use maximum occurrence from referencing object AggregatedClass (LI_Lineageand LI_Source) Lines87-91 87.descriptionstepDescdescriptionoftheevent,including relatedparametersortolerances M1CharacterStringFreeText 88.rationalestepRatrequirementorpurposeforthe processstep O1CharacterStringFreeText 89.dateTimestepDateTmdateandtimeorrangeofdateand timeonoroverwhichtheprocess stepoccurred O1ClassDateTime(B.4.2) 90.processorstepProcidentificationof,andmeansof communicationwith,person(s)and organization(s)associatedwiththe processstep ONClassCI_ResponsibleParty <>(B.3.2) ISO 19115:2003(E) © ISO 2003 — All rights reserved 49 91.Rolename: source stepSrcinformationaboutthesourcedata usedincreatingthedataspecified bythescope ONAssociationLI_Source(B.2.4.2.3) B.2.4.2.3Sourceinformation Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 92.LI_SourceSourceinformationaboutthesourcedata usedincreatingthedataspecified bythescope Useobligationfrom referencingobject Use maximum occurrence from referencing object AggregatedClass (LI_Lineageand LI_ProcessStep) Lines93-98 93.descriptionsrcDescdetaileddescriptionofthelevelof thesourcedata C/ sourceExtentnot provided? 1CharacterStringFreeText 94.scaleDenominatorsrcScaledenominatoroftherepresentative fractiononasourcemap O1ClassMD_RepresentativeFraction <>(B.2.2.4) 95.sourceReferenceSystemsrcRefSysspatialreferencesystemusedby thesourcedata O1ClassMD_ReferenceSystem(B.2.7) 96.sourceCitationsrcCitatnrecommendedreferencetobe usedforthesourcedata O1ClassCI_Citation <>(B.3.2) 97.sourceExtentsrcExtinformationaboutthespatial, verticalandtemporalextentofthe sourcedata C/ descriptionnot provided? NClassEX_Extent <>(B.3.1) 98.Rolename: sourceStep srcStepinformationaboutaneventinthe creationprocessforthesource data ONAssociationLI_ProcessStep(B.2.4.2.2) ISO 19115:2003(E) 50 © ISO 2003 — All rights reserved B.2.4.3Dataqualityelementinformation Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 99.DQ_ElementDQElementaspectofquantitativequality information Useobligationfrom referencingobject Use maximum occurrence from referencing object AggregatedClass (DQ_DataQuality) <> Lines100-107 100.nameOfMeasuremeasNamenameofthetestappliedtothe data ONCharacterStringFreetext 101.measureIdentificationmeasIdcodeidentifyingaregistered standardprocedure O1ClassMD_Identifier <>(B.2.7.3) 102.measureDescriptionmeasDescdescriptionofthemeasureO1CharacterStringFreetext 103.evaluationMethodTypeevalMethTypetypeofmethodusedtoevaluate qualityofthedataset O1ClassDQ_EvaluationMethodType Code <>(B.5.6) 104.evaluationMethodDescriptionevalMethDescdescriptionoftheevaluation method O1CharacterStringFreetext 105.evaluationProcedureevalProcreferencetotheprocedure information O1ClassCI_Citation <>(B.3.2) 106.dateTimemeasDateTmdateorrangeofdatesonwhicha dataqualitymeasurewasapplied ONClassDateTime(B.4.2) 107.resultmeasResultvalue(orsetofvalues)obtained fromapplyingadataquality measureortheoutcomeof evaluatingtheobtainedvalue(or setofvalues)againstaspecified acceptableconformancequality level M2ClassDQ_Result <>(B.2.4.4) 108.DQ_CompletenessDQCompletepresenceandabsenceoffeatures, theirattributesandtheir relationships Useobligationfrom referencingobject Use maximum occurrence from referencing object SpecifiedClass (DQ_Element) <> Lines100-107 ISO 19115:2003(E) © ISO 2003 — All rights reserved 51 Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 109.DQ_Completeness Commission DQCompCommexcessdatapresentinthedataset, asdescribedbythescope Useobligationfrom referencingobject Use maximum occurrence from referencing object SpecifiedClass (DQ_Completeness) Lines100-107 110.DQ_CompletenessOmissionDQCompOmdataabsentfromthedataset,as describedbythescope Useobligationfrom referencingobject Use maximum occurrence from referencing object SpecifiedClass (DQ_Completeness) Lines100-107 111.DQ_LogicalConsistencyDQLogConsisdegreeofadherencetological rulesofdatastructure,attribution andrelationships(datastructure canbeconceptual,logicalor physical) Useobligationfrom referencingobject Use maximum occurrence from referencing object SpecifiedClass (DQ_Element) <> Lines100-107 112.DQ_ConceptualConsistencyDQConcConsisadherencetorulesofthe conceptualschema Useobligationfrom referencingobject Use maximum occurrence from referencing object SpecifiedClass (DQ_Logical Consistency) Lines100-107 113.DQ_DomainConsistencyDQDomConsisadherenceofvaluestothevalue domains Useobligationfrom referencingobject Use maximum occurrence from referencing object SpecifiedClass (DQ_Logical Consistency) Lines100-107 114.DQ_FormatConsistencyDQFormConsisdegreetowhichdataisstoredin accordancewiththephysical structureofthedataset,as describedbythescope Useobligationfrom referencingobject Use maximum occurrence from referencing object SpecifiedClass (DQ_Logical Consistency) Lines100-107 ISO 19115:2003(E) 52 © ISO 2003 — All rights reserved Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 115.DQ_TopologicalConsistencyDQTopConsiscorrectnessoftheexplicitly encodedtopologicalcharacteristics ofthedatasetasdescribedbythe scope Useobligationfrom referencingobject Use maximum occurrence from referencing object SpecifiedClass (DQ_Logical Consistency) Lines100-107 116.DQ_PositionalAccuracyDQPosAccaccuracyofthepositionoffeaturesUseobligationfrom referencingobject Use maximum occurrence from referencing object SpecifiedClass (DQ_Element) <> Lines100-107 117.DQ_AbsoluteExternal PositionalAccuracy DQAbsExtPosAc c closenessofreportedcoordinate valuestovaluesacceptedasor beingtrue Useobligationfrom referencingobject Use maximum occurrence from referencing object SpecifiedClass (DQ_Positional Accuracy) Lines100-107 118.DQ_GriddedDataPositional Accuracy DQGridDataPos Acc closenessofgriddeddataposition valuestovaluesacceptedasor beingtrue Useobligationfrom referencingobject Use maximum occurrence from referencing object SpecifiedClass (DQ_Positional Accuracy) Lines100-107 119.DQ_RelativeInternalPositional Accuracy DQRelIntPosAccclosenessoftherelativepositions offeaturesinthescopetotheir respectiverelativepositions acceptedasorbeingtrue Useobligationfrom referencingobject Use maximum occurrence from referencing object SpecifiedClass (DQ_Positional Accuracy) Lines100-107 120.DQ_TemporalAccuracyDQTempAccaccuracyofthetemporalattributes andtemporalrelationshipsof features Useobligationfrom referencingobject Use maximum occurrence from referencing object SpecifiedClass (DQ_Element) <> Lines100-107 ISO 19115:2003(E) © ISO 2003 — All rights reserved 53 Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 121.DQ_AccuracyOfATime Measurement DQAccTime Meas correctnessofthetemporal referencesofanitem(reportingof errorintimemeasurement) Useobligationfrom referencingobject Use maximum occurrence from referencing object SpecifiedClass (DQ_Temporal Accuracy) Lines100-107 122.DQ_TemporalConsistencyDQTempConsiscorrectnessoforderedeventsor sequences,ifreported Useobligationfrom referencingobject Use maximum occurrence from referencing object SpecifiedClass (DQ_Temporal Accuracy) Lines100-107 123.DQ_TemporalValidityDQTempValidvalidityofdataspecifiedbythe scopewithrespecttotime Useobligationfrom referencingobject Use maximum occurrence from referencing object SpecifiedClass (DQ_Temporal Accuracy) Lines100-107 124.DQ_ThematicAccuracyDQThemAccaccuracyofquantitativeattributes andthecorrectnessofnon- quantitativeattributesandofthe classificationsoffeaturesandtheir relationships Useobligationfrom referencingobject Use maximum occurrence from referencing object SpecifiedClass (DQ_Element) <> Lines100-107 125.DQ_ThematicClassification Correctness DQThemClass Cor comparisonoftheclasses assignedtofeaturesortheir attributestoauniverseof discourse Useobligationfrom referencingobject Use maximum occurrence from referencing object SpecifiedClass (DQ_Thematic Accuracy) Lines100-107 126.DQ_NonQuantitativeAttribute Accuracy DQNonQuanAtt Acc accuracyofnon-quantitative attributes Useobligationfrom referencingobject Use maximum occurrence from referencing object SpecifiedClass (DQ_Thematic Accuracy) Lines100-107 ISO 19115:2003(E) 54 © ISO 2003 — All rights reserved Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 127.DQ_QuantitativeAttribute Accuracy DQQuanAttAccaccuracyofquantitativeattributesUseobligationfrom referencingobject Use maximum occurrence from referencing object SpecifiedClass (DQ_Thematic Accuracy) Lines100-107 B.2.4.4Resultinformation Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 128.DQ_ResultResultgeneralizationofmorespecific resultclasses Useobligationfrom referencingobject Use maximum occurrence from referencing object Class <> 129.DQ_ConformanceResultConResultInformationabouttheoutcomeof evaluatingtheobtainedvalue(or setofvalues)againstaspecified acceptableconformancequality level Useobligationfrom referencingobject Use maximum occurrence from referencing object SpecifiedClass (DQ_Result) Lines130-132 130.specificationconSpeccitationofproductspecificationor userrequirementagainstwhich dataisbeingevaluated M1ClassCI_Citation <>(B.3.2) 131.explanationconExplexplanationofthemeaningof conformanceforthisresult M1CharacterStringFreetext 132.passconPassindicationoftheconformance resultwhere0=failand1=pass M1Boolean1=yes 0=no 133.DQ_QuantitativeResultQuanResultthevaluesorinformationaboutthe value(s)(orsetofvalues)obtained fromapplyingadataquality measure Useobligationfrom referencingobject Use maximum occurrence from referencing object SpecifiedClass (DQ_Result) Lines134-137 ISO 19115:2003(E) © ISO 2003 — All rights reserved 55 Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 134.valueTypequanValTypevaluetypeforreportingadata qualityresult O1ClassRecordType <>(B.4.3) 135.valueUnitquanValUnitvalueunitforreportingadata qualityresult M1ClassUnitOfMeasure(B.4.3) 136.errorStatisticerrStatstatisticalmethodusedto determinethevalue O1CharacterStringFreetext 137.valuequanValquantitativevalueorvalues, contentdeterminedbythe evaluationprocedureused MNClassRecord(B.4.3) B.2.4.5Scopeinformation Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 138.DQ_ScopeDQScopeextentofcharacteristic(s)ofthe dataforwhichqualityinformation isreported Useobligationfrom referencingobject Use maximum occurrence from referencing object Class <> Lines139-141 139.levelscpLvlhierarchicallevelofthedata specifiedbythescope M1ClassMD_ScopeCode <>(B.5.25) 140.extentscpExtinformationaboutthehorizontal, verticalandtemporalextentofthe dataspecifiedbythescope O1ClassEX_Extent <>(B.3.1) 141.levelDescriptionscpLvlDescdetaileddescriptionaboutthelevel ofthedataspecifiedbythescope C/ levelnotequal “dataset”or“series”? NClassMD_ScopeDescription <>(B.2.5.2) ISO 19115:2003(E) 56 © ISO 2003 — All rights reserved B.2.5Maintenanceinformation B.2.5.1General •UMLmodelshowninFigureA.7 Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 142.MD_MaintenanceInformationMaintInfoinformationaboutthescopeand frequencyofupdating Useobligationfrom referencingobject Use maximum occurrence from referencing object AggregatedClass (MD_Metadataand MD_Identification) Lines143-148.1 143.maintenanceAndUpdate Frequency maintFreqfrequencywithwhichchangesand additionsaremadetotheresource aftertheinitialresourceis completed M1ClassMD_MaintenanceFrequency Code <>(B.5.18) 144.dateOfNextUpdatedateNextscheduledrevisiondatefor resource O1ClassDate(B.4.2) 145.userDefinedMaintenance Frequency usrDefFreqmaintenanceperiodotherthan thosedefined O1ClassTM_PeriodDuration(B.4.5) 146.updateScopemaintScpscopeofdatatowhich maintenanceisapplied ONClassMD_ScopeCode <>(B.5.25) 147.updateScopeDescriptionupScpDescadditionalinformationaboutthe rangeorextentoftheresource ONClassMD_ScopeDescription <>(B.2.5.2) 148.maintenanceNotemaintNoteinformationregardingspecific requirementsformaintainingthe resource ONCharacterStringFreetext 148.1contactmaintContidentificationof,andmeansof communicatingwith,person(s)and organization(s)withresponsibility formaintainingthemetadata ONClassCI_ResponsibleParty <>(B.3.2) ISO 19115:2003(E) © ISO 2003 — All rights reserved 57 B.2.5.2Scopedescriptioninformation Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 149.MD_ScopeDescriptionScpDescdescriptionoftheclassof informationcoveredbythe information Useobligationfrom referencingobject Use maximum occurrence from referencing object Class <> Lines150-155 150.attributesattribSetattributestowhichtheinformation applies C/features, featureInstances, attributeInstances, datasetandothernot documented? 1Set (B.4.7) GF_AttributeType(B.4.4) 151.featuresfeatSetfeaturestowhichtheinformation applies C/attributes, featureInstances, attributeInstances, datasetandothernot documented? 1Set (B.4.7) GF_FeatureType(B.4.4) 152.featureInstancesfeatIntSetfeatureinstancestowhichthe informationapplies C/attributes, features, attributeInstances, datasetandothernot documented? 1Set (B.4.7) GF_FeatureType(B.4.4) 153.attributeInstancesattribIntSetattributeinstancestowhichthe informationapplies C/attributes, features, featureInstances, datasetandothernot documented? 1Set (B.4.7) GF_AttributeType(B.4.4) 154.datasetdatasetSetdatasettowhichtheinformation applies C/attributes, features, featureInstances, attributeInstances, andothernot documented? 1CharacterStringFreetext ISO 19115:2003(E) 58 © ISO 2003 — All rights reserved Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 155.otherotherclassofinformationthatdoesnot fallintotheothercategoriesto whichtheinformationapplies C/attributes, features, featureInstances, attributeInstances, anddatasetnot documented? 1CharacterStringFreetext B.2.6Spatialrepresentationinformation(includesgridandvectorrepresentation) B.2.6.1General •UMLmodelshowninFigureA.8 Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 156.MD_SpatialRepresentationSpatRepdigitalmechanismusedto representspatialinformation Use obligation/condition fromreferencing object Use maximum occurrence from referencing object AggregatedClass (MD_Metadata) <> 157.MD_GridSpatial Representation GridSpatRepinformationaboutgridspatial objectsinthedataset Use obligation/condition fromreferencing object Use maximum occurrence from referencing object SpecifiedClass (MD_Spatial Representation) Lines158-161 158.numberOfDimensionsnumDimsnumberofindependentspatial- temporalaxes M1IntegerInteger 159.axisDimensionsPropertiesaxDimPropsinformationaboutspatial-temporal axisproperties M1Sequence(B.4.7)MD_Dimension <>(B.2.6.2) 160.cellGeometrycellGeoidentificationofgriddataaspoint orcell M1ClassMD_CellGeometryCode <>(B.5.9) ISO 19115:2003(E) © ISO 2003 — All rights reserved 59 Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 161.transformationParameter Availability tranParaAvindicationofwhetherornot parametersfortransformation betweenimagecoordinatesand geographicormapcoordinates exist(areavailable) M1Boolean1=yes0=no 162.MD_GeorectifiedGeorectgridwhosecellsareregularly spacedinageographic(i.e.,lat/ long)ormapcoordinatesystem definedintheSpatialReferencing System(SRS)sothatanycellin thegridcanbegeolocatedgiven itsgridcoordinateandthegrid origin,cellspacing,andorientation Use obligation/condition fromreferencing object Use maximum occurrence from referencing object Specified (MD_GridSpatial Representation) Lines163-169and158-161 163.checkPointAvailabilitychkPtAvindicationofwhetherornot geographicpositionpointsare availabletotesttheaccuracyof thegeoreferencedgriddata M1Boolean1=yes 0=no 164.checkPointDescriptionchkPtDescdescriptionofgeographicposition pointsusedtotesttheaccuracyof thegeoreferencedgriddata C/ checkPointAvailability equals“yes”? 1CharacterStringFreetext 165.cornerPointscornerPtsearthlocationinthecoordinate systemdefinedbytheSpatial ReferenceSystemandthegrid coordinateofthecellsatopposite endsofgridcoveragealongtwo diagonalsinthegridspatial dimensions.Therearefourcorner pointsinageorectifiedgrid;at leasttwocornerpointsalongone diagonalarerequired M1Sequence (B.4.7) GM_Point <>(B.4.6) 166.centerPointcenterPtearthlocationinthecoordinate systemdefinedbytheSpatial ReferenceSystemandthegrid coordinateofthecellhalfway betweenoppositeendsofthegrid inthespatialdimensions O1ClassGM_Point <>(B.4.6) 167.pointInPixelptInPixelpointinapixelcorrespondingto theEarthlocationofthepixel M1ClassMD_PixelOrientationCode <>(B.5.22) ISO 19115:2003(E) 60 © ISO 2003 — All rights reserved Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 168.transformationDimension Description transDimDescgeneraldescriptionofthe transformation O1CharacterStringFreetext 169.transformationDimension Mapping transDimMapinformationaboutwhichgridaxes arethespatial(map)axes O2CharacterStringFreetext 170.MD_GeoreferenceableGeorefgridwithcellsirregularlyspacedin anygivengeographic/map projectioncoordinatesystem, whoseindividualcellscanbe geolocatedusinggeolocation informationsuppliedwiththedata butcannotbegeolocatedfromthe gridpropertiesalone Use obligation/condition fromreferencing object Use maximum occurrence from referencing object SpecifiedClass (MD_GridSpatial Representation) Lines171-175and158-161 171.controlPointAvailabilityctrlPtAvindicationofwhetherornotcontrol point(s)exists M1Boolean1=yes 0=no 172.orientationParameter Availability orieParaAvindicationofwhetherornot orientationparametersare available M1Boolean1=yes 0=no 173.orientationParameter Description orieParaDsdescriptionofparametersusedto describesensororientation O1CharacterStringFreetext 174.georeferencedParametersgeorefParstermswhichsupportgriddata georeferencing M1ClassRecord(B.4.3) 175.parameterCitationparaCitreferenceprovidingdescriptionof theparameters ONClassCI_Citation <>(B.3.2) 176.MD_VectorSpatial Representation VectSpatRepinformationaboutthevectorspatial objectsinthedataset Use obligation/condition fromreferencing object Use maximum occurrence from referencing object SpecifiedClass (MD_Spatial Representation) Lines177-178 177.topologyLeveltopLvlcodewhichidentifiesthedegreeof complexityofthespatial relationships O1ClassMD_TopologyLevelCode <>(B.5.28) 178.geometricObjectsgeometObjsinformationaboutthegeometric objectsusedinthedataset ONClassMD_GeometricObjects <>(B.2.6.3) ISO 19115:2003(E) © ISO 2003 — All rights reserved 61 B.2.6.2Dimensioninformation Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 179.MD_DimensionDimenaxispropertiesUse obligation/condition fromreferencing object Use maximum occurrence from referencing object Class <> Lines180-182 180.dimensionNamedimNamenameoftheaxisM1ClassMD_DimensionNameType Code <>(B.5.14) 181.dimensionSizedimSizenumberofelementsalongtheaxisM1IntegerInteger 182.resolutiondimResoldegreeofdetailinthegriddatasetO1ClassMeasure(B.4.3) B.2.6.3Geometricobjectinformation Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 183.MD_GeometricObjectsGeometObjsnumberofobjects,listedby geometricobjecttype,usedinthe dataset Use obligation/condition fromreferencing object Use maximum occurrence from referencing object Class <> Lines184-185 184.geometricObjectTypegeoObjTypnameofpointorvectorobjects usedtolocatezero-,one-,two-,or three-dimensionalspatiallocations inthedataset M1ClassMD_GeometricObjectType Code <>(B.5.15) 185.geometricObjectCountgeoObjCnttotalnumberofthepointorvector objecttypeoccurringinthedataset O1Integer>0 ISO 19115:2003(E) 62 © ISO 2003 — All rights reserved B.2.7Referencesysteminformation(includestemporal,coordinateandgeographicidentifiers) B.2.7.1General •UMLmodelshowninFigureA.9 Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 186.MD_ReferenceSystemRefSysteminformationaboutthereference system Use obligation/condition fromreferencing object Use maximum occurrence from referencing object AggregatedClass (MD_Metadata) Line187 187.referenceSystemIdentifierrefSysIdnameofreferencesystemC/ MD_CRS.projection, MD_CRS.ellipsoid, andMD_CRS.datum notdocumented? 1ClassRS_Identifier(B.2.7.3) 188.intentionallyleftblank 189.MD_CRSMdCoRefSysmetadataaboutacoordinate systeminwhichattributeshave beenderivedfromSC_CRSas definedinISO19111–Spatial referencingbycoordinates Use obligation/condition fromreferencing object Use maximum occurrence from referencing object SpecifiedClass (MD_Reference System) Lines190-194and187 190.projectionprojectionidentityoftheprojectionusedO1ClassRS_Identifier(B.2.7.3) 191.ellipsoidellipsoididentityoftheellipsoidusedO1ClassRS_Identifier(B.2.7.3) 192.datumdatumidentityofthedatumusedO1ClassRS_Identifier(B.2.7.3) 193.rolename: ellipsoidParameters ellParassetofparametersthatdescribethe ellipsoid O1AssociationMD_EllipsoidParameters (B.2.7.2) 194.rolename: projectionParameters projParassetofparametersthatdescribethe projection O1AssociationMD_ProjectionParameters (B.2.7.6) ISO 19115:2003(E) © ISO 2003 — All rights reserved 63 Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 195.RS_ReferenceSystemRefSysdescriptionofthespatialand temporalreferencesystemsused inthedataset Use obligation/condition fromreferencing object Use maximum occurrence from referencing object Class <> Lines196-197 196.namerefSysNamenameofreferencesystemusedM1ClassRS_Identifier(B.2.7.3) 197.domainOfValiditydomOValidrangewhichisvalidforthe referencesystem ONClassEX_Extent <>(B.3.1) 198.intentionallyleftblank 199.intentionallyleftblank 200.intentionallyleftblank B.2.7.2Ellipsoidparameterinformation Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 201.MD_EllipsoidParametersEllParassetofparametersthatdescribethe ellipsoid Use obligation/condition fromreferencing object Use maximum occurrence from referencing object AggregatedClass (MD_CRS) Lines202-204 202.semiMajorAxissemiMajAxradiusoftheequatorialaxisofthe ellipsoid M1Real>0,0 203.axisUnitsaxisUnitsunitsofthesemi-majoraxisM1ClassUomLength(B.4.3) 204.denominatorOfFlatteningRatiodenFlatRatratioofthedifferencebetweenthe equatorialandpolarradiiofthe ellipsoidtotheequatorialradius whenthenumeratorissetto1 C/notaspheroid?1Real>0,0 ISO 19115:2003(E) 64 © ISO 2003 — All rights reserved B.2.7.3Identifierinformation Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 205.MD_IdentifierMdIdentvalueuniquelyidentifyinganobject withinanamespace Use obligation/condition fromreferencing object Use maximum occurrence from referencing object ClassLines206-207 206.authorityidentAuthpersonorpartyresponsiblefor maintenanceofthenamespace O1ClassCI_Citation <>(B.3.2) 207.codeidentCodealphanumericvalueidentifyingan instanceinthenamespace M1CharacterStringFreetext 208.RS_IdentifierRsIdentidentifierusedforreference systems Use obligation/condition fromreferencing object Use maximum occurrence from referencing object SpecifiedClass (MD_Identifier) Lines206-207and208.1- 208.2 208.1codeSpaceidentCodeSpacenameoridentifierofthepersonor organizationresponsiblefor namespace O1CharacterStringFreetext 208.2versionidentVrsnversionidentifierforthe namespace O1CharacterStringFreetext B.2.7.4Obliquelineazimuthinformation Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 209.MD_ObliqueLineAzimuthObLineAzimethodusedtodescribetheline alongwhichanobliquemercator mapprojectioniscentredusingthe mapprojectionoriginandan azimuth Use obligation/condition fromreferencing object Use maximum occurrence from referencing object AggregatedClass (MD_Projection Parameters) Lines210-211 ISO 19115:2003(E) © ISO 2003 — All rights reserved 65 Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 210.azimuthAngleaziAngleanglemeasuredclockwisefrom north,andexpressedindegrees M1RealReal 211.azimuthMeasurePoint Longitude aziPtLonglongitudeofthemapprojection origin M1RealReal B.2.7.5Obliquelinepointinformation Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 212.MD_ObliqueLinePointObLinePtmethodusedtodescribetheline alongwhichanobliquemercator mapprojectioniscentredusing twopointsnearthelimitsofthe mappedregionthatdefinethe centreline Use obligation/condition fromreferencing object Use maximum occurrence from referencing object AggregatedClass (MD_Projection Parameters) Lines213-214 213.obliqueLineLatitudeobLineLatlatitudeofapointdefiningthe obliqueline M1RealReal 214.obliqueLineLongitudeobLineLonglongitudeofapointdefiningthe obliqueline M1RealReal B.2.7.6Projectionparameterinformation Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 215.MD_ProjectionParametersProjParassetofparametersthatdescribethe projection Use obligation/condition fromreferencing object Use maximum occurrence from referencing object AggregatedClass (MD_CRS) Lines216-231 216.zonezoneuniqueidentifierfor100,000metre gridzone O1IntegerInteger ISO 19115:2003(E) 66 © ISO 2003 — All rights reserved Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 217.standardParallelstanParallineofconstantlatitudeatwhich thesurfaceoftheEarthandthe planeordevelopablesurface intersect O2RealReal 218.longitudeOfCentralMeridianlongCntMerlineoflongitudeatthecentreofa mapprojectiongenerallyusedas thebasisforconstructingthe projection O1RealReal 219.latitudeOfProjectionOriginlatProjOrilatitudechosenastheoriginof rectangularcoordinatesforamap projection O1RealReal 220.falseEastingfalEastngvalueaddedtoall“x”valuesinthe rectangularcoordinatesforamap projection.Thisvaluefrequentlyis assignedtoeliminatenegative numbers.Expressedintheunitof measureidentifiedinPlanar CoordinateUnits O1RealReal 221.falseNorthingfalNorthngvalueaddedtoall“y”valuesinthe rectangularcoordinatesforamap projection.Thisvaluefrequentlyis assignedtoeliminatenegative numbers.Expressedintheunitof measureidentifiedinPlanar CoordinateUnits O1RealReal 222.falseEastingNorthingUnitsfalENUnitsunitsoffalsenorthingandfalse easting O1ClassUomLength(B.4.3) 223.scaleFactorAtEquatorsclFacEquratiobetweenphysicaldistance andcorrespondingmapdistance, alongtheequator O1Real>0,0 224.heightOfProspectivePoint AboveSurface hgtProsPtheightofviewpointabovethe Earth,expressedinmetres O1Real>0,0 225.longitudeOfProjectionCenterlongProjCntlongitudeofthepointofprojection forazimuthalprojections O1RealReal 226.latitudeOfProjectionCenterlatProjCntlatitudeofthepointofprojection forazimuthalprojections O1RealReal ISO 19115:2003(E) © ISO 2003 — All rights reserved 67 Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 227.scaleFactorAtCenterLinesclFacCntratiobetweenphysicaldistance andcorrespondingmapdistance, alongthecentreline O1RealReal 228.straightVerticalLongitudeFrom Pole stVrLongPllongitudetobeorientedstraightup fromtheNorthorSouthPole O1RealReal 229.scaleFactorAtProjectionOriginsclFacPrOrmultiplierforreducingadistance obtainedfromamapby computationorscalingtothe actualdistanceattheprojection origin O1RealReal 230.rolename: obliqueLineAzimuthParameter obLnAziParsparametersdescribingtheoblique lineazimuth O1AssociationMD_ObliqueLineAzimuth (B.2.7.4) 231.rolename: obliqueLinePointParameter obLnPtParsparametersdescribingtheoblique linepoint O2AssociationMD_ObliqueLinePoint (B.2.7.5) B.2.8Contentinformation(includesFeaturecatalogueandCoveragedescriptions) B.2.8.1General •UMLmodelshowninFigureA.10 Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 232.MD_ContentInformationContInfodescriptionofthecontentofa dataset Use obligation/condition fromreferencing object Use maximum occurrence from referencing object AggregatedClass (MD_Metadata) <> ISO 19115:2003(E) 68 © ISO 2003 — All rights reserved Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 233.MD_FeatureCatalogue Description FetCatDescinformationidentifyingthefeature catalogueortheconceptual schema Use obligation/condition fromreferencing object Use maximum occurrence from referencing object SpecifiedClass (MD_Content Information) Lines234-238 234.complianceCodecompCodeindicationofwhetherornotthe citedfeaturecataloguecomplies withISO19110 O1Boolean0-notcompliant 1-compliant 235.languagecatLanglanguage(s)usedwithinthe catalogue ONCharacterStringISO639-2,otherpartscanbe used 236.includedWithDatasetincWithDSindicationofwhetherornotthe featurecatalogueisincludedwith thedataset M1Boolean0=no 1=yes 237.featureTypescatFetTypssubsetoffeaturetypesfromcited featurecatalogueoccurringin dataset ONClassGenericName(B.4.8) 238.featureCatalogueCitationcatCitationcompletebibliographicreferenceto oneormoreexternalfeature catalogues MNClassCI_Citation <>(B.3.2) 239.MD_CoverageDescriptionCovDescinformationaboutthecontentofa griddatacell Use obligation/condition fromreferencing object Use maximum occurrence from referencing object SpecifiedClass (MD_Content Information) Lines240-242 240.attributeDescriptionattDescdescriptionoftheattribute describedbythemeasurement value M1ClassRecordType <>(B.4.3) 241.contentTypecontentTyptypeofinformationrepresentedby thecellvalue M1ClassMD_CoverageContentType Code <>(B.5.12) 242.Rolename: dimension covDiminformationonthedimensionsof thecellmeasurementvalue ONClassMD_RangeDimension (B.2.8.2) ISO 19115:2003(E) © ISO 2003 — All rights reserved 69 Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 243.MD_ImageDescriptionImgDescinformationaboutanimage’s suitabilityforuse OUse maximum occurrence from referencing object SpecifiedClass (MD_Coverage Description) Lines244-255and240-242 244.illuminationElevationAngleillElevAngilluminationelevationmeasuredin degreesclockwisefromthetarget planeatintersectionoftheoptical lineofsightwiththeEarth’s surface.Forimagesfroma scanningdevice,refertothe centrepixeloftheimage O1Real-90–90 245.illuminationAzimuthAngleillAziAngilluminationazimuthmeasuredin degreesclockwisefromtruenorth atthetimetheimageistaken.For imagesfromascanningdevice, refertothecentrepixelofthe image O1Real0,00–360 246.imagingConditionimagCondconditionsaffectedtheimageO1ClassMD_ImagingConditionCode <>(B.5.16) 247.imageQualityCodeimagQuCodespecifiestheimagequalityO1ClassMD_Identifier <>(B.2.7.3) 248.cloudCoverPercentagecloudCovPerareaofthedatasetobscuredby clouds,expressedasapercentage ofthespatialextent O1Real0,0–100,0 249.processingLevelCodeprcTypCdeimagedistributor’scodethat identifiesthelevelofradiometric andgeometricprocessingthathas beenapplied O1ClassMD_Identifier <>(B.2.7.3) 250.compressionGeneration Quantity cmpGenQuancountofthenumberoflossy compressioncyclesperformedon theimage O1IntegerInteger 251.triangulationIndicatortrianIndindicationofwhetherornot triangulationhasbeenperformed upontheimage O1Boolean0-no 1-yes ISO 19115:2003(E) 70 © ISO 2003 — All rights reserved Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 252.radiometricCalibrationData Availability radCalDatAvindicationofwhetherornotthe radiometriccalibrationinformation forgeneratingtheradiometrically calibratedstandarddataproductis available O1Boolean0-no 1-yes 253.cameraCalibrationInformation Availability camCalInAvindicationofwhetherornot constantsareavailablewhich allowforcameracalibration corrections O1Boolean0-no 1-yes 254.filmDistortionInformation Availability filmDistInAvindicationofwhetherornot CalibrationReseauinformationis available O1Boolean0-no 1-yes 255.lensDistortionInformation Availability lensDistInAvindicationofwhetherornotlens aberrationcorrectioninformationis available O1Boolean0-no 1-yes B.2.8.2Rangedimensioninformation(includesBandinformation) Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 256.MD_RangeDimensionRangeDiminformationontherangeofeach dimensionofacellmeasurement value Use obligation/condition fromreferencing object Use maximum occurrence from referencing object AggregatedClass (MD_Coverage Description) Lines257-258 257.sequenceIdentifierseqIDnumberthatuniquelyidentifies instancesofbandsofwavelengths onwhichasensoroperates O1ClassMemberName(B.4.8) 258.descriptordimDescrpdescriptionoftherangeofacell measurementvalue O1CharacterStringFreetext ISO 19115:2003(E) © ISO 2003 — All rights reserved 71 Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 259.MD_BandBandrangeofwavelengthsinthe electromagneticspectrum Use obligation/condition fromreferencing object Use maximum occurrence from referencing object SpecifiedClass (MD_RangeDimension) Lines260-267and257-258 260.maxValuemaxVallongestwavelengththatthesensor iscapableofcollectingwithina designatedband O1RealReal 261.minValueminValshortestwavelengththatthe sensoriscapableofcollecting withinadesignatedband O1RealReal 262.unitsvalUnitunitsinwhichsensorwavelengths areexpressed C/minValueor maxValueprovided? 1ClassUomLength(B.4.3) 263.peakResponsepkRespwavelengthatwhichtheresponse isthehighest O1RealReal 264.bitsPerValuebitsPerValmaximumnumberofsignificant bitsintheuncompressed representationforthevaluein eachbandofeachpixel O1IntegerInteger 265.toneGradationtoneGradnumberofdiscretenumerical valuesinthegriddata O1IntegerInteger 266.scaleFactorsclFacscalefactorwhichhasbeen appliedtothecellvalue O1RealReal 267.offsetoffsetthephysicalvaluecorresponding toacellvalueofzero O1RealReal ISO 19115:2003(E) 72 © ISO 2003 — All rights reserved B.2.9Portrayalcatalogueinformation •UMLmodelshowninFigureA.11 Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 268.MD_PortrayalCatalogue Reference PortCatRefinformationidentifyingtheportrayal catalogueused Use obligation/condition fromreferencing object Use maximum occurrence from referencing object AggregatedClass (MD_Metadata) Line269 269.portrayalCatalogueCitationportCatCitbibliographicreferencetothe portrayalcataloguecited MNClassCI_Citation <>(B.3.2) B.2.10Distributioninformation B.2.10.1General •UMLmodelshowninFigureA.12 Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 270.MD_DistributionDistribinformationaboutthedistributorof andoptionsforobtainingthe resource Use obligation/condition fromreferencing object Use maximum occurrence from referencing object AggregatedClass (MD_Metadata) Lines271-273 271.Rolename: distributionFormat distFormatprovidesadescriptionofthe formatofthedatatobedistributed C/MD_Distributor. distibutorFormatnot documented? NAssociationMD_Format(B.2.10.4) 272.Rolename: distributor distributorprovidesinformationaboutthe distributor ONAssociationMD_Distributor(B.2.10.3) ISO 19115:2003(E) © ISO 2003 — All rights reserved 73 Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 273.Rolename: transferOptions distTranOpsprovidesinformationabout technicalmeansandmediaby whicharesourceisobtainedfrom thedistributor ONAssociationMD_DigitalTransferOptions (B.2.10.2) B.2.10.2Digitaltransferoptionsinformation Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 274.MD_DigitalTransferOptionsDigTranOpstechnicalmeansandmediaby whicharesourceisobtainedfrom thedistributor Use obligation/condition fromreferencing object Use maximum occurrence from referencing object AggregatedClass (MD_Distributionand MD_Distributor) Lines275-278 275.unitsOfDistributionunitsODisttiles,layers,geographicareas, etc.,inwhichdataisavailable O1CharacterStringFreetext 276.transferSizetransSizeestimatedsizeofaunitinthe specifiedtransferformat, expressedinmegabytes.The transfersizeis>0.0 O1Real>0,0 277.onLineonLineSrcinformationaboutonlinesources fromwhichtheresourcecanbe obtained ONClassCI_OnlineResource <>(B.3.2.5) 278.offLineoffLineMedinformationaboutofflinemediaon whichtheresourcecanbe obtained O1ClassMD_Medium <>(B.2.10.5) ISO 19115:2003(E) 74 © ISO 2003 — All rights reserved B.2.10.3Distributorinformation Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 279.MD_DistributorDistributorinformationaboutthedistributorUse obligation/condition fromreferencing object Use maximum occurrence from referencing object AggregatedClass (MD_Distributionand MD_Format) Lines280-283 280.distributorContactdistorContpartyfromwhomtheresourcemay beobtained.Thislistneednotbe exhaustive M1ClassCI_ResponsibleParty <>(B.3.2) 281.Rolename: distributionOrderProcess distorOrdPrcprovidesinformationabouthowthe resourcemaybeobtained,and relatedinstructionsandfee information ONAssociationMD_StandardOrderProcess (B.2.10.6) 282.Rolename: distributorFormat distorFormatprovidesinformationaboutthe formatusedbythedistributor C/MD_Distribution. distributionFormatnot documented? NAssociationMD_Format(B.2.10.4) 283.Rolename: distributorTransferOptions distorTranprovidesinformationaboutthe technicalmeansandmediaused bythedistributor ONAssociationMD_DigitalTransferOptions (B.2.10.2) B.2.10.4Formatinformation Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 284.MD_FormatFormatdescriptionofthecomputer languageconstructthatspecifies therepresentationofdataobjects inarecord,file,message,storage deviceortransmissionchannel Use obligation/condition fromreferencing object Use maximum occurrence from referencing object AggregatedClass (MD_Distribution, MD_Identification,and MD_Distributor) Lines285-290 285.nameformatNamenameofthedatatransferformat(s)M1CharacterStringFreetext 286.versionformatVerversionoftheformat(date, number,etc.) M1CharacterStringFreetext ISO 19115:2003(E) © ISO 2003 — All rights reserved 75 Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 287.amendmentNumberformatAmdNumamendmentnumberoftheformat version O1CharacterStringFreetext 288.specificationformatSpecnameofasubset,profile,or productspecificationoftheformat O1CharacterStringFreetext 289.fileDecompressionTechniquefileDecmTechrecommendationsofalgorithmsor processesthatcanbeappliedto readorexpandresourcestowhich compressiontechniqueshave beenapplied O1CharacterStringFreetext 290.Rolename: formatDistributor formatDistprovidesinformationaboutthe distributor’sformat ONAssociationMD_Distributor(B.2.10.3) B.2.10.5Mediuminformation Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 291.MD_MediumMediuminformationaboutthemediaon whichtheresourcecanbe distributed Use obligation/condition fromreferencing object Use maximum occurrence from referencing object Class <> Lines292-297 292.namemedNamenameofthemediumonwhichthe resourcecanbereceived O1ClassMD_MediumNameCode <>(B.5.20) 293.densitymedDensitydensityatwhichthedatais recorded ONReal>0,0 294.densityUnitsmedDenUnitsunitsofmeasurefortherecording density C/density documented? 1CharacterStringFreetext 295.volumesmedVolnumberofitemsinthemedia identified O1Integer>0,0 296.mediumFormatmedFormatmethodusedtowritetothe medium ONClassMD_MediumFormatCode <>(B.5.19) ISO 19115:2003(E) 76 © ISO 2003 — All rights reserved Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 297.mediumNotemedNotedescriptionofotherlimitationsor requirementsforusingthemedium O1CharacterStringFreetext B.2.10.6Standardorderprocessinformation Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 298.MD_StandardOrderProcessStanOrdProccommonwaysinwhichthe resourcemaybeobtainedor received,andrelatedinstructions andfeeinformation Use obligation/condition fromreferencing object Use maximum occurrence from referencing object AggregatedClass (MD_Distributor) Lines299-302 299.feesresFeesfeesandtermsforretrievingthe resource.Includemonetaryunits (asspecifiedinISO4217) O1CharacterStringFreetext 300.plannedAvailableDateTimeplanAvDtTmdateandtimewhentheresource willbeavailable O1ClassDateTime(B.4.2) 301.orderingInstructionsordInstrgeneralinstructions,termsand servicesprovidedbythedistributor O1CharacterStringFreetext 302.turnaroundordTurntypicalturnaroundtimeforthe fillingofanorder O1CharacterStringFreetext ISO 19115:2003(E) © ISO 2003 — All rights reserved 77 B.2.11Metadataextensioninformation B.2.11.1General •UMLmodelshowninFigureA.13 Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 303.MD_MetadataExtension Information MdExtInfoinformationdescribingmetadata extensions Use obligation/condition fromreferencing object Use maximum occurrence from referencing object AggregatedClass (MD_Metadata) Lines304-305 304.extensionOnLineResourceextOnResinformationabouton-linesources containingthecommunityprofile nameandtheextendedmetadata elements.Informationforallnew metadataelements O1ClassCI_OnlineResource <>(B.3.2.5) 305.Rolename: extendedElementInformation extEleInfoprovidesinformationaboutanew metadataelement,notfoundin ISO19115,whichisrequiredto describegeographicdata ONAssociationMD_ExtendedElement Information(B.2.11.2) B.2.11.2Extendedelementinformation Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 306.MD_ExtendedElemen tInformation ExtEleInfonewmetadataelement,notfound inISO19115,whichisrequiredto describegeographicdata Use obligation/condition fromreferencing object Use maximum occurrence from referencing object AggregatedClass (MD_Metadata ExtensionInformation) Lines307-319 307.nameextEleNamenameoftheextendedmetadata element M1CharacterStringFreetext ISO 19115:2003(E) 78 © ISO 2003 — All rights reserved Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 308.shortNameextShortNameshortformsuitableforuseinan implementationmethodsuchas XMLorSGML.NOTEother methodsmaybeused C/dataType notEqual “codelistElement”? 1CharacterStringFreetext 309.domainCodeextDomCodethreedigitcodeassignedtothe extendedelement C/isdataType “codelistElement”? 1IntegerInteger 310.definitionextEleDefdefinitionoftheextendedelementM1CharacterStringFreetext 311.obligationextEleObobligationoftheextendedelementC/dataTypenot “codelist”, “enumeration”or “codelistElement”? 1ClassMD_ObligationCode <>(B.5.21) 312.conditionextEleCondconditionunderwhichthe extendedelementismandatory C/obligation= “Conditional”? 1CharacterStringFreetext 313.dataTypeeleDataTypecodewhichidentifiesthekindof valueprovidedintheextended element M1ClassMD_DatatypeCode <>(B.5.13) 314.maximumOccurrenceextEleMxOcmaximumoccurrenceofthe extendedelement C/dataTypenot “codelist”, “enumeration”or “codelistElement”? 1CharacterStringNoranyinteger 315.domainValueextEleDomValvalidvaluesthatcanbeassigned totheextendedelement C/dataTypenot “codelist“, “enumeration”or “codelistElement”? 1CharacterStringFreetext 316.parentEntityextEleParEntnameofthemetadataentity(s) underwhichthisextended metadataelementmayappear. Thename(s)maybestandard metadataelement(s)orother extendedmetadataelement(s) MNCharacterStringFreetext 317.ruleextEleRulespecifieshowtheextended elementrelatestootherexisting elementsandentities M1CharacterStringFreetext 318.rationaleextEleRatreasonforcreatingtheextended element ONCharacterStringFreetext ISO 19115:2003(E) © ISO 2003 — All rights reserved 79 Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 319.sourceextEleSrcnameofthepersonororganization creatingtheextendedelement MNClassCI_ResponsibleParty <>(B.3.2) B.2.12Applicationschemainformation •UMLmodelshowninFigureA.14 Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 320.MD_ApplicationSchema Information AppSchInfoinformationabouttheapplication schemausedtobuildthedataset Use obligation/condition fromreferencing object Use maximum occurrence from referencing object AggregatedClass (MD_Metadata) Lines321-327 321.nameasNamenameoftheapplicationschema used M1ClassCI_Citation <>(B.3.2) 322.schemaLanguageasSchLangidentificationoftheschema languageused M1CharacterStringFreetext 323.constraintLanguageasCstLangformallanguageusedin ApplicationSchema M1CharacterStringFreetext 324.schemaAsciiasAsciifullapplicationschemagivenasan ASCIIfile O1CharacterStringFreetext 325.graphicsFileasGraFilefullapplicationschemagivenasa graphicsfile O1BinaryBinary 326.softwareDevelopmentFileasSwDevFilefullapplicationschemagivenasa softwaredevelopmentfile O1BinaryBinary 327.softwareDevelopmentFile Format asSwDevFiFtsoftwaredependentformatused fortheapplicationschema softwaredependentfile O1CharacterStringFreetext 328.intentionallyleftblank 329.intentionallyleftblank ISO 19115:2003(E) 80 © ISO 2003 — All rights reserved Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 330.intentionallyleftblank 331.intentionallyleftblank 332.intentionallyleftblank 333.intentionallyleftblank B.3Datatypeinformation B.3.1Extentinformation B.3.1.1General •UMLmodelshowninFigureA.15 Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 334.EX_ExtentExtentinformationabouthorizontal, vertical,andtemporalextent Use obligation/condition fromreferencing object Use maximum occurrence from referencing object Class<>Lines335-338 335.descriptionexDescspatialandtemporalextentforthe referringobject C/ geographicElement andtemporalElement andverticalElement notdocumented? 1CharacterStringFreetext 336.Rolename: geographicElement geoEleprovidesgeographiccomponentof theextentofthereferringobject C/descriptionand temporalElementand verticalElementnot documented? NAssociationEX_GeographicExtent <>(B.3.1.2) 337.Rolename: temporalElement tempEleprovidestemporalcomponentof theextentofthereferringobject C/descriptionand geographicElement andverticalElement notdocumented? NAssociationEX_TemporalExtent(B.3.1.3) ISO 19115:2003(E) © ISO 2003 — All rights reserved 81 Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 338.Rolename: verticalElement vertEleprovidesverticalcomponentofthe extentofthereferringobject C/descriptionand geographicElement andtemporalElement notdocumented? NAssociationEX_VerticalExtent(B.3.1.4) B.3.1.2Geographicextentinformation Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 339.EX_GeographicExtentGeoExtentgeographicareaofthedatasetUse obligation/condition fromreferencing object Use maximum occurrence from referencing object AggregatedClass (EX_Extentand EX_SpatialTemporal Extent) <> Line340 340.extentTypeCodeexTypeCodeindicationofwhetherthebounding polygonencompassesanarea coveredbythedataoranarea wheredataisnotpresent O1Boolean0–exclusion 1–inclusion 341.EX_BoundingPolygonBoundPolyboundaryenclosingthedataset, expressedastheclosedsetof (x,y)coordinatesofthepolygon (lastpointreplicatesfirstpoint) Use obligation/condition fromreferencing object Use maximum occurrence from referencing object SpecifiedClass (EX_GeographicExtent) Line342and340 342.polygonpolygonsetsofpointsdefiningthe boundingpolygon MNClassGM_Object(B.4.6) -90to90latitude -180to360longitude 343.EX_GeographicBoundingBoxGeoBndBoxgeographicpositionofthedataset NOTEThisisonlyanapproximate referencesospecifyingthe coordinatereferencesystemis unnecessary Use obligation/condition fromreferencing object Use maximum occurrence from referencing object SpecifiedClass (EX_GeographicExtent) Lines344-347and340 ISO 19115:2003(E) 82 © ISO 2003 — All rights reserved Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 344.westBoundLongitudewestBLwestern-mostcoordinateofthe limitofthedatasetextent, expressedinlongitudeindecimal degrees(positiveeast) M1Angle(B.4.3) -180,0<=WestBounding Longitude Value<=180,0 345.eastBoundLongitudeeastBLeastern-mostcoordinateofthe limitofthedatasetextent, expressedinlongitudeindecimal degrees(positiveeast) M1ClassAngle(B.4.3) -180,0<=EastBounding Longitude Value<=180,0 346.southBoundLatitudesouthBLsouthern-mostcoordinateofthe limitofthedatasetextent, expressedinlatitudeindecimal degrees(positivenorth) M1ClassAngle(B.4.3) -90,0<=SouthBounding Latitude Value<=90,0;South BoundingLatitudeValue<= NorthboundingLatitude Value 347.northBoundLatitudenorthBLnorthern-most,coordinateofthe limitofthedatasetextent expressedinlatitudeindecimal degrees(positivenorth) M1ClassAngle(B.4.3) -90,0<=NorthBounding Latitude Value<=90,0;North BoundingLatitudeValue>= SouthBoundingLatitude Value 348.EX_GeographicDescriptionGeoDescdescriptionofthegeographicarea usingidentifiers Use obligation/condition fromreferencing object Use maximum occurrence from referencing object SpecifiedClass (EX_GeographicExtent) Line349and340 349.geographicIdentifiergeoIdidentifierusedtorepresenta geographicarea M1ClassMD_Identifier(B.2.7.3) ISO 19115:2003(E) © ISO 2003 — All rights reserved 83 B.3.1.3Temporalextentinformation Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 350.EX_TemporalExtentTempExtenttimeperiodcoveredbythecontent ofthedataset Use obligation/condition fromreferencing object Use maximum occurrence from referencing object AggregatedClass (EX_Extent) Line351 351.extentexTempdateandtimeforthecontentofthe dataset M1ClassTM_Primitive(B.4.5) 352.EX_SpatialTemporalExtentSpatTempExextentwithrespecttodate/time andspatialboundaries Use obligation/condition fromreferencing object Use maximum occurrence from referencing object SpecifiedClass (EX_TemporalExtent) Line353and351 353.rolename: spatialExtent exSpatspatialextentcomponentof compositespatialandtemporal extent MNAssociationEX_GeographicExtent <>(B.3.1.2) B.3.1.4Verticalextentinformation Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 354.EX_VerticalExtentVertExtentverticaldomainofdatasetUse obligation/condition fromreferencing object Use maximum occurrence from referencing object AggregatedClass (EX_Extent) Lines355-358 355.minimumValuevertMinVallowestverticalextentcontainedin thedataset M1RealReal 356.maximumValuevertMaxValhighestverticalextentcontainedin thedataset M1RealReal ISO 19115:2003(E) 84 © ISO 2003 — All rights reserved Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 357.unitOfMeasurevertUoMverticalunitsusedforvertical extentinformationExamples: metres,feet,millimetres, hectopascals M1ClassUomLength(B.4.3) 358.rolename: verticalDatum vertDatumprovidesinformationaboutthe originfromwhichthemaximum andminimumelevationvaluesare measured M1AssociationSC_VerticalDatum(B.4.9) B.3.2Citationandresponsiblepartyinformation B.3.2.1General •UMLmodelshowninFigureA.16 Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 359.CI_CitationCitationstandardizedresourcereferenceUse obligation/condition fromreferencing object Use maximum occurrence from referencing object Class <> Lines360-373 360.titleresTitlenamebywhichthecitedresource isknown M1CharacterStringFreetext 361.alternateTitleresAltTitleshortnameorotherlanguage namebywhichthecited informationisknown.Example: "DCW"asanalternativetitlefor "DigitalChartoftheWorld” ONCharacterStringFreetext 362.dateresRefDatereferencedateforthecited resource MNClassCI_Date(B.3.2.4) <> 363.editionresEdversionofthecitedresourceO1CharacterStringFreetext 364.editionDateresEdDatedateoftheeditionO1ClassDate(B.4.2) ISO 19115:2003(E) © ISO 2003 — All rights reserved 85 Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 365.identifiercitIdvalueuniquelyidentifyinganobject withinanamespace ONClassMD_Identifier <>(B.2.7.3) 366.intentionallyleftblank 367.citedResponsiblePartycitRespPartynameandpositioninformationfor anindividualororganizationthatis responsiblefortheresource ONClassCI_ResponsibleParty <>(B.3.2) 368.presentationFormpresFormmodeinwhichtheresourceis represented ONClassCI_PresentationFormCode <>(B.5.4) 369.seriesdatasetSeriesinformationabouttheseries,or aggregatedataset,ofwhichthe datasetisapart O1ClassCI_Series <>(B.3.2.6) 370.otherCitationDetailsotherCitDetotherinformationrequiredto completethecitationthatisnot recordedelsewhere O1CharacterStringFreetext 371.collectiveTitlecollTitlecommontitlewithholdingsnote NOTEtitleidentifieselementsofa seriescollectively,combinedwith informationaboutwhatvolumes areavailableatthesourcecited O1CharacterStringFreetext 372.ISBNisbninternationalStandardBook Number O1CharacterStringFreetext 373.ISSNissninternationalStandardSerial Number O1CharacterStringFreetext 374.CI_ResponsiblePartyRespPartyidentificationof,andmeansof communicationwith,person(s)and organizationsassociatedwiththe dataset Use obligation/condition fromreferencing object Use maximum occurrence from referencing object Class <> Lines375-379 375.individualNamerpIndNamenameoftheresponsibleperson- surname,givenname,title separatedbyadelimiter C/organisationName andpositionNamenot documented? 1CharacterStringFreetext 376.organisationNamerpOrgNamenameoftheresponsible organization C/individualName andpositionNamenot documented? 1CharacterStringFreetext ISO 19115:2003(E) 86 © ISO 2003 — All rights reserved Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 377.positionNamerpPosNameroleorpositionoftheresponsible person C/individualName and organisationNamenot documented? 1CharacterStringFreetext 378.contactInforpCntInfoaddressoftheresponsiblepartyO1ClassCI_Contact <>(B.3.2.3) 379.rolerolefunctionperformedbythe responsibleparty M1ClassCI_RoleCode <>(B.5.5) B.3.2.2Addressinformation Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 380.CI_AddressAddresslocationoftheresponsible individualororganization Use obligation/condition fromreferencing object Use maximum occurrence from referencing object Class <> Lines381-386 381.deliveryPointdelPointaddresslineforthelocation(as describedinISO11180,AnnexA) ONCharacterStringFreetext 382.citycitycityofthelocationO1CharacterStringFreetext 383.administrativeAreaadminAreastate,provinceofthelocationO1CharacterStringFreetext 384.postalCodepostCodeZIPorotherpostalcodeO1CharacterStringFreetext 385.countrycountrycountryofthephysicaladdressO1CharacterStringISO3166-3,otherpartsmay beused 386.electronicMailAddresseMailAddaddressoftheelectronicmailbox oftheresponsibleorganizationor individual ONCharacterStringFreetext ISO 19115:2003(E) © ISO 2003 — All rights reserved 87 B.3.2.3Contactinformation Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 387.CI_ContactContactinformationrequiredtoenable contactwiththeresponsible personand/ororganization Use obligation/condition fromreferencing object Use maximum occurrence from referencing object Class <> Lines388-392 388.phonecntPhonetelephonenumbersatwhichthe organizationorindividualmaybe contacted O1ClassCI_Telephone <>(B.3.2.7) 389.addresscntAddressphysicalandemailaddressat whichtheorganizationorindividual maybecontacted O1ClassCI_Address <>(B.3.2.2) 390.onlineResourcecntOnlineReson-lineinformationthatcanbe usedtocontacttheindividualor organization O1ClassCI_OnlineResource <>(B.3.2.5) 391.hoursOfServicecntHourstimeperiod(includingtimezone) whenindividualscancontactthe organizationorindividual O1CharacterStringFreetext 392.contactInstructionscntInstrsupplementalinstructionsonhow orwhentocontacttheindividualor organization O1CharacterStringFreetext B.3.2.4Dateinformation Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 393.CI_DateDateRefreferencedateandeventusedto describeit Use obligation/condition fromreferencing object Use maximum occurrence from referencing object Class <> Lines394-395 ISO 19115:2003(E) 88 © ISO 2003 — All rights reserved Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 394.daterefDatereferencedateforthecited resource M1ClassDate(B.4.2) 395.dateTyperefDateTypeeventusedforreferencedateM1ClassCI_DateTypeCode <>(B.5.2) B.3.2.5OnLineresourceinformation Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 396.CI_OnlineResourceOnlineResinformationabouton-linesources fromwhichthedataset, specification,orcommunityprofile nameandextendedmetadata elementscanbeobtained Use obligation/condition fromreferencing object Use maximum occurrence from referencing object Class <> Lines397-402 397.linkagelinkagelocation(address)foron-line accessusingaUniformResource Locatoraddressorsimilar addressingschemesuchas http://www.statkart.no/isotc211 M1ClassURL (IETFRFC1738 IETFRFC2056) 398.protocolprotocolconnectionprotocoltobeusedO1CharacterStringFreetext 399.applicationProfileappProfilenameofanapplicationprofilethat canbeusedwiththeonline resource O1CharacterStringFreetext 400.nameorNamenameoftheonlineresourceO1CharacterStringFreetext 401.descriptionorDescdetailedtextdescriptionofwhat theonlineresourceis/does O1CharacterStringFreetext 402.functionorFunctcodeforfunctionperformedbythe onlineresource O1ClassCI_OnLineFunctionCode <>(B.5.3) ISO 19115:2003(E) © ISO 2003 — All rights reserved 89 B.3.2.6Seriesinformation Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 403.CI_SeriesDatasetSeriesinformationabouttheseries,or aggregatedataset,towhicha datasetbelongs Use obligation/condition fromreferencing object Use maximum occurrence from referencing object Class <> Lines404-406 404.nameseriesNamenameoftheseries,oraggregate dataset,ofwhichthedatasetisa part O1CharacterStringFreetext 405.issueIdentificationissIdinformationidentifyingtheissueof theseries O1CharacterStringFreetext 406.pageartPagedetailsonwhichpagesofthe publicationthearticlewas published O1CharacterStringFreetext B.3.2.7Telephoneinformation Name/RoleNameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 407.CI_TelephoneTelephonetelephonenumbersforcontacting theresponsibleindividualor organization Use obligation/condition fromreferencing object Use maximum occurrence from referencing object Class <> Lines408-409 408.voicevoiceNumtelephonenumberbywhich individualscanspeaktothe responsibleorganizationor individual ONCharacterStringFreetext 409.facsimilefaxNumtelephonenumberofafacsimile machinefortheresponsible organizationorindividual ONCharacterStringFreetext ISO 19115:2003(E) 90 © ISO 2003 — All rights reserved ISO 19115:2003(E) © ISO 2003 — All rights reserved 91 B.4 Externally referenced entities B.4.1 Introduction There are several entities referenced by this International Standard that are documented by another, external, standard. Those externally referenced entities are explained below. B.4.2 Date and DateTime information Date: gives values for year, month and day. Character encoding of a date is a string which shall follow the format for date specified by ISO 8601. This class is documented in full in ISO/TS 19103. DateTime: combination of a date and a time type (given by an hour, minute and second). Character encoding of a DateTime shall follow ISO 8601. This class is documented in full in ISO/TS 19103. B.4.3 Distance, angle, measure, number, record, recordType, scale and UomLength information Distance: This class is documented in full in ISO/TS 19103. Angle: Amount of rotation need to bring one line or plane into coincidence with another, generally measured in radians or degrees. This class is documented in full in ISO/TS 19103. Measure: result from performing the act or process of ascertaining the extent, dimensions, or quantity of some entity. This class is documented in full in ISO/TS 19103. Number: abstract class that can be sub-typed to a specific number type (real, integer, decimal, double, float). This class is documented in full in ISO/TS 19103. Record: This class is documented in full in ISO/TS 19103. RecordType: This class is documented in full in ISO/TS 19103. Scale: This class is documented in full in ISO/TS 19103. UnitOfMeasure: This class is documented in full in ISO/TS 19103. UomLength: any of the measuring systems to measure the length, distance between two entities. This class is documented in full in ISO/TS 19103. B.4.4 Feature type, property type, and attribute type information GF_AttributeType: class of attribute definitions of a feature type. This class is fully documented in ISO 19109. GF_FeatureType: textual information describing the concept of a feature type, containing all feature types. This class is documented in full in ISO 19109. GF_PropertyType: textual information related to the feature type because its text comprises characteristics and behaviour of any property of a feature type, as well as its roles within associations between features. This class is documented in full in ISO 19109. B.4.5 PeriodDuration and temporal primitive information TM_PeriodDuration: duration of a period as specified by ISO 8601. This class is fully documented in ISO 19108. ISO 19115:2003(E) 92 © ISO 2003 — All rights reserved TM_Primitive: an abstract class representing a non-decomposed element of geometry or topology. This class is fully documented in ISO 19108. B.4.6 Point and Object information GM_Point: 0-dimensional geometric primitive, representing a position, but not having extent. This class is fully documented in ISO 19107. GM_Object: root class of the geometric object taxonomy and supports interfaces common to all geographically referenced geometric objects. This class is fully documented in ISO 19107. B.4.7 Set and Sequence information Set: finite collection of objects, where each object appears in the collection only once. A set shall not contain any duplicated instances. The order of the elements of the set is not specified. This class is documented in full in ISO/TS 19103. Sequence: A sequence refers to a collection of sequential ordering between its elements. Sequences can be repeated, and may be used as a list or an array. This class is documented in full in ISO/TS 19103. B.4.8 Type name information AttributeName: This class is documented in full in ISO/TS 19103. GenericName: This class is documented in full in ISO/TS 19103. MemberName: This class is documented in full in ISO/TS 19103. B.4.9 Vertical datum information SC_VerticalDatum: set of parameters describing the relation of gravity-related heights to the Earth. This class is fully documented in ISO 19111. B.5 CodeLists and enumerations B.5.1 Introduction The stereotype classes <> and <> can be found below. These two stereotype classes do not contain “obligation / condition”, “maximum occurrence”, “data type” and “domain” attributes. These two stereotype classes also do not contain any “other” values as <>s are closed (not extendable) and <>s are extendable. Consult Annex C and Annex F for information about how to extend <>s. B.5.2 CI_DateTypeCode <> Name Domain code Definition 1. CI_DateTypeCode DateTypCd identification of when a given event occurred 2. creation 001 date identifies when the resource was brought into existence 3. publication 002 date identifies when the resource was issued 4. revision 003 date identifies when the resource was examined or re-examined and improved or amended ISO 19115:2003(E) © ISO 2003 — All rights reserved 93 B.5.3 CI_OnLineFunctionCode <> Name Domain code Definition 1. CI_OnLineFunctionCode OnFunctCd function performed by the resource 2. download 001 online instructions for transferring data from one storage device or system to another 3. information 002 online information about the resource 4. offlineAccess 003 online instructions for requesting the resource from the provider 5. order 004 online order process for obtaining the resource 6. search 005 online search interface for seeking out information about the resource B.5.4 CI_PresentationFormCode <> Name Domain code Definition 1. CI_PresentationFormCode PresFormCd mode in which the data is represented 2. documentDigital 001 digital representation of a primarily textual item (can contain illustrations also) 3. documentHardcopy 002 representation of a primarily textual item (can contain illustrations also) on paper, photographic material, or other media 4. imageDigital 003 likeness of natural or man-made features, objects, and activities acquired through the sensing of visual or any other segment of the electromagnetic spectrum by sensors, such as thermal infrared, and high resolution radar and stored in digital format 5. imageHardcopy 004 likeness of natural or man-made features, objects, and activities acquired through the sensing of visual or any other segment of the electromagnetic spectrum by sensors, such as thermal infrared, and high resolution radar and reproduced on paper, photographic material, or other media for use directly by the human user 6. mapDigital 005 map represented in raster or vector form 7. mapHardcopy 006 map printed on paper, photographic material, or other media for use directly by the human user 8. modelDigital 007 multi-dimensional digital representation of a feature, process, etc. 9. modelHardcopy 008 3-dimensional, physical model 10. profileDigital 009 vertical cross-section in digital form 11. profileHardcopy 010 vertical cross-section printed on paper, etc. 12. tableDigital 011 digital representation of facts or figures systematically displayed, especially in columns 13. tableHardcopy 012 representation of facts or figures systematically displayed, especially in columns, printed on paper, photographic material, or other media 14. videoDigital 013 digital video recording 15. videoHardcopy 014 video recording on film B.5.5 CI_RoleCode <> Name Domain code Definition 1. CI_RoleCode RoleCd function performed by the responsible party 2. resourceProvider 001 party that supplies the resource 3. custodian 002 party that accepts accountability and responsibility for the data and ensures appropriate care and maintenance of the resource ISO 19115:2003(E) 94 © ISO 2003 — All rights reserved Name Domain code Definition 4. owner 003 party that owns the resource 5. user 004 party who uses the resource 6. distributor 005 party who distributes the resource 7. originator 006 party who created the resource 8. pointOfContact 007 party who can be contacted for acquiring knowledge about or acquisition of the resource 9. principalInvestigator 008 key party responsible for gathering information and conducting research 10. processor 009 party who has processed the data in a manner such that the resource has been modified 11. publisher 010 party who published the resource 12. author 011 party who authored the resource B.5.6 DQ_EvaluationMethodTypeCode <> Name Domain code Definition 1. DQ_EvaluationMethodTyp eCode EvalMethTypeCd type of method for evaluating an identified data quality measure 2. directInternal 001 method of evaluating the quality of a dataset based on inspection of items within the dataset, where all data required is internal to the dataset being evaluated 3. directExternal 002 method of evaluating the quality of a dataset based on inspection of items within the dataset, where reference data external to the dataset being evaluated is required 4. indirect 003 method of evaluating the quality of a dataset based on external knowledge B.5.7 DS_AssociationTypeCode <> Name Domain code Definition 1. DS_AssociationTypeCode AscTypeCd justification for the correlation of two datasets 2. crossReference 001 reference from one dataset to another 3. largerWorkCitation 002 reference to a master dataset of which this one is a part 4. partOfSeamlessDatabase 003 part of same structured set of data held in a computer 5. source 004 mapping and charting information from which the dataset content originates 6. stereoMate 005 part of a set of imagery that when used together, provides three-dimensional images B.5.8 DS_InitiativeTypeCode <> Name Domain code Definition 1. DS_InitiativeTypeCode InitTypCd type of aggregation activity in which datasets are related 2. campaign 001 series of organized planned actions 3. collection 002 accumulation of datasets assembled for a specific purpose 4. exercise 003 specific performance of a function or group of functions 5. experiment 004 process designed to find if something is effective or valid 6. investigation 005 search or systematic inquiry ISO 19115:2003(E) © ISO 2003 — All rights reserved 95 Name Domain code Definition 7. mission 006 specific operation of a data collection system 8. sensor 007 device or piece of equipment which detects or records 9. operation 008 action that is part of a series of actions 10. platform 009 vehicle or other support base that holds a sensor 11. process 010 method of doing something involving a number of steps 12. program 011 specific planned activity 13. project 012 organized undertaking, research, or development 14. study 013 examination or investigation 15. task 014 piece of work 16. trial 015 process of testing to discover or demonstrate something B.5.9 MD_CellGeometryCode <> Name Domain code Definition 1. MD_CellGeometryCode CellGeoCd code indicating whether grid data is point or area 2. point 001 each cell represents a point 3. area 002 each cell represents an area B.5.10 MD_CharacterSetCode <> Name Domain code Definition 1. MD_CharacterSetCode CharSetCd name of the character coding standard used for the resource 2. ucs2 001 16-bit fixed size Universal Character Set, based on ISO/IEC 10646 3. ucs4 002 32-bit fixed size Universal Character Set, based on ISO/IEC 10646 4. utf7 003 7-bit variable size UCS Transfer Format, based on ISO/IEC 10646 5. utf8 004 8-bit variable size UCS Transfer Format, based on ISO/IEC 10646 6. utf16 005 16-bit variable size UCS Transfer Format, based on ISO/IEC 10646 7. 8859part1 006 ISO/IEC 8859-1, Information technology – 8-bit single-byte coded graphic character sets – Part 1: Latin alphabet No. 1 8. 8859part2 007 ISO/IEC 8859-2, Information technology – 8-bit single-byte coded graphic character sets – Part 2: Latin alphabet No. 2 9. 8859part3 008 ISO/IEC 8859-3, Information technology – 8-bit single-byte coded graphic character sets – Part 3: Latin alphabet No. 3 10. 8859part4 009 ISO/IEC 8859-4, Information technology – 8-bit single-byte coded graphic character sets – Part 4: Latin alphabet No. 4 11. 8859part5 010 ISO/IEC 8859-51, Information technology – 8-bit single-byte coded graphic character sets – Part 5: Latin/Cyrillic alphabet 12. 8859part6 011 ISO/IEC 8859-6, Information technology – 8-bit single-byte coded graphic character sets – Part 6: Latin/Arabic alphabet 13. 8859part7 012 ISO/IEC 8859-7, Information technology – 8-bit single-byte coded graphic character sets – Part 7: Latin/Greek alphabet 14. 8859part8 013 ISO/IEC 8859-8, Information technology – 8-bit single-byte coded graphic character sets – Part 8: Latin/Hebrew alphabet 15. 8859part9 014 ISO/IEC8859-9, Information technology – 8-bit single-byte coded graphic character sets – Part 9: Latin alphabet No. 5 ISO 19115:2003(E) 96 © ISO 2003 — All rights reserved Name Domain code Definition 16. 8859part10 015 ISO/IEC 8859-10, Information technology – 8-bit single-byte coded graphic character sets – Part 10: Latin alphabet No. 6 17. 8859part11 016 ISO/IEC 8859-11, Information technology – 8-bit single-byte coded graphic character sets – Part 11: Latin/Thai alphabet 18. (reserved for future use) 017 a future ISO/IEC 8-bit single-byte coded graphic character set (e.g. possibly 8859 part 12) 19. 8859part13 018 ISO/IEC 8859-13, Information technology – 8-bit single-byte coded graphic character sets – Part 13: Latin alphabet No. 7 20. 8859part14 019 ISO/IEC 8859-14, Information technology – 8-bit single-byte coded graphic character sets – Part 14: Latin alphabet No. 8 (Celtic) 21. 8859part15 020 ISO/IEC 8859-15, Information technology – 8-bit single-byte coded graphic character sets – Part 15: Latin alphabet No. 9 22. 8859part16 021 ISO/IEC 8859-16, Information technology – 8-bit single-byte coded graphic character sets – Part 16: Latin alphabet No. 10 23. jis 022 japanese code set used for electronic transmission 24. shiftJIS 023 japanese code set used on MS-DOS based machines 25. eucJP 024 japanese code set used on UNIX based machines 26. usAscii 025 united states ASCII code set (ISO 646 US) 27. ebcdic 026 ibm mainframe code set 28. eucKR 027 korean code set 29. big5 028 traditional Chinese code set used in Taiwan, Hong Kong of China and other areas 30. GB2312 029 simplified Chinese code set B.5.11 MD_ClassificationCode <> Name Domain code Definition 1. MD_ClassificationCode ClasscationCd name of the handling restrictions on the dataset 2. unclassified 001 available for general disclosure 3. restricted 002 not for general disclosure 4. confidential 003 available for someone who can be entrusted with information 5. secret 004 kept or meant to be kept private, unknown, or hidden from all but a select group of people 6. topSecret 005 of the highest secrecy B.5.12 MD_CoverageContentTypeCode <> Name Domain code Definition 1. MD_CoverageContentTyp eCode ContentTypCd specific type of information represented in the cell 2. image 001 meaningful numerical representation of a physical parameter that is not the actual value of the physical parameter 3. thematicClassification 002 code value with no quantitative meaning, used to represent a physical quantity 4. physicalMeasurement 003 value in physical units of the quantity being measured ISO 19115:2003(E) © ISO 2003 — All rights reserved 97 B.5.13 MD_DatatypeCode <> Name Domain code Definition 1. MD_DatatypeCode DatatypeCd datatype of element or entity 2. class 001 descriptor of a set of objects that share the same attributes, operations, methods, relationships, and behavior 3. codelist 002 flexible enumeration useful for expressing a long list of values, can be extended 4. enumeration 003 data type whose instances form a list of named literal values, not extendable 5. codelistElement 004 permissible value for a codelist or enumeration 6. abstractClass 005 class that cannot be directly instantiated 7. aggregateClass 006 class that is composed of classes it is connected to by an aggregate relationship 8. specifiedClass 007 subclass that may be substituted for its superclass 9. datatypeClass 008 class with few or no operations whose primary purpose is to hold the abstract state of another class for transmittal, storage, encoding or persistent storage 10. interfaceClass 009 named set of operations that characterize the behavior of an element 11. unionClass 010 class describing a selection of one of the specified types 12. metaClass 011 class whose instances are classes 13. typeClass 012 class used for specification of a domain of instances (objects), together with the operations applicable to the objects. A type may have attributes and associations 14. characterString 013 free text field 15. integer 014 numerical field 16. association 015 semantic relationship between two classes that involves connections among their instances B.5.14 MD_DimensionNameTypeCode <> Name Domain code Definition 1. MD_DimensionNameType Code DimNameTypCd name of the dimension 2. row 001 ordinate (y) axis 3. column 002 abscissa (x) axis 4. vertical 003 vertical (z) axis 5. track 004 along the direction of motion of the scan point 6. crossTrack 005 perpendicular to the direction of motion of the scan point 7. line 006 scan line of a sensor 8. sample 007 element along a scan line 9. time 008 duration B.5.15 MD_GeometricObjectTypeCode <> Name Domain code Definition 1. MD_GeometricObjectType Code GeoObjTypCd name of point or vector objects used to locate zero-, one-, two-, or threedimensional spatial locations in the dataset 2. complex 001 set of geometric primitives such that their boundaries can be represented as a union of other primitives ISO 19115:2003(E) 98 © ISO 2003 — All rights reserved Name Domain code Definition 3. composite 002 connected set of curves, solids or surfaces 4. curve 003 bounded, 1-dimensional geometric primitive, representing the continuous image of a line 5. point 004 zero-dimensional geometric primitive, representing a position but not having an extent 6. solid 005 bounded, connected 3-dimensional geometric primitive, representing the continuous image of a region of space 7. surface 006 bounded, connected 2-dimensional geometric primitive, representing the continuous image of a region of a plane B.5.16 MD_ImagingConditionCode <> Name Domain code Definition 1. MD_ImagingConditionCod e ImgCondCd code which indicates conditions which may affect the image 2. blurredImage 001 portion of the image is blurred 3. cloud 002 portion of the image is partially obscured by cloud cover 4. degradingObliquity 003 acute angle between the plane of the ecliptic (the plane of the Earth’s orbit) and the plane of the celestial equator 5. fog 004 portion of the image is partially obscured by fog 6. heavySmokeOrDust 005 portion of the image is partially obscured by heavy smoke or dust 7. night 006 image was taken at night 8. rain 007 image was taken during rainfall 9. semiDarkness 008 image was taken during semi-dark conditions—twilight conditions 10. shadow 009 portion of the image is obscured by shadow 11. snow 010 portion of the image is obscured by snow 12. terrainMasking 011 the absence of collection data of a given point or area caused by the relative location of topographic features which obstruct the collection path between the collector(s) and the subject(s) of interest B.5.17 MD_KeywordTypeCode <> Name Domain code Definition 1. MD_KeywordTypeCode KeyTypCd methods used to group similar keywords 2. discipline 001 keyword identifies a branch of instruction or specialized learning 3. place 002 keyword identifies a location 4. stratum 003 keyword identifies the layer(s) of any deposited substance 5. temporal 004 keyword identifies a time period related to the dataset 6. theme 005 keyword identifies a particular subject or topic ISO 19115:2003(E) © ISO 2003 — All rights reserved 99 B.5.18 MD_MaintenanceFrequencyCode <> Name Domain code Definition 1. MD_MaintenanceFrequen cyCode MaintFreqCd frequency with which modifications and deletions are made to the data after it is first produced 2. continual 001 data is repeatedly and frequently updated 3. daily 002 data is updated each day 4. weekly 003 data is updated on a weekly basis 5. fortnightly 004 data is updated every two weeks 6. monthly 005 data is updated each month 7. quarterly 006 data is updated every three months 8. biannually 007 data is updated twice each year 9. annually 008 data is updated every year 10. asNeeded 009 data is updated as deemed necessary 11. irregular 010 data is updated in intervals that are uneven in duration 12. notPlanned 011 there are no plans to update the data 13. unknown 012 frequency of maintenance for the data is not known B.5.19 MD_MediumFormatCode <> Name Domain code Definition 1. MD_MediumFormatCode MedFormCd method used to write to the medium 2. cpio 001 CoPy In / Out (UNIX file format and command) 3. tar 002 Tape ARchive 4. highSierra 003 high sierra file system 5. iso9660 004 information processing – volume and file structure of CD-ROM 6. iso9660RockRidge 005 rock ridge interchange protocol (UNIX) 7. iso9660AppleHFS 006 hierarchical file system (Macintosh) B.5.20 MD_MediumNameCode <> Name Domain code Definition 1. MD_MediumNameCode MedNameCd name of the medium 2. cdRom 001 read-only optical disk 3. dvd 002 digital versatile disk 4. dvdRom 003 digital versatile disk, read only 5. 3halfInchFloppy 004 3,5 inch magnetic disk 6. 5quarterInchFloppy 005 5,25 inch magnetic disk 7. 7trackTape 006 7 track magnetic tape 8. 9trackTape 007 9 track magnetic tape 9. 3480Cartridge 008 3480 cartridge tape drive 10. 3490Cartridge 009 3490 cartridge tape drive 11. 3580Cartridge 010 3580 cartridge tape drive ISO 19115:2003(E) 100 © ISO 2003 — All rights reserved Name Domain code Definition 12. 4mmCartridgeTape 011 4 millimetre magnetic tape 13. 8mmCartridgeTape 012 8 millimetre magnetic tape 14. 1quarterInchCartridgeTape 013 0,25 inch magnetic tape 15. digitalLinearTape 014 half inch cartridge streaming tape drive 16. onLine 015 direct computer linkage 17. satellite 016 linkage through a satellite communication system 18. telephoneLink 017 communication through a telephone network 19. hardcopy 018 pamphlet or leaflet giving descriptive information B.5.21 MD_ObligationCode <> Name Domain code Definition 1. MD_ObligationCode ObCd obligation of the element or entity 2. mandatory 001 element is always required 3. optional 002 element is not required 4. conditional 003 element is required when a specific condition is met B.5.22 MD_PixelOrientationCode <> Name Domain code Definition 1. MD_PixelOrientationCode PixOrientCd point in a pixel corresponding to the Earth location of the pixel 2. center 001 point halfway between the lower left and the upper right of the pixel 3. lowerLeft 002 the corner in the pixel closest to the origin of the SRS; if two are at the same distance from the origin, the one with the smallest x-value 4. lowerRight 003 next corner counterclockwise from the lower left 5. upperRight 004 next corner counterclockwise from the lower right 6. upperLeft 005 next corner counterclockwise from the upper right B.5.23 MD_ProgressCode <> Name Domain code Definition 1. MD_ProgressCode ProgCd status of the dataset or progress of a review 2. completed 001 production of the data has been completed 3. historicalArchive 002 data has been stored in an offline storage facility 4. obsolete 003 data is no longer relevant 5. onGoing 004 data is continually being updated 6. planned 005 fixed date has been established upon or by which the data will be created or updated 7. required 006 data needs to be generated or updated 8. underDevelopment 007 data is currently in the process of being created ISO 19115:2003(E) © ISO 2003 — All rights reserved 101 B.5.24 MD_RestrictionCode <> Name Domain code Definition 1. MD_RestrictionCode RestrictCd limitation(s) placed upon the access or use of the data 2. copyright 001 exclusive right to the publication, production, or sale of the rights to a literary, dramatic, musical, or artistic work, or to the use of a commercial print or label, granted by law for a specified period of time to an author, composer, artist, distributor 3. patent 002 government has granted exclusive right to make, sell, use or license an invention or discovery 4. patentPending 003 produced or sold information awaiting a patent 5. trademark 004 a name, symbol, or other device identifying a product, officially registered and legally restricted to the use of the owner or manufacturer 6. license 005 formal permission to do something 7. intellectualPropertyRights 006 rights to financial benefit from and control of distribution of non-tangible property that is a result of creativity 8. restricted 007 withheld from general circulation or disclosure 9. otherRestrictions 008 limitation not listed B.5.25 MD_ScopeCode <> Name Domain code Definition 1. MD_ScopeCode ScopeCd class of information to which the referencing entity applies 2. attribute 001 information applies to the attribute class 3. attributeType 002 information applies to the characteristic of a feature 4. collectionHardware 003 information applies to the collection hardware class 5. collectionSession 004 information applies to the collection session 6. dataset 005 information applies to the dataset 7. series 006 information applies to the series 8. nonGeographicDataset 007 information applies to non-geographic data 9. dimensionGroup 008 information applies to a dimension group 10. feature 009 information applies to a feature 11. featureType 010 information applies to a feature type 12. propertyType 011 information applies to a property type 13. fieldSession 012 information applies to a field session 14. software 013 information applies to a computer program or routine 15. service 014 information applies to a capability which a service provider entity makes available to a service user entity through a set of interfaces that define a behaviour, such as a use case 16. model 015 information applies to a copy or imitation of an existing or hypothetical object 17. tile 016 information applies to a tile, a spatial subset of geographic data ISO 19115:2003(E) 102 © ISO 2003 — All rights reserved B.5.26 MD_SpatialRepresentationTypeCode <> Name Domain code Definition 1. MD_SpatialRepresentation TypeCode SpatRepTypCd method used to represent geographic information in the dataset 2. vector 001 vector data is used to represent geographic data 3. grid 002 grid data is used to represent geographic data 4. textTable 003 textual or tabular data is used to represent geographic data 5. tin 004 triangulated irregular network 6. stereoModel 005 three-dimensional view formed by the intersecting homologous rays of an overlapping pair of images 7. video 006 scene from a video recording B.5.27 MD_TopicCategoryCode << Enumeration>> Name Domain code Definition 1. MD_TopicCategoryCode TopicCatCd high-level geographic data thematic classification to assist in the grouping and search of available geographic data sets. Can be used to group keywords as well. Listed examples are not exhaustive. NOTE It is understood there are overlaps between general categories and the user is encouraged to select the one most appropriate. 2. farming 001 rearing of animals and/or cultivation of plants Examples: agriculture, irrigation, aquaculture, plantations, herding, pests and diseases affecting crops and livestock 3. biota 002 flora and/or fauna in natural environment Examples: wildlife, vegetation, biological sciences, ecology, wilderness, sealife, wetlands, habitat 4. boundaries 003 legal land descriptions Examples: political and administrative boundaries 5. climatologyMeteorologyAt mosphere 004 processes and phenomena of the atmosphere Examples: cloud cover, weather, climate, atmospheric conditions, climate change, precipitation 6. economy 005 economic activities, conditions and employment Examples: production, labour, revenue, commerce, industry, tourism and ecotourism, forestry, fisheries, commercial or subsistence hunting, exploration and exploitation of resources such as minerals, oil and gas 7. elevation 006 height above or below sea level Examples: altitude, bathymetry, digital elevation models, slope, derived products 8. environment 007 environmental resources, protection and conservation Examples: environmental pollution, waste storage and treatment, environmental impact assessment, monitoring environmental risk, nature reserves, landscape 9. geoscientificInformation 008 information pertaining to earth sciences Examples: geophysical features and processes, geology, minerals, sciences dealing with the composition, structure and origin of the earth’s rocks, risks of earthquakes, volcanic activity, landslides, gravity information, soils, permafrost, hydrogeology, erosion 10. health 009 health, health services, human ecology, and safety Examples: disease and illness, factors affecting health, hygiene, substance abuse, mental and physical health, health services ISO 19115:2003(E) © ISO 2003 — All rights reserved 103 Name Domain code Definition 11. imageryBaseMapsEarthCo ver 010 base maps Examples: land cover, topographic maps, imagery, unclassified images, annotations 12. intelligenceMilitary 011 military bases, structures, activities Examples: barracks, training grounds, military transportation, information collection 13. inlandWaters 012 inland water features, drainage systems and their characteristics Examples: rivers and glaciers, salt lakes, water utilization plans, dams, currents, floods, water quality, hydrographic charts 14. location 013 positional information and services Examples: addresses, geodetic networks, control points, postal zones and services, place names 15. oceans 014 features and characteristics of salt water bodies (excluding inland waters) Examples: tides, tidal waves, coastal information, reefs 16. planningCadastre 015 information used for appropriate actions for future use of the land Examples: land use maps, zoning maps, cadastral surveys, land ownership 17. society 016 characteristics of society and cultures Examples: settlements, anthropology, archaeology, education, traditional beliefs, manners and customs, demographic data, recreational areas and activities, social impact assessments, crime and justice, census information 18. structure 017 man-made construction Examples: buildings, museums, churches, factories, housing, monuments, shops, towers 19. transportation 018 means and aids for conveying persons and/or goods Examples: roads, airports/airstrips, shipping routes, tunnels, nautical charts, vehicle or vessel location, aeronautical charts, railways 20. utilitiesCommunication 019 energy, water and waste systems and communications infrastructure and services Examples: hydroelectricity, geothermal, solar and nuclear sources of energy, water purification and distribution, sewage collection and disposal, electricity and gas distribution, data communication, telecommunication, radio, communication networks ISO 19115:2003(E) 104 © ISO 2003 — All rights reserved B.5.28 MD_TopologyLevelCode <> Name Domain code Definition 1. MD_TopologyLevelCode TopoLevCd degree of complexity of the spatial relationships 2. geometryOnly 001 geometry objects without any additional structure which describes topology 3. topology1D 002 1-dimensional topological complex – commonly called “chain-node” topology 4. planarGraph 003 1-dimensional topological complex that is planar. (A planar graph is a graph that can be drawn in a plane in such a way that no two edges intersect except at a vertex.) 5. fullPlanarGraph 004 2-dimensional topological complex that is planar. (A 2-dimensional topological complex is commonly called “full topology” in a cartographic 2D environment.) 6. surfaceGraph 005 1-dimensional topological complex that is isomorphic to a subset of a surface. (A geometric complex is isomorphic to a topological complex if their elements are in a one-to-one, dimensional-and boundry-preserving correspondence to one another.) 7. fullSurfaceGraph 006 2-dimensional topological complex that is isomorphic to a subset of a surface 8. topology3D 007 3-dimensional topological complex. (A topological complex is a collection of topological primitives that are closed under the boundary operations.) 9. fullTopology3D 008 complete coverage of a 3D Euclidean coordinate space 10. abstract 009 topological complex without any specified geometric realisation ISO 19115:2003(E) © ISO 2003 — All rights reserved 105 Annex C (normative) Metadata extensions and profiles C.1 Background Annexes A, B and Clause 6 of this International Standard provide standard metadata and an associated structure that will serve a wide variety of digital geographic data. The definitions and domain values are intended to be sufficiently generic to satisfy the metadata needs of various disciplines. However, the very diversity of data means that generic metadata may not accommodate all applications. This annex provides the rules for defining and applying additional metadata to better serve special user needs. C.2 Types of extensions The following types of extensions shall be allowed: 1) adding a new metadata section; 2) creating a new metadata codelist to replace the domain of an existing metadata element that has “free text” listed as its domain value; 3) creating new metadata codelist elements (expanding a codelist); 4) adding a new metadata element; 5) adding a new metadata entity; 6) imposing a more stringent obligation on an existing metadata element; 7) imposing a more restrictive domain on an existing metadata element. C.3 Creating an extension Prior to the creation of extended metadata a careful review of the existing metadata within this International Standard must be performed to confirm that suitable metadata does not already exist. For each extended metadata section, entity, and/or element, the name, short name, definition, obligation, condition, maximum occurrence, data type, and domain values shall be defined. Relationships as provided in Annex A shall be defined so a structure and schema can be determined. C.4 Rules for creating an extension 1) Extended metadata elements shall not be used to change the name, definition or data type of an existing element. 2) Extended metadata may be defined as entities and may include extended and existing metadata elements as components. ISO 19115:2003(E) 106 © ISO 2003 — All rights reserved 3) An extension is permitted to impose more stringent obligation on existing metadata elements than the standard requires. (Metadata elements that are optional in the standard may be mandatory in an extension.) 4) An extension is permitted to contain metadata elements with domains that are more restrictive than the standard. (Metadata elements whose domains have free text in the standard may have a closed list of appropriate values in the profile.) 5) An extension is permitted to restrict the use of domain values allowed by the standard. (If the standard contains five values in the domain of an existing metadata element, the extension may specify that its domain consists of three domain values. The extension shall require that the user select a value from the three domain values.) 6) An extension is permitted to expand the number of values in a codelist. 7) An extension shall not permit anything not allowed by the standard. C.5 Community profile If the information to be added is extensive, involving the creation of many metadata elements within a metadata entity, specific to a discipline or application, co-ordination of the proposed extension via user groups and creation of a community profile is recommended. This International Standard defines almost 300 metadata elements, with most of these being listed as "optional". They are explicitly defined in order to help users understand exactly what is being described. Individual communities, nations, or organizations may develop a "community profile" of this International Standard. They will make a select set of metadata elements mandatory. A given metadata element (e.g., the “price” of a dataset) may be established as "mandatory" for a certain community that will always want that metadata element reported. A community of users may want to establish additional metadata elements that are not in this International Standard. For example, a community may want to develop metadata elements for the status of datasets within their system to help manage production. However, these added elements will not be known outside the community unless they are published. A community profile should establish field sizes and domains for all metadata elements. If one system within a community uses thirty-two (32) characters for the title of a dataset and another system handles eight (8) characters, interoperability will not be achieved. Standardizing selected domains within a community is important to allow more efficient searches and better system control. See ISO 19106 for more information on community profiles. Figure C.1 illustrates the relationship between the Core Metadata components, the comprehensive metadata application profile and national, regional, domain specific or organizational profiles. ISO 19115:2003(E) © ISO 2003 — All rights reserved 107 Comprehensive metadata profile Extended metadata Community Profile 1 Core metadata components Figure C.1 — Metadata community profile The inner circle contains the core metadata components. The comprehensive metadata includes the core metadata components. A community profile shall contain the core metadata components, but not necessarily all the other metadata components. Additionally it may contain metadata extensions (shaded area) which shall be defined following the metadata extension rules in this annex. C.6 Rules for creating a profile 1) Before creating a profile, the user shall check registered profiles. 2) A profile must adhere to the rules for defining an extension. 3) A profile shall not change the name, definition, or data type of a metadata element. 4) A profile shall include:  the core metadata collected for a digital geographic dataset  all mandatory metadata elements in all mandatory sections  all conditional metadata elements in all mandatory sections, if the dataset meets the condition required by the metadata element  all mandatory metadata elements in all conditional sections, if the dataset meets the condition required by the section  all conditional metadata elements in all conditional sections, if the dataset meets the condition required by the metadata element and the section 5) Relationships, as provided in Annex A, shall be defined so that a structure and schema can be determined. 6) A profile shall be made available to anyone receiving metadata that was created according to that profile. ISO 19115:2003(E) 108 © ISO 2003 — All rights reserved Annex D (normative) Abstract test suite D.1 Abstract test suite This abstract test suite applies to the comprehensive profile and any profile derived from this International Standard. Metadata shall be provided as specified in Clause 6 and Annexes A and B. User-defined metadata shall be defined and provided as specified in Annex C. User-defined metadata shall satisfy the requirements as stated in D.3. D.2 Metadata test suite D.2.1 Test case identifier: Completeness test a) Test Purpose: to determine conformance by the inclusion of all metadata sections, metadata entities, and metadata elements that are specified with an obligation of “mandatory” or mandatory under the conditions specified. NOTE Many elements designated as mandatory are contained within optional entities. These elements become mandatory only when their containing entity is used. b) Test Method: a comparison between this International Standard and a subject metadata set to be tested shall be performed to determine if all metadata defined as mandatory in annex B are present. A comparison test shall also be performed to determine if all metadata elements defined as conditional in Annex B are present if the conditions set out in this International Standard apply. c) Reference: Annex B. d) Test Type: Basic. The following test cases apply at all levels of obligation – mandatory, conditional, and optional. D.2.2 Test case identifier: Maximum occurrence test a) Test Purpose: to ensure each metadata element occurs no more than the number of times specified in this International Standard. b) Test Method: examine a subject metadata set for the number of occurrences of each metadata section, metadata entity, and metadata element provided. The number of occurrences for each shall be compared with its “Maximum Occurrences” attribute specified in Annex B. c) Reference: Annex B. d) Test Type: Basic. D.2.3 Test case identifier: Short name test a) Test Purpose: to determine if short names used in a subject metadata set fall within the domain specified within this International Standard. ISO 19115:2003(E) © ISO 2003 — All rights reserved 109 b) Test Method: the short name for each metadata element in a subject metadata set is examined to determine if it is defined in this International Standard. c) Reference: Annex B. d) Test Type: Basic. D.2.4 Test case identifier: Data type test a) Test Purpose: to determine if each metadata element within a subject metadata set uses the specified data type. b) Test Method: the value of each provided metadata element is tested to ensure its data type adheres to the data type specified. c) Reference: Annex B. d) Test Type: Basic. D.2.5 Test case identifier: Domain test a) Test Purpose: to determine if each provided metadata element within a subject metadata set falls within the specified domain. b) Test Method: the values of each metadata element are tested to ensure they fall within the specified domain. c) Reference: Annex B. d) Test Type: Basic. D.2.6 Test case identifier: Schema test a) Test Purpose: to determine if a subject metadata set follows the schema specified in this International Standard. b) Test Method: test each metadata element and ensure it is contained within the specified metadata entity. c) Reference: Annex B. d) Test Type: Basic. D.3 User-defined extension metadata test suite D.3.1 Test case identifier: Exclusiveness test a) Test Purpose: to verify that each user-defined metadata section, metadata entity, and metadata element is unique and not already defined in this International Standard. b) Test Method: each user-defined metadata entity and metadata element is tested to ensure it is unique and not previously used. c) Reference: Annex B. d) Test Type: Basic. ISO 19115:2003(E) 110 © ISO 2003 — All rights reserved D.3.2 Test case identifier: Definition test a) Test Purpose: to verify that user-defined metadata entities and metadata elements have been defined as specified in this International Standard. b) Test Method: each user-defined metadata entity and metadata element is tested to ensure that all attributes have been defined. c) Reference: Annex B. d) Test Type: Basic. D.3.3 Test case identifier: Standard metadata test a) Test Purpose: to verify that user-defined metadata within a subject metadata set fulfils the same requirements as ISO 19115 standard metadata. b) Test Method: all user-defined metadata in a subject metadata set is tested in accordance with D.2 of this International Standard. c) Reference: 2.3. d) Test Type: Basic. D.4 Metadata profiles D.4.1 Test case identifier: Metadata profiles a) Test Purpose: to verify that a profile follows the rules specified in this International Standard. b) Test Method: apply tests defined in Clauses D.2 and D.3 of this International Standard. c) Reference: 2.2. d) Test Type: Basic. ISO 19115:2003(E) © ISO 2003 — All rights reserved 111 Annex E (normative) Comprehensive dataset metadata application profile E.1 Comprehensive dataset metadata application schema The ISO 19100 series of geographic information standards define, in the abstract, the classes of information needed to: 1) model geographic phenomena; and 2) manipulate, manage and understand these models. In order to implement these standards, profiles must be developed. Typically, an information community with special requirements will develop profiles that use the appropriate parts provided by this series of standards. This comprehensive dataset metadata profile is a basic profile. It provides an international standardized profile applicable to a wide range of information communities. Use of this profile will promote interoperability between information communities. The comprehensive dataset metadata profile is a subset of packages, classes, attributes and relationships defined in Annexes A and B. Only the classes, attributes and relationships necessary to fulfill the requirements for general-purpose dataset metadata are present. The following are changes that were made to create the profile: • Removed MD_ServiceIdentification class from the Identification information package • Replaced simple conceptual types (Binary, Boolean, CharacterString, Date, DateTime, GenericName, Integer, and RecordType) with ISO/TS 19103-equivalent types • Replaced simple conceptual type, CharacterString, with the newly-defined XML type, nonNullString (based on the ISO/TS 19103 CharacterString type), in cases where the attribute is not optional • Replaced simple conceptual type Real with newly-defined types (decimalLatitude, decimalLongitude, nonNegativeDecimal, and positiveDecimal), which are based on ISO/TS 19103 type, Decimal, in contextually appropriate cases, otherwise with the ISO/TS 19103 type, Decimal • Replaced simple conceptual type TM_PeriodDuration with the XSD-equivalent type, duration • Replaced complex conceptual types MemberName and Record with ISO/TS 19103-equivalent types • Replaced complex conceptual types GF_AttributeType and GF_FeatureType with ISO 19109-equivalent types • Replaced complex conceptual types (Angle, Distance, GM_Object, GM_Point, Measure, TM_Primitive and UomLength ) with newly-defined XML-equivalent types • Removed the Metadata application package (which contained classes of geographic information to which metadata applies – eg. DS_Aggregate, DS_Dataset, DS_Initiative, DS_OtherAggregate) • Removed the aggregate relationship between MD_Distribution and MD_Format • Constrained the implementation of the EX_BoundingPolygon’s polygon attribute to be a Box (upper and lower corner Points) or Polygon (outer and inner bounding Rings) • Changed all non-conforming class associations (e.g. two-way association, one-way ByReference or Unspecified aggregation) to be one-way ByValue aggregation relationships ISO 19115:2003(E) 112 © ISO 2003 — All rights reserved E.2 Comprehensive dataset metadata profile – UML model The comprehensive dataset metadata profile is presented in a UML metadata application schema, Figure E.1. The attributes within each class and codelist have not been displayed in the model in order to simplify the diagram. Note that the diagram does not reference the relevant application schemas for the conceptual model since all conceptual types from these schemas have been replaced with other XML equivalent types. The models of these XML equivalent types are also not displayed in order to simplify the diagram. MD_LegalConstraints (from Constraint information) MD_SecurityConstraints (from Constraint information) MD_CRS (from Reference system information) MD_VectorSpatialRepresentation (from Spatial representation information) MD_CoverageDescription (from Content information) MD_GridSpatialRepresentation (from Spatial representation information) MD_FeatureCatalogueDescription (from Content information) <> MD_SpatialRepresentation (from Spatial representation information) MD_Distribution (from Distribution information) MD_MetadataExtensionInformation (from Metadata extension information) MD_ApplicationSchemaInformation (from Application schema information) MD_Constraints (from Constraint information) MD_PortrayalCatalogueReference (from Portrayal catalogue information) MD_DataIdentification (from Identification information) MD_ReferenceSystem (from Reference system information) DQ_DataQuality (from Data quality information) MD_Metadata (from Metadata entity set information) 0..* +spatialRepresentationInfo 0..* +contentInfo 0..1 +distributionInfo 0..* +metadataExtensionInfo 0..* +applicationSchemaInfo 0..1 +metadataMaintenance 0..* +metadataConstraints 0..* +portrayalCatalogueInfo 1..* +identificationInfo 0..* +referenceSystemInfo 0..* +dataQualityInfo <> MD_Identification (from Identification information) MD_MaintenanceInformation (from Mantenance information) <> MD_ContentInformatin (from Content information) Figure E.1 — Comprehensive dataset metadata profile ISO 19115:2003(E) © ISO 2003 — All rights reserved 113 Annex F (informative) Metadata extension methodology F.1 Metadata extensions methodology The following nine-stage methodology should be followed in order to define additional metadata. F.2 Review of existing metadata elements (Stage 1) Stage 1 of the methodology is intended to ensure that only valid extensions are made to the standard set defined by ISO 19115. A full review of the standard set of metadata described in Annex B and any formally documented/published profiles should be conducted. This review should not only cover the metadata entity/element name, but also the definition, data type, obligation, domain, and the maximum number of occurrences. It is possible that a new entity/element is not required as an existing entity/element meets the requirements. If a suitable entity/element can be identified, then the relationships of this entity/element should be reviewed with those in Annex A to ensure that the candidate entity/element is not precluded by excluded combinations with other entities/elements. METHOD: EITHER I) An existing metadata element or entity is identified as meeting the requirement. ACTION Utilize the existing metadata entity/element, no metadata extensions are required. II) A new section of metadata entities is needed to meet the new requirement. ACTION - Go to Stage 2. III) An existing metadata element is identified whose domain could logically be restricted to meet the identified requirement by taking the action of limiting the existing “free text” domain. ACTION – Go to Stage 3. IV) An existing metadata element is identified whose domain could logically be expanded to meet the identified requirement by taking the action of adding values to the existing codelist. ACTION – Go to Stage 4. V) A new metadata element is needed to meet the requirement. Check that no existing metadata element could be modified to meet the requirement. ACTION - Go to Stage 5. VI) A new metadata entity is needed to meet the requirement. A metadata entity is a group of related elements, that in conjunction, meet the needs of the new requirement. Check that no existing metadata entity could be modified to meet the requirements by the addition of metadata elements. ACTION - Go to Stage 6. VII) An existing metadata element or entity or section meets the requirement, but the profile requires that a more stringent obligation is applied than that defined in this International Standard. The metadata obligations defined in the ISO 19115 cannot be relaxed in a profile. ACTION - Go to Stage 7. ISO 19115:2003(E) 114 © ISO 2003 — All rights reserved VIII) An existing metadata element meets the requirements, but the domain required by the profile is a subset of the ISO 19115 domain. ACTION - Go to Stage 8. F.3 Definition of a new metadata section (Stage 2) A new metadata section is to be defined, but no existing metadata section from ISO 19115 is suitable, nor can any existing section be expanded to meet the requirement. In this case, a new metadata section may be defined. The new metadata section should be defined in a style consistent with that of ISO 19115 (which is based on ISO/IEC 11179-3). METHOD: I) Go to Stage 5 to define the new metadata elements required to populate the section. II) Go to Stage 6 to define the new metadata entities required to populate the section. III) Go to Stage 9. F.4 Definition of a new metadata codelist (Stage 3) An existing metadata element is suitable, given that the “free text” domain of the identified element is restricted. No existing metadata codelist can be identified within the metadata standard that meets the requirements. In this circumstance a new metadata codelist may be defined to meet the specific requirements of the profile. The new metadata codelist should be defined in a style consistent with that of ISO 19115 (which is based on ISO/IEC 11179-3). METHOD: I) Define the new metadata codelist in terms of Definition (B.1.4), Name (B.1.2), and Short Name (B.1.3). The definition of the new codelist should be done so as to be consistent with the existing codelists which can be found in Clause B.5. II) Define the new metadata codelist elements in terms of Definition (B.1.4) and Domain code and Short Name (B.1.3). This definition should also be done so as to be consistent with the existing codelist elements found in Clause B.5. III) Got to Stage 9. F.5 Definition of a new metadata codelist element (Stage 4) An existing metadata element is suitable, given that the metadata codelist of the identified element is expanded. The new metadata codelist elements should be defined with reference to the existing set of elements. The expanded metadata codelist must be a logical expansion of the standard set of values. If the proposed new metadata domain element does not logically build upon the original domain then it may be that the identified element is not suitable for expansion, and the developer should return to Stage 1. To document the new metadata codelist element go to Stage 9. ISO 19115:2003(E) © ISO 2003 — All rights reserved 115 F.6 Definition of a new metadata element (Stage 5) No existing metadata element can be identified within the metadata standard that meets the requirements. In this circumstance a new metadata element may be defined to meet the specific requirements of the profile. The new metadata element should be defined in a style consistent with that of ISO 19115 (which is based on ISO/IEC 11179-3). METHOD: I) Using the metadata schema described in Annex A and the data dictionary given in Annex B and any existing extensions to the metadata standard, identify the existing metadata entity to which the new element should be added. If no suitable grouping can be found then go to Stage 6. II) Define the new metadata element in terms of the extended element information as described in B.2.11.2: name, shortName, domainCode, definition, obligation, condition, dataType, domainValue, maximumOccurence, parentEntity, rule, rationale and source. Identify any excluded metadata relationships with the newly defined element. See Annex A for the metadata UML model. III) Utilize the new metadata element to meet the requirement. IV) Go to Stage 9. F.7 Definition of a new metadata entity (Stage 6) No existing metadata element or entity can be identified within the metadata standard that meets the requirements, nor can an existing metadata entity be modified by the addition of simple metadata elements to meet the requirements. In this circumstance a new metadata entity may be defined to meet the specific requirements of the profile. The new metadata entity should be defined in a style consistent with that of ISO 19115 (which is based on ISO/IEC 11179-3). METHOD: I) Using the schema described in Annex A and the data dictionary given in Annex B and any existing extensions to the metadata standard, identify which grouping of metadata best describe the function of the new Metadata entity. Choose from: 6.3.2.1 Metadata entity set 6.3.2.2 Identification 6.3.2.3 Constraints 6.3.2.4 Data quality 6.3.2.5 Maintenance 6.3.2.6 Spatial representation 6.3.2.7 Reference system 6.3.2.8 Content ISO 19115:2003(E) 116 © ISO 2003 — All rights reserved 6.3.2.9 Portrayal catalogue 6.3.2.10 Distribution 6.3.2.11 Metadata extension 6.3.2.12 Application schema 6.4.1 Extent 6.4.2 Citation and responsible party If no suitable grouping can be found then go to Stage 2. II) Define the new metadata entity in terms of the extended element information as described in B.2.11.2: name, shortName, domainCode, definition, obligation, condition, dataType, domainValue, maximumOccurence, parentEntity, rule, rationale and source. Data type is ‘Class’ for a metadata entity. III) Identify the elements that form the metadata entity, by following the steps outlined in Stage 5. IV) Identify any excluded metadata relationships with the newly defined entity. See Annex A for the UML metadata schema models. V) Utilize the new metadata entity to meet the requirement. VI) Go to Stage 9. F.8 Definition of a more stringent metadata obligation (Stage 7) An existing metadata element, entity or section meets the requirement, but the profile requires that the obligation category is more stringent than that defined in the ISO standard. (Where optional (O) is the least and mandatory (M) the most stringent obligation category). METHOD: I) Identify the new Obligation/Condition (B.1.5) value to be applied to the element, entity or section. If the chosen obligation is conditional, then the conditions under which the metadata is to be applied should be identified. The rules for creating conditions can be found in B.1.5.3. II) Go to Stage 9. F.9 Definition of more restrictive metadata codelist (Stage 8) An existing metadata codelist meets the requirement, but the profile requires that the elements defined for the codelist be a restricted subset of the standard domain defined in the ISO standard. METHOD: I) Identify the restricted elements needed to meet the new requirement. II) Go to Stage 9. ISO 19115:2003(E) © ISO 2003 — All rights reserved 117 F.10 Documentation of metadata extensions (Stage 9) Once new metadata entities/elements have been defined, it is essential that the changes from the base standard be recorded clearly. The modifications must be recorded in the profile document, in a standard format, which is derived from the ISO 19115 document itself and issued as a document along with the dataset and the metadata. Metadata issued according to the profile must also record the changes to the standard metadata set by completing the metadata extension fields defined in ISO 19115 (B.2.11.2). Seven possible types of extensions may be documented: • Definition of a new metadata section. • Definition of new metadata codelist to replace a “free text” domain. • Definition of additional metadata codelist elements. • Definition of a new metadata element. • Definition of new metadata entity. • Definition of a restricted metadata domain. • Definition of more stringent metadata obligation. METHOD: I) Update the metadata extension information field in the metadata for the product. This field should describe the extensions made to the metadata, including a definition of new elements. II) IF a new metadata section is defined: Create a UML schema for the new metadata section based on those from Annex A. III) IF new metadata entities defined: In accordance with ISO/IEC 11179 and using B.2.11.2 as a template, record the new metadata entity description in terms of name, shortName, domainCode, definition, obligation, condition, dataType, domainValue, maximumOccurence, parentEntity, rule, rationale and source. Update the appropriate UML schemas in Annex A with the new extension information. IV) IF new metadata elements defined: In accordance with ISO/IEC 11179 and using B.2.11.2 as a template, record the new metadata elements description in terms of name, shortName, definition, obligation, condition, dataType, domainValue, maximumOccurence, parentEntity, rule, rationale and source. Update the appropriate UML schemas in Annex A with the new extension information. V) IF an existing metadata codelist expanded: In accordance with ISO/IEC 11179 and using B.2.11.2 and B.5 identify the metadata code list and record the new domain elements as described in B.2.11.2. ISO 19115:2003(E) 118 © ISO 2003 — All rights reserved VI) IF new metadata codelist created: In accordance with ISO/IEC 11179 and using B.2.11.2 and B.5 as a template, record the new metadata codelist in terms of name, shortName, definition and dataType. Record any new metadata codelist elements as described in B.2.11.2. VII) IF an existing metadata element domain restricted: In accordance with ISO/IEC 11179 and using Clause B.1 identify the metadata element and record the modified domain set in terms of dataType and domainValue. VIII) IF an existing metadata element or entity obligation made more stringent. In accordance with ISO/IEC 11179 and using Annex B identify the metadata entity/element and record the modified obligation characteristics in terms of Obligation/Condition (B.1.5). Update the appropriate UML schemas in Annex A with the new extension information. ISO 19115:2003(E) © ISO 2003 — All rights reserved 119 Annex G (informative) Metadata implementation G.1 Background G.1.1 Problem statement The body of this International Standard defines the content of a set of metadata elements, their definitions, data types, and inherent dependencies. The logical model of the metadata specifies the content and not the form of implementation or the form of presentation. A primary goal in the management of metadata for geographic data is the ability to access the metadata and the related spatial data it describes. This requires software implementations using common encoding methods to achieve operational use of the metadata for geographic data. Implementation methods are required to provide for the exchange of metadata between data management systems, the presentation of the metadata element tags in a variety of forms and languages, and to ensure means to assess the conformance of metadata produced and made available. G.1.2 Scope and objectives This annex provides an overview of methods for the encoding of metadata element structure and content for the purposes of search and retrieval, metadata exchange, and presentation. The intent of this International Standard is to permit flexibility in the local management of the metadata while standardizing the understanding of metadata for geographic data. The intent of this implementation annex is to provide guidance on the creation of a metadata for geographic data service (Clearinghouse) on a local or wide-area network. G.1.3 Granularity of spatial data supported The notion of cataloguing a set of related documents together in a discoverable series is common in map catalogues. With digital spatial data, the definition of what constitutes a “dataset” is more problematic and reflects the institutional and software environments of the originating organization. Common metadata can be derived for a series of related spatial datasets, and such metadata is generally relevant or can be inherited by each of the dataset instances. Software to support this inheritance of metadata for geographic data within a cataloguing system can simplify data entry, update and reporting. There is a potential hierarchy of re-usable metadata that can be employed in implementing a metadata collection. By creating several levels of abstraction, a linked hierarchy can assist in filtering or targeting user queries to the requested level of detail. The hierarchy should not necessarily be interpreted to require multiple copies of metadata being managed on-line. Conversely, the definition of general metadata can be supplemented by spatially specific metadata that, when queried, either inherits or overrides the general case. Through use of pointers this method can reduce the redundancy of metadata managed at a site and provide for different views of the holdings by users. This hierarchy of metadata can be graphically represented as shown in Figure G.1. ISO 19115:2003(E) 120 © ISO 2003 — All rights reserved Dataset series Dataset Dataset Feature type Attribute type Feature instance Attribute instance Figure G.1 — Metadata hierarchy G.2 Metadata hierarchy levels G.2.1 Dataset series metadata (optional) A dataset series is a collection of spatial data that shares similar characteristics of theme, source date, resolution, and methodology. The exact definition of what constitutes a series entry will be determined by the data provider. Examples of dataset series metadata entries may include:  A flight line of digital aerial photographs collected during a single flight with one camera and film type. A continuous scan swathe collected from a satellite using the same sensors on a single orbital pass.  A collection of raster map data captured from a common series of paper maps.  A collection of vector datasets depicting surface hydrography with associated attribution for multiple administrative areas within a country. The creation of a “dataset series” metadata level is an optional feature that allows users to consult higher-level characteristics for data search. The definition of this type of metadata may be adequate for the initial characterization of available spatial data, but may not be adequate for detailed assessment of data quality of specific datasets. G.2.2 Dataset metadata For the purposes of this International Standard, a dataset should be a consistent spatial data product instance that can be generated or made available by a spatial data distributor. A dataset may be a member of a data series, as defined in the previous subclause. A dataset may be composed of a set of identified feature types and instances, and attribute types and instances as described in the following four subclauses. On a demand basis, metadata from series and dataset information will be merged to present the user with a view of the metadata at the dataset level of abstraction. Metadata for which no hierarchy is listed are interpreted to be “dataset” metadata, by default. ISO 19115:2003(E) © ISO 2003 — All rights reserved 121 G.2.3 Feature type metadata (optional) Constructs known as features are grouped with common characteristics. Spatial data services may elect to support feature type-level metadata where it is available and make such metadata available for query or retrieval. Feature Type -level metadata, together with feature instance-, attribute type- and attribute instancelevel metadata, will be grouped into datasets, as defined in the previous subclause. Examples of feature type metadata entries may include:  All bridges within a dataset. G.2.4 Feature instance metadata (optional) Feature instances are spatial constructs (features) that have a direct correspondence with a real world object. Spatial data services may elect to support feature instance-level metadata where it is available and make such metadata available for query or retrieval. Feature Instance-level metadata, together with feature type-, attribute type- and attribute instance-level metadata, will be grouped into datasets, as defined in G.2.2. Examples of feature instance metadata entries may include:  The Sydney harbour bridge.  The Golden Gate bridge, in San Francisco. G.2.5 Attribute type metadata (optional) Attribute types are the digital parameters that describe a common aspect of grouped spatial primitives (0-, 1-, 2-, and 3-dimensional geometric objects). Spatial data services may elect to support attribute type-level metadata where it is available and make such metadata available for query or retrieval. Attribute type-level metadata, together with feature type-, feature instance-, and attribute instance-level metadata, will be grouped into datasets, as defined in G.2.2. Examples of attribute type metadata entries may include:  Overhead clearance associated with a bridge. G.2.6 Attribute instance metadata (optional) Attribute instances are the digital parameters that describe an aspect of a feature instance. Spatial data services may elect to support attribute instance-level metadata where it is available and make such metadata available for query or retrieval. Attribute instance-level metadata, together with feature type-, feature instance-, and attribute type-level metadata, will be grouped into datasets, as defined in G.2.2. Examples of attribute instance metadata entries may include:  The overhead clearance associated with a specific bridge across a road. ISO 19115:2003(E) 122 © ISO 2003 — All rights reserved Annex H (informative) Hierarchical levels of metadata H.1 Levels of metadata At first sight, it can appear that there are many levels of metadata to be maintained. In the majority of cases, this is not so, as only metadata exceptions are defined at lower levels. If the metadata values are not changed, then the metadata is aggregated at a high level. It is anticipated that this situation would be the most common, with additional levels of metadata only being defined as the original data is maintained over a period of time. When the lower levels of the metadata hierarchy are populated, only the revised metadata values are recorded. So, if the distributor of the data remains the same, this need not be carried down the structure. In order to clarify this concept, the following example follows the life cycle of an example set of geographic data. H.2 Example 1) Consider a geographic data provider generating vector mapping data for three Administrative areas (A, B and C). Initially the vector mapping was generated using a common series of paper maps, which were processed in the same way into a vector format. The bulk of the metadata for this initial data could be carried at a single level, (Dataset series). This metadata would describe the quality, citation, source, processing, of the data for the three administrative areas. So, the metadata could be carried exclusively at Dataset Series level. Dataset series – Administrative areas A, B & C Metadata entity set Identification Citation and responsible party Extent Constraints Data quality Maintenance Spatial representation Reference system Content Portrayal catalogue Distribution Metadata extension Application schema 2) After some time alternate vector mapping of Administrative area A becomes available. The metadata would then be extended for Administrative area A, to describe the new quality date values. These values would supersede those given for the Dataset series, but only for Administrative area A. The metadata for B and C would remain unchanged. This new metadata would be recorded at Dataset level. So, additional metadata is required at Dataset level to describe the new Administrative area A data. The minimum level of metadata required to reflect this change would be: ISO 19115:2003(E) © ISO 2003 — All rights reserved 123 Dataset series – Administrative areas A, B & C Metadata entity set Identification Citation and responsible party Extent Constraints Data quality Maintenance Spatial representation Reference system Content Portrayal catalogue Distribution Metadata extension Application schema Dataset - Administrative area A Dataset Identification Citation and Responsible Party Extent 3) Eventually further data becomes available for Administrative area A, with a complete re-survey of the road network. Again this implies new metadata for the affected feature types. This metadata would be carried at Feature type level for Administrative area A. All other metadata relating to other feature types remains unaffected. Only the metadata for roads in Administrative area A is modified. This road metadata is recorded at Feature type level. So, additional metadata is required at Feature type level to describe the new Administrative area A road data. The minimum level of metadata required to reflect this change would be: Dataset series – Administrative areas A, B & C Metadata entity set Identification Citation and responsible party Extent Constraints Data quality Maintenance Spatial representation Reference system Content Portrayal catalogue Distribution Metadata extension Application schema Dataset – Administrative area A Dataset Identification Citation and Responsible Party Extent Feature type - Administrative area A - Road network Dataset Identification Citation and Responsible Party 4) An anomaly in the road survey is identified, in that all Overhead clearances for the Administrative area A have been surveyed to the nearest metre. These are re-surveyed to the nearest decimetre. This re-survey implies new metadata for the affected attribute type ‘Overhead Clearance’. All other ISO 19115:2003(E) 124 © ISO 2003 — All rights reserved metadata for Administrative area A remains unaffected. This ‘Overhead Clearance’ metadata is recorded at Attribute Type level. So, additional metadata is required at Attribute type level to describe the new Administrative area A ‘Overhead Clearance’ data. The minimum level of metadata required reflecting this change would be: Dataset series – Administrative areas A, B & C Metadata entity set Identification Citation and responsible party Extent Constraints Data quality Maintenance Spatial representation Reference system Content Portrayal catalogue Distribution Metadata extension Application schema Dataset - Administrative area A Dataset Identification Citation and Responsible Party Extent Feature type - Administrative area A - Road network Dataset Identification Citation and Responsible Party Attribute type - Administrative area A - ‘Overhead Clearance’ Dataset Identification Citation and Responsible Party Data quality 5) A new bridge is constructed in Administrative area A. This new data is reflected in the geographic data for Administrative area A, and new metadata is required to record this new feature. All other metadata for Administrative area A remains unaffected. This new feature metadata is recorded at Feature instance level. So, additional metadata is required at Feature instance level to describe the new Bridge. The minimum level of metadata required reflecting this change would be: Dataset series – Administrative areas A, B & C Metadata entity set Identification Citation and responsible party Extent Constraints Data quality Maintenance Spatial representation Reference system Content Portrayal catalogue Distribution Metadata extension Application schema ISO 19115:2003(E) © ISO 2003 — All rights reserved 125 Dataset - Administrative area A Dataset Identification Citation and Responsible Party Extent Feature type - Administrative area A - Road network Dataset Identification Citation and Responsible Party Attribute type - Administrative area A - ‘Overhead Clearance’ Dataset Identification Citation and Responsible Party Data Quality Feature instance - Administrative area A - New bridge Dataset Identification Citation and Responsible Party Extent 6) The overhead clearance attribute of the new bridge was wrongly recorded, and is modified. Again this new attribute requires new metadata to describe the modification. All other metadata for Administrative area A remains unaffected. This new attribute metadata is recorded at Attribute instance level. So, additional metadata is required at Attribute Instance level to describe the new Overhead Clearance. The minimum level of metadata required reflecting this change would be: Dataset series – Administrative areas A, B & C Metadata entity set Identification Citation and responsible party Extent Constraints Data quality Maintenance Spatial representation Reference system Content Portrayal catalogue Distribution Metadata extension Application schema Dataset - Administrative area A Dataset Identification Citation and Responsible Party Extent Feature type - Administrative area A - Road network Dataset Identification Citation and Responsible Party Attribute type - Administrative area A - ‘Overhead Clearance’ Dataset Identification Citation and Responsible Party Data Quality Feature instance - Administrative area A - New bridge Dataset Identification Citation and Responsible Party Extent Attribute instance - Administrative area A - New bridge - Overhead clearance Dataset Identification Citation and Responsible Party Data Quality ISO 19115:2003(E) 126 © ISO 2003 — All rights reserved Annex I (informative) Implementation examples I.1 Metadata examples Two examples are provided. One example is for a dataset titled “Exploration Licences for Minerals”. The other example illustrates an extension of the metadata standard. Examples are presented in English. However, countries and users are allowed to use their own natural language(s) in the implementation of this International Standard. I.2 Example 1 – Exploration Licences for Minerals The example below is provided in a tabbed-outline format with element values underlined and role names denoted with a “+”. This example illustrates the hierarchical structure of ISO 19115 metadata and is based on an implementation schema that governs the ordering of the elements within the metadata instance document. MD_Metadata +identificationInfo MD_DataIdentification citation: . CI_Citation . title: Exploration Licences for Minerals . date: . CI_Date . dateType: 001 . date: 193001 abstract: Location of all current mineral Exploration Licences issued under the Mining Act, 1971. Exploration Licences provide exclusive tenure rights to explore for mineral resources for up to a maximum of 5 years. Comment is sought on applications for Exploration Licences from numerous sources before granting. Exploration programs are subject to strict environmental and heritage conditions. Exploitation of identified resources must be made under separate mineral production leases. status: 004 pointOfContact: . CI_ResponsibleParty .. contactInfo: .. CI_Contact .. phone: .. ….CI_Telephone .. ….voice: 61 8 8463 3306 .. ….facsimile: 61 8 8463 3268 .. address: .. ….CI_Address .. ….deliveryPoint: GPO Box 167 .. ….city: Adelaide .. ….administrativeArea: South Australia .. ….postalCode: 5001 .. ….country: Australia .. ….electronicMailAddress: pirsa.spatial@saugov.sa.gov.au .. onlineResource: ISO 19115:2003(E) © ISO 2003 — All rights reserved 127 .. ….CI_OnlineResource .. ….linkage: http://www.pir.sa.gov.au .. role: 007 ..organisationName: Department of Primary Industries and Resources SA ..positionName: GIS Coordinator +resourceConstraints .. MD_Constraints .. useLimitation: The data should not be used at a scale larger than 1:50 000. +resourceFormat .. MD_Format ..name: ArcInfo Export ..version: 8.0.2 +resourceFormat .. MD_Format ..name: MapInfo ..version: 6.0 +resourceFormat .. MD_Format ..name: DXF .. version: 14 +resourceFormat .. MD_Format ..name: Plotted Maps ..version: Not applicable +resourceSpecificUsage . MD_Usage . specificUsage: Used to supply government, industry and the general public with an up-to-date status and extent of mineral exploration activities throughout the State. . userContactInfo: . CI_ResponsibleParty . role: 007 . positionName: GIS Coordinator +resourceMaintenance ..MD_MaintenanceInformation ..maintenanceAndUpdateFrequency: 002 +descriptiveKeywords .. MD_Keywords .. keyword: BOUNDARIES Administrative ..keyword: INDUSTRY Mining Exploration ..keyword: MINERALS Exploration ..thesaurusName: .. CI_Citation .. title: ANZLIC Search Words .. date: .. ….CI_Date .. ….dateType: 002 .. ….date: 199607 purpose: The dataset was developed to record information necessary for the administration of the Mining Act. spatialRepresentationType: 001 spatialResolution: .. MD_Resolution ..equivalentScale: .. MD_RepresentativeFraction .. denominator: 50000 characterSet: 001 topicCategory: 003 topicCategory: 008 extent: .. EX_Extent ISO 19115:2003(E) 128 © ISO 2003 — All rights reserved …….. +geographicElement …….. EX_GeographicBoundingBox .. ….westBoundLongitude: 129.0 .. ….eastBoundLongitude: 141.0 .. ….southBoundLatitude: -26.0 .. ….northBoundLatitude: -38.5 …….. description: South Australia language: en +dataQualityInformation DQ_DataQuality scope: . DQ_Scope . level: dataset +lineage . LI_Lineage . statement: Source Data History: Exploration Licence boundaries were sourced from the official Mining Register licence documents. Licence boundaries are legally defined to follow lines of latitude and longitude. The register has existed since 1930. Processing Steps: Coordinates entered by keyboard from licence documents. Linework cleaned to remove duplicate arcs. Data adjusted for accurate state border and coastline. Where appropriate, cadastral parcels removed from licence polygons. Associated attribute data also captured from licence documents. +report . DQ_CompletenessOmission . result: . DQ_QuantitativeResult . valueUnit . ….uomName: percent . value: Spatial data is 100% complete. Associated attribute data is 100% complete. . DQ_TopologicalConsistency . result: . DQ_QuantitativeResult . valueUnit . ….uomName: percent . value: The dataset contains no overshoots, undershoots or duplicate lines. All polygons representing licences contain only one label. . DQ_PositionalAccuracy . result: . DQ_ConformanceResult . specification: . CI_Citation . ….title: Map Boundries . ….date . …. CI_Date . …. dateType: 002 . …. date: 199703 . explanation: Most boundary locations are constructed from lines of latitude and longitude, hence are scale independent. The accuracy of other boundaries is dependent upon the source, eg. state border, coastline, cadastre. . pass: 1 . DQ_ThematicAccuracy . result: . DQ_QuantitativeResult . valueUnit . ….uomName: percent . value: Validation checks are performed periodically, resulting in an estimated 99% accuracy. These checks include comparisons between reports from the spatial dataset and the digital Mining Register. +referenceSystemInfo MD_ReferenceSystem referenceSystemIdentifier: ISO 19115:2003(E) © ISO 2003 — All rights reserved 129 . RS_Identifier . code: GDA 94 . codeSpace: DIPR fileIdentifier: ANZSA1000001233 language: en characterSet: 001 contact: CI_ResponsibleParty role: 002 organisationName: Department of Primary Industries and Resources SA dateStamp: 20000803 metadataStandardName: ISO 19115 metadataStandardVersion: FDIS dataset: https://info.pir.sa.gov.au/geometa/migs/MIGS_Down_cat.jsp I.3 Example 2 – Example of extended metadata This example illustrates the addition of new metadata entities and an extended codelist that can be used to document a hierarchical classification-based taxonomy. Figure I.1 presents a UML model of the extension information, Clause I.4 provides data dictionary entries for the extended entities and elements. MD_Identification (from ISO 19115 Metadata) +theTaxonomySystem 0..1 0..* +descriptiveKeywords MD_Keywords (from ISO 19115 Metadata) + keywords [1..*] : CharacterString + type [0..1] : MD_KeywordTypeCode + thesaurusName [0..1] : CI_Citation + classificationSystemAuthority : CI_Citation + classificationSystemModifications [0..1] : CharacterString + generalTaxonomicScope [0..1] : CharacterString + identificationReference : CI_Citation + observer [0..*] : CI_ResponsibleParty + identificationTaxonomicProcedures : CharacterString + identificationTaxonomicCompleteness [0..1] : CharacterString TaxonomySystem MD_Keywords (modified) + discipline + placed + stratum + temporal + theme + taxon (new) Vouchers + specimen : CharacterString + repository : CI_ResponsibleParty TaxonomicClassification + commonName [0..*] : CharacterString + taxonRankName : CharacterString + taxonRankValue : CharacterString + hiearchialClass [0..*] : TaxonomicClassification +theTaxonomicClassification+theVouchers 0..* 1 Figure I.1 — Examples of extended metadata I.4Datadictionaryfortheextendedelements NameShort Name Domain Code DefinitionObligation/ Condition DataTypeDomainMax Occur ParentEntityRuleRationaleSource Rolename: theTaxonomy System taxonomyinformationonthe taxa(1ormore) includedinthedata set,including keywords,taxonomic systemandcoverage information,and taxonomic classificationsystem. OAssociation1MD_IdentificationNewMetadata section Toprovidefor documentationof taxonomic information National Biological Information Infrastructure (NBII) Taxonomy System Taxonsysdocumentationof taxonomicsources, procedures,and treatments. OClass1MD_IdentificationNewMetadata sectionasaclass to MD_Identification Thesetofdata elementscontained withinthisclass elementrepresents anattemptto providebetter documentationof taxonomicsources, procedures,and treatments. National Biological Information Infrastructure (NBII) Classification System Authority classsysinformationaboutthe Classificationsystem orauthorityused MClassCI_CitationNTaxonomySystemNewMetadata class Together,the Classification systemandany modificationsmade toitrepresenta significantpieceof information concerningthedata beingdocumented. National Biological Information Infrastructure (NBII) Classification System Modifications classmoddescriptionofany modificationsor exceptionsmadeto theClassification systemorauthority used C/ taxonomic classification system modified? Character String Freetext1classificationSyste mAuthority NewMetadata attribute Manytimesa standardsystemis used,butexceptions aremadetospecific taxaorgroups,this elementallowsfor exceptionsor modificationstobe described. National Biological Information Infrastructure (NBII) ISO 19115:2003(E) 130 © ISO 2003 — All rights reserved NameShort Name Domain Code DefinitionObligation/ Condition DataTypeDomainMax Occur ParentEntityRuleRationaleSource General Taxonomic Scope taxogendescriptionofthe rangeoftaxa addressedinthedata setorcollection.For example,"allvascular plantswereidentified tofamilyorspecies, mossesandlichens wereidentifiedas mossorlichen." OCharacter String Freetext1TaxonomySystemNewMetadata attribute Toprovidethe capabilityto documentthetaxa addressedinthe datasetorcollection viaafreetext description.Thisis especiallyimportant withdatasetsor collectionswhich containexamplesof amanytaxonomic levels. National Biological Information Infrastructure (NBII) Identification Reference idrefinformationonany non-authoritative materials(e.g.field guides)usefulfor reconstructingthe actualprocess MClassNTaxonomySystemNewMetadata class Thisinformationcan beusefulfor someonewho wishestomakeuse ofadataset,and perhapsexpandon it,followingsimilar procedures National Biological Information Infrastructure (NBII) observerobsinformationaboutthe individual(s) responsibleforthe identification(s)ofthe specimensor sightings,etc. OClassCI_Respo nsibleParty NTaxonomySystemNewMetadata class Ifthereareany questionsonthe identificationof specimensorfield sightings,this shouldprovide someinsightintothe datacreator. National Biological Information Infrastructure (NBII) Identification Taxonomic Procedures taxonprodescriptionofthe methodsusedfor taxonomic identification.Could includespecimen processing, comparisonwith museummaterials, keys,andkey characters,chemical orgeneticanalyses, etc. MCharacter String Freetext1TaxonomySystemNewMetadata attribute National Biological Information Infrastructure (NBII) ISO 19115:2003(E) © ISO 2003 — All rights reserved 131 NameShort Name Domain Code DefinitionObligation/ Condition DataTypeDomainMax Occur ParentEntityRuleRationaleSource Identification Taxonomic Completeness taxoncominformation concerningthe proportionsand treatmentof unidentifiedmaterials (i.e.materialssentto experts,andnotyet determined); estimatesofthe importance,and identitiesof misidentifications, uncertain determinations, synonymsorother incorrectusages;taxa notwelltreatedor requiringfurtherwork; andexpertiseoffield workers. OCharacter String Freetext1TaxonomySystemNewMetadata attribute National Biological Information Infrastructure (NBII) Rolename: theVouchers voucherinformationaboutthe voucher Association VouchersVouchersinformationonthe typesofspecimen, therepository,and theindividualswho identifiedthe vouchers. C/vouchers used? ClassNTaxonomicSystemNewMetadata class National Biological Information Infrastructure (NBII) ISO 19115:2003(E) 132 © ISO 2003 — All rights reserved NameShort Name Domain Code DefinitionObligation/ Condition DataTypeDomainMax Occur ParentEntityRuleRationaleSource specimenspecimenwordorphrase describingthetypeof specimencollected (e.g.herbarium specimens,blood samples, photographs, individuals,or batches). Example:"herbarium specimens""blood samples" "photographs" "individuals"freetext MCharacter String freetext1VouchersNewMetadata attribute National Biological Information Infrastructure (NBII) repositoryrepositinformationaboutthe curatororcontact personand/oragency responsibleforthe specimens. MClassCI_Respo nsibleParty 1VouchersNewMetadata class If,foranyreason, thespecimens shouldneedtobe referredto, informationabout wheretheyare beinghousedand whoisresponsible forthemshouldbe keptalongwiththe documentationof thedataset.Ifthey havenotbeen archived,thisshould benoted. National Biological Information Infrastructure (NBII) Rolename: theTaxonomic Classification informationaboutthe taxonomic classification M1 ISO 19115:2003(E) © ISO 2003 — All rights reserved 133 NameShort Name Domain Code DefinitionObligation/ Condition DataTypeDomainMax Occur ParentEntityRuleRationaleSource Taxonomic Classification Taxonclinformationaboutthe rangeoftaxa addressedinthedata setorcollection.Itis recommendedthat oneprovide informationstarting fromthetaxonomic rankofkingdom,toa levelwhichreflects thedatasetor collectionbeing documented.The levelsofKingdom, Division/Phylum, Class,Order,Family, Genus,andSpecies shouldbeincludedas ranksasappropriate. Forexample,ifthe datasetdealswith thespecies"red maple"orAcer rubrumvar.rubrum, thenthecontents mightlooklikethe following: MClass1Taxonomic Classification NewMetadata class Toprovidethe capabilityto describeprecisely thetaxaaddressed inthedatasetor collection.Thiscan beaccomplished usingahierarchical structuretospecify fromKingdomdown totheappropriate taxonomiclevel. National Biological Information Infrastructure (NBII) commonNamecommonspecificationof applicablecommon names.These commonnamesmay begeneral descriptionsofa groupoforganismsif appropriate(e.g. insects,vertebrate, grasses,waterfowl, vascularplants,etc.) OCharacter String freetextNTaxonomic Classification NewMetadata attribute Toprovidethe capabilityto describeprecisely thetaxaaddressed inthedatasetor collection. National Biological Information Infrastructure (NBII) ISO 19115:2003(E) 134 © ISO 2003 — All rights reserved NameShort Name Domain Code DefinitionObligation/ Condition DataTypeDomainMax Occur ParentEntityRuleRationaleSource taxonRank Name taxonrnnameofthe taxonomicrankfor whichthe Taxon_Rank_Valueis provided.Seethe exampleincludedin thedefinitionof Taxonomic_Classifica tion Example:"Kingdom" "Division""Phylum" "Subphylum" "SuperClass""Class" "SubClass" "InfraClass" "Superorder""Order" "Suborder" "Infraorder" "Superfamily""Family" "Subfamily""Tribe" "Subtribe""Genus" "Species" MCharacter String freetext1Taxonomic Classification NewMetadata attribute Toprovidethe capabilityto describeprecisely thetaxaaddressed inthedatasetor collection. National Biological Information Infrastructure (NBII) taxonRank Value taxonrynamerepresenting thetaxonomicrankof thetaxonbeing described.Seethe exampleincludedin thedefinitionof Taxonomic Classification. MCharacter String Freetext1Taxonomic Classification NewMetadata attribute Toprovidethe capabilityto describeprecisely thetaxaaddressed inthedatasetor collection. National Biological Information Infrastructure (NBII) Hierachical Class hiclassnumberofrecursive setsoftaxonomic classificationsystems OCharacter String FreetextNTaxonomic Classification NewMetadata attribute Toprovidethe capabilitytodeclare thenumberof recursivetaxonomic classification systems National Biological Information Infrastructure (NBII) ISO 19115:2003(E) © ISO 2003 — All rights reserved 135 ISO 19115:2003(E) 136 © ISO 2003 — All rights reserved I.5 MD_KeywordType (Modified) Name Domain code Definition MD_KeywordType Methods used to group similar keywords discipline 001 Keyword identifies a branch of instruction or specialized learning place 002 Keyword identifies a location stratum 003 Keyword identifies the layer(s) of any deposited subsurface temporal 004 Keyword identifies a time period related to the dataset theme 005 Keyword identifies a particular subject or topic taxon 006 Keyword identifies a taxonomy of the dataset ISO 19115:2003(E) © ISO 2003 — All rights reserved 137 Annex J (informative) Multilingual support for free text metadata element J.1 Free text metadata elements In this International Standard a free text element may include multiple instances of information in different languages. Where the language is different from the language defined for the whole dataset, it may be identified, along with an optional attribute that specifies the variant of the language used in a particular country, and the character set used when that differs from the default for the whole dataset. Defined in Clause J.2 are metadata elements that allow for the specification of free text in multiple languages. Optionally, everywhere in this International Standard where “free text” is specified as the domain the class PT_FreeText can be used. An example of how the free text metadata elements may be used is described in J.3. The metadata element “useLimitation” is used in the example. It can be found in B.2.3 of this International Standard. J.2Datastructureforhandlingmulti-languagessupportinfreetextmetadataelements Name/RolenameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 1xPT_FreeTextPtFreeTextdescriptionofamulti-language freetextmetadataelement Useobligationfrom referencingobject Use maximum occurrence from referencing object ClassLine2x 2xRolename: textGroup textGroupinformationaboutthemetadata elementsrequiredtosupport multilingualfreetextfields MNAssociationPT_Group 3xPT_GroupPtGroupdescriptionofmetadataelements requiredtosupportmulti- languagesinfreetextmetadata elements Useobligationfrom referencingobject Use maximum occurrence from referencing object AggregatedClass (PT_FreeText) Lines2xand4x-7x 4xlanguageCodePtLangCodelanguageusedfordocumentinga plaintext O1ClassLanguageCode <>(ISO639, recommended3-alphabetic digitscode) 5xcountryPtCountrycountryoflanguageusedfor documentingaplaintext O1CharacterStringCountry <>(ISO3166 recommended3-numeric digitscode) 6xcharacterSetCodePtCharCodefullnameoftheISOcharacter codingstandardusedfor documentingaplaintext O1ClassMD_CharacterSetCode <>(B5.10) 7xplainTextPtTextcontentofafreetextmetadata element M1CharacterStringFreetext ISO 19115:2003(E) 138 © ISO 2003 — All rights reserved J.3Exampleofmulti-languagesfreetextinametadataelement Themetadataelement“useLimitation”isusedinthefollowingexample(B.2.3line68). NameShortNameDefinitionObligation/ Condition Maximum occurrence DatatypeDomain 68useLimitationuseLimitlimitationaffectingthefitnessfor useoftheresourceormetadata. Example,“nottobeusedfor navigation” ONCharacterStringFreetext Exampleofmulti-languagesoccurrences onfreetextmetadataelementtitled“useLimitation” Languagecode (Optional) Countrycode (Optional) Charactersetcode (Optional) Plaintext (Mandatory) eng (English) (seeNote) 826 (UnitedKingdom) (seeNote) 017 (ISO/IEC8859-15) (seeNote) Weightrestrictiononbridges Lorriesexceedingfivemetrictonnesgrossweightarenotpermittedonbridges fra (French) 017 (ISO/IEC8859-15) Limitationdepoidssurlesponts: Lescamionsdontlepoidstotalexcède5tonnesmétriquesnesontpasautorisésàcirculersurlesponts. ara (Arabic) 011 (ISO/IEC8859-6) zho (Chinese) 029 (GB2312) NOTEIf“English”,“UnitedKingdom”and“ISO/IEC8859-15”wouldhavebeenspecifiedasdefaultvaluesfortheentiremetadatafile,itwouldnothavebeen necessarytospecifytheminthisoccurrence. ISO 19115:2003(E) © ISO 2003 — All rights reserved 139 ISO 19115:2003(E) 140 © ISO 2003 — All rights reserved Bibliography [1] ISO/IEC 646, Information technology — ISO 7-bit coded character set for information interchange [2] ISO 690:1987, Documentation — Bibliographic references — Content, form and structure [3] ISO 8601:2000, Data elements and interchange formats — Information interchange — Representation of dates and times [4] ISO 11180, Postal addressing [5] ISO/TS 19103:―2), Geographic information ― Conceptual schema language [6] ISO 19104:—2), Geographic information — Terminology [7] ISO 19116:—2), Geographic information — Positioning services [8] ISO 19119:—2), Geographic information — Services [9] ISO 19123:—2), Geographic information — Schema for coverage geometry and functions [10] ISO 23950:1998, Information and documentation — Information retrieval (Z39.50) — Application service definition and protocol specification [11] ISO/TR 19121:2000, Geographic information ― Imagery and gridded data [12] IETF RFC 1738, Uniform Resource Locators (URL) [13] IETF RFC 2056, Uniform Resource Locators for Z39.50 2) To be published. ISO 19115:2003(E) ICS 35.240.70 Price based on 140 pages © ISO 2003 — All rights reserved