Methods, apparatus and readable storage media for standardizing electronic map cartographic data

By matching template project files and XML file media, the standardized processing of electronic map cartographic data is realized, solving the problem of low cartographic efficiency in existing technologies and achieving automated standardization and efficient matching of data.

CN117725135BActive Publication Date: 2026-11-17CHINA MOBILE SHANGHAI ICT CO LTD +2
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202211090903.4
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-09-07
Publication Date
2026-11-17
Estimated Expiration
2042-09-07

AI Technical Summary

Technical Problem

The current electronic map production process requires a lot of time and manpower, resulting in low efficiency and an inability to achieve fast, convenient, efficient, and standardized data processing.

Method used

By matching template project files, geographic information data in the master database is matched with template data in the template database to generate a standard database. XML files are used as a medium to realize data exchange between heterogeneous databases, and after successful matching, the data is imported into the template database to form standardized data.

Benefits of technology

It automates the process from inputting data to loading data, avoids manual calibration, improves the efficiency of electronic map making, and ensures the accuracy of data content integration and matching with the framework.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117725135B_ABST
    Figure CN117725135B_ABST
Patent Text Reader

Abstract

This invention provides a method, apparatus, and readable storage medium for standardizing electronic map mapping data. The method includes: matching geographic information data in a master database with template data in a template database using a matching template engineering file; importing the geographic information data into the template database if a successful match is found; and defining the template database after importing the geographic information data as a standard database. The data in the standard database is standardized data. The matching template engineering file stores the correspondence between the geographic information data and the template data. The template data includes at least one of the following: a template layer, template fields under the template layer, and attributes of the template fields. Therefore, the matching template engineering file can be used to standardize the data, enabling a one-step automated process from inputting data, matching data, to loading data to complete the mapping, minimizing manual calibration and thus improving the efficiency of electronic map creation.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of electronic map cartographic data processing, and in particular to methods, apparatus and readable storage media for standardizing electronic map cartographic data. Background Technology

[0002] Against the backdrop of rapid development in computer technology, network technology, and digital cartography, electronic mapmaking has gradually become the mainstream cartographic mode. With the rise of geolocation services and the continuous development of data acquisition technologies, mapmaking faces significant challenges, including large volumes of map data, diverse and abundant data types and sources, varied map styles, and a large user base. Furthermore, traditional online mapmaking not only requires cartographers to possess high levels of cartographic and aesthetic literacy but also certain programming skills, and suffers from problems such as repetitive workloads and low efficiency. Therefore, achieving rapid, convenient, and efficient mapmaking from geospatial data has become a research hotspot. Standardizing and streamlining geospatial data has become a convenient and fast way to create electronic maps.

[0003] Current data processing methods mostly standardize the format or name of the data. During the mapping process, manual verification and proofreading are required, making it impossible to reuse the data. Alternatively, in the map matching stage after data processing, manual verification and correction of mismatched data are required each time. As a result, electronic map production requires a lot of time and manpower, resulting in low efficiency. Summary of the Invention

[0004] To address the problems of high time and manpower consumption and low efficiency in electronic map creation in the prior art, this invention provides a method, apparatus, and readable storage medium for standardizing electronic map creation data. Specifically, it is implemented as follows:

[0005] In a first aspect, embodiments of the present invention provide a method for standardizing electronic map cartographic data, the method comprising:

[0006] By matching template project files, geographic information data in the master database is matched with template data in the template database;

[0007] If a match is found to be successful, the geographic information data is imported into the template database;

[0008] The template database after importing the geographic information data is designated as the standard database; wherein, the data in the standard database is standardized data.

[0009] The matching template project file stores the correspondence between the geographic information data and the template data; the template data includes at least one of the following: template layer, template field under template layer, and attribute of template field.

[0010] Preferably, the matching template project file is generated through the following steps:

[0011] Determine the data relationships corresponding to geographic information data in the initial master database;

[0012] Generate a node tree structure based on the data relationships;

[0013] Store the node tree structure in an XML file;

[0014] Parse the node tree structure in the XML file and import the parsed data into the template database;

[0015] The parsed data is matched with the template data;

[0016] After confirming a successful match, a matching template project file is generated.

[0017] Preferably, the data relationships include at least one of the following: the correspondence between geographic information data and layers, the correspondence between layers and fields, the correspondence between fields and field attributes, and the correspondence between fields and field content; generating a node tree structure based on the data relationships includes:

