Standard number: GB/T 28585-2012 Standard name: Geographic information-Methodology for feature cataloguing English name: Geographic information-Methodology for feature cataloguing (ISO19110:2005,IDT) Standard format: PDF Release time: 2012-06-29 Implementation time: 2012-10-01 Standard size: 15.4M Standard introduction: This standard was drafted in accordance with the rules given in GB/T1.1-2009. This standard adopts the translation method and is equivalent to the international standard IsO19110:2005 "Geographic Information Feature Cataloguing Method" and its first revision Iso19110:2005/Amd1:2011. The Chinese documents that have consistent correspondence with the international documents normatively referenced in this standard are as follows: GB/T19710-2005 Geographic Information Metadata (ISO19115:2003, MOD); GB/Z24357-2009 Geographic Information Metadata XML Schema Implementation (ISO/TS19139:2007, MOD). This standard has been edited as follows: "This international standard" and "ISO19110" have been changed to "This standard"; The foreword of the original international standard has been deleted; The content of ISO19110:2005 "Methods for cataloguing geographic information elements" has been modified in accordance with ISO19110:2005/Amd1:2011, and normative appendices E and F, as well as informative appendix G have been supplemented. The note under Table 1 in the amendment was deleted; "Eiffel Tower" in 4.1 was changed to "Pearl Tower"; the responsible unit and contact information examples in Table C.1 were changed to relevant units of my country, and "military projects" were changed to "transportation hub projects"; the nicknames for "waterway" in Table C.31 (original C.33) were changed to "Brook", "Kil", "River", "Seaway", "Stream" is translated as "river", "river", "chuan", "qu", "xi", and "qu" respectively; The number "1)" in paragraph b) of A.11 is deleted, and the two natural paragraphs of the paragraph are merged Geographic features are abstractions of real-world phenomena related to locations on the earth, and their data are collected, maintained, and distributed. Feature catalogs define the types, operations, attributes, and associations of features represented in geographic data, and are indispensable for transforming data into usable information. Feature catalogs can promote the distribution, sharing, and use of geographic data by providing easier-to-understand data content and meaning. Unless the providers and users of geographic data have a common understanding of the various real-world phenomena represented by the data, users cannot determine whether the data provided is suitable for their purposes. The practicality of a standardized feature catalog that can be reused is reflected in reducing the cost of data acquisition and simplifying the processing of geographic data sets according to product specifications. This standard provides a standard framework for organizing and recording the classification of real-world phenomena in geographic data sets. Any geographic data set is a greatly simplified, complex and diverse real-world phenomenon. The feature type catalogue cannot be as rich as geographic reality. However, the feature catalogue should clearly and accurately describe the specific abstract concepts represented in a given dataset in a form that is easily understood and accessible to data users. Geographic features appear at two levels: the instance level and the type level. At the instance level, geographic features are represented as discrete phenomena associated with geographic and temporal coordinates and can be represented by specific graphical symbols. These individual feature instances are grouped into classes with common characteristics - feature types. It can be said that geographic information is subjectively perceived and its content depends on the needs of specific applications. Such specific application needs determine the way in which instances are grouped into types according to specific classification patterns. ISO19109:2005 "Rules for application models for geographic information" specifies how data can be organized according to similar data requirements to reflect specific application requirements. Note: A complete description of the content and structure of a geographic dataset is given according to the application model specified in ISO19109:2005. The feature catalogue defines the meaning of feature types and the feature attributes, feature operations and feature associations contained in the application model and related to them.||tt
|| This standard defines a method for cataloging feature types, specifies how to organize feature types into feature catalogs, and how to provide them to users of geographic data. This standard is applicable to the establishment of catalogs for feature types that have not been cataloged before, and existing feature catalogs can also be revised according to the provisions of this standard. It is applicable to the cataloging of feature types represented in digital form. Its principles can also be extended to the cataloging of other forms of geographic data. The feature catalog is independent of the feature concept dictionary defined in ISO 19126, and cataloging is possible without using or establishing a feature concept dictionary.

