Some standard content:
Industry Standard of the People's Republic of China
Standard for urban geospatial framework dataCJJ 103—2004
Approval department: Ministry of Construction of the People's Republic of China Implementation date: December 1, 2004
China Construction Engineering Corporation
2004 Beijing
Industry Standard of the People's Republic of China
Standard for urban geospatial framework dataCJJ 103—2004
Published and distributed by China Architecture & Building Press (Baiwan Village, western suburbs of Beijing) Distributed by Xinhua Bookstore
Printed by Beijing Miyun Hongguang Printing Factory
Format: 850×1168mm 1/32 Printing sheet: 3 Word count: 80,000 words First edition in September 2004 First printing in September 2004 Print run: 1—10,000 copies
Price: 12.0 yuan
Unified book number: 15112+11683
Proofreading All reprinting is subject to prosecution
If there is any problem with the printing and binding quality, please send it to our company for return (postal code 100037)
Our website: http://china-abp.con.cn Online bookstore: http://china-building.com.cnT KAONT KAca
Ministry of Construction of the People's Republic of China
No. 261
Announcement of the Ministry of Construction on the Release of Industry Standards
"Urban Geographic Space Framework Data Standard" The "Urban Geographic Space Framework Data Standard" is now approved as an industry standard, numbered CJJ1032004, and will be implemented from December 1, 2004. Among them, Articles 3.1.3, 3.2.1, and 3.2.2 are mandatory provisions and must be strictly implemented. This standard is organized by the Standard and Quota Research Institute of the Ministry of Construction and published by China Building Industry Press.
Ministry of Construction of the People's Republic of China
August 18, 2004
According to the requirements of the Ministry of Construction's Construction Standard No. 12003104, the standard compilation team has formulated this standard after in-depth investigation and research, careful analysis and summary of domestic and foreign scientific research results, combined with practical experience, and on the basis of extensive solicitation of opinions. The main technical contents of this standard are: 1: General principles: 2. Terms and codes: 3. Basic regulations: 4. Basic framework data of urban geospatial space: 5. Special framework data of urban geospatial space: 6. Quality of urban geospatial framework data: 7. Spatial registration of other data with urban geospatial framework data. The Ministry of Construction is responsible for the management and interpretation of the mandatory provisions of this standard, and the editor-in-chief is responsible for the interpretation of the specific technical contents.
Editor-in-chief of this standard: Construction Comprehensive Survey Research and Design Institute (No. 177, Dongzhimennei Street, Beijing, Postal Code 100007
Participating units of this standard: Ministry of Construction Information Center National Basic Geographic Information Center
Wuhan Planning and Land Management Information Center
Beijing Institute of Surveying and Mapping Design
Beijing Economic Information Center
Beijing Planning Commission Dongcheng Branch
Beijing Municipal Government Information Center
Shanghai Urban Development Information Research Center
Zibo Digital City Leading Group Office Zibo Planning Information Center| |tt||The main drafters of this standard: Wang Dan, Huang Jian, Ji Li Zonghua, Chen Zhuo, Xue Shu, Gao Ping, Sun Jianzhong, Wang YiwwW.bzxz.Net
Liu Ruomei, Wang Yuanjing, Yang Jiming, Cui Kehui
Wang Zujin, Li Haiming
HirKAoNirKAca
2 Terms and codes
2.2 Codes
3 Basic regulations
3.1 General requirements
3.2 Data base
3.3 Data description and expression
3.4 Basic attribute data
3.5 Metadata
4 Basic framework data of urban geographic space
4. 1Administrative division data
Road data
Water body data
Place name data
Building (structure) data
4.6Underground space facility data
Address data
Cadastral (land ownership) data
Mathematical image data
Elevation data
Survey control point data
5Urban geographic space special framework data
5.1Land use status data
Planned land use data
5.3Garden and green space data
5.4Special management area data||tt ||5.5 Public facilities data
5.6 Environmental data
6 Quality of urban geospatial framework data
6.1 Requirements for quality description of urban framework data6.2 Requirements for point accuracy of urban framework data6.3 Quality inspection and acceptance of urban framework data7 Spatial registration of other data with urban geospatial framework data7.1 General provisions
7.2 Registration methods and requirements
Appendix A High-level classification code for urban geospatial framework dataAppendix B Metadata content of urban geospatial framework dataExplanation of terms used in this standard
Explanation of clauses
T KAONT KAca
1 General Principles
1.0.1 This standard is formulated to standardize the content and quality of urban geospatial framework data, promote the application of urban geospatial data and the integration of geospatial data with national economic and social development information, and promote the construction, sharing and updating of urban public data resources.
1..2 This standard is applicable to the acquisition, processing, management and application services of geospatial framework data and public data in urban informatization construction, and is also applicable to the construction of urban information resources and various urban geographic information systems. 1.0.3 The creation of urban geospatial framework data shall comply with the following principles: 1 Urban geospatial framework data shall be created by the cooperation of various urban competent departments and used as shared geospatial data resources. 2 Urban geospatial framework data shall be the basic data that can provide users with thematic data on which to build.
1.0.4 The production and updating of urban geospatial framework data shall actively adopt advanced technologies and methods, and shall meet the quality requirements specified in this standard. 1.0.5 The production and update of urban geospatial framework data shall comply with the relevant national mandatory standards in addition to this standard. 2 Terms and codes
2.1 Terms
2.1.1 Urban geospatial data urban geospatial data Data on urban natural and human phenomena directly or indirectly related to the surface and underground locations.
2.1.2 Urban geospatial framework data urban geospatialframework data A widely used urban geospatial data, referred to as urban framework data. It is a set of geospatial data that describes the spatial characteristics, attribute characteristics and temporal characteristics of urban geographic framework elements collected and organized according to certain rules. It can be divided into basic framework data and special framework data.
2.1.3 Framework data code frameworkdat code The high-level classification code of the element in the framework data. 2.1.4 Identification code idenlilie
A code that uniquely identifies a geographic entity or element in a data set. 2.1.5 Geometric fidelity The degree of fidelity of the shape and shape of the real-world objects represented by geographic spatial elements.
2.1.6 Spatial characteristics The abstract expression of real-world elements in framework data. 2.1.7 Geographical name The proper name of different regions or geographical entities given by humans, referred to as place name. 2.1.8 Standard geographical name Standard geographical name Geographical name written in standardized language and characters and officially recognized. 2.1.9 Door number plate The place name sign indicating the name of the courtyard and independent door. In this standard, it refers to the place name sign for the courtyard and independent door.
HirKAoNrKAca
2.1.10 Storied building name plate The place name sign indicating the name of the numbered building. In this standard, it refers to the place name sign for the numbered building.
2.1.11Addressaddress
provides a positioning implementation for people, buildings and other spatial objects. It is used to uniquely identify points of interest, access and deliver to specific locations, and implement location-based positioning of geographic data. 2.1.12Postal addresspostal addressThe standard address for postal delivery is the identifier used by the post office to deliver mail to the recipient. It only contains the necessary address elements to distinguish each delivery point in the area. 2.2Code
GISGeographic Information Systemgeographical informalion systerGNSSGlobal Navigation Satellite Systemglobal Navigation Satellite SystemDigital Elevation Modeldigital elevation modelDEM
GMLGeographic Markup Languagegeographic Markup LanguageFwFramework Dataframeworkdata
DIdentifieridentifier
RMSE, root mean square error, that is, median error
root mean square error error.
Accuracy value at 95% confidence level
Mmandatory
Cmandatory when conditions are met
optional
3 Basic provisions
3.1 General requirements
3.1.1 Urban geographic spatial framework data should consist of basic framework data and special framework data, and should meet the following requirements:
1 Basic framework data should include administrative division data, road data, water body data, place name data, building (structure) data, underground space facility data, address data, cadastral (land ownership) data, digital image data, elevation data and measurement control point data, and its content and requirements should meet the requirements of Chapter 4 of this standard. 2 Special framework data may include land use status data, planned land use data, garden and green space data, special management area data, public service facility data and ecological environment data, and its content and requirements should meet the requirements of Chapter 5 of this standard. 3 All framework data shall comply with the basic provisions of this chapter and meet the quality requirements of Chapter 6 of this standard.
3.1.2 Each city may expand or delete framework data in the following ways as needed: 1. Add or reduce basic framework data classes or their subclasses. 2. Add or reduce special framework data classes or their subclasses. 3. Add or limit attribute items of framework data. 4. Add or limit attribute value range of framework data. 3.1.3 The establishment and update of urban framework data shall use the legal topographic allocation, land surveying and mapping, real estate surveying and mapping, and boundary measurement results as data sources. 3.1.4 The original scale of the data source used to establish or update urban framework data shall comply with the following provisions:
1-type area: 1:500~1:2000.
2 Category II area: 1:2000～1:5000, 3 Category III area: 1:5000～1:10000, Note: Category I area includes urban built-up area, planning area, key construction area and suburban main city 4
HiKAoNiKAca
town center area, etc.: Category II area refers to other areas in suburban areas, etc.: Category III area refers to other areas in remote suburbs, etc.
3.1.5 Urban framework data should be updated in a timely manner and should comply with the following provisions: 1 The updated data should be consistent with the accuracy of the original data. 2 When updating data, it should be ensured that spatial data, attribute data and corresponding metadata are updated synchronously.
3.1.6 The storage and exchange of urban framework data should comply with the following provisions: 1 Data formats that can be recognized by commercial GIS systems should be used for data storage. 2 The naming of data storage units should be concise and clear, and the name of the metadata file should be associated with the name of the physical data storage unit it describes. 3 When exchanging data, the current national standard "Earth Space Data Exchange Format" GB/T17798 or GML format can be used, and the element compilation table of the framework data and the corresponding metadata file should be submitted. 3.2 Data Datum
3.2.1 The framework data of a city must use a unified plane coordinate system and elevation system.
3.2.2 The plane coordinate system and elevation system of the city framework data should be consistent with the plane coordinate system and elevation system used for the basic surveying and mapping of the city, and should be connected with the national plane coordinate system and elevation system. 3.3 Data Description and Expression
3.3.1 The city framework data should describe the basic spatial characteristics and attribute characteristics of the city framework elements: and should include the temporal characteristics of data acquisition or update. 3.3.2 The description and expression of the spatial characteristics of the city framework data should comply with the provisions of Table 3.3.2.
3.3.3 The attribute characteristics of the city framework data should be expressed using a set of attribute information that describes the type, characteristics and related information of the elements. 3.3.4 The temporal characteristics of urban framework data should be expressed using a set of attribute information that describes the data acquisition or update status.
Spatial characteristics
Surface characteristics
Line characteristics
Point characteristics
Description and expression of spatial characteristics
Closed contour line
Closed boundary line
Boundary line
Boundary line
Center line
Center (center) point
Identification point
Polygon
Polygon
Polygon
3.3.5 Urban framework data should have a framework data code, and each element should have a classification code. Both the framework data code and the feature classification code can be expanded and should meet the following requirements:
1 The framework data code only defines the high-order code of the feature, which should be composed of 6 digits, of which the first two digits use "FW" to represent the framework data, the middle two digits are the code of the data class, and the last two digits are the code of the data subclass. The codes of the data class and data subclass should comply with the provisions of Appendix A Urban Geographic Spatial Framework Data High-level Classification Code. 2 The feature classification code should comply with the provisions of the current national standard push. The length of the feature classification code should not exceed 10 digits, and the value range should be 0~9 and A~Y (remove the letters I and 0).
3.3.6 The framework data should have an identification code (ID) and should meet the following requirements: 1 The identification code should be unique in the data set
2 When the identification code is changed, a change comparison table, change time and change number should be provided. The identification code should remain consistent during the data maintenance process. 3 The length of the identification code should be less than 20 digits, and the value range should be 0 to 9 and A to Y (excluding I and 0 in letters), and the first digit should not be 0. 3.4 Basic attribute data
3.4.1 All urban framework data should include the description framework number specified in Table 3.4.16
HirkAoNiikAca1 The urban geographic spatial framework data shall consist of basic framework data and special framework data, and shall meet the following requirements:
1 The basic framework data shall include administrative division data, road data, water body data, place name data, building (structure) data, underground space facility data, address data, cadastral (land ownership) data, digital image data, elevation data and measurement control point data, and its content and requirements shall comply with the provisions of Chapter 4 of this standard. 2 Special framework data may include land use status data, planned land use data, garden and green space data, special management area data, public service facility data and ecological environment data, etc., and its content and requirements shall comply with the provisions of Chapter 5 of this standard. 3 All framework data shall comply with the basic provisions of this chapter and shall meet the quality requirements of Chapter 6 of this standard.
3.1.2 Cities may expand or delete framework data in the following ways as needed: 1 Add or reduce basic framework data classes or their subclasses. 2 Add or reduce special framework data classes or their subclasses. 3. Add or limit the attribute items of framework data, 4. Add or limit the attribute value range of framework data. 3.1.3 The establishment and update of urban framework data should use the legal terrain allocation, land surveying and mapping, real estate surveying and mapping, and boundary measurement results as data sources. 3.1.4 The original scale of the data source used to establish or update urban framework data shall comply with the following provisions:
1. Class I area: 1:500～1:2000.
2. Class II area: 1:2000～1:5000, 3. Class III area: 1:5000～1:10000, Note: Class I area includes urban built-up area, planning area, key construction area and suburban main city 4
HiKAoNiKAca
town center area, etc.; Class II area refers to other areas in the suburbs, etc.; Class III area refers to other areas in the far suburbs, etc.
3.1.5 Urban framework data should be updated in a timely manner and should comply with the following provisions: 1 The updated data should be consistent with the accuracy of the original data. 2 When updating data, it should be ensured that spatial data, attribute data and corresponding metadata are updated synchronously.
3.1.6 The storage and exchange of urban framework data should comply with the following provisions: 1 Data should be stored in a data format that can be recognized by commercial GIS systems. 2 The naming of data storage units should be concise and clear, and the name of the metadata file should be associated with the name of the physical data storage unit it describes. 3 When exchanging data, the current national standard "Earth Space Data Exchange Format" GB/T17798 or GML format can be used, and the element compilation table of the framework data and the corresponding metadata file should be submitted. 3.2 Data Datum
3.2.1 The framework data of a city must use a unified plane coordinate system and elevation system.
3.2.2 The plane coordinate system and elevation system of the urban framework data shall be consistent with the plane coordinate system and elevation system used in the basic surveying and mapping of the city, and shall be integrally linked to the national plane coordinate system and elevation system. 3.3 Data description and expression
3.3.1 The urban framework data shall describe the basic spatial characteristics and attribute characteristics of the urban framework elements: and shall include the temporal characteristics of data acquisition or update. 3.3.2 The description and expression of the spatial characteristics of the urban framework data shall comply with the provisions of Table 3.3.2.
3.3.3 The attribute characteristics of the urban framework data shall be expressed using a set of attribute information that describes the type, characteristics and related information of the elements. 3.3.4 The temporal characteristics of urban framework data should be expressed using a set of attribute information that describes the data acquisition or update status.
Spatial characteristics
Surface characteristics
Line characteristics
Point characteristics
Description and expression of spatial characteristics
Closed contour line
Closed boundary line
Boundary line
Boundary line
Center line
Center (center) point
Identification point
Polygon
Polygon
Polygon
3.3.5 Urban framework data should have a framework data code, and each element should have a classification code. Both the framework data code and the feature classification code can be expanded and should meet the following requirements:
1 The framework data code only defines the high-order code of the feature, which should be composed of 6 digits, of which the first two digits use "FW" to represent the framework data, the middle two digits are the code of the data class, and the last two digits are the code of the data subclass. The codes of the data class and data subclass should comply with the provisions of Appendix A Urban Geographic Spatial Framework Data High-level Classification Code. 2 The feature classification code should comply with the provisions of the current national standard push. The length of the feature classification code should not exceed 10 digits, and the value range should be 0~9 and A~Y (remove the letters I and 0).
3.3.6 The framework data should have an identification code (ID) and should meet the following requirements: 1 The identification code should be unique in the data set
2 When the identification code is changed, a change comparison table, change time and change number should be provided. The identification code should remain consistent during the data maintenance process. 3 The length of the identification code should be less than 20 digits, and the value range should be 0 to 9 and A to Y (excluding I and 0 in letters), and the first digit should not be 0. 3.4 Basic attribute data
3.4.1 All urban framework data should include the description framework number specified in Table 3.4.16
HirkAoNiikAca1 The urban geographic spatial framework data shall consist of basic framework data and special framework data, and shall meet the following requirements:
1 The basic framework data shall include administrative division data, road data, water body data, place name data, building (structure) data, underground space facility data, address data, cadastral (land ownership) data, digital image data, elevation data and measurement control point data, and its content and requirements shall comply with the provisions of Chapter 4 of this standard. 2 Special framework data may include land use status data, planned land use data, garden and green space data, special management area data, public service facility data and ecological environment data, etc., and its content and requirements shall comply with the provisions of Chapter 5 of this standard. 3 All framework data shall comply with the basic provisions of this chapter and shall meet the quality requirements of Chapter 6 of this standard.
3.1.2 Cities may expand or delete framework data in the following ways as needed: 1 Add or reduce basic framework data classes or their subclasses. 2 Add or reduce special framework data classes or their subclasses. 3. Add or limit the attribute items of framework data, 4. Add or limit the attribute value range of framework data. 3.1.3 The establishment and update of urban framework data should use the legal terrain allocation, land surveying and mapping, real estate surveying and mapping, and boundary measurement results as data sources. 3.1.4 The original scale of the data source used to establish or update urban framework data shall comply with the following provisions:
1. Class I area: 1:500～1:2000.
2. Class II area: 1:2000～1:5000, 3. Class III area: 1:5000～1:10000, Note: Class I area includes urban built-up area, planning area, key construction area and suburban main city center area, etc.; Class II area refers to other areas in the suburbs, etc.; Class III area refers to other areas in the far suburbs, etc.
3.1.5 Urban framework data should be updated in a timely manner and should comply with the following provisions: 1 The updated data should be consistent with the accuracy of the original data. 2 When updating data, it should be ensured that spatial data, attribute data and corresponding metadata are updated synchronously.
3.1.6 The storage and exchange of urban framework data should comply with the following provisions: 1 Data should be stored in a data format that can be recognized by commercial GIS systems. 2 The naming of data storage units should be concise and clear, and the name of the metadata file should be associated with the name of the physical data storage unit it describes. 3 When exchanging data, the current national standard "Earth Space Data Exchange Format" GB/T17798 or GML format can be used, and the element compilation table of the framework data and the corresponding metadata file should be submitted. 3.2 Data Datum
3.2.1 The framework data of a city must use a unified plane coordinate system and elevation system.
3.2.2 The plane coordinate system and elevation system of the urban framework data shall be consistent with the plane coordinate system and elevation system used in the basic surveying and mapping of the city, and shall be integrally linked to the national plane coordinate system and elevation system. 3.3 Data description and expression
3.3.1 The urban framework data shall describe the basic spatial characteristics and attribute characteristics of the urban framework elements: and shall include the temporal characteristics of data acquisition or update. 3.3.2 The description and expression of the spatial characteristics of the urban framework data shall comply with the provisions of Table 3.3.2.
3.3.3 The attribute characteristics of the urban framework data shall be expressed using a set of attribute information that describes the type, characteristics and related information of the elements. 3.3.4 The temporal characteristics of urban framework data should be expressed using a set of attribute information that describes the data acquisition or update status.
Spatial characteristics
Surface characteristics
Line characteristics
Point characteristics
Description and expression of spatial characteristics
Closed contour line
Closed boundary line
Boundary line
Boundary line
Center line
Center (center) point
Identification point
Polygon
Polygon
Polygon
3.3.5 Urban framework data should have a framework data code, and each element should have a classification code. Both the framework data code and the feature classification code can be expanded and should meet the following requirements:
1 The framework data code only defines the high-order code of the feature, which should be composed of 6 digits, of which the first two digits use "FW" to represent the framework data, the middle two digits are the code of the data class, and the last two digits are the code of the data subclass. The codes of the data class and data subclass should comply with the provisions of Appendix A Urban Geographic Spatial Framework Data High-level Classification Code. 2 The feature classification code should comply with the provisions of the current national standard push. The length of the feature classification code should not exceed 10 digits, and the value range should be 0~9 and A~Y (remove the letters I and 0).
3.3.6 The framework data should have an identification code (ID) and should meet the following requirements: 1 The identification code should be unique in the data set
2 When the identification code is changed, a change comparison table, change time and change number should be provided. The identification code should remain consistent during the data maintenance process. 3 The length of the identification code should be less than 20 digits, and the value range should be 0 to 9 and A to Y (excluding I and 0 in letters), and the first digit should not be 0. 3.4 Basic attribute data
3.4.1 All urban framework data should include the description framework number specified in Table 3.4.16
HirkAoNiikAca5 The urban framework data should have a framework data code, and each element should have a classification code. Both the framework data code and the element classification code can be expanded and should meet the following requirements:
1 The framework data code only defines the high-order code of the element, which should be composed of 6 digits, of which the first two digits use "FW" to represent the framework data, the middle two digits are the code of the data class, and the last two digits are the code of the data subclass. The codes of the data class and data subclass should comply with the provisions of Appendix A Urban Geographic Spatial Framework Data High-order Classification Code. 2 The element classification code should comply with the provisions of the current national standard push. The length of the element classification code should not exceed 10 digits, and the value range should be 0~9 and A~Y (remove the letters I and 0).
3.3.6 The framework data should have an identification code (ID) and should meet the following requirements: 1 The identification code should be unique in the data set
2 When the identification code is changed, a change comparison table, change time and change number should be provided. The identification code should remain consistent during the data maintenance process. 3 The length of the identification code should be less than 20 digits, and the value range should be 0 to 9 and A to Y (excluding I and 0 in letters), and the first digit should not be 0. 3.4 Basic attribute data
3.4.1 All urban framework data should include the description framework number specified in Table 3.4.16
HirkAoNiikAca5 The urban framework data should have a framework data code, and each element should have a classification code. Both the framework data code and the element classification code can be expanded and should meet the following requirements:
1 The framework data code only defines the high-order code of the element, which should be composed of 6 digits, of which the first two digits use "FW" to represent the framework data, the middle two digits are the code of the data class, and the last two digits are the code of the data subclass. The codes of the data class and data subclass should comply with the provisions of Appendix A Urban Geographic Spatial Framework Data High-order Classification Code. 2 The element classification code should comply with the provisions of the current national standard push. The length of the element classification code should not exceed 10 digits, and the value range should be 0~9 and A~Y (remove the letters I and 0).
3.3.6 The framework data should have an identification code (ID) and should meet the following requirements: 1 The identification code should be unique in the data set
2 When the identification code is changed, a change comparison table, change time and change number should be provided. The identification code should remain consistent during the data maintenance process. 3 The length of the identification code should be less than 20 digits, and the value range should be 0 to 9 and A to Y (excluding I and 0 in letters), and the first digit should not be 0. 3.4 Basic attribute data
3.4.1 All urban framework data should include the description framework number specified in Table 3.4.16
HirkAoNiikAca
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.