[0018] Convert the layer into node A;

[0019] Convert the field names corresponding to the layer into child node B of node A;

[0020] Convert the field attribute corresponding to the field name into a child node C of the child node B;

[0021] Convert the field content corresponding to the field name into a child node D of child node C;

[0022] The attributes in the field are transformed into leaf nodes b of the child node B;

[0023] Generate a node tree structure according to the correspondence between nodes and child nodes.

[0024] Preferably, matching the parsed data with the template data includes:

[0025] Match the layers corresponding to the geographic information data with the template layers;

[0026] After a successful match, the field name is matched against the template field name;

[0027] After a successful match, the field's attributes are matched against the template field's attributes.

[0028] Preferably, after matching the field attributes with the template field attributes, the method further includes:

[0029] After a successful match, the content of the field corresponding to the field name will be used as the content of the template field name;

[0030] Use the content of the attribute of the field name as the content of the attribute of the template field;

[0031] The attribute includes at least one of the following: field type, field length, and field decimal places.

[0032] Preferably, before matching the geographic information data in the master database with the template data in the template database by matching the template project file, the method further includes:

[0033] Establish a master database, wherein establishing the master database includes:

[0034] Acquire basic geographic information data;

[0035] Clean the aforementioned basic geographic information data;

[0036] The cleaned basic geographic information data is divided into point data sets, line data sets, and polygon data sets.

[0037] Merge the point data set, line data set, and polygon data set;

[0038] The merged dataset is defined as the parent dataset.

[0039] Preferably, the point data set includes at least one of the following: key point set, high-density point set, and low-density point set; the line data set includes at least one of the following: road line set, water system line set, and provincial / municipal / district boundary line set; the surface data set includes at least one of the following: provincial interface, scene surface, functional surface, green ground, water system surface, lake / reservoir surface, building surface, and residential ground.

[0040] Preferably, before matching the geographic information data in the master database with the template data in the template database by matching the template project file, the method further includes:

[0041] Establishing the template database includes:

[0042] Establish an initial database; wherein the initial database is a database that imports layer name specification tables and field name specification tables; wherein the initial database includes: layers, fields under layers, and field attributes;

[0043] According to user-preset rules, calibrate the layers, fields under the layers, and attributes of the fields in the initial database;

[0044] The calibrated initial database is determined as the template database.

[0045] In a second aspect, embodiments of the present invention provide an apparatus for standardizing electronic map cartographic data, the apparatus being used to perform the method described in the first aspect, the apparatus comprising:

[0046] The matching module is used to match geographic information data in the master database with template data in the template database by matching template project files;

[0047] The import module is used to import the geographic information data into the template database when a match is found to be successful.

[0048] The determination module is used to determine the template database after importing the geographic information data as a standard database; wherein the data in the standard database is standardized data;

[0049] The matching template project file stores the correspondence between the geographic information data and the template data; the template data includes at least one of the following: template layer, template field under template layer, and attribute of template field.

[0050] Preferably, the device further includes:

[0051] The generation module is used to generate a matching template project file, including: determining the data relationships corresponding to the geographic information data in the initial data master database; generating a node tree structure based on the data relationships; storing the node tree structure in an XML file; parsing the node tree structure in the XML file and importing the parsed data into the template database; matching the parsed data with the template data; and generating a matching template project file after confirming a successful match.

[0052] Preferably, the data relationships include at least one of the following: the correspondence between geographic information data and layers, the correspondence between layers and fields, the correspondence between fields and field attributes, and the correspondence between fields and field content.

[0053] The generation module is specifically used to convert a layer into node A; convert the field name corresponding to the layer into a child node B of node A; convert the field attribute corresponding to the field name into a child node C of child node B; convert the field content corresponding to the field name into a child node D of child node C; convert the attribute in the field into a leaf node b of child node B; and generate a node tree structure according to the correspondence between nodes and child nodes.

[0054] Preferably, the generation module is specifically used to match the layer corresponding to the geographic information data with the template layer; after a successful match, to match the field name with the template field name; and after a successful match, to match the field attribute with the template field attribute.

[0055] Preferably, the generation module is specifically used to use the field content corresponding to the field name as the field content of the template field name after successfully matching the field attribute with the template field attribute;

[0056] Use the content of the attribute of the field name as the content of the attribute of the template field;