ICS35.240.70;07.040
National Standard of the People's Republic of China
GB/T28585—2012/IS019110.2005 Geographic information-Methodology for feature cataloguing cataloguing（ISO19110:2005.IDT）
2012-06-29 Issued
General Administration of Quality Supervision, Inspection and Quarantine of the People's Republic of China Standardization Administration of China
2012-10-01 Implementation
1 Scope
Conformance
Normative references
Terms and definitions
Abbreviations
Principles and requirements
6.1 Element catalogue
6.2 Information elements
Appendix A (Normative)
Appendix B (Normative)
Appendix C ( Informative Appendix)
Appendix D (Informative Appendix)
Appendix E (Normative Appendix)
Appendix F (Normative Appendix)
Appendix G (Informative Appendix)
References
Abstract test suite
Feature catalog template
Feature catalog example
Feature catalog concept
Coding instructions
Feature catalog registry management
XML implementation example
GB/T28585—2012/ISO19110:200512
This standard was drafted in accordance with the rules given in GB/T1.1-2009. GB/T28585-2012/ISO19110:2005 This standard adopts the translation method to adopt the international standard ISO19110:2005 "Method for cataloguing geographic information elements" and its first revision ISO19110:2005/Amd1:2011. The Chinese documents that have a consistent correspondence with the international documents normatively referenced in this standard are as follows: - GB/T19710-2005 Geographic Information Metadata (ISO19115:2003, MOD); GB/Z24357-2009 Geographic Information Metadata XML Schema Implementation (ISO/TS19139:2007, MOD). This standard has been modified as follows:
- "This international standard" and "ISO19110" have been changed to "this standard"; the foreword of the original international standard has been deleted;
The content of ISO19110:2005 "Method for cataloguing geographic information elements" has been modified in accordance with ISO19110:2005/Amd1:2011, and the normative appendices E and F, as well as the informative appendix G have been supplemented. The note under Table 1 in the amendment was deleted;
"Eiffel Tower" in 4.1 was changed to "Pearl Tower"; the responsible unit and contact information examples in Table C.1 were changed to relevant Chinese units, and "military projects" were changed to "transportation hub projects"; the nicknames of "waterway" "Brook", "Kil", "River", "Seaway" and "Stream" in Table C.31 (original C.33) were translated into "river", "river", "stream", "curve", "stream" and "channel" respectively; the number "1)" in paragraph b) of A.11 was deleted, and the two paragraphs of the paragraph were merged; since ISO19110:2005/AMD1:2011 deleted Tables C.6 and C.19 of Appendix C of ISO19110:2005, the serial numbers of the tables in the appendix were adjusted accordingly, and the table serial numbers in the relevant citations were modified; "FACC (Feature and Attribute Coding Catalogue)" in 5 and "L5] Digital Geographie Information Working Group(DGIWG).Digital Geographic Information ExchangeStandard,Part 4:Feature and Attribute Coding Catalog(FACC)Data Dictionary Lonline].Ed.2.1.Washington:DGIWG,2000.[cited 13December 2003].Availablefrom World WideWeb：,\, and the relevant citation numbers in the text, Appendix D and references have been modified accordingly.
This standard is proposed by the National Administration of Surveying, Mapping and Geoinformation. This standard is under the jurisdiction of the National Technical Committee for Geographic Information Standardization (SAC/TC230). The drafting unit of this standard is the National Basic Geographic Information Center. The main drafters of this standard are Liu Ruomei, Jiang Jingtong, Jia Yunpeng and Zhou Xu. m
GB/T28585-2012/IS019110:2005 Introduction
Geographic features are abstractions of real-world phenomena related to locations on the earth, and their data are collected, maintained and distributed. The feature catalog defines the types, operations, attributes and associations of the features represented in geographic data, and is indispensable for converting data into usable information. The feature catalog can promote the distribution, sharing and use of geographic data by providing easier-to-understand data content and meaning. Unless the providers and users of geographic data have a common understanding of the various real-world phenomena represented by the data, users cannot judge whether the provided data is suitable for their purposes.
The utility of a standardized, reusable feature catalog is to reduce the cost of data acquisition and to simplify the processing of geographic data sets to product specifications.
This standard provides a standard framework for organizing and recording the classification of real-world phenomena in geographic data sets. Any geographic data set is a greatly simplified abstraction of the complex and diverse real world. A feature type catalog cannot be as rich as the geographic reality. However, a feature catalog should clearly and accurately describe the specific abstract concepts represented in a given data set in a form that is easily understood and accessible to data users.
Geographic features appear at two levels: the instance level and the type level. At the instance level, geographic features are represented as discrete phenomena associated with geographic and time coordinates and can be represented by specific graphical symbols. These individual feature instances are grouped into classes with common characteristics, the feature type. It can be assumed that geographic information is subjectively perceived and its content depends on the needs of a specific application. Such specific application needs determine the way in which instances are grouped into types according to a specific classification scheme. ISO 19109:2005 "Rules for Geographic Information Application Schemas" specifies how to organize data according to similar data requirements to reflect specific application requirements. Note: A complete description of the content and structure of a geographic dataset is given in accordance with the application schema specified in ISO 19109:2005. The feature catalog defines the meaning of feature types and the feature attributes, feature operations and feature associations associated with them contained in the application schema. This standard does not specify integration criteria for identifying individual real-world phenomena and representing them as feature instances in a dataset. Therefore, the integration criteria should be described separately in the product specification of each dataset. A standard method for organizing feature catalog information does not automatically lead to coordination or interoperability between applications. In the case of different feature classifications, this standard can at least be used to distinguish their differences, thereby helping to avoid errors caused by ignoring them. This standard can also serve as a standard framework for coordinating existing overlapping feature catalogs. IV
1 Scope
Geographic Information
GB/T28585—2012/ISO19110:2005 Method for cataloguing features
This standard defines a method for cataloguing feature types, specifies how to organize feature types into feature catalogues, and how to provide them to users of geographic data. This standard is applicable to the establishment of catalogues for feature types that have not been catalogued before, and existing feature catalogues can also be revised in accordance with the provisions of this standard. This standard is applicable to the cataloguing of feature types represented in digital form. Its principles can also be extended to the cataloguing of other forms of geographic data. The feature catalogue is independent of the feature concept dictionary defined in ISO19126, and cataloguing can be done without using or establishing a feature concept dictionary. This standard can be used to define geographic features at the type level, but is not applicable to representing individual instances of each feature type. This standard does not involve the graphical representation model defined in GB/T24355—2009. This standard can be used as the basis for defining a domain in the modeling of a specific application, or to standardize the general characteristics of real-world features in the modeling of more than one application.
2-Conformance
Since many of the options specified in this standard are not required for all feature catalogs, this chapter specifies five conformance categories. These categories differ in the following aspects: a) Which elements of the feature type are required in the catalog: 1) Only feature attributes; or
2) Feature attributes and feature associations: or
3) Feature attributes, feature associations, and feature operations. b) Whether it is necessary to define global feature attributes, feature associations, and feature operations that may be bound to multiple feature types. c) Whether inheritance relationships are included in the feature catalog. Appendix A specifies the test modules for each conformance category shown in Table 1. Table 1 Conformance Type
Only Feature Attributes
Normative References
Feature Attributes and
References
Feature Attributes, Features
Associations and Feature Operations
Global Properties
Inheritance Relationships
Test Modules
The following documents are essential for the application of this document. For any dated referenced document, only the dated version applies to this document. For any undated referenced document, the latest version (including all amendments) applies to this document. ISO/TS 19103:2005
language)
Geographic information
Geographic information Conceptual schema ISO 19109:2005 Geographic information Application schema rules (Geographic information rules for application schema) ISO 19115:2003 Geographic information
Metadata (Geographic information - Metadata) ISO/TS 19135:2005
Geographic information item registration procedures (Geographic information - Procedures for item registration)
ISO/TS 19139:2007
Geographic information
XML schema implementation)
4 Terms and definitions
The following terms and definitions apply to this document. 4.1
Feature
Abstract real-world phenomenon.
[ISO19101]
Metadata XML Schema Implementation (Geographicinformation-Metadata-Example, the phenomenon named "Pearl Tower\" can be classified as a feature type "tower" together with other similar phenomena. Note: Features can appear as types or instances. When only one meaning is expressed, only feature types or only feature instances should be used. 4.2
Feature Association
The link relationship between an instance of a feature (4.1) type and other instances of the same or different feature types. 4.3
Feature attribute
Feature attribute
Characteristic of a feature (4.1).
[ISO19101]]
Example 1: A feature attribute named "color" might have a value of "green" and a data type of "text". Example 2: A feature attribute named "length" might have a value of \82.4", and a data type of "real" Note: A feature attribute consists of a name, a data type, and a value domain associated with it. A feature attribute of a feature instance also has attribute values ​​that conform to the value domain. 4.4
Feature cataloguefeaturecatalogue
A catalogue containing definitions and descriptions of the types of features (4.1), feature attributes (4.3), and feature relationships (4.7) that appear in one or more geographic datasets, as well as any feature operations (4.5) that can be performed. 4.5
feature operation
Feature operation
An operation that can be performed on each instance of a feature (4.1) type. For example, a feature operation on a dam is to raise the dam. The result of this operation is to increase the height of the dam and the water level of the reservoir. Note: Sometimes, feature operations provide the basis for the definition of feature types. 4.6
Feature inheritance
The mechanism for merging more detailed features and generalizing the behavior of related features. 4.7
featurerelationship
featurerelationship
feature association (4.2) or feature inheritance (4.6). 2
functional languagefunctional language
a language for formally defining feature operations (4.5). NOTE The use of a functional language allows the representation of feature types as abstract data types. 5 Abbreviations
The following abbreviations apply to this document.
DIGEST
6 Principles and Requirements
6.1 Feature Catalog
GB/T28585—2012/ISO191102005 Digital Geographic Information Exchange Standard Geographic Feature Cataloguing General Feature Model Hypertext Transfer Protocol International Hydrographic Organization Technical Specification Unified Modeling Language Uniform Resource Identifier eXtensible Markup Language The feature catalog should describe the abstraction of reality represented in one or more geographic datasets. The basic level of abstraction in the feature catalog should be the feature type. The feature catalog of any geographic dataset containing features should be provided in electronic form. Feature catalogs independent of any existing geographic dataset may also comply with the provisions of this standard. 6.2 Information Elements
6.2.1 Overview
The following clauses specify general and specific requirements for feature catalog information elements. Annex B specifies the detailed requirements. Annex C describes the application of these requirements. Annex D discusses the application of feature operations as a conceptual basis for identifying feature types in a feature catalog. Annex E specifies the XML encoding of a feature catalog. Annex F specifies the concepts for managing a feature catalog as a multi-part register or a hierarchical register containing multiple parts in accordance with ISO 19135:2005. Annex G gives an example of an XML implementation of this standard. 6.2.2 Completeness
Annex B specifies a template for representing a feature catalog that describes all feature types present in a given geographic dataset. A feature catalog shall contain the identification information specified in Annex B. A feature catalog shall contain definitions and descriptions of all feature types present in the data, including any feature attributes and feature associations contained in the data associated with each feature type, and, where appropriate, feature operations supported by the data. To ensure the predictability and comparability of the content of feature catalogs between different applications, it is recommended that feature catalogs contain only the elements specified in Appendix B. To maximize the effectiveness of feature catalogs between different applications, it is recommended that feature catalog information be modeled using a conceptual schema language.
Note: The natural language definition of the feature catalog, feature index type aliases, criteria for the creation and deletion of index instances, and other semantic elements can be included in the conceptual schema as structured annotations or attributes. 3
GB/T28585—2012/ISO19110.20056.2.3—General requirements
6.2.3.1 Name format
All feature types and feature properties (i.e., feature attributes, feature associations, association roles, and feature operations) contained in the feature catalog should be identified by name. The name of a feature type is unique in the feature catalog. The name of a feature property (whether it is a global property bound to a feature type or a local property of a feature type) is unique within its feature type. The name of a global feature property is unique within the feature catalog.
6.2.3.2 Definition Form
The definitions of feature types, feature attributes, feature attribute list values, feature associations, association roles, and feature operations shall be described in natural language. These definitions shall be included in the catalog, unless the catalog indicates another source for the definition. If the same term appears in both the definition source and the feature catalog, the definition in the feature catalog shall be used. 6.2.4 Feature Type Requirements
Each feature type shall be identified by a name, defined in natural language. Each feature type may also be identified by a unique alphanumeric code in the feature catalog and may have multiple aliases. For each feature type, the feature catalog shall also include the feature operations it may have, the associated feature attributes, feature associations, and association roles. It is recommended that feature types be defined in a functional language. 6.2.5 Feature Operation Requirements
For each feature type, if there is a feature operation, it shall be identified and defined. Since any feature type is affected by an operation, the feature attributes involved in each feature operation shall be stated. The definition shall include a natural language definition and may also be formalized in a functional language. 6.2.6 Requirements for Feature Attributes
For each feature type, if any, feature attributes shall be identified and defined. The definition shall include a natural language definition and a description of the data type of the attribute value. Each feature attribute may also be identified by an alphanumeric code that is unique in the feature catalog. 6.2.7 Requirements for Feature Attribute List Values
If any, each feature attribute shall be labeled. The label shall be unique among the feature attributes to which the feature attribute list value belongs. Each feature attribute list value may also be identified by an alphanumeric code that is unique among the feature attributes to which the feature attribute list value belongs.
6.2.8 Requirements for Feature Associations
If any, feature associations shall be named and defined. Each feature association may also be identified by an alphanumeric code that is unique in the feature catalog. The names and roles of the feature types participating in the association shall be described. 6.2.9 Requirements for Association Roles
If any, feature association roles shall be named and defined. The names of the feature types that have the roles and participate in the association shall be described. A.1 Overview
Appendix A
(Normative Appendix)
Abstract Test Suite
GB/T285852012/IS019110:2005
This appendix specifies the abstract test suite for testing conformance with this standard. The abstract test suite contains 15 test cases and 12 test modules: test cases for the presence and form of feature catalog information (A.2), test cases for general feature catalog requirements (A.3), test cases for each major feature catalog information class (A.4 to A.16), and test modules for specific subsets of feature catalog functionality (A.17 to A.28)
The test cases are based on each major feature catalog information class as specified in Table B.1, Table B, 16. Each class-based test case consists of checking the elements (attributes or roles) of each class and checking that: · the constraints/conditions on the occurrence of the element are met; · the maximum number of occurrences of the element is not exceeded; the type of the element value is correct;
Note: Unless otherwise specified, if types from well-known packages or ISO standards are specified, the type descriptions specified in ISO/TS19103:2005 may be used. · the value of the element is consistent with the description of the element; · any constraints specified for the element are met. The class is tested as a whole, as specified in Tables B.1 to B.16 and/or implemented by the test module. The test module is based on a useful subset of the functionality of the feature catalog template specified in Annex B. The organization of the subset starts with the core functionality that can represent feature types and feature attributes that are unique to feature types (see A.17). The core representation functionality is extended by supporting one of the following: · Extensions to feature property types (see A.18 for association roles; A.19 for association roles and feature operations), or · Extensions to relationships between feature catalog information elements (see A.20 for multi-purpose feature attributes; A.23 for inheritance: A.26 for multi-purpose feature attributes and inheritance), or
both feature property types and relationships between feature catalog information elements (see A.21, A.22, A.24, A.25, ·
A.27 and A.28).
The test modules are described by the test cases of the application. Test modules A.18 to A.28 extend the core representation functionality described in test module A.17. These extensions are summarized in Table 1.
To check the conformance of a feature catalog with this standard, it shall be checked whether all the requirements of at least one test module are met. A,2 Test cases for the existence and form of feature catalog information The information of the test cases is as follows:
a) Test purpose: Check the existence and form of the feature catalog: Test method: Check whether the feature catalog exists and b) can be obtained in electronic form by obtaining a copy of the feature catalog, such as a disk, or by file transfer;
Reference: 6.1;
d) Test type: Basic test.
3 Test cases for general feature catalog requirements
The information of the test cases is as follows:
GB/T28585—2012/1SO19110:2005 Test purpose: Check that the requirements of the general feature catalog are met. a)
Test Method: Check if:
If a feature catalog is used for a given geographic dataset, then the feature catalog describes all feature types in that geographic dataset: 1)
All feature types, all feature associations, and all global feature properties (feature attributes that do not directly belong to a feature type) are identified with names that are unique in the feature catalog; 2)
all feature attribute list values ​​are identified with tags that are unique among the feature attributes to which the list values ​​belong; 3)
all All feature types, feature attributes, feature associations, association roles, and feature operations are defined or referenced from other sources4)
Definitions;
Any feature type, feature attribute, or feature association is identified by an alphanumeric code that is unique in the feature catalog; 5)
Any feature attribute list value is identified by an alphanumeric code that is unique among the feature attributes to which the list value belongs6)
;
7) The carriers of all characteristics of a feature type are identified by names that are unique in the context of that feature type. e) Reference: 6.2.
Test type: Capability test.
A.4 Test cases for feature catalog class
The information of the test case is as follows:
a) Test purpose: Check whether the required information is contained in the object of feature catalog class; b) Test method: Check whether the description, constraints, maximum number of occurrences, type and restrictions of each attribute and role listed in Table B.1 are in compliance with the regulations;
Reference: Table B.1:
d) Test type: Capability test.
A.5 Test cases for feature type class
The information of the test case is as follows:
a) Test purpose: Check whether the required information is contained in the object of feature type class; Test method: Check whether the description, constraints, maximum number of occurrences, type and restrictions of each attribute and role listed in Table B.2 are in compliance with the regulations;
Reference: Table B.2
Test type: Capability test.
A.6 Test case for inheritance relationship class
The information of the test case is as follows:
Test purpose: Check whether the required information is contained in the objects of the inheritance relationship class; a)
Test method: Check whether the description, constraints, maximum number of occurrences, type and restrictions of each attribute and role listed in Table B.3 b)
all comply with the regulations;
Reference: Table B.3;
Test type: capability test.
Test cases for feature operation classes
The information of the test cases is as follows:
Test purpose: Check whether the required information is contained in the objects of the feature operation class; a
GB/T285852012/IS019110.2005
b) Test method: Check whether the description, constraints, maximum number of occurrences, types and restrictions of each attribute and role listed in Table B.5 (and Table B.4) comply with the regulations;
Reference: Table B.4 and Table B.5;
d) Test type: Capability test.
Test case for binding class
The information of the test case is as follows:
Test purpose: Check whether the required information is contained in the object of the binding class;a)
Test method: Check whether the description, constraints, maximum number of occurrences, type and restrictions of each attribute listed in Table B.6 are allb)
Comply with the regulations:
Reference: Table B.6;
Test type: Capability test.
Test case for restriction class
The information of the test case is as follows:
Test purpose: Check whether the required information is contained in the object of the restriction class;a)
Test method: Check whether the description, constraints, maximum number of occurrences, type and restrictions of each attribute listed in Table B.7 are allb)
Comply with the regulations;
Reference: Table B.7;
Test type: Capability test.
Test cases for feature attribute classes
The information of the test cases is as follows:
Test purpose: Check that the required information is contained in the objects of the feature attribute class; a)
Test method: Check whether the description, constraints, maximum number of occurrences, type and restrictions of each attribute and role listed in Table B.8 and Table B.4 comply with the regulations; b)
Reference: Table B.4 and Table B.8;
Test type: Capability test.
Test case for associated role class
The information of the test case is as follows:
Test purpose: Check that the required information is contained in the objects of the associated role class; a)
Test method: Check whether the description, constraints, maximum number of occurrences, type and restrictions of each attribute and role listed in Table B.9 (and B.4) comply with the regulations, and check whether the attribute type value (row 9.2 of Table B.9) is the domain code in Table B.10; 7
GB/T28585-2012/ISO19110:2005 Reference: Table B.4, Table B.9 and Table B.10; Test type: capability test.
A.12 Test case for list value class
The information of the test case is as follows:
Test purpose: Check that the required information is contained in the objects of the list value class; a)
Test method: Check whether the description, constraints, maximum number of occurrences, types and restrictions of each attribute and role listed in Table B.11b)
are in compliance with the regulations;
Reference: Table B.11:
Test type, capability test.
Test case for feature association class
The information of the test case is as follows:
Test purpose: Check that the required information is contained in the objects of the feature association class; Test method: Check whether the detailed description, constraints, maximum number of occurrencesb)
number of occurrences, types and restrictions of each attribute and role listed in Table B.12 (and Table B.2) are in compliance with the regulations; Reference: Table B.2 and Table B.12;
Test type: capability test.
A.14 Test case for defining provenance class
The information of the test case is as follows:
a) Test purpose: Check that the required information is contained in the object defining the provenance class; Test method: Check whether the description, constraints, maximum number of occurrences, type and restrictions of each attribute listed in Table B.13 are all b)
compliant;
Reference: Table B.13:
d) Test type: Capability test.
Test case for defining reference class
The information of the test case is as follows;
a) Test purpose: Check that the required information is contained in the object defining the reference class; Test method: Check whether the detailed description, constraints, maximum number of occurrences, type and b)
restrictions of each attribute and role listed in Table B.14 are all in compliance;
Reference: Table B.14;
Test type: Capability test.
Test case for binding feature attribute class
The information of the test case is as follows:
Test purpose: Check that the required information is contained in the object of the binding feature attribute class; a)2005Test Purpose: Check that the requirements of the general feature catalog are met. a)
Test Method: Check whether:
If a feature catalog is used for a given geographic dataset, the feature catalog describes all feature types in the geographic dataset: 1)
All feature types, all feature associations, and all global feature properties (feature attributes that are not directly subordinate to a feature type) 2)
All feature attributes, feature attributes, or feature operations are identified with names that are unique in the feature catalog; all feature attribute list values ​​are identified with tags that are unique among the feature attributes to which the list values ​​belong; 3)
All feature attributes are identified with tags that are unique among the feature attributes to which the list values ​​belong; All feature types, feature attributes, feature associations, association roles, and feature operations are defined or referenced from other sources4)
Definitions;
Any feature type, feature attribute, or feature association is identified by an alphanumeric code that is unique in the feature catalog; 5)
Any feature attribute list value is identified by an alphanumeric code that is unique among the feature attributes to which the list value belongs6)
;
7) The carriers of all characteristics of a feature type are identified by names that are unique in the context of that feature type. e) Reference: 6.2.
Test type: Capability test.
A.4 Test cases for feature catalog class
The information of the test case is as follows:
a) Test purpose: Check whether the required information is contained in the object of feature catalog class; b) Test method: Check whether the description, constraints, maximum number of occurrences, type and restrictions of each attribute and role listed in Table B.1 are in compliance with the regulations;
Reference: Table B.1:
d) Test type: Capability test.
A.5 Test cases for feature type class
The information of the test case is as follows:
a) Test purpose: Check whether the required information is contained in the object of feature type class; Test method: Check whether the description, constraints, maximum number of occurrences, type and restrictions of each attribute and role listed in Table B.2 are in compliance with the regulations;
Reference: Table B.2
Test type: Capability test.
A.6 Test case for inheritance relationship class
The information of the test case is as follows:
Test purpose: Check whether the required information is contained in the objects of the inheritance relationship class; a)
Test method: Check whether the description, constraints, maximum number of occurrences, type and restrictions of each attribute and role listed in Table B.3 b)
all comply with the regulations;
Reference: Table B.3;
Test type: capability test.
Test cases for feature operation classes
The information of the test cases is as follows:
Test purpose: Check whether the required information is contained in the objects of the feature operation class; a
GB/T285852012/IS019110.2005
b) Test method: Check whether the description, constraints, maximum number of occurrences, types and restrictions of each attribute and role listed in Table B.5 (and Table B.4) comply with the regulations;
Reference: Table B.4 and Table B.5;
d) Test type: Capability test.
Test case for binding class
The information of the test case is as follows:
Test purpose: Check whether the required information is contained in the object of the binding class;a)
Test method: Check whether the description, constraints, maximum number of occurrences, type and restrictions of each attribute listed in Table B.6 are allb)
Comply with the regulations:
Reference: Table B.6;
Test type: Capability test.
Test case for restriction class
The information of the test case is as follows:
Test purpose: Check whether the required information is contained in the object of the restriction class;a)
Test method: Check whether the description, constraints, maximum number of occurrences, type and restrictions of each attribute listed in Table B.7 are allb)
Comply with the regulations;
Reference: Table B.7;
Test type: Capability test.
Test cases for feature attribute classes
The information of the test cases is as follows:
Test purpose: Check that the required information is contained in the objects of the feature attribute class; a)
Test method: Check whether the description, constraints, maximum number of occurrences, type and restrictions of each attribute and role listed in Table B.8 and Table B.4 comply with the regulations; b)
Reference: Table B.4 and Table B.8;
Test type: Capability test.
Test case for associated role class
The information of the test case is as follows:
Test purpose: Check that the required information is contained in the objects of the associated role class; a)
Test method: Check whether the description, constraints, maximum number of occurrences, type and restrictions of each attribute and role listed in Table B.9 (and B.4) comply with the regulations, and check whether the attribute type value (row 9.2 of Table B.9) is the domain code in Table B.10; 7
GB/T28585-2012/ISO19110:2005 Reference: Table B.4, Table B.9 and Table B.10; Test type: capability test.
A.12 Test case for list value class
The information of the test case is as follows:
Test purpose: Check that the required information is contained in the objects of the list value class; a)
Test method: Check whether the description, constraints, maximum number of occurrences, types and restrictions of each attribute and role listed in Table B.11b)
are in compliance with the regulations;
Reference: Table B.11:
Test type, capability test.
Test case for feature association class
The information of the test case is as follows:
Test purpose: Check that the required information is contained in the objects of the feature association class; Test method: Check whether the detailed description, constraints, maximum number of occurrencesb)
number of occurrences, types and restrictions of each attribute and role listed in Table B.12 (and Table B.2) are in compliance with the regulations; Reference: Table B.2 and Table B.12;
Test type: capability test.
A.14 Test case for defining provenance class
The information of the test case is as follows:
a) Test purpose: Check that the required information is contained in the object defining the provenance class; Test method: Check whether the description, constraints, maximum number of occurrences, type and restrictions of each attribute listed in Table B.13 are all b)
compliant;
Reference: Table B.13:
d) Test type: Capability test.
Test case for defining reference class
The information of the test case is as follows;
a) Test purpose: Check that the required information is contained in the object defining the reference class; Test method: Check whether the detailed description, constraints, maximum number of occurrences, type and b)
restrictions of each attribute and role listed in Table B.14 are all in compliance;
Reference: Table B.14;
Test type: Capability test.
Test case for binding feature attribute class
The information of the test case is as follows:
Test purpose: Check that the required information is contained in the object of the binding feature attribute class; a)2005Test Purpose: Check that the requirements of the general feature catalog are met. a)
Test Method: Check whether:
If a feature catalog is used for a given geographic dataset, the feature catalog describes all feature types in the geographic dataset: 1)
All feature types, all feature associations, and all global feature properties (feature attributes that are not directly subordinate to a feature type) 2)
All feature attributes, feature attributes, or feature operations are identified with names that are unique in the feature catalog; all feature attribute list values ​​are identified with tags that are unique among the feature attributes to which the list values ​​belong; 3)
All feature attributes are identified with tags that are unique among the feature attributes to which the list values ​​belong; All feature types, feature attributes, feature associations, association roles, and feature operations are defined or referenced from other sources4)
Definitions;
Any feature type, feature attribute, or feature association is identified by an alphanumeric code that is unique in the feature catalog; 5)
Any feature attribute list value is identified by an alphanumeric code that is unique among the feature attributes to which the list value belongs6)
;
7) The carriers of all characteristics of a feature type are identified by names that are unique in the context of that feature type. e) Reference: 6.2.
Test type: Capability test.
A.4 Test cases for feature catalog class
The information of the test case is as follows:
a) Test purpose: Check whether the required information is contained in the object of feature catalog class; b) Test method: Check whether the description, constraints, maximum number of occurrences, type and restrictions of each attribute and role listed in Table B.1 are in compliance with the regulations;
Reference: Table B.1:
d) Test type: Capability test.
A.5 Test cases for feature type class
The information of the test case is as follows:
a) Test purpose: Check whether the required information is contained in the object of feature type class; Test method: Check whether the description, constraints, maximum number of occurrences, type and restrictions of each attribute and role listed in Table B.2 are in compliance with the regulations;
Reference: Table B.2
Test type: Capability test.
A.6 Test case for inheritance relationship class
The information of the test case is as follows:
Test purpose: Check whether the required information is contained in the objects of the inheritance relationship class; a)
Test method: Check whether the description, constraints, maximum number of occurrences, type and restrictions of each attribute and role listed in Table B.3 b)
all comply with the regulations;
Reference: Table B.3;
Test type: capability test.
Test cases for feature operation classes
The information of the test cases is as follows:
Test purpose: Check whether the required information is contained in the objects of the feature operation class; a
GB/T285852012/IS019110.2005
b) Test method: Check whether the description, constraints, maximum number of occurrences, types and restrictions of each attribute and role listed in Table B.5 (and Table B.4) comply with the regulations;
Reference: Table B.4 and Table B.5;
d) Test type: Capability test.
Test case for binding class
The information of the test case is as follows:
Test purpose: Check whether the required information is contained in the object of the binding class;a)
Test method: Check whether the description, constraints, maximum number of occurrences, type and restrictions of each attribute listed in Table B.6 are allb)
Comply with the regulations:
Reference: Table B.6;
Test type: Capability test.
Test case for restriction class
The information of the test case is as follows:
Test purpose: Check whether the required information is contained in the object of the restriction class;a)
Test method: Check whether the description, constraints, maximum number of occurrences, type and restrictions of each attribute listed in Table B.7 are allb)
Comply with the regulations;
Reference: Table B.7;
Test type: Capability test.
Test cases for feature attribute classes
The information of the test cases is as follows:
Test purpose: Check that the required information is contained in the objects of the feature attribute class; a)
Test method: Check whether the description, constraints, maximum number of occurrences, type and restrictions of each attribute and role listed in Table B.8 and Table B.4 comply with the regulations; b)
Reference: Table B.4 and Table B.8;
Test type: Capability test.
Test case for associated role class
The information of the test case is as follows:
Test purpose: Check that the required information is contained in the objects of the associated role class;a)
Test method: Check whether the description, constraints, maximum number of occurrences, type and restrictions of each attribute and role listed in Table B.9 (and B.4) comply with the regulations, and check whether the attribute type value (row 9.2 of Table B.9) is the domain code in Table B.10;7
GB/T28585-2012/ISO19110:2005 Reference: Table B.4, Table B.9 and Table B.10; Test type: capability test.
A.12 Test case for list value class
The information of the test case is as follows:
Test purpose: Check that the required information is contained in the objects of the list value class; a)
Test method: Check whether the description, constraints, maximum number of occurrences, types and restrictions of each attribute and role listed in Table B.11b)
are in compliance with the regulations;
Reference: Table B.11:
Test type, capability test.
Test case for feature association class
The information of the test case is as follows:
Test purpose: Check that the required information is contained in the objects of the feature association class; Test method: Check whether the detailed description, constraints, maximum number of occurrencesb)
number of occurrences, types and restrictions of each attribute and role listed in Table B.12 (and Table B.2) are in compliance with the regulations; Reference: Table B.2 and Table B.12;
Test type: capability test.
A.14 Test case for defining provenance class
The information of the test case is as follows:
a) Test purpose: Check that the required information is contained in the object defining the provenance class; Test method: Check whether the description, constraints, maximum number of occurrences, type and restrictions of each attribute listed in Table B.13 are all b)
compliant;
Reference: Table B.13:
d) Test type: Capability test.
Test case for defining reference class
The information of the test case is as follows;
a) Test purpose: Check that the required information is contained in the object defining the reference class; Test method: Check whether the detailed description, constraints, maximum number of occurrences, type and b)
restrictions of each attribute and role listed in Table B.14 are all in compliance;
Reference: Table B.14;
Test type: Capability test.
Test case for binding feature attribute class
The information of the test case is as follows:
Test purpose: Check that the required information is contained in the object of the binding feature attribute class; a)5 Test cases for feature type class
The information of the test case is as follows:
a) Test purpose: Check whether the required information is contained in the object of feature type class; Test method: Check whether the description, constraint, maximum number of occurrences, type and restriction of each attribute and role listed in Table B.2b)
All meet the requirements;
Reference: Table B.2
Test type: Capability test.
A.6 Test cases for inheritance relationship class
The information of the test case is as follows:
Test purpose: Check whether the required information is contained in the object of inheritance relationship class; a)
Test method: Check whether the description, constraint, maximum number of occurrences, type and restriction of each attribute and role listed in Table B.3b)
All meet the requirements;
Reference: Table B.3;
Test type: Capability test.
Test cases for feature operation classes
The information of the test cases is as follows:
Test purpose: Check whether the required information is contained in the objects of the feature operation class; a
GB/T285852012/IS019110.2005
b) Test method: Check whether the description, constraints, maximum number of occurrences, types and restrictions of each attribute and role listed in Table B.5 (and Table B.4) comply with the regulations;
Reference: Table B.4 and Table B.5;
d) Test type: Capability test.
Test case for binding class
The information of the test case is as follows:
Test purpose: Check whether the required information is contained in the object of the binding class;a)
Test method: Check whether the description, constraints, maximum number of occurrences, type and restrictions of each attribute listed in Table B.6 are allb)
Comply with the regulations:
Reference: Table B.6;
Test type: Capability test.
Test case for restriction class
The information of the test case is as follows:
Test purpose: Check whether the required information is contained in the object of the restriction class;a)
Test method: Check whether the description, constraints, maximum number of occurrences, type and restrictions of each attribute listed in Table B.7 are allb)
Comply with the regulations;
Reference: Table B.7;
Test type: Capability test.
Test cases for feature attribute classes
The information of the test cases is as follows:
Test purpose: Check that the required information is contained in the objects of the feature attribute class; a)
Test method: Check whether the description, constraints, maximum number of occurrences, type and restrictions of each attribute and role listed in Table B.8 and Table B.4 comply with the regulations; b)
Reference: Table B.4 and Table B.8;
Test type: Capability test.
Test case for associated role class
The information of the test case is as follows:
Test purpose: Check that the required information is contained in the objects of the associated role class;a)
Test method: Check whether the description, constraints, maximum number of occurrences, type and restrictions of each attribute and role listed in Table B.9 (and B.4) comply with the regulations, and check whether the attribute type value (row 9.2 of Table B.9) is the domain code in Table B.10;7
GB/T28585-2012/ISO19110:2005 Reference: Table B.4, Table B.9 and Table B.10; Test type: capability test.
A.12 Test case for list value class
The information of the test case is as follows:
Test purpose: Check that the required information is contained in the objects of the list value class; a)
Test method: Check whether the description, constraints, maximum number of occurrences, types and restrictions of each attribute and role listed in Table B.11b)
are in compliance with the regulations;
Reference: Table B.11:
Test type, capability test.
Test case for feature association class
The information of the test case is as follows:
Test purpose: Check that the required information is contained in the objects of the feature association class; Test method: Check whether the detailed description, constraints, maximum number of occurrencesb)
number of occurrences, types and restrictions of each attribute and role listed in Table B.12 (and Table B.2) are in compliance with the regulations; Reference: Table B.2 and Table B.12;
Test type: capability test.
A.14 Test case for defining provenance class
The information of the test case is as follows:
a) Test purpose: Check that the required information is contained in the object defining the provenance class; Test method: Check whether the description, constraints, maximum number of occurrences, type and restrictions of each attribute listed in Table B.13 are all b)
compliant;
Reference: Table B.13:
d) Test type: Capability test.
Test case for defining reference class
The information of the test case is as follows;
a) Test purpose: Check that the required information is contained in the object defining the reference class; Test method: Check whether the detailed description, constraints, maximum number of occurrences, type and b)
restrictions of each attribute and role listed in Table B.14 are all in compliance;
Reference: Table B.14;
Test type: Capability test.
Test case for binding feature attribute class
The information of the test case is as follows:
Test purpose: Check that the required information is contained in the object of the binding feature attribute class; a)5 Test cases for feature type classes
The information of the test cases is as follows:
a) Test purpose: Check whether the required information is contained in the objects of the feature type class; Test method: Check whether the description, constraints, maximum number of occurrences, types and restrictions of each attribute and role listed in Table B.2b)
All meet the requirements;
Reference: Table B.2
Test type: Capability test.
A.6 Test cases for inheritance relationship classes
The information of the test cases is as follows:
Test purpose: Check whether the required information is contained in the objects of the inheritance relationship class; a)
Test method: Check whether the description, constraints, maximum number of occurrences, types and restrictions of each attribute and role listed in Table B.3b)
All meet the requirements;
Reference: Table B.3;
Test type: Capability test.
Test cases for feature operation classes
The information of the test cases is as follows:
Test purpose: Check whether the required information is contained in the objects of the feature operation class; abZxz.net
GB/T285852012/IS019110.2005
b) Test method: Check whether the description, constraints, maximum number of occurrences, types and restrictions of each attribute and role listed in Table B.5 (and Table B.4) comply with the regulations;
Reference: Table B.4 and Table B.5;
d) Test type: Capability test.
Test case for binding class
The information of the test case is as follows:
Test purpose: Check whether the required information is contained in the object of the binding class;a)
Test method: Check whether the description, constraints, maximum number of occurrences, type and restrictions of each attribute listed in Table B.6 are allb)
Comply with the regulations:
Reference: Table B.6;
Test type: Capability test.
Test case for restriction class
The information of the test case is as follows:
Test purpose: Check whether the required information is contained in the object of the restriction class;a)
Test method: Check whether the description, constraints, maximum number of occurrences, type and restrictions of each attribute listed in Table B.7 are allb)
Comply with the regulations;
Reference: Table B.7;
Test type: Capability test.
Test cases for feature attribute classes
The information of the test cases is as follows:
Test purpose: Check that the required information is contained in the objects of the feature attribute class; a)
Test method: Check whether the description, constraints, maximum number of occurrences, type and restrictions of each attribute and role listed in Table B.8 and Table B.4 comply with the regulations; b)
Reference: Table B.4 and Table B.8;
Test type: Capability test.
Test case for associated role class
The information of the test case is as follows:
Test purpose: Check that the required information is contained in the objects of the associated role class; a)
Test method: Check whether the description, constraints, maximum number of occurrences, type and restrictions of each attribute and role listed in Table B.9 (and B.4) comply with the regulations, and check whether the attribute type value (row 9.2 of Table B.9) is the domain code in Table B.10; 7
GB/T28585-2012/ISO19110:2005 Reference: Table B.4, Table B.9 and Table B.10; Test type: capability test.
A.12 Test case for list value class
The information of the test case is as follows:
Test purpose: Check that the required information is contained in the objects of the list value class; a)
Test method: Check whether the description, constraints, maximum number of occurrences, types and restrictions of each attribute and role listed in Table B.11b)
are in compliance with the regulations;
Reference: Table B.11:
Test type, capability test.
Test case for feature association class
The information of the test case is as follows:
Test purpose: Check that the required information is contained in the objects of the feature association class; Test method: Check whether the detailed description, constraints, maximum number of occurrencesb)
number of occurrences, types and restrictions of each attribute and role listed in Table B.12 (and Table B.2) are in compliance with the regulations; Reference: Table B.2 and Table B.12;
Test type: capability test.
A.14 Test case for defining provenance class
The information of the test case is as follows:
a) Test purpose: Check that the required information is contained in the object defining the provenance class; Test method: Check whether the description, constraints, maximum number of occurrences, type and restrictions of each attribute listed in Table B.13 are all b)
compliant;
Reference: Table B.13:
d) Test type: Capability test.
Test case for defining reference class
The information of the test case is as follows;
a) Test purpose: Check that the required information is contained in the object defining the reference class; Test method: Check whether the detailed description, constraints, maximum number of occurrences, type and b)
restrictions of each attribute and role listed in Table B.14 are all in compliance;
Reference: Table B.14;
Test type: Capability test.
Test case for binding feature attribute class
The information of the test case is as follows:
Test purpose: Check that the required information is contained in the object of the binding feature attribute class; a)4) Whether the description, constraint, maximum number of occurrences, type and restriction of each attribute and role listed are in compliance with the regulations, and check whether the attribute type value (row 9.2 of Table B.9) is the domain code in Table B.10; 7
GB/T28585——2012/ISO19110:2005 Reference: Table B.4, Table B.9 and Table B.10; Test type: capability test.
A.12 Test case for list value class
The information of the test case is as follows:
Test purpose: Check that the required information is contained in the object of the list value class; a)
Test method: Check whether the description, constraint, maximum number of occurrences, type and restriction of each attribute and role listed in Table B.11 are in compliance with the regulations;
Reference: Table B.11:
Test type, capability test.
Test case for feature association class
The information of the test case is as follows:
Test purpose: Check that the required information is included in the object of the feature association class; Test method: Check whether the detailed description, constraints, maximum number of occurrences, types and restrictions of each attribute and role listed in Table B.12 (and Table B.2) are in compliance with the regulations; Reference: Table B.2 and Table B.12;
Test type: Capability test.
A.14 Test case for definition of provenance class
The information of the test case is as follows:
a) Test purpose: Check that the required information is included in the object of the definition of provenance class; Test method: Check whether the description, constraints, maximum number of occurrences, types and restrictions of each attribute listed in Table B.13 are in compliance with the regulations;
Reference: Table B.13:
d) Test type: Capability test.
Test case for defining reference class
The information of the test case is as follows;
a) Test purpose: Check whether the required information is contained in the object of the defined reference class; Test method: Check whether the detailed description, constraints, maximum number of occurrences, type and b)
limits of each attribute and role listed in Table B.14 are in compliance with the regulations;
Reference: Table B.14;
Test type: Capability test.
Test case for binding feature attribute class
The information of the test case is as follows:
Test purpose: Check whether the required information is contained in the object of the binding feature attribute class;a)4) Whether the description, constraint, maximum number of occurrences, type and restriction of each attribute and role listed are in compliance with the regulations, and check whether the attribute type value (row 9.2 of Table B.9) is the domain code in Table B.10; 7
GB/T28585——2012/ISO19110:2005 Reference: Table B.4, Table B.9 and Table B.10; Test type: capability test.
A.12 Test case for list value class
The information of the test case is as follows:
Test purpose: Check that the required information is contained in the object of the list value class; a)
Test method: Check whether the description, constraint, maximum number of occurrences, type and restriction of each attribute and role listed in Table B.11 are in compliance with the regulations;
Reference: Table B.11:
Test type, capability test.
Test case for feature association class
The information of the test case is as follows:
Test purpose: Check that the required information is included in the object of the feature association class; Test method: Check whether the detailed description, constraints, maximum number of occurrences, types and restrictions of each attribute and role listed in Table B.12 (and Table B.2) are in compliance with the regulations; Reference: Table B.2 and Table B.12;
Test type: Capability test.
A.14 Test case for definition of provenance class
The information of the test case is as follows:
a) Test purpose: Check that the required information is included in the object of the definition of provenance class; Test method: Check whether the description, constraints, maximum number of occurrences, types and restrictions of each attribute listed in Table B.13 are in compliance with the regulations;
Reference: Table B.13:
d) Test type: Capability test.
Test case for defining reference class
The information of the test case is as follows;
a) Test purpose: Check whether the required information is contained in the object of the defined reference class; Test method: Check whether the detailed description, constraints, maximum number of occurrences, type and b)
limits of each attribute and role listed in Table B.14 are in compliance with the regulations;
Reference: Table B.14;
Test type: Capability test.
Test case for binding feature attribute class
The information of the test case is as follows:
Test purpose: Check whether the required information is contained in the object of the binding feature attribute class;a)
Tip: This standard content only shows part of the intercepted content of the complete standard. If you need the complete standard, please go to the top to download the complete standard document for free.