Sign In |Help & Support
ALL SECTORS
  • ALL SECTORS
  • GB(National Standard)
  • CB(Shipping)
  • CECS(Engineering Construction)
  • CJ(Urban Construction)
  • CY(News and Publication)
  • DB(Provincial Standard)
  • DL(Electricity & Power)
  • DZ(Geology & Mineralogy)
  • FZ(Spinning & Textile)
  • GA(Public Security)
  • HB(Aviation)
  • HG(Chemical Industry)
  • HJ(Environmental Protection)
  • JB(Machinery)
  • JC(Building Materials)
  • JG(Building & Construction)
  • JJ(Metering)
  • JT(Highway & Transportation)
  • LY(Forestry)
  • MT(Coal)
  • NB(Energy)
  • NY(Agriculture)
  • QB(Light Industry)
  • QC(Automobile & Vehicle)
  • QJ(Aerospace)
  • SH(Petrochemical)
  • SJ(Electronics)
  • SL(Water Resources)
  • SN(Commodity Inspection)
  • SY(Oil & Gas)
  • TB(Railway & Train)
  • YB(Ferrous Metallurgy)
  • YC(Tobacco)
  • YD(Telecommunication)
  • YY(Medical Device)
Database: 365,228(8 Aug 2026)
motor circuits forestry microclimate observation instrument emulsifier s-80
MZ/T 150-2020 in English

MZ/T 150-2020 in English

VALID

Administrative boundary data interchange format

  • Issued on:2020-03-24
  • Implemented on:2020-03-24
  • File Format:PDF
  • Delivery:Via email within 1~3 business days
Price(USD): $220.00
$214.00
Standard No: MZ/T 150-2020
Document status: VALID
Title in English: Administrative boundary data interchange format
Title in Chinese: 行政区域界线数据交换格式
Language: English
File Format: Electronic (PDF)
Delivery: Via email within 1~3 business days
Issued on: 2020-03-24
Implemented on: 2020-03-24
Professional Classification: MZ-Civil Affairs
Related Topics: line data
mz
Number of lines
Number world
area factor
Interface gauge specifications
Data mere
administrative district
district line
Boundary sub-region
pattern area
Region generation model
Format
exchange format
Data dual-machine switching industry


Introduction

Interpretation of the core content of the standard

Data category Format requirements Encoding standard Typical application
Attribute data CSV text (GB18030) RFC4180 specification Boundary approval document management
Spatial data Shapefile four-piece set GB/T2260 encoding GIS system integration
Multimedia data MP4/MP3/PDF Three-level directory storage Boundary survey process traceability

Key technical specifications

Boundary coding system

Adopts hierarchical combination coding: provincial boundaries are 4 digits (such as the Beijing-Tianjin line "1112"), municipal boundaries are 6 digits (such as the Changsha-Zhuzhou line "430102"), and county boundaries are 8-10 digits (for example, the Wangcheng-Ningxiang line "43011282"). The coding rules strictly follow the GB/T2260 administrative division code.

Spatial data requirements

Must include four core fields: identification code (GUID), boundary code, boundary name, and boundary level. The topological relationship of the linear features must be completely closed.


Implementation Suggestions

  1. Data Collection Phase: It is necessary to collect 20 types of documents such as boundary survey agreements and joint inspection reports simultaneously. Multimedia files are named according to the "boundary name + content type + serial number" rule.
  2. When connecting to the system: Note that the multimedia fields in the attribute data use "|" to separate multiple files (such as: Beijing-Tianjin Line Previous Meetings Multimedia 01.mp4|02.mp4)
  3. Security Control: Confidential multimedia materials should be stored separately and encrypted, and marked as "not available" in the attribute data.

Standard Evolution Analysis

This standard unifies the exchange format and storage specification of administrative boundary data for the first time, making up for the system interoperability difficulties caused by the independent practices of various regions. Compared with traditional surveying and mapping data standards, it innovatively incorporates multimedia boundary survey process records into the standardized management system.

Sample only — not a preview of MZ/T 150-2020
Page: 1 / 0
100%

Loading PDF document...

Error loading PDF. Please make sure the file is valid and try again.

We also recommend