[0057] The attribute includes at least one of the following: field type, field length, and field decimal places.

[0058] Preferably, the device further includes:

[0059] The first module is used to create a master database before matching the geographic information data in the master database with the template data in the template database by matching the template project file.

[0060] The establishment of the data master database includes: acquiring basic geographic information data; cleaning the basic geographic information data; dividing the cleaned basic geographic information data into point data sets, line data sets, and polygon data sets; merging the point data sets, line data sets, and polygon data sets; and determining the merged data set as the data master database.

[0061] Preferably, the point data set includes at least one of the following: key point set, high-density point set, and low-density point set; the line data set includes at least one of the following: road line set, water system line set, and provincial / municipal / district boundary line set; the surface data set includes at least one of the following: provincial interface, scene surface, functional surface, green ground, water system surface, lake / reservoir surface, building surface, and residential ground.

[0062] Preferably, the device further includes: a second establishment module, used to establish the template database, wherein establishing the template database includes: establishing an initial database; wherein the initial database is a database that imports a layer name specification table and a field name specification table; calibrating the layers, fields under the layers, and attributes of the fields in the initial database according to user preset rules; and determining the calibrated initial database as the template database; wherein the initial database includes: layers, fields under the layers, and attributes of the fields.

[0063] Thirdly, embodiments of the present invention provide an electronic device, including: a processor, a memory, and a program stored in the memory and executable on the processor, wherein when the program is executed by the processor, it implements the steps of the method for standardizing electronic map cartographic data as described in the first aspect.

[0064] Fourthly, embodiments of the present invention provide a computer-readable storage medium storing a computer program. When executed by a processor, the computer program implements the steps of the method for standardizing electronic map cartographic data as described in the first aspect. In the matching template engineering file described in the embodiments of the present invention, a correspondence between geographic information data and template data is stored. This application utilizes the matching template engineering file to achieve the matching of geographic information data in the master database and template data in the template database. The geographic information data provides specific data content, while the template data includes template layers, template fields under the template layers, and attributes of the template fields, providing a data framework. After successful matching, the geographic information data is imported into the template database, thereby achieving the fusion of data content and data framework, and thus achieving data standardization. A standard database is obtained. Therefore, the matching template engineering file can be used to standardize data, thereby achieving an automated process from inputting data, matching data, to loading data to complete the mapping in one step, while minimizing manual calibration, thereby improving the efficiency of electronic map cartography. Attached Figure Description

[0065] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the invention. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings:

[0066] Figure 1 A flowchart of an electronic map cartographic data standardization method provided in an embodiment of the present invention;

[0067] Figure 2 This invention provides a method that differs from... Figure 1 The flowchart shown illustrates the standardization method for electronic map cartographic data.

[0068] Figure 3 This invention provides a method that differs from... Figure 1 , Figure 2 The flowchart shown illustrates the standardization method for electronic map cartographic data.

[0069] Figure 4 A structural block diagram of an electronic map cartographic data standardization device provided in an embodiment of the present invention;

[0070] Figure 5 This invention provides a method that differs from... Figure 4 The diagram shows the structural block diagram of the electronic map cartographic data standardization device.

[0071] Figure 6 This invention provides a method that differs from... Figure 4 , Figure 5 The diagram shows the structural block diagram of the electronic map cartographic data standardization device.

[0072] Figure 7 This is a structural block diagram of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0073] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0074] With the continuous development of technology, electronic maps are widely used in various fields of society. Electronic map creation often involves various types of data, and these different data often have different formats and types, frequently resulting in heterogeneous databases. Therefore, based on the needs of electronic map users, relevant technologies are used for data integration, format unification, and template processing. This can, to a certain extent, standardize data in heterogeneous databases, enabling fast, convenient, and streamlined map creation operations when dealing with repetitive and large amounts of geospatial data. Based on this, this invention discloses a method for standardizing electronic map creation data, such as... Figure 1 As shown, the method includes:

[0075] Step S101: Match the geographic information data in the master database with the template data in the template database by matching the template project file;

[0076] Step S102: If the match is successful, import the geographic information data into the template database;

[0077] Step S103: Determine the template database after importing geographic information data as the standard database;

[0078] In step S101, this application utilizes a matching template project file to match the geographic information data in the master database with the template data in the template database. The matching template project file is pre-generated and stores the correspondence between geographic information data and template data. The master database stores geographic information data, which serves as the source data for electronic map creation. Users need to collect and organize geographic information data according to their mapping needs and store the organized geographic information data in the master database. Examples of geographic information data include: fire departments, judicial departments, zoos, hotels, schools, etc. Geographic information data includes specific data content, such as: the specific address, latitude and longitude of a hotel, and the hotel's front desk telephone number. The template database stores template data, which includes at least one of the following: template layers, template fields under the template layers, and attributes of the template fields. This provides a data framework for the geographic information data in the master database.

[0079] In step S102, if the geographic information data and template data are successfully matched, the geographic information data is imported into the template database. If the matching fails, the data matching continues until a match is successful. It is understood that a matching time limit can be preset. If a match is not successful within the preset time limit, a prompt signal is sent to the user. The prompt signal can be an audio signal or a text signal to instruct the user to check the mapping software.

[0080] In step S103, the data in the standard database is standardized data. Therefore, the specific content of geographic information data can be integrated with the standard data framework to form standardized data, and the database storing this standardized data can be called a standard database. The standard database can be directly used in subsequent mapping processes.

[0081] In the matching template engineering file described in this embodiment of the invention, the correspondence between geographic information data and template data is stored. This application utilizes the matching template engineering file to achieve the matching of geographic information data in the master database and template data in the template database. The geographic information data provides specific data content, while the template data, including template layers, template fields under template layers, and attributes of template fields, provides a data framework. After successful matching, the geographic information data is imported into the template database, thereby achieving the fusion of data content and data framework, and thus realizing data standardization. A standard database is obtained. Therefore, the solution shown in this embodiment of the application uses the matching template engineering file to standardize the data, standardizing it from the database, data layers, and data fields. This allows for a one-step automated process from inputting data to loading data to complete the mapping, minimizing manual calibration and improving the efficiency of electronic map production.

[0082] In a preferred implementation, such as Figure 2 As shown, the matching template project file is generated through the following steps:

[0083] Step S201: Determine the data relationships corresponding to the geographic information data in the initial data master database;

[0084] Step S202: Generate a node tree structure based on the data relationships;

[0085] Step S203: Store the node tree structure in an XML file;

[0086] Step S204: Parse the node tree structure in the XML file and import the parsed data into the template database;

[0087] Step S205: Match the parsed data with the template data;

[0088] Step S206: After confirming a successful match, generate the matching template project file.

[0089] Understandably, the master database and the template database are two databases with different structures. The template database is a database with a standardized data structure formed according to the user's needs for creating thematic maps. The master database is a database of raw basic geographic information data after preprocessing and classification (the establishment of the master database and template database will be described in detail in the following implementation method, and will not be repeated here). Databases with different structures cannot directly exchange data. To achieve data exchange between two databases with different structures, it is necessary to extract data information and content from the master database and store the extracted data information in a specific file format. Moreover, the file must be able to describe the data information, store the data content, and facilitate transmission. In this preferred implementation method, XML is selected as the medium file.

[0090] XML is an extensible markup language that emphasizes structural descriptions and reveals various relationships between data when describing related data. It is characterized by its extensibility, simplicity, convenience, and openness. XML also describes the structure of data in a database in text form, thus enabling cross-platform data exchange. These files consist of several elements, all described using tags. This tagging allows data to maintain its original structure and meaning during exchange, thereby ensuring the accuracy and flexibility of data exchange between heterogeneous databases. Therefore, XML files are used as a medium for data transmission between heterogeneous databases. The process involves using XML files as an intermediary to achieve data exchange between the database and the XML file. The data to be exchanged is first converted into an XML file by an XML file converter and exported from the parent database. After parsing, validation, and other syntax analysis processing, the corresponding data template is called through the XML file template. Finally, the data is converted into the corresponding database data format by the data converter and imported into the target database.

[0091] When the above method is applied to this invention, then as follows: Figure 2 As shown, firstly, the data relationships corresponding to the geographic information data in the initial master database are determined. These data relationships include at least one of the following: the correspondence between geographic information data and layers, the correspondence between layers and fields, the correspondence between fields and field attributes, and the correspondence between fields and field content (table). Based on these data relationships, a node tree structure is generated: layers are converted into node A; field names corresponding to layers are converted into child nodes B of node A; field attributes corresponding to field names are converted into child nodes C of child node B; field content corresponding to field names is converted into child nodes D of child node C; and attributes in fields are converted into leaf nodes of child node B. Child node b is used to generate a node tree structure based on the correspondence between nodes and child nodes. This node tree structure is then stored in an XML file. The node tree structure in the XML file is parsed, and the parsed data is imported into the template database. It's important to ensure uninterrupted transmission and data integrity during data transfer using XML files. Furthermore, the XML file's format should be checked at the template database end. If an error is found, it should be corrected or retransmitted until the correct format is achieved. Finally, the data information and content in the XML file are parsed and extracted, and the parsed data is imported into the template database. Thus, the conversion between databases with different structures has been achieved using XML files.

[0092] It should be noted that after data conversion, this application also discloses: matching the parsed data with template data, and generating a matching template project file after successful matching. It should be noted that the XML file only serves as a transmission medium to solve the problem of direct data exchange between two databases with different structures; the XML file does not change the data content. Therefore, the parsed data consists of the geographic information data, layers, fields, field attributes, and field content in the parent database. Based on this, the specific matching process is as follows: matching the layers corresponding to the geographic information data with the template layers; after successful matching, matching the field names with the template field names; after successful matching, matching the field attributes with the template field attributes. Specifically, after layer matching, the fields and field attributes under the layer are automatically matched, and the matching of fields and their attributes can be calibrated during the matching process. Fields with incorrect or no matching can be adjusted or deleted until a successful match is achieved. After successful matching, the data content can be filled into the data frame one by one, that is, the geographic information data in the parent database is represented in a standardized frame. Specifically: the content of the field corresponding to the field name is used as the content of the template field name, and the content of the field name's attributes is used as the content of the template field's attributes; whereby the attributes include at least one of the following: field type, field length, and field decimal places. Based on this, the geographic information data in the parent database has been imported into the template database, and the standard database has been generated, which can be used for subsequent mapping processes. However, it should be noted that... Figure 2 The preferred implementation shown ultimately aims to generate a matching template project file. This file, in XML format, serves as a complete record of the matching process, storing the correspondence between geographic information data and template data. Once the matching template project file is determined, it can be executed during subsequent electronic map production. Figure 1 The method described above emphasizes that the master database used for each mapping operation must meet the conditions for matching using the matching template project file. Specifically, the master database used for each mapping operation must have the same layers, fields, and mapping patterns as the master database used when determining the matching template project file. Therefore, the master database can be directly matched with the template database using the matching template project file. After a successful match, the geographic information data is imported into the template database, which is then designated as the standard database. This improves the efficiency of matching basic geographic information data with the template. Furthermore, by standardizing the data, a perfect match between the data and the map can be achieved when loading the map, improving matching accuracy and shortening matching time. Moreover, by setting the matching template project file, the matching scheme can be used cyclically, achieving a standardized and automated matching process, avoiding manual intervention, and improving data processing efficiency.

[0093] In a preferred implementation, such as Figure 3 As shown, before matching the geographic information data in the master database with the template data in the template database by matching the template project file, the method further includes:

[0094] Establish a master database, which includes:

[0095] Step S301: Obtain basic geographic information data;

[0096] Step S302: Clean the basic geographic information data;

[0097] Step S303: Divide the cleaned basic geographic information data into point data sets, line data sets, and polygon data sets;

[0098] Step S304: Merge the point data set, line data set, and area data set;

[0099] Step S305: Determine the merged data set as the parent database.

[0100] Geographic data cleaning primarily involves standardizing the collected, measured, and quality-checked basic geographic information data. The specific process is as follows: First, a large amount of raw basic geographic information data is collected to ensure basic data quality and richness, meeting the needs of cartography. Second, the data is checked for special characters, their causes are analyzed, and special characters are deleted. Then, the data format is standardized; specifically, non-Chinese characters are converted to English characters, and full-width characters are converted to half-width characters. Outliers are then deleted, such as NULL values, to optimize data quality and remove duplicate data. Specifically, data with identical coordinates, attributes, and category names are defined as duplicates and deleted. Finally, the coordinate system is standardized by using the data processing module in the FME (Feature Manipulate Engine) software to perform coordinate system transformation according to cartographic requirements, ensuring that the acquired data have the same coordinate system. It should be noted that the above steps are not restricted by their execution order; only one possible implementation method is shown.

[0101] After cleaning the basic geographic information data, the cleaned and formatted basic geographic information data can be classified and divided into several datasets according to the data categories through data merging, data fusion, topology processing, and other methods.

[0102] Preferably, all cleaned basic geographic information data can be divided into three categories: point data, line data, and area data. Among them, point data is geographic feature interest point data, which is divided into general landmarks, government and party organs, catering and accommodation, sightseeing and tourism, cultural and sports leisure, shopping malls and supermarkets, transportation services, scientific research and education, public services, and commercial institutions according to traditional classification habits. The detailed classification details are shown in Table 1.

[0103]

[0104]

[0105] Table 1

[0106] Preferably, the point data shown in Table 1 can be divided into three point sets in this application: the point data set includes at least one of the following: a key point set, a high-density point set, and a low-density point set. The key point set includes seven types of points of interest: municipal and above-level government agencies, top-tier hospitals (Grade A and above), 4A-level and above scenic spots, key universities, major railway stations, airports, and subway stations. The high-density point set mainly refers to other points of interest that people pay attention to in urban life, excluding the key point sets, encompassing all aspects of people's daily lives, such as shopping malls, education, medical care, and housing. The low-density point set mainly refers to points of interest with low distribution density, such as mountains and bridges in suburban areas, township government agencies in towns and villages, and points of interest related to people's daily lives. The line data set includes at least one of the following: a road line set, a water system line set, and a provincial / municipal / district boundary line set. The surface data set includes at least one of the following: provincial boundaries, scene surfaces, functional surfaces, green areas, water system surfaces, lake and reservoir surfaces, building surfaces, and residential ground surfaces. After data classification, data of the same category can be stored in the same GDB database. Then, using ArcGIS data processing tools, the classified data can be integrated into a single dataset, and the dataset names can be standardized to establish a unified master database. This process first acquires a large amount of basic geographic information data, ensuring its basic quality and richness, and providing sufficient data for cartography. Cleaning the basic geographic information data further guarantees its quality. The cleaned data is then classified, organized, and merged into a unified master database, providing a data source foundation for subsequent data standardization steps.

[0107] In a preferred implementation, before matching the geographic information data in the master database with the template data in the template database through a matching template project file, the method further includes: establishing a template database, which includes: establishing an initial database; wherein the initial database is a database that imports layer name specification tables and field name specification tables; wherein the initial database includes: layers, fields under the layers, and field attributes; calibrating the layers, fields under the layers, and field attributes in the initial database according to user-preset rules; and determining the calibrated initial database as the template database. This implementation provides a detailed introduction to how to establish a template database. First, an initial database can be established, which can be a database storing data in GDB format to define the data attribute standards of the template database. Two data table files need to be imported into the initial database: a layer name specification table and a field name specification table. These two tables are determined according to the national standard GB13923-2016 Basic Geographic Information Classification and Codes and user requirements. Table 2 is the layer name specification table. It should be noted that the field name specification table standardizes the fields under each layer. Table 3 is the field name specification table corresponding to the POI layer as an example.

[0108]

[0109] Table 2

[0110]

[0111]

[0112] Table 3

[0113] The initial database includes layers, fields under those layers, and field attributes, but the actual data content is empty. After establishing the initial database, the layers, fields, and field attributes within it can be calibrated according to user-preset rules, and the calibrated initial database is then designated as the template database. Specifically, each layer and field can be further checked to ensure it meets user requirements or is error-free. Layer names can be added, modified, or deleted. After this process, field names under each layer can be added, modified, or deleted. The type, length, and precision (decimal places) of each field are determined, and the coordinate system of the database is unified according to requirements. The calibrated initial database is then designated as the template database. It should be noted that the above steps are not restricted in their execution order; only one possible implementation method is shown. Thus, the template database is established, providing a standardized data framework for matching basic geographic information data with the parent database. This improves the efficiency of matching basic geographic information data with the template, and by standardizing the data, perfect matching between data and maps can be achieved when loading maps, improving matching accuracy and shortening matching time. Furthermore, by setting up matching template project files, the matching scheme can be used cyclically, achieving patterned and automated matching, avoiding manual intervention, and improving data processing efficiency.

[0114] Figure 4 An apparatus 40 for standardizing electronic map cartographic data according to an embodiment of the present invention is shown. The apparatus 40 is used to perform... Figure 1 The method shown, the apparatus 40 includes:

[0115] Matching module 401 is used to match geographic information data in the master database with template data in the template database by matching template project files;

[0116] Import module 402 is used to import geographic information data into the template database when a match is found to be successful.

[0117] The determination module 403 is used to determine the template database after importing geographic information data as a standard database; wherein, the data in the standard database is standardized data;

[0118] The matching template project file stores the correspondence between geographic information data and template data. The template data includes at least one of the following: template layer, template field under the template layer, and attributes of the template field. Therefore, by using the matching template project file to standardize the data—from the database and data layers to the data fields—an automated process from inputting data to loading it for mapping can be achieved in one step, minimizing manual calibration and improving the efficiency of electronic map production.

[0119] In a preferred implementation, such as Figure 5 As shown, the device 40 also includes: a generation module 404, used to generate a matching template project file, including: determining the data relationship corresponding to the geographic information data in the initial data master database; generating a node tree structure according to the data relationship; storing the node tree structure in an XML file; parsing the node tree structure in the XML file and importing the parsed data into the template database; matching the parsed data with the template data; and generating a matching template project file after confirming a successful match.

[0120] In a preferred implementation, the data relationships include at least one of the following: the correspondence between geographic information data and layers, the correspondence between layers and fields, the correspondence between fields and field attributes, and the correspondence between fields and field content.

[0121] In a preferred implementation, the generation module 404 is specifically used to convert the layer into node A; convert the field name corresponding to the layer into child node B of node A; convert the field attribute corresponding to the field name into child node C of child node B; convert the field content corresponding to the field name into child node D of child node C; convert the attribute in the field into leaf node b of child node B; and generate a node tree structure according to the correspondence between nodes and child nodes.

[0122] The generation module 404 is specifically used to match the layer corresponding to the geographic information data with the template layer; after a successful match, it matches the field name with the template field name; after a successful match, it matches the field attribute with the template field attribute.

[0123] In a preferred implementation, the generation module 404 is specifically used to, after successfully matching the field attribute with the template field attribute, use the field content corresponding to the field name as the field content of the template field name; and use the content of the attribute of the field name as the content of the attribute of the template field; wherein the attribute includes at least one of the following: field type, field length, and field decimal places.

[0124] In a preferred implementation, such as Figure 6 As shown, the device 40 further includes: a first establishment module 405, used to establish a data master database before matching the geographic information data in the data master database with the template data in the template database through the matching template project file; wherein, establishing the data master database includes: acquiring basic geographic information data; cleaning the basic geographic information data; dividing the cleaned basic geographic information data into point data sets, line data sets and polygon data sets; merging the point data sets, line data sets and polygon data sets; and determining the merged data set as the data master database.

[0125] The device 40 further includes: a second creation module 406, used to create a template database, wherein creating the template database includes: creating an initial database; wherein the initial database is a database that imports layer name specification tables and field name specification tables; calibrating layers, fields under layers, and field attributes in the initial database according to user preset rules; and determining the calibrated initial database as the template database; wherein the initial database includes: layers, fields under layers, and field attributes.

[0126] The point dataset includes at least one of the following: key point set, high-density point set, low-density point set; the line dataset includes at least one of the following: road line set, water system line set, provincial and municipal boundary line set; the surface dataset includes at least one of the following: provincial interface, scene surface, functional surface, green ground, water system surface, lake and reservoir surface, building surface, residential ground.

[0127] Therefore, by using matching template project files to standardize the data, from the database, data layers to data fields, the process can be automated in one step, from inputting data to loading data to complete the mapping, minimizing manual calibration and improving the efficiency of electronic map making.

[0128] This invention also provides an electronic device, such as... Figure 7 As shown, it includes: a processor 701, a memory 702, and a program stored in the memory 702 and executable on the processor. When the program is executed by the processor 701, it implements as follows: Figure 1 , Figure 2 , Figure 3 The steps of the method for standardizing electronic map cartographic data are shown.

[0129] This invention also provides an electronic device 70, such as... Figure 7 As shown, it includes: a processor 701, a memory 702, and a program stored in the memory 702 and executable on the processor. When the program is executed by the processor 701, it implements as follows: Figure 1 , Figure 2 , Figure 3 The steps of the method for standardizing electronic map cartographic data are shown.

[0130] This invention also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the above-described... Figure 1 , Figure 2 , Figure 3The steps of the method for standardizing electronic map cartographic data shown are identical to those used to achieve the same technical effect, and will not be repeated here to avoid repetition. The computer-readable storage medium mentioned includes, for example, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0131] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0132] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of the present invention.

[0133] The embodiments of the present invention have been described above with reference to the accompanying drawings. However, the present invention is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of the present invention without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of the present invention.

Claims

1. A method for standardizing electronic map cartographic data, characterized in that, The method includes: By matching template project files, geographic information data in the master database is matched with template data in the template database; If a match is found to be successful, the geographic information data is imported into the template database; The template database after importing the geographic information data is designated as the standard database; wherein, the data in the standard database is standardized data. The matching template project file stores the correspondence between the geographic information data and the template data; the template data includes at least one of the following: template layer, template field under template layer, and attribute of template field; The matching template project file is generated through the following steps: determining the data relationships corresponding to the geographic information data in the initial data master database; generating a node tree structure based on the data relationships; storing the node tree structure in an XML file; parsing the node tree structure in the XML file and importing the parsed data into the template database; matching the parsed data with the template data; and generating the matching template project file after confirming a successful match. Before matching the geographic information data in the master database with the template data in the template database by matching the template project file, the method further includes: establishing the template database, wherein establishing the template database includes: establishing an initial database; wherein the initial database is a database that imports layer name specification tables and field name specification tables; wherein the initial database includes: layers, fields under the layers, and field attributes; calibrating the layers, fields under the layers, and field attributes in the initial database according to user-preset rules; and determining the calibrated initial database as the template database.

2. The method according to claim 1, characterized in that, The data relationships include at least one of the following: the correspondence between geographic information data and layers, the correspondence between layers and fields, the correspondence between fields and field attributes, and the correspondence between fields and field content; Based on the data relationships, generating the node tree structure includes: Convert the layer into node A; Convert the field names corresponding to the layer into child node B of node A; Convert the field attribute corresponding to the field name into a child node C of the child node B; Convert the field content corresponding to the field name into a child node D of child node C; The attributes in the field are transformed into leaf nodes b of the child node B; Generate a node tree structure according to the correspondence between nodes and child nodes.

3. The method according to claim 2, characterized in that, Matching the parsed data with the template data includes: Match the layers corresponding to the geographic information data with the template layers; After a successful match, the field name is matched against the template field name; After a successful match, the field's attributes are matched against the template field's attributes.

4. The method according to claim 3, characterized in that, After matching the field attributes with the template field attributes, the method further includes: After a successful match, the content of the field corresponding to the field name will be used as the content of the template field name; Use the content of the attribute of the field name as the content of the attribute of the template field; The attribute includes at least one of the following: field type, field length, and field decimal places.

5. The method according to claim 1, characterized in that, Before matching the geographic information data in the master database with the template data in the template database by matching the template project file, the method further includes: Establish a master database, wherein establishing the master database includes: Acquire basic geographic information data; Clean the aforementioned basic geographic information data; The cleaned basic geographic information data is divided into point data sets, line data sets, and polygon data sets. Merge the point data set, line data set, and polygon data set; The merged dataset is defined as the parent dataset.

6. The method according to claim 5, characterized in that, The point data set includes at least one of the following: a key point set, a high-density point set, and a low-density point set; The line data set includes at least one of the following: road line set, water system line set, and provincial / municipal / district boundary line set; The surface data set includes at least one of the following: provincial interface, scene surface, functional surface, green ground, water system surface, lake and reservoir surface, building surface, and residential ground.

7. A device for standardizing electronic map cartographic data, characterized in that, The apparatus is used to perform the method according to any one of claims 1-6, the apparatus comprising: The matching module is used to match geographic information data in the master database with template data in the template database by matching template project files; The import module is used to import the geographic information data into the template database when a match is found to be successful. The determination module is used to determine the template database after importing the geographic information data as a standard database; wherein the data in the standard database is standardized data; The matching template project file stores the correspondence between the geographic information data and the template data; the template data includes at least one of the following: template layer, template field under template layer, and attribute of template field.

8. An electronic device, characterized in that, include: A processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps of the method for standardizing electronic map cartographic data as claimed in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the method for standardizing electronic map cartographic data as described in any one of claims 1 to 6.

Citation Information

Patent Citations

  • Template based one-button type thematic map automatic forming method and system

    CN104008162A

  • Map style file editing method and device and electronic equipment

    CN114546373A