Quality inspection method, device, electronic device and storage medium for multi-source place name database production

Abstract

The present invention provides a quality inspection method, device, electronic device and storage medium for the production of a multi-source place name database, belonging to the technical field of quality inspection of place name databases. In the method, inspection rules are used for automatic inspection, data problems can be discovered in batches, and the quality inspection efficiency and accuracy of massive place name data are improved. In addition, phased real-time inspection and full inspection are used to speed up the discovery of data problems, alleviate the production and quality inspection pressure in the project achievement stage, avoid excessive backlog of data problems, and improve the data processing speed.

Description

Technical Field

[0001] The present invention relates to the technical field of quality inspection of place name databases, and in particular to a quality inspection method, device, electronic equipment and storage medium for the production of multi-source place name databases. Background Art

[0002] Place names are an important type of spatial information. Place name information is an important information resource involving national politics, economy, diplomacy and other fields, and is closely related to economic construction, social management, scientific research and people's lives. For the masses, accurate place name information is an indispensable basic resource for their production and life; for the government, political exchanges, cultural exchanges and economic transactions between countries and regions cannot be separated from the support of place name data.

[0003] In the era of big data, place names need more standardized and systematic digital management. The construction of global place name data resources, through the collection, translation, integration and update of global place name data, produces and processes multi-scale place name data of key countries and regions around the world, to make up for the shortage of multi-scale place name data resources.

[0004] Although the place name database is being gradually created at this stage, the quality inspection method for place name data is currently mostly manual, which is inefficient, misses many problems, and the data quality cannot be guaranteed. In addition, manual quality inspection is generally carried out after the completion of each stage or after the results stage. Problems cannot be discovered and solved in time during the production process, resulting in the accumulation of errors, the production of wrong data on wrong results, and a waste of production costs, which brings great pressure to subsequent quality inspection and modification issues.

[0005] In summary, how to improve the efficiency and accuracy of quality inspection, alleviate the pressure of production and quality inspection in the project results stage, and avoid excessive backlog of data problems has become a technical problem that needs to be solved urgently. Summary of the invention

[0006] In view of this, the purpose of the present invention is to provide a quality inspection method, device, electronic device and storage medium for the production of a multi-source place name database, so as to alleviate the technical problems of low efficiency, poor accuracy and accumulated data problems of existing manual quality inspection methods.

[0007] In a first aspect, an embodiment of the present invention provides a quality inspection method for producing a multi-source place name database, comprising:

[0008] Acquire the initial production data produced in the current stage of the multi-source place name database production, and use the real-time inspection rules of the current stage to perform real-time inspection on the initial production data, wherein the current stage is to traverse all the following stages in sequence: preprocessing stage, single-source normalization stage, multi-source fusion stage and repair processing stage;

[0009] If the real-time check is passed, the initial production data that has passed the real-time check is saved as the intermediate data of the current stage to the intermediate database of the current stage;

[0010] If the real-time check fails, the current stage of production is performed again, and the real-time check is performed again until there is no problem, and then the correct initial production data of the production is saved as the current stage intermediate data in the current stage intermediate database;

[0011] After the current stage is completed, the full amount check rule of the current stage is used to perform a full amount check on the intermediate data of the current stage;

[0012] If the full inspection is passed, the intermediate data of the current stage that has passed the full inspection will be saved as the current stage achievement data in the current stage achievement database;

[0013] If the full inspection fails, the current stage of production is carried out again, and the real-time inspection and full inspection are carried out again in sequence until there is no problem, and then the correct current stage intermediate data of production is saved as the current stage result data in the current stage result database;

[0014] The current stage result data is used as the initial data for the next stage of production, so as to carry out the next stage of production on the initial data and obtain the initial production data for the next stage, until the repair processing stage is traversed, and the repair processing result database finally obtained is used as the product library after quality inspection.

[0015] Further, the production of the current stage is performed again, and the real-time inspection is re-performed until there are no problems, and then the correct initial production data of the production is saved as the intermediate data of the current stage to the intermediate database of the current stage, including:

[0016] The generated real-time inspection error record is stored in the real-time inspection result, and the "whether to modify" field in the real-time inspection error record is assigned a value of unmodified, and the corresponding erroneous initial production data is manually confirmed and modified;

[0017] If the erroneous initial production data is confirmed to be correct, the "whether to modify" field in the corresponding real-time check error record is assigned a value of confirming not to modify, and the confirmed correct initial production data is saved as the current stage intermediate data in the current stage intermediate database;

[0018] If the erroneous initial production data is confirmed to be an error, the current stage of production will be carried out on the erroneous initial production data, and a real-time check will be performed again until there is no problem. The correct initial production data produced will then be saved as the current stage intermediate data to the current stage intermediate database, and the "Whether Modified" field in the corresponding real-time check error record will be assigned a value of Modified.

[0019] Further, the current stage of production is performed again, and real-time inspection and full inspection are performed again in sequence until there are no problems, and then the correct current stage intermediate data of production is saved as the current stage result data in the current stage result database, including:

[0020] Compare the error records of the full inspection with the error records of the real-time inspection in the corresponding real-time inspection results;

[0021] If the error record of the full check exists in the error record of the real-time check, and the value assigned to the "Whether to modify" field in the error record of the real-time check is not confirmation not to modify, the error record of the full check is stored in the full check result, and the value assigned to the "Whether to modify" field in the error record of the full check is confirmation to modify;

[0022] If the error record of the full check does not exist in the error record of the real-time check, the error record of the full check is stored in the full check result, and the "whether modified" field in the error record of the full check is assigned a value of not modified;

[0023] Manually confirm and modify the current stage intermediate data by assigning the value of "modify" to the field "modify" in the full inspection result as confirmed modification or unmodified;

[0024] If the confirmation is correct, the corresponding "whether to modify" field is assigned a value of confirming not to modify, and the confirmed correct current stage intermediate data is saved as the current stage achievement data to the current stage achievement database;

[0025] If an error is confirmed, the current stage production will be carried out on the current stage intermediate data with the confirmed error, and real-time inspection and full inspection will be re-performed until there is no problem, and then the correct current stage intermediate data produced will be saved as the current stage result data in the current stage result database.

[0026] Furthermore, the real-time inspection rule and the full inspection rule are formulated according to the processing of the corresponding stage, and the attributes of the real-time inspection rule and the full inspection rule include: inspection rule number, inspection principle, inspection output, inspection attribution and inspection stage.

[0027] Furthermore, if the current stage is a preprocessing stage, the initial production data is obtained by preprocessing the original data in the original database.

[0028] Furthermore, the error records of the real-time inspection and the error records of the full inspection include: serial number, inspection rule number, inspection output, error data coordinates, "whether to modify" field, inspection attribution, inspection stage and remarks, wherein the "whether to modify" field includes: not modified, confirmed not to modify, modified and confirmed to modify.

[0029] In a second aspect, an embodiment of the present invention further provides a quality inspection device for multi-source place name database production, comprising:

[0030] A real-time inspection unit is used to obtain the initial production data produced in the current stage of the multi-source place name database production, and use the real-time inspection rules of the current stage to perform real-time inspection on the initial production data, wherein the current stage is to traverse all the following stages in sequence: preprocessing stage, single-source normalization stage, multi-source fusion stage and repair processing stage;

[0031] A first setting unit is used to save the initial production data that has passed the real-time inspection as the current stage intermediate data to the current stage intermediate database if the real-time inspection passes;

[0032] The re-production and real-time inspection unit is used to, if the real-time inspection fails, re-produce the current stage of production and re-inspect the real-time inspection until there is no problem, and then save the correct initial production data of the production as the current stage intermediate data to the current stage intermediate database;

[0033] A full inspection unit, configured to perform a full inspection on the intermediate data of the current stage using the full inspection rule of the current stage after the current stage is completed;

[0034] The second setting unit is used to save the intermediate data of the current stage that has passed the full inspection as the result data of the current stage to the result database of the current stage if the full inspection has passed;

[0035] The re-production and real-time inspection full quantity inspection unit is used to, if the full quantity inspection fails, re-produce the current stage of production, and re-perform the real-time inspection and the full quantity inspection in sequence until there is no problem, and then save the correct current stage intermediate data of the production as the current stage result data into the current stage result database;

[0036] The production unit is used to use the current stage result data as the initial data for the next stage of production, so as to carry out the next stage of production on the initial data and obtain the initial production data for the next stage, until traversing to the repair processing stage, and use the final repair processing result database as the product library after quality inspection.

[0037] Furthermore, the re-production and real-time inspection unit is also used for:

[0038] The generated real-time inspection error record is stored in the real-time inspection result, and the "whether to modify" field in the real-time inspection error record is assigned a value of unmodified, and the corresponding erroneous initial production data is manually confirmed and modified;

[0039] If the erroneous initial production data is confirmed to be correct, the "whether to modify" field in the corresponding real-time check error record is assigned a value of confirming not to modify, and the confirmed correct initial production data is saved as the current stage intermediate data in the current stage intermediate database;

[0040] If the erroneous initial production data is confirmed to be an error, the current stage of production will be carried out on the erroneous initial production data, and a real-time check will be performed again until there is no problem. The correct initial production data produced will then be saved as the current stage intermediate data to the current stage intermediate database, and the "Whether Modified" field in the corresponding real-time check error record will be assigned a value of Modified.

[0041] In a third aspect, an embodiment of the present invention further provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of any one of the methods described in the first aspect when executing the computer program.

[0042] In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium, wherein the computer-readable storage medium stores machine-executable instructions. When the machine-executable instructions are called and executed by a processor, the machine-executable instructions prompt the processor to execute any method described in the first aspect above.

[0043] In an embodiment of the present invention, a quality inspection method for the production of a multi-source place name database is provided, comprising: obtaining initial production data produced in the current stage of the production of the multi-source place name database, and using the real-time inspection rules of the current stage to perform real-time inspection on the initial production data, wherein the current stage is to traverse all the following stages in sequence: a preprocessing stage, a single-source normalization stage, a multi-source fusion stage, and a repair processing stage; if the real-time inspection passes, the initial production data that passes the real-time inspection is saved as the intermediate data of the current stage to the intermediate database of the current stage; if the real-time inspection fails, the production of the current stage is performed again, and the real-time inspection is performed again until there is no problem, and then the correct initial production data produced is saved as the intermediate data of the current stage to the intermediate database of the current stage; in the current stage After completion, the full inspection rules of the current stage are used to perform a full inspection on the intermediate data of the current stage; if the full inspection passes, the intermediate data of the current stage that passes the full inspection is saved as the current stage result data in the current stage result database; if the full inspection fails, the current stage production is carried out again, and the real-time inspection and full inspection are carried out again in sequence until there are no problems, and then the correct current stage intermediate data of the production is saved as the current stage result data in the current stage result database; the current stage result data is used as the initial data for the next stage production, so as to carry out the next stage production on the initial data and obtain the initial production data produced in the next stage, until it traverses to the repair processing stage, and the final repair processing result database is used as the product library after quality inspection. From the above description, it can be seen that in the quality inspection method for the production of the multi-source place name database of the present invention, inspection rules are used for automatic inspection, which can discover data problems in batches, improve the quality inspection efficiency and quality inspection accuracy of massive place name data, and adopt phased real-time inspection and full inspection to speed up the discovery of data problems, alleviate the production and quality inspection pressure in the project results stage, avoid excessive backlog of data problems, improve data processing speed, and alleviate the technical problems of low efficiency, poor accuracy, and accumulated data problems of existing manual quality inspection methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0045] Figure 1 A flow chart of a quality inspection method for a multi-source place name database provided by an embodiment of the present invention;

[0046] Figure 2A quality inspection method and flow chart for the production of a multi-source place name database provided by an embodiment of the present invention;

[0047] Figure 3 A schematic diagram of a fusion processing result database provided by an embodiment of the present invention;

[0048] Figure 4 A schematic diagram of the first repair performed by the repair software provided by the embodiment of the present invention;

[0049] Figure 5 A schematic diagram after the first repair process provided by an embodiment of the present invention;

[0050] Figure 6 A schematic diagram of the repair software provided by the embodiment of the present invention performing a second repair;

[0051] Figure 7 A schematic diagram after the second repair process provided by an embodiment of the present invention;

[0052] Figure 8 A schematic diagram of a repair processing intermediate database provided by an embodiment of the present invention;

[0053] Fig. 9 A schematic diagram of correcting erroneous data provided by an embodiment of the present invention;

[0054] Fig.10 A schematic diagram of a repair processing result database provided by an embodiment of the present invention;

[0055] Fig.11 A schematic diagram of a quality inspection device for a multi-source place name database provided by an embodiment of the present invention;

[0056] Fig.12 A schematic diagram of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0057] The technical solution of the present invention will be clearly and completely described below in conjunction with the embodiments. Obviously, the described embodiments are part of the embodiments of the present invention, rather than all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0058] Traditional manual quality inspection methods are inefficient, inaccurate, and have serious data problems.

[0059] Based on this, in the quality inspection method for the production of the multi-source place name database of the present invention, inspection rules are used for automatic inspection, which can discover data problems in batches, improve the quality inspection efficiency and accuracy of massive place name data, and adopt phased real-time inspection and full inspection to speed up the discovery of data problems, alleviate the production and quality inspection pressure in the project results stage, avoid excessive backlog of data problems, and improve data processing speed.

[0060] To facilitate understanding of this embodiment, a quality inspection method for producing a multi-source place name database disclosed in an embodiment of the present invention is first introduced in detail.

[0061] Embodiment 1:

[0062] According to an embodiment of the present invention, an embodiment of a quality inspection method for the production of a multi-source place name database is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0063] Figure 1 is a flow chart of a quality inspection method for multi-source place name database production according to an embodiment of the present invention. Figure 1 As shown, the method comprises the following steps:

[0064] Step S102, obtaining the initial production data produced in the current stage of the multi-source place name database production, and using the real-time inspection rules of the current stage to perform real-time inspection on the initial production data, wherein the current stage is to traverse all the following stages in sequence: preprocessing stage, single-source normalization stage, multi-source fusion stage and repair processing stage;

[0065] In an embodiment of the present invention, the production process of a multi-source place name database generally includes: a preprocessing stage, a single-source normalization stage, a multi-source fusion stage, and a repair processing stage. The method of the present invention is a full-process quality inspection method for the production of a multi-source place name database. Corresponding quality inspections are set at each stage, and the quality inspection methods include: real-time inspections and full inspections. Real-time inspections refer to inspections performed during data processing at each stage, mainly by checking trigger conditions (clicking the Finish / OK button after modification or triggering the button during the current stage of production) to check the correctness of intermediate data in real time. Full inspections refer to inspections performed in the intermediate database of each stage after each stage is completed, mainly through full inspection rules to check the integrity, logic, and correctness of the data.

[0066] Specifically, if the current stage is the preprocessing stage, the initial production data is obtained by preprocessing the original data in the original database.

[0067] Step S104, if the real-time check is passed, the initial production data that has passed the real-time check is saved as the current stage intermediate data in the current stage intermediate database;

[0068] Step S106, if the real-time check fails, the current stage of production is performed again, and the real-time check is performed again until there is no problem, and then the correct initial production data of the production is saved as the current stage intermediate data in the current stage intermediate database;

[0069] Specifically, the initial production data of the new production is re-checked in real time.

[0070] Step S108, after the current stage is completed, the full amount check rule of the current stage is used to perform a full amount check on the intermediate data of the current stage;

[0071] Step S110, if the full inspection is passed, the intermediate data of the current stage that has passed the full inspection is saved as the current stage achievement data in the current stage achievement database;

[0072] Step S112: If the full inspection fails, the current stage of production is performed again, and the real-time inspection and full inspection are performed again in sequence until there is no problem, and then the correct current stage intermediate data of the production is saved as the current stage result data in the current stage result database;

[0073] Specifically, the initial production data of new production is rechecked in real time, and after the current stage is completed, a full check is performed.

[0074] Step S114, using the current stage result data as the initial data for the next stage of production, so as to carry out the next stage of production on the initial data, and obtain the initial production data produced in the next stage, until traversing to the repair processing stage, and using the final repair processing result database as the product library after quality inspection.

[0075] Specifically, the next stage of production is performed on the initial data to obtain the initial production data produced in the next stage, and then the next stage is taken as the current stage, and the step of obtaining the initial production data produced in the current stage of production of the multi-source place name database is returned to execute until the repair processing stage is traversed, and the final repair processing result database is used as the product library after quality inspection.

[0076] In an embodiment of the present invention, a quality inspection method for the production of a multi-source place name database is provided, comprising: obtaining initial production data produced in the current stage of the production of the multi-source place name database, and using the real-time inspection rules of the current stage to perform real-time inspection on the initial production data, wherein the current stage is to traverse all the following stages in sequence: a preprocessing stage, a single-source normalization stage, a multi-source fusion stage, and a repair processing stage; if the real-time inspection passes, the initial production data that passes the real-time inspection is saved as the intermediate data of the current stage to the intermediate database of the current stage; if the real-time inspection fails, the production of the current stage is performed again, and the real-time inspection is performed again until there is no problem, and then the correct initial production data produced is saved as the intermediate data of the current stage to the intermediate database of the current stage; in the current stage After completion, the full inspection rules of the current stage are used to perform a full inspection on the intermediate data of the current stage; if the full inspection passes, the intermediate data of the current stage that passes the full inspection is saved as the current stage result data in the current stage result database; if the full inspection fails, the current stage production is carried out again, and the real-time inspection and full inspection are carried out again in sequence until there are no problems, and then the correct current stage intermediate data of the production is saved as the current stage result data in the current stage result database; the current stage result data is used as the initial data for the next stage production, so as to carry out the next stage production on the initial data and obtain the initial production data produced in the next stage, until it traverses to the repair processing stage, and the final repair processing result database is used as the product library after quality inspection. From the above description, it can be seen that in the quality inspection method for the production of the multi-source place name database of the present invention, inspection rules are used for automatic inspection, which can discover data problems in batches, improve the quality inspection efficiency and quality inspection accuracy of massive place name data, and adopt phased real-time inspection and full inspection to speed up the discovery of data problems, alleviate the production and quality inspection pressure in the project results stage, avoid excessive backlog of data problems, improve data processing speed, and alleviate the technical problems of low efficiency, poor accuracy, and accumulated data problems of existing manual quality inspection methods.

[0077] The above content briefly introduces the quality inspection method for the production of the multi-source place name database of the present invention. The specific contents involved are described in detail below.

[0078] In an optional embodiment of the present invention, the production of the current stage is performed again, and the real-time inspection is re-performed until there is no problem, and then the correct initial production data of the production is saved as the intermediate data of the current stage to the intermediate database of the current stage, which specifically includes the following steps:

[0079] (1) The generated real-time inspection error record is stored in the real-time inspection result, and the "whether to modify" field in the real-time inspection error record is assigned a value of "not modified", and the corresponding erroneous initial production data is manually confirmed and modified;

[0080] (2) If the erroneous initial production data is confirmed to be correct, the "Whether to modify" field in the corresponding real-time check error record is assigned a value of "confirmed not to modify", and the confirmed correct initial production data is saved as the current stage intermediate data in the current stage intermediate database;

[0081] (3) If the erroneous initial production data is confirmed to be an error, the current stage of production will be carried out on the erroneous initial production data, and a real-time check will be performed again until there is no problem. Then, the correct initial production data will be saved as the current stage intermediate data in the current stage intermediate database, and the "Whether Modified" field in the corresponding real-time check error record will be assigned the value of Modified.

[0082] In an optional embodiment of the present invention, the current stage of production is performed again, and the real-time inspection and the full inspection are performed again in sequence until there are no problems, and then the correct current stage intermediate data of the production is saved as the current stage result data in the current stage result database, which specifically includes the following steps:

[0083] (1) Compare the error records of the full inspection with the error records of the real-time inspection in the corresponding real-time inspection results;

[0084] (2) If the error record of the full check exists in the error record of the real-time check, and the value assigned to the "Whether to modify" field in the error record of the real-time check is not confirmation not to modify, then the error record of the full check is stored in the full check result, and the value assigned to the "Whether to modify" field in the error record of the full check is confirmation to modify;

[0085] (3) If the error record of the full check does not exist in the error record of the real-time check, the error record of the full check is stored in the full check result, and the "whether modified" field in the error record of the full check is assigned a value of not modified;

[0086] (4) manually confirm and modify the current intermediate data by assigning the value of "modify" to the field "modify" in the full inspection result, or not modifying it;

[0087] (5) If the confirmation is correct, the corresponding "whether to modify" field is assigned a value of "confirm not to modify", and the confirmed correct current stage intermediate data is saved as the current stage result data in the current stage result database;

[0088] (6) If an error is confirmed, the current stage production is carried out on the current stage intermediate data with the confirmed error, and real-time inspection and full inspection are re-performed until there is no problem, and then the correct current stage intermediate data produced is saved as the current stage result data in the current stage result database.

[0089] In an optional embodiment of the present invention, the real-time inspection rules and the full inspection rules are formulated according to the processing of the corresponding stages, and the attributes of the real-time inspection rules and the full inspection rules include: inspection rule number, inspection principle, inspection output, inspection attribution and inspection stage.

[0090] In an optional embodiment of the present invention, the error records of real-time inspection and the error records of full inspection include: serial number, inspection rule number, inspection output, error data coordinates, "whether to modify" field, inspection attribution, inspection stage and remarks, wherein the "whether to modify" field includes: not modified, confirmed not to modify, modified and confirmed to modify.

[0091] The following is a detailed introduction to the entire quality inspection process. Figure 2 :

[0092] The first step is to obtain the original database. The original database stores unprocessed multi-source place name data. Multi-source place name data includes: open source data and other data. Generally, open source data is obtained through direct download, open interface, Internet crawler, text parsing, etc. For paper place name data, it is obtained through vectorization. Other data is unpublished data provided by customers.

[0093] The second step is to preprocess the original data and obtain the preprocessed intermediate result data. Since the sources of each data are different, the data format, spatial reference, coding system, and scope information are all different. Therefore, format conversion, spatial reference conversion, coding mapping, and scope unification are performed in the preprocessing stage to obtain multi-source data with consistent format, spatial reference, coding, and scope, forming preprocessed intermediate result data, providing basic guarantee for multi-source fusion. Among them, format conversion is to convert the format into a unified format; spatial reference conversion is to convert the spatial reference to CGCS2000; coding mapping is to unify the coding to the existing result coding; scope unification is to determine the scope of a certain area through various data analysis, and then cut each data source according to the unified regional scope. The preprocessed intermediate result data includes: Chinese name of the place name, foreign name, coding, type, and preprocessing unique identifier. (This step is the production link of the multi-source place name database, and it is only briefly described here).

[0094] The third step is real-time inspection of preprocessing. During the preprocessing production process, the real-time inspection rules of the preprocessing stage are triggered to conduct real-time inspection of the preprocessing intermediate data (i.e., the initial production data produced in the preprocessing stage), and the results of the real-time inspection of preprocessing are stored in the preprocessing intermediate database. During preprocessing, according to the data integrity, logic, and correctness inspection rules in the real-time inspection of the preprocessing stage (see Appendix 1 for the specific rule structure), check whether the preprocessing intermediate data is correct. If correct, save it to the preprocessing intermediate database (i.e., the intermediate database of the preprocessing stage - the preprocessing intermediate database). If it is incorrect, the generated real-time inspection error record will be stored in the real-time inspection result, and the "Whether to modify" field in the real-time inspection error record (see Appendix 2 for specific error record attributes) will be assigned a value of "Not modified", and then the corresponding erroneous initial production data will be manually confirmed and modified. If the erroneous initial production data is confirmed to be correct and does not need to be modified, the "Whether to modify" field in the corresponding real-time inspection error record will be assigned a value of confirmed not to be modified, and the confirmed correct initial production data will be saved as preprocessing intermediate data in the preprocessing intermediate database; if the erroneous initial production data is confirmed to be erroneous and needs to be modified, the erroneous initial production data will be preprocessed (i.e., production at the current stage), and real-time inspection will be performed again until there is no problem. Finally, the correct initial production data of the production will be saved as preprocessing intermediate data in the preprocessing intermediate database, and the "Whether to modify" field in the corresponding real-time inspection error record will be assigned a value of modified.

[0095] Note: Pre-processing real-time checks include: data integrity check: whether there are any omissions in data attribute content; correctness check: whether the data format, data location, and data attribute content are correct; logical check: logic within the table during the pre-processing stage.

[0096] The fourth step is to pre-process the full amount of inspection. After the pre-processing is completed (there is no erroneous data in the pre-processing real-time inspection), check whether the data in the pre-processing intermediate database is correct according to the data integrity, logic, and correctness inspection rules in the full inspection of the pre-processing stage (see Appendix 1 for the specific rule structure). If correct, store the data in the pre-processing intermediate database in the pre-processing results database (i.e., the results database of the current stage); if incorrect, compare the error records of the full inspection with the error records of the real-time inspection in the corresponding real-time inspection results (see Appendix 2 for the specific error record attributes). If the error records of the full inspection exist in the real-time inspection error records, and the "Whether to modify" field in the real-time inspection error records is not assigned a value of "confirmed not to modify", but has not been modified or has been modified, then the error records of the full inspection (see Appendix 2 for the specific error record attributes) are stored in the full inspection results, and the "Whether to modify" field in the error records of the full inspection is assigned a value of "confirmed to modify"; if the error records of the full inspection do not exist in the error records of the real-time inspection, then the error records of the full inspection are stored in the full inspection results. And assign the value of "Not modified" to the "Is it modified" field in the error record of the full inspection; then manually confirm and modify the data with the values ​​of "Confirm modification" and "Not modified" in the "Is it modified" field in the full inspection result. If it is manually confirmed to be correct and does not need to be modified, the corresponding "Is it modified" field will be assigned the value of "Confirm not modified", and the confirmed correct data will be saved in the preprocessing results database; if it is manually confirmed to be an error and needs to be modified, the confirmed error data will be preprocessed (that is, the current stage of production). After the preprocessing and modification, the new data will be checked in real time first. After the real-time check passes, the full inspection will be re-performed until there are no problems. Finally, the correct data produced will be saved in the preprocessing results database, and the value of "Is it modified" in the corresponding error record of the full inspection will be assigned to "Modified".

[0097] Note: The full inspection in the preprocessing stage is mainly carried out on the preprocessing intermediate database. The inspection content is mainly to check for omissions in the real-time inspection and to check the integrity, correctness and logic of the database as a whole. Integrity check: whether there are omissions in the file data; Correctness check: whether the place name range is correct, whether the coding mapping is unified, whether the character merging is correct, etc.; Logical check: logical consistency check between libraries (original database-preprocessing intermediate database-preprocessing result database), logical consistency check between tables (original data table, process table, entity table).

[0098] The fifth step is to normalize the preprocessing result data of each source in the preprocessing result library to obtain the normalized intermediate data. Due to the different place name expression rules of the preprocessing result data of each source, there will be two or more place name expressions for the same place name entity. For example: 1. Two pieces of data from the same source have overlapping areas at the connected position, resulting in two identical place names at the same location; 2. In the osm data, the same road is truncated many times, and each section of the road corresponds to the same road name; 3. During the open source data collection process, the same entity is collected by multiple people, and there are multiple duplicate place names or similar place names at the same location. Therefore, in order to achieve the purpose of normalization without affecting the data results, it is necessary to normalize the same entities with the same or similar names, close distances or similar trends, and the same or similar types of the preprocessing result data from the same source after the preprocessing is completed. (This step is the production link of the multi-source place name database, and is only briefly described here).

[0099] Step 6: Real-time check of single-source normalization processing. During the process of normalization processing production, according to the data integrity, logic, and correctness check rules in the real-time check of the single-source normalization stage (see Appendix 1 for the specific rule structure), check whether the normalization processing intermediate data (i.e., the initial production data produced in the single-source normalization stage) is correct. If correct, save it to the single-source normalization processing intermediate database (i.e., the intermediate database of the single-source normalization processing stage - the single-source normalization processing intermediate database). If it is incorrect, the generated real-time inspection error record (specific error record attributes are shown in Appendix 2) will be stored in the real-time inspection result, and the "Whether to modify" field in the real-time inspection error record will be assigned a value of "Not modified", and then the corresponding erroneous initial production data will be manually confirmed and modified. If the erroneous initial production data is confirmed to be correct and does not need to be modified, the "Whether to modify" field in the corresponding real-time inspection error record will be assigned a value of "Confirmed not to modify", and the confirmed correct initial production data will be saved as single-source normalization processing intermediate data in the single-source normalization processing intermediate database; if the erroneous initial production data is confirmed to be erroneous and needs to be modified, the erroneous initial production data will be subjected to single-source normalization processing (i.e. production at the current stage), and real-time inspection will be performed again until there is no problem. Finally, the correct initial production data of the production will be saved as single-source normalization processing intermediate data in the single-source normalization processing intermediate database, and the "Whether to modify" field in the corresponding real-time inspection error record will be assigned a value of "Modified".

[0100] Note: Real-time checks of normalization processing include: data integrity: whether there are any omissions in data attribute content; correctness check: whether the data format, data location, data attribute content are correct, and whether the normalization processing is correct; logic check: data logic before and after single-source normalization processing.

[0101] Step 7: Full inspection of single-source normalization processing. After the single-source normalization processing is completed, check whether the data in the intermediate database of the single-source normalization processing is correct according to the data integrity, logic, and correctness inspection rules in the full inspection of the single-source normalization stage (see Appendix 1 for the specific rule structure). If correct, store the data in the intermediate database of the single-source normalization processing in the single-source normalization results database (i.e., the results database of the current stage); if incorrect, compare the error records of the full inspection with the error records of the real-time inspection in the corresponding real-time inspection results. If the error records of the full inspection exist in the real-time inspection error records, and the "Whether to modify" field in the real-time inspection error records is not assigned a value of "confirmed not to modify", but has not been modified or has been modified, then the error records of the full inspection (see Appendix 2 for specific error record attributes) are stored in the full inspection results, and the "Whether to modify" field in the error records of the full inspection is assigned a value of "confirmed modification"; if the error records of the full inspection do not exist in the error records of the real-time inspection, then the error records of the full inspection are stored in the full inspection results, and the error records of the full inspection are The "Is it modified" field in the record is assigned the value of "Not modified"; then the data with the values ​​of "Confirm modification" and "Not modified" in the full inspection result is manually confirmed and modified. If it is manually confirmed to be correct and does not need to be modified, the corresponding "Is it modified" field is assigned the value of "Confirm not modified", and the confirmed correct data is saved in the single-source normalization processing result database; if it is manually confirmed to be wrong and needs to be modified, the confirmed erroneous data is processed by single source normalization (that is, the current stage of production). After the single-source normalization processing and modification, the new data is first checked in real time. After the real-time check passes, the full inspection is re-performed until there is no problem. Finally, the correct data of the production is saved in the single-source normalization processing result database, and the "Is it modified" field in the corresponding error record of the full inspection is assigned the value of "Modified".

[0102] Note: The full inspection of the single-source normalization stage is mainly carried out on the intermediate database of the single-source normalization processing. The inspection content is mainly to check for omissions in real-time inspections, and to check the integrity, correctness, and logic of the intermediate database of the single-source normalization processing as a whole. Integrity check: whether there are omissions in file data; correctness check: whether there are omissions or errors in the single-source normalization processing; logic check: logical consistency check between libraries (pre-processing results database-single-source normalization processing intermediate database-single-source normalization processing results database), and logical consistency check between tables (process table, entity table).

[0103] The eighth step is to fuse the single-source normalization processing result data of each source in the single-source normalization processing result database to obtain the fused processing intermediate data. The fusion processing here is to associate the same place name entity in each data source through a unique identifier to form a set of comprehensive, detailed and accurate place name data. (This step is the production link of the multi-source place name database, and is only briefly described here).

[0104] Step 9: Real-time check of fusion processing. When fusion processing is being carried out, check whether the intermediate data of fusion processing (i.e., the initial production data produced in the fusion processing stage) is correct according to the data integrity, logic, and correctness check rules in the real-time check of the fusion processing stage (see Appendix 1 for the specific rule structure). If correct, save it to the intermediate database of fusion processing (i.e., the intermediate database of the fusion processing stage - the intermediate database of fusion processing). If it is incorrect, the generated real-time inspection error record will be stored in the real-time inspection result, and the "Whether to modify" field in the real-time inspection error record (see Appendix 2 for specific error record attributes) will be assigned a value of "Not modified", and then the corresponding erroneous initial production data will be manually confirmed and modified. If the erroneous initial production data is confirmed to be correct and does not need to be modified, the "Whether to modify" field in the corresponding real-time inspection error record will be assigned a value of "Confirmed not to modify", and the confirmed correct initial production data will be saved as fusion processing intermediate data in the fusion processing intermediate database; if the erroneous initial production data is confirmed to be erroneous and needs to be modified, the erroneous initial production data will be fused (i.e., production at the current stage), and real-time inspection will be performed again until there is no problem. Finally, the correct initial production data of the production will be saved as fusion processing intermediate data in the fusion processing intermediate database, and the "Whether to modify" field in the corresponding real-time inspection error record will be assigned a value of "Modified".

[0105] Note: The real-time check of fusion processing includes: data integrity: whether there are any omissions in data attribute content; correctness check: whether the data format, data location, data attribute content are correct, and whether the fusion processing is correct; logic check: the logic of data before and after multi-source fusion processing.

[0106] Step 10: Full inspection of fusion processing. After the fusion processing is completed, check whether the data in the fusion processing intermediate database is correct according to the data integrity, logic, and correctness inspection rules in the full inspection of the multi-source fusion stage (see Appendix 1 for the specific rule structure). If correct, store the data in the fusion processing intermediate database in the multi-source fusion processing result database (that is, the fusion processing result database). If incorrect, compare the error record of the full inspection with the error record of the real-time inspection in the corresponding real-time inspection result (see Appendix 2 for the specific error record attributes). If the error record of the full inspection exists in the real-time inspection error record, and the "Whether to modify" field in the real-time inspection error record is not assigned "confirmed not to modify", but "not modified" or "modified", then the error record of the full inspection (see Appendix 2 for the specific error record attributes) is stored in the full inspection result, and the "Whether to modify" field in the error record of the full inspection is assigned "confirmed to modify"; if the error record of the full inspection does not exist in the error record of the real-time inspection, then the error record of the full inspection is stored in the full inspection result, and the "Whether to modify" field in the error record of the full inspection is assigned The value is "Not modified"; then the "Is it modified" field in the full inspection result is assigned the value of "Confirm modification" and "Not modified" for manual confirmation and modification. If it is manually confirmed to be correct and does not need to be modified, the corresponding "Is it modified" field is assigned the value of "Confirm not modified", and the confirmed correct data is saved in the fusion processing result database; if it is manually confirmed to be an error and needs to be modified, the confirmed error data is fusion processed (that is, the current stage of production). After the fusion processing and modification, the new data is first checked in real time. After the real-time check passes, the full inspection is re-performed until there is no problem. Finally, the correct data produced is saved in the fusion processing result database, and the "Is it modified" field in the corresponding error record of the full inspection is assigned the value of "Modified".

[0107] Note: The full inspection in the multi-source fusion stage is mainly carried out on the intermediate database of fusion processing. The inspection content is mainly to check for omissions in real-time inspections and to check the integrity, correctness and logic of the intermediate database of fusion processing as a whole. Integrity check: whether there are omissions in file data; correctness check: whether there are omissions or errors in fusion processing; logic check: logical consistency check between libraries (single-source normalization processing result database-fusion processing intermediate database-fusion processing result database), and logical consistency check between tables (process table, entity table, fusion table).

[0108] The eleventh step is to repair the fusion processing result data in the fusion processing result database to obtain the repaired intermediate data. When multi-source (multiple sets) place name data are fused into a set of place name result data, it is necessary to select the optimal name, optimal location, optimal code, etc. from the multi-source fusion processing result data according to the characteristics of each source fusion processing result data. This will lead to mismatch or incorrect selected names, locations, and codes. In addition, since the multi-source fusion processing result data obtains place names from different sources, the place names of various landform groups may be the same in foreign languages ​​but different in Chinese. At this time, it is necessary to repair the fusion processing result data in the fusion processing result database to finally form a place name result with consistent name, location, and code. (This step is the production link of the multi-source place name database, and is only briefly described here).

[0109] Step 12: Real-time inspection of repair processing. When performing repair processing, check whether the intermediate data of repair processing (i.e., the initial production data produced in the repair processing stage) is correct according to the data integrity, logic, and correctness inspection rules in the real-time inspection of the repair processing stage (see Appendix 1 for the specific rule structure). If correct, save it to the intermediate database of repair processing (i.e., the intermediate database of the repair processing stage - the intermediate database of repair processing). If it is incorrect, the generated real-time inspection error record is stored in the real-time inspection result, and the "Whether to modify" field in the real-time inspection error record (see Appendix 2 for specific error record attributes) is assigned a value of "Not modified", and then the corresponding erroneous initial production data is manually confirmed and modified. If the erroneous initial production data is confirmed to be correct and does not need to be modified, the "Whether to modify" field in the corresponding real-time inspection error record is assigned a value of "Confirmed not to modify", and the confirmed correct initial production data is saved as repair processing intermediate data in the repair processing intermediate database; if the erroneous initial production data is confirmed to be erroneous and needs to be modified, the erroneous initial production data is repaired (i.e., production at the current stage), and real-time inspection is performed again until there is no problem. Finally, the correct initial production data of the production is saved as repair processing intermediate data in the repair processing intermediate database, and the "Whether to modify" field in the corresponding real-time inspection error record is assigned a value of "Modified".

[0110] Note: The real-time check of the repair process includes: data integrity: whether there are any omissions in the data attribute content; correctness check: whether the data repair is correct and whether the repair is omitted; logic check: data logic before and after the repair process.

[0111] Step 13: Full inspection of the repair process. After the repair process is completed, check whether the data in the repair process intermediate database is correct according to the data integrity, logic, and correctness inspection rules in the full inspection of the repair process stage (see Appendix 1 for the specific rule structure). If correct, store the data in the repair process intermediate database in the repair process result database (i.e., the result database of the current stage). If incorrect, compare the error record of the full inspection with the error record of the real-time inspection in the corresponding real-time inspection result (see Appendix 2 for the specific error record attributes). If the error record of the full inspection exists in the real-time inspection error record, and the "Whether to modify" field in the real-time inspection error record is not assigned "confirmed not to modify", but "not modified" or "modified", then the error record of the full inspection (see Appendix 2 for the specific error record attributes) is stored in the full inspection result, and the "Whether to modify" field in the error record of the full inspection is assigned "confirmed to modify"; if the error record of the full inspection does not exist in the error record of the real-time inspection, then the error record of the full inspection is stored in the full inspection result, and the "Whether to modify" field in the error record of the full inspection is assigned is "Not modified"; then the "Is it modified" field in the full inspection result is assigned the value of "Confirm modification" and the corresponding data of "Not modified" is manually confirmed and modified. If it is manually confirmed to be correct and does not need to be modified, the corresponding "Is it modified" field is assigned the value of "Confirm not modified", and the confirmed correct data is saved in the repair processing results database; if it is manually confirmed to be an error and needs to be modified, the confirmed error data is repaired (that is, the current stage of production). After the repair processing and modification, the new data is first checked in real time. After the real-time check passes, the full inspection is re-performed until there is no problem. Finally, the correct data produced is saved in the repair processing results database, and the "Is it modified" field in the corresponding error record of the full inspection is assigned the value of "Modified".

[0112] Note: The full inspection in the repair processing stage is mainly carried out on the intermediate database of the repair processing. The inspection content is mainly to check for omissions in the real-time inspection, and to check the integrity, correctness and logic of the intermediate database of the repair processing as a whole. Integrity check: whether there are omissions in file data; correctness check: whether there are omissions or errors in the repair processing; logic check: logical consistency check between libraries (original database-single-source normalization processing result database-multi-source fusion processing result database-result library), logical consistency check between tables (process table, entity table, fusion table).

[0113] Step 14: Generate a product library. Generate a product library based on product requirements.

[0114] Generally speaking, there are many sources of multi-source place name data, complex data processing processes, and huge amounts of data. If each process, each set of data sources, and each place name are manually checked, it will consume a lot of manpower, material resources, and time. The full-process quality inspection method for the production of multi-source place name databases mentioned in this plan can quickly and effectively discover problems such as incomplete, inconsistent, and incorrect place name data.

[0115] The four stages of multi-source place name database production all use a combination of real-time and full-volume inspection. Due to the different stages, the corresponding production content is different, and the inspection content is relatively different, but the inspection process is basically the same. In order to make it easier to understand the inspection method that combines real-time and full-volume inspection, this plan takes the inspection of the repair processing stage of a certain area as an example to explain the specific inspection rules and methods.

[0116] The multi-source data used in a certain area of ​​this plan include: GNS (GEOnet Names Server), OSM data (Open Street Map), and world atlas vector data.

[0117] By preprocessing, single-source normalization, and fusion processing of multi-source data (GNS, OSM data, world atlas vector data), a multi-source fusion processing results database "1" is obtained.

[0118] This corresponds to step 12 of the above process: real-time inspection of repair processing.

[0119] 1. Repair. Figure 3 As shown, in the multi-source fusion processing result database "1", the place names "Chuadanga" and "Jiuwadonga Station" belong to the same land feature group. The foreign names corresponding to "Chuadanga" and "Jiuwadonga" are both "Chuadanga", but the Chinese names are different. According to the restoration principle (within the same land feature group, place names with the same foreign name should also have the same corresponding Chinese names, and the name restoration priority is: tjcn>gnscn>osmcn), "Jiuwadonga Station" is repaired.

[0120] Repair priority is determined based on the repair principle or relevance principle.

[0121] Reasons for repair: Since place names have the characteristics of regional consistency, they are derived from surrounding features and form a feature group together with the names of the features they are attached to. For example, the surrounding place names derived from residential areas (Xi'an City, Xi'an Railway Station, Xi'an Bus Station, Xi'an Jiaotong University, Xi'an Traditional Chinese Medicine Hospital); but due to the differences in production and translation methods, multi-source place name data have problems such as different Chinese characters with the same pronunciation, the same foreign proper nouns but different Chinese characters (actually the same characters), and such problems cannot be handled during fusion selection, and place name repair is required based on the geographical location of the local feature group. For example, taking the "San Francisco" feature group in the U.S. administrative district as an example, according to the geographical characteristics of San Francisco, there are place names containing "San Francisco" in San Francisco, such as "San Francisco Palace of Fine Arts", "San Francisco Bay", "San Francisco Street", "San Francisco Public Library", etc. Due to different data sources and different translation habits, different place names appear ("San Francisco Bay", "San Francisco Street"). At this time, it is necessary to repair "San Francisco Bay" and "San Francisco Street" into "San Francisco Bay" and "San Francisco Street" according to the geographical characteristics and the place names of the administrative district.

[0122] Restoration principles:

[0123] After analyzing the current situation, publicity, reliability and correctness of multi-source data, the repair principles are determined:

[0124] 1) The names of administrative regions and resident places are given priority. If other geographical features and geographical names conflict with the latest administrative regions and resident place names, other conflicting geographical features and geographical names will be modified; 2) The names of geographical features and geographical names are modified according to the name selection rules. That is, if other geographical features and geographical names conflict with the names with higher priority, the geographical features and geographical names with lower priority will be modified.

[0125] Note: Name selection rules: 1) Used ones are preferred; 2) Authoritative materials are preferred; 3) Those announced by the Ministry of Foreign Affairs are preferred; 4) Current information is preferred.

[0126] Repair priority uses: low priority ones are repaired according to the names of high priority ones.

[0127] In summary, the data sources involved in the example include: World Atlas, GNS, OSM. World Atlas is a book published by China Map Publishing House, which is widely used and authoritative. GNS is a global place name database covering areas outside the continental United States. The data comes from the National Geographic-Intelligence Agency (NGA) and the Board on Geographic Names (BGN). It is updated at least once a week and is less authoritative than the World Atlas. OSM is an online map collaboration program. Any registered user can upload and edit regional data that they are familiar with. It has low accuracy and reliability and is not authoritative. Therefore, the repair priority in this example is World Atlas, GNS, OSM, which is reflected in the Chinese names of tjcn, gnscn, and osmcn. In the data source of the place name "Juwadonga", the name with the highest priority is tjcn; in the data source of the place name "Juwadonga Station", the name with the highest priority is gnscn. It can be seen that "Juwadonga" has a higher priority, so "Juwadonga Station" should be modified according to "Juwadonga Station".

[0128] In order to reflect the inspection process, here we take error repair as an example. Repair by integrating the results repair software, such as Figure 4 As shown, Figure 5 The repair result is shown in the figure. The xfcn is still "Jiuwadonga Station" and "Jiuwadonga Station" has not been repaired to "Juwadonga Station". The correct repair should be to repair "Jiuwadonga Station" to "Juwadonga Station"

[0129] 2. Trigger real-time inspection. Figure 4 After completing the repair content, click the "Finish" button in the interface to trigger real-time inspection and perform real-time inspection of the intermediate data of the repair process.

[0130] Table 1 Repair processing real-time inspection rules

[0131]

[0132]

[0133] In the real-time inspection rules for repair processing, the inspection rule number is the number of each repair correctness inspection rule and is unique; when the inspection output is that there is an error in the data, the rule outputs the content to inform the processing personnel where the error is; the inspection principle is the specific inspection content and standard of the corresponding inspection rule; the inspection is classified as real-time inspection; and the inspection stage is the repair processing stage.

[0134] Of course, inspection attribution is not limited to real-time inspection, it includes: real-time inspection and full inspection, and the inspection stage includes: preprocessing, single-source normalization, multi-source fusion, and repair processing. When the inspection is triggered, targeted inspections need to be carried out according to the specific attribution of the specific stage.

[0135] 3. Output error results. When the triggered real-time check finds an error, the error record of the check is output and displayed to the processing personnel. The error record attribute information is shown in the following table:

[0136] Table 2 Error record attributes

[0137] Fields illustrate Serial number serial number Check rule number Same as the "Check Rule Number" in the repair processing real-time check rule base Check the output Same as "Check Output" in the Repair Processing Real-time Check Rule Base Error data coordinates Location information of incorrect place names, used for positioning Modify 1. Not modified; 2. Confirm not to modify; 3. Modified; 4. Confirm modification Check attribution Real-time inspection; full inspection Inspection Phase Preprocessing, single source normalization, multi-source fusion, repair processing Remark Special Instructions

[0138] In this example, the output error records are shown in the following table:

[0139] Table 3 Example error record output information

[0140]

[0141] 4. Error modification. Modify the place name according to the "check output" content and "error data coordinates" in the error record. Figure 6 At the same time, you need to change the "Modified" field in the error record to "Modified".

[0142] 5. Trigger the real-time check again. After the error is corrected, click the Finish button to trigger the real-time check again. No error records are output in the instance. At this time, the data is stored in the repair processing intermediate database "11". Figure 7 shown.

[0143] Corresponding to the thirteenth step of the above process: full inspection of the repair process. After the repair process is completed, according to the data integrity, logic, and correctness inspection rules in the full inspection of the repair process stage, the repair process intermediate database is fully inspected, and the final results of the repair process stage are stored in the results library.

[0144] 1. Obtain the final repair processing intermediate database "11", such as Figure 8 shown.

[0145] 2. Perform a full check on the intermediate database for repair processing. Use manual triggering to perform a full check on all data in the intermediate database for repair processing.

[0146] This should be the full inspection rule for repair processing. It is the inspection rule defined by risk assessment based on the data repair processing standard.

[0147] The maintenance of this rule includes two situations: 1. The data repair processing standard changes, and the corresponding inspection rules need to be modified and maintained; 2. The originally defined inspection rules do not meet the standards and need to be modified.

[0148] This rule maintenance method, in general, manually modifies the inspection principles and implements the inspection requirements by having programmers modify the code.

[0149] Note: Under normal circumstances, the real-time inspection and full inspection of each stage are stored in a rule base, which includes the inspection rule content and implementation code, etc. Through inspection attribution, the inspection stage matching is used in inspections at different stages.

[0150] Table 4 Repair processing full volume inspection rules

[0151]

[0152] In the full inspection rules for repair processing, the inspection rule number is the number of each repair correctness inspection rule and is unique; when the inspection output is that there is an error in the data, the rule outputs the content to inform the processing personnel where the error is; the inspection principle is the specific inspection content and standard of the corresponding inspection rule; the inspection category is the full inspection; and the inspection stage is the repair processing stage.

[0153] Of course, inspection attribution is not limited to full inspection, it includes: real-time inspection and full inspection, and the inspection stage includes: preprocessing, single source normalization, multi-source fusion, and repair processing. When the inspection is triggered, targeted inspections need to be carried out according to the specific attribution of the specific stage.

[0154] 3. Output error results. When errors are found in the full inspection, the error records will be output and displayed in shp format to the processing personnel for modification one by one. The error record attribute information is shown in the following table:

[0155] Table 5 Error record attributes

[0156]

[0157]

[0158] In this example, the output error records are shown in the following table:

[0159] Table 6 Example error record output information

[0160]

[0161] 4. Error correction. Use the location information in the error record to find the error data and correct it. After the correction, you need to re-trigger the real-time check for "Nanji Utara", such as Fig. 9 shown.

[0162] 5. Re-execute the full check. When all error records are modified, manually trigger the full check again until there are no problems, and obtain the final repair processing results database, such as Fig.10 shown.

[0163] In order to alleviate the technical problems of low quality inspection efficiency and low quality inspection accuracy caused by traditional manual quality inspection of massive place name data; at the same time, by discovering and modifying data problems in a decentralized manner in steps, the production and quality inspection pressure in the project achievement stage is alleviated, excessive backlog of data problems is avoided, and data rework is reduced. The method of the present invention is proposed. The method uses inspection rules instead of manual inspection, and can discover data problems in batches, thereby improving the quality inspection efficiency and quality inspection accuracy of massive place name data; using phased real-time inspection and full inspection, the speed of discovering data problems is accelerated, the production and quality inspection pressure in the project achievement stage is alleviated, and the data processing speed is improved.

[0164] Embodiment 2:

[0165] An embodiment of the present invention also provides a quality inspection device for the production of a multi-source place name database. The quality inspection device for the production of a multi-source place name database is mainly used to execute the quality inspection method for the production of a multi-source place name database provided in the first embodiment of the present invention. The following is a specific introduction to the quality inspection device for the production of a multi-source place name database provided in the embodiment of the present invention.

[0166] Fig.11 is a schematic diagram of a quality inspection device for multi-source place name database production according to an embodiment of the present invention. Fig.11 As shown, the device mainly includes: a real-time inspection unit 10, a first setting unit 20, a re-production and real-time inspection unit 30, a full quantity inspection unit 40, a second setting unit 50, a re-production and real-time inspection full quantity inspection unit 60 and a production unit 70, wherein:

[0167] A real-time inspection unit is used to obtain the initial production data produced in the current stage of the multi-source place name database production, and use the real-time inspection rules of the current stage to perform real-time inspection on the initial production data, wherein the current stage is to traverse all the following stages in sequence: preprocessing stage, single-source normalization stage, multi-source fusion stage and repair processing stage;

[0168] A first setting unit is used to save the initial production data that has passed the real-time inspection as the current stage intermediate data to the current stage intermediate database if the real-time inspection passes;

[0169] The re-production and real-time inspection unit is used to, if the real-time inspection fails, re-produce the current stage of production and re-inspect the real-time inspection until there is no problem, and then save the correct initial production data of the production as the current stage intermediate data to the current stage intermediate database;

[0170] A full check unit is used to perform a full check on the intermediate data of the current stage using the full check rules of the current stage after the current stage is completed;

[0171] The second setting unit is used to save the intermediate data of the current stage that has passed the full inspection as the result data of the current stage to the result database of the current stage if the full inspection has passed;

[0172] The re-production and real-time inspection full quantity inspection unit is used to, if the full quantity inspection fails, re-produce the current stage of production, and re-perform the real-time inspection and full quantity inspection in sequence until there is no problem, and then save the correct current stage intermediate data of the production as the current stage result data into the current stage result database;

[0173] The production unit is used to use the current stage results data as the initial data for the next stage of production, so as to carry out the next stage of production on the initial data and obtain the initial production data produced in the next stage, until it traverses to the repair processing stage, and uses the final repair processing results database as the product library after quality inspection.

[0174] In an embodiment of the present invention, a quality inspection device for multi-source place name database production is provided, including: obtaining initial production data produced in the current stage of multi-source place name database production, and using the real-time inspection rules of the current stage to perform real-time inspection on the initial production data, wherein the current stage is to traverse all the following stages in sequence: preprocessing stage, single-source normalization stage, multi-source fusion stage, and repair processing stage; if the real-time inspection passes, the initial production data that passes the real-time inspection is saved as the intermediate data of the current stage to the intermediate database of the current stage; if the real-time inspection fails, the production of the current stage is performed again, and the real-time inspection is re-performed until there is no problem, and then the correct initial production data produced is saved as the intermediate data of the current stage to the intermediate database of the current stage; in the current stage After completion, the full inspection rules of the current stage are used to perform a full inspection on the intermediate data of the current stage; if the full inspection passes, the intermediate data of the current stage that passes the full inspection is saved as the current stage result data in the current stage result database; if the full inspection fails, the current stage production is carried out again, and the real-time inspection and full inspection are carried out again in sequence until there are no problems, and then the correct current stage intermediate data of the production is saved as the current stage result data in the current stage result database; the current stage result data is used as the initial data for the next stage production, so as to carry out the next stage production on the initial data and obtain the initial production data produced in the next stage, until it traverses to the repair processing stage, and the final repair processing result database is used as the product library after quality inspection. From the above description, it can be seen that in the quality inspection device produced by the multi-source place name database of the present invention, inspection rules are used for automatic inspection, which can discover data problems in batches, improve the quality inspection efficiency and quality inspection accuracy of massive place name data, and adopt phased real-time inspection and full inspection to speed up the discovery of data problems, alleviate the production and quality inspection pressure in the project results stage, avoid excessive backlog of data problems, improve data processing speed, and alleviate the technical problems of low efficiency, poor accuracy and accumulation of data problems in existing manual quality inspection methods.

[0175] Optionally, the re-production and real-time inspection unit is also used to: store the generated real-time inspection error record into the real-time inspection result, and assign the value of "modify" to the field in the real-time inspection error record as unmodified, and manually confirm and modify the corresponding erroneous initial production data; if the erroneous initial production data is confirmed to be correct, assign the value of "modify" to the field in the corresponding real-time inspection error record as confirmed not to be modified, and save the confirmed correct initial production data as the intermediate data of the current stage to the intermediate database of the current stage; if the erroneous initial production data is confirmed to be wrong, perform the current stage production on the erroneous initial production data, and re-perform real-time inspection until there is no problem, and then save the correct initial production data as the intermediate data of the current stage to the intermediate database of the current stage, and assign the value of "modify" to the field in the corresponding real-time inspection error record as modified.

[0176] Optionally, the re-production and real-time inspection full inspection unit is also used to: compare the error record of the full inspection with the error record of the real-time inspection in the corresponding real-time inspection result; if the error record of the full inspection exists in the error record of the real-time inspection, and the value assigned to the "Whether to modify" field in the error record of the real-time inspection is not confirmation not to modify, then the error record of the full inspection is stored in the full inspection result, and the value assigned to the "Whether to modify" field in the error record of the full inspection is confirmation to modify; if the error record of the full inspection does not exist in the error record of the real-time inspection, then the error record of the full inspection is stored in the full inspection result, and the error record of the full inspection is stored in the full inspection result. The "Is it modified" field in the full inspection result is assigned the value of "Not modified"; the current stage intermediate data that has been assigned the value of confirmed modification and not modified in the "Is it modified" field in the full inspection result is manually confirmed and modified; if the confirmation is correct, the corresponding "Is it modified" field is assigned the value of confirmed not modified, and the current stage intermediate data that has been confirmed correct is saved as the current stage result data to the current stage result database; if the confirmation is wrong, the current stage production is carried out for the current stage intermediate data that has been confirmed incorrectly, and real-time inspection and full inspection are re-performed until there are no problems, and then the correct current stage intermediate data produced is saved as the current stage result data to the current stage result database.

[0177] Optionally, the real-time inspection rule and the full inspection rule are formulated according to the processing of the corresponding stage, and the attributes of the real-time inspection rule and the full inspection rule include: inspection rule number, inspection principle, inspection output, inspection attribution and inspection stage.

[0178] Optionally, if the current stage is a preprocessing stage, the initial production data is obtained by preprocessing the original data in the original database.

[0179] Optionally, the error records of real-time inspection and full inspection include: serial number, inspection rule number, inspection output, error data coordinates, "whether to modify" field, inspection attribution, inspection stage and remarks, wherein the "whether to modify" field includes: not modified, confirmed not to modify, modified and confirmed to modify.

[0180] The device provided in the embodiment of the present invention has the same implementation principle and technical effects as those of the aforementioned method embodiment. For the sake of brief description, for matters not mentioned in the device embodiment, reference may be made to the corresponding contents in the aforementioned method embodiment.

[0181] like Fig.12 As shown, an electronic device 600 provided in an embodiment of the present application includes: a processor 601, a memory 602 and a bus, wherein the memory 602 stores machine-readable instructions executable by the processor 601. When the electronic device is running, the processor 601 communicates with the memory 602 through the bus, and the processor 601 executes the machine-readable instructions to perform the steps of the quality inspection method produced by the multi-source place name database as mentioned above.

[0182] Specifically, the above-mentioned memory 602 and processor 601 can be general-purpose memory and processor, which are not specifically limited here. When the processor 601 runs the computer program stored in the memory 602, it can execute the quality inspection method produced by the above-mentioned multi-source place name database.

[0183] The processor 601 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the hardware integrated logic circuit or software instructions in the processor 601. The above processor 601 can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in the embodiments of the present application can be directly embodied as a hardware decoding processor for execution, or a combination of hardware and software modules in the decoding processor for execution. The software module may be located in a storage medium mature in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory 602, and the processor 601 reads the information in the memory 602 and completes the steps of the above method in combination with its hardware.

[0184] Corresponding to the quality inspection method for the above-mentioned multi-source place name database production, an embodiment of the present application also provides a computer-readable storage medium, which stores machine-executable instructions. When the computer-executable instructions are called and executed by the processor, the computer-executable instructions prompt the processor to execute the steps of the quality inspection method for the above-mentioned multi-source place name database production.

[0185] The quality inspection device for the multi-source place name database provided in the embodiment of the present application can be specific hardware on the device or software or firmware installed on the device. The device provided in the embodiment of the present application, its implementation principle and the technical effect produced are the same as those in the aforementioned method embodiment. For the sake of brief description, where the device embodiment is not mentioned, reference can be made to the corresponding content in the aforementioned method embodiment. Those skilled in the art can clearly understand that for the convenience and conciseness of description, the specific working processes of the systems, devices and units described above can all refer to the corresponding processes in the aforementioned method embodiment, and will not be repeated here.

[0186] In the embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some communication interfaces, and the indirect coupling or communication connection of the devices or units can be electrical, mechanical or other forms.

[0187] For another example, the flowchart and block diagram in the accompanying drawings show the possible architecture, function and operation of the device, method and computer program product according to multiple embodiments of the present application. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of the code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or the flowchart, and the combination of the boxes in the block diagram and / or the flowchart can be implemented with a dedicated hardware-based system that performs a specified function or action, or can be implemented with a combination of dedicated hardware and computer instructions.

[0188] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0189] In addition, each functional unit in the embodiments provided in the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0190] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium, including a number of instructions to enable an electronic device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the quality inspection method for the production of a multi-source place name database described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, referred to as ROM), random access memory (Random Access Memory, referred to as RAM), disk or optical disk and other media that can store program codes.

[0191] It should be noted that similar numbers and letters represent similar items in the following figures. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures. In addition, the terms "first", "second", "third", etc. are only used to distinguish the description and are not to be understood as indicating or implying relative importance.

[0192] Finally, it should be noted that the above-described embodiments are only specific implementation methods of the present application, which are used to illustrate the technical solution of the present application, rather than to limit it. The protection scope of the present application is not limited thereto. Although the present application is described in detail with reference to the aforementioned embodiments, ordinary technicians in the field should understand that any technician familiar with the technical field can still modify the technical solution recorded in the aforementioned embodiments within the technical scope disclosed in the present application, or can easily think of changes, or make equivalent replacements for some of the technical features therein; and these modifications, changes or replacements do not make the essence of the corresponding technical solution deviate from the scope of the technical solution of the embodiment of the present application. They should all be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.

Claims

1. A quality inspection method for the production of a multi-source place name database, characterized in that: include: Acquire the initial production data produced in the current stage of the multi-source place name database production, and use the real-time inspection rules of the current stage to perform real-time inspection on the initial production data, wherein the current stage is to traverse all the following stages in sequence: preprocessing stage, single-source normalization stage, multi-source fusion stage and repair processing stage; If the real-time check is passed, the initial production data that has passed the real-time check is saved as the intermediate data of the current stage to the intermediate database of the current stage; If the real-time check fails, the current stage of production is performed again, and the real-time check is performed again until there is no problem, and then the correct initial production data of the production is saved as the current stage intermediate data in the current stage intermediate database; After the current stage is completed, the full amount check rule of the current stage is used to perform a full amount check on the intermediate data of the current stage; If the full inspection is passed, the intermediate data of the current stage that has passed the full inspection will be saved as the current stage achievement data in the current stage achievement database; If the full inspection fails, the current stage of production is carried out again, and the real-time inspection and full inspection are carried out again in sequence until there is no problem, and then the correct current stage intermediate data of production is saved as the current stage result data in the current stage result database; The result data of the current stage is used as the initial data for the next stage of production, so as to perform the next stage of production on the initial data, and obtain the initial production data produced in the next stage, until the repair processing stage is traversed, and the repair processing result database finally obtained is used as the product library after quality inspection; The current stage of production is performed again, and real-time inspection is performed again until there are no problems, and then the correct initial production data of the production is saved as the current stage intermediate data to the current stage intermediate database, including: The generated real-time check error record is stored in the real-time check result, and the "whether to modify" field in the real-time check error record is assigned a value of unmodified, and the corresponding erroneous initial production data is manually confirmed and modified; If the erroneous initial production data is confirmed to be correct, the "whether to modify" field in the corresponding real-time check error record is assigned a value of confirming not to modify, and the confirmed correct initial production data is saved as the current stage intermediate data in the current stage intermediate database; If the erroneous initial production data is confirmed to be erroneous, the current stage production is carried out on the erroneous initial production data, and real-time inspection is re-performed until there is no problem, and then the correct initial production data produced is saved as the current stage intermediate data to the current stage intermediate database, and the "Whether Modified" field in the corresponding real-time inspection error record is assigned a value of Modified; Among them, the current stage of production is carried out again, and the real-time inspection and the full inspection are carried out again in sequence until there are no problems, and then the correct current stage intermediate data of production is saved as the current stage result data in the current stage result database, including: Compare the error records of the full inspection with the error records of the real-time inspection in the corresponding real-time inspection results; If the error record of the full check exists in the error record of the real-time check, and the value assigned to the "Whether to modify" field in the error record of the real-time check is not confirmation not to modify, the error record of the full check is stored in the full check result, and the value assigned to the "Whether to modify" field in the error record of the full check is confirmation to modify; If the error record of the full check does not exist in the error record of the real-time check, the error record of the full check is stored in the full check result, and the "whether modified" field in the error record of the full check is assigned a value of unmodified; Manually confirm and modify the current intermediate data by assigning the value of "modify" to the field "modify" in the full inspection result as confirmed modification or unmodified; If the confirmation is correct, the corresponding "whether to modify" field is assigned a value of confirming not to modify, and the confirmed correct current stage intermediate data is saved as the current stage achievement data to the current stage achievement database; If an error is confirmed, the current stage production will be carried out on the current stage intermediate data with the confirmed error, and real-time inspection and full inspection will be re-performed until there is no problem, and then the correct current stage intermediate data produced will be saved as the current stage result data in the current stage result database.

2. The method according to claim 1, characterized in that The real-time inspection rule and the full inspection rule are formulated according to the processing of the corresponding stage, and the attributes of the real-time inspection rule and the full inspection rule include: inspection rule number, inspection principle, inspection output, inspection attribution and inspection stage.

3. The method according to claim 1, characterized in that If the current stage is a preprocessing stage, the initial production data is obtained by preprocessing the original data in the original database.

4. The method according to claim 1, characterized in that: The error records of the real-time inspection and the error records of the full inspection include: serial number, inspection rule number, inspection output, error data coordinates, "whether to modify" field, inspection attribution, inspection stage and remarks, wherein the "whether to modify" field includes: not modified, confirmed not to modify, modified and confirmed to modify.

5. A quality inspection device for multi-source place name database production, characterized in that: include: A real-time inspection unit is used to obtain the initial production data produced in the current stage of the multi-source place name database production, and use the real-time inspection rules of the current stage to perform real-time inspection on the initial production data, wherein the current stage is to traverse all the following stages in sequence: preprocessing stage, single-source normalization stage, multi-source fusion stage and repair processing stage; A first setting unit is used to save the initial production data that has passed the real-time inspection as the current stage intermediate data to the current stage intermediate database if the real-time inspection passes; The re-production and real-time inspection unit is used to, if the real-time inspection fails, re-produce the current stage of production and re-inspect the real-time inspection until there is no problem, and then save the correct initial production data of the production as the current stage intermediate data to the current stage intermediate database; A full inspection unit, configured to perform a full inspection on the intermediate data of the current stage using the full inspection rule of the current stage after the current stage is completed; The second setting unit is used to save the intermediate data of the current stage that has passed the full inspection as the result data of the current stage to the result database of the current stage if the full inspection has passed; The re-production and real-time inspection full quantity inspection unit is used to, if the full quantity inspection fails, re-produce the current stage of production, and re-perform the real-time inspection and the full quantity inspection in sequence until there is no problem, and then save the correct current stage intermediate data of the production as the current stage result data into the current stage result database; The production unit is used to use the result data of the current stage as the initial data for the next stage of production, so as to perform the next stage of production on the initial data, and obtain the initial production data produced in the next stage, until the repair processing stage is traversed, and the repair processing result database finally obtained is used as the product library after quality inspection; Wherein, the re-production and real-time inspection unit is further used for: storing the generated real-time inspection error record into the real-time inspection result, and assigning the value of "modify" to the field in the real-time inspection error record as unmodified, and manually confirming and modifying the corresponding erroneous initial production data; if the erroneous initial production data is confirmed to be correct, assigning the value of "modify" to the field in the corresponding real-time inspection error record as confirmed not to be modified, and saving the confirmed correct initial production data as the current stage intermediate data to the current stage intermediate database; if the erroneous initial production data is confirmed to be wrong, the current stage production is carried out on the erroneous initial production data, and real-time inspection is re-performed until there is no problem, and then the correct initial production data produced is saved as the current stage intermediate data to the current stage intermediate database, and the "modify" field in the corresponding real-time inspection error record is assigned as modified; Among them, the re-production and real-time inspection full inspection unit is also used to: compare the error record of the full inspection with the error record of the real-time inspection in the corresponding real-time inspection result; if the error record of the full inspection exists in the error record of the real-time inspection, and the value assigned to the "Whether to modify" field in the error record of the real-time inspection is not confirmation not to modify, then the error record of the full inspection is stored in the full inspection result, and the "Whether to modify" field in the error record of the full inspection is assigned to confirmation to modify; if the error record of the full inspection does not exist in the error record of the real-time inspection, then the error record of the full inspection is stored in the full inspection result, and the full inspection result is The "Is it modified" field in the error record of the quantity inspection is assigned the value of "Not modified"; the current stage intermediate data that has been assigned the value of "Is it modified" in the full quantity inspection result is manually confirmed and modified; if the confirmation is correct, the corresponding "Is it modified" field is assigned the value of "Confirmed not modified", and the current stage intermediate data that has been confirmed correct is saved as the current stage result data to the current stage result database; if the confirmation is wrong, the current stage production is carried out for the current stage intermediate data that has been confirmed wrong, and real-time inspection and full quantity inspection are re-performed until there is no problem, and then the correct current stage intermediate data produced is saved as the current stage result data to the current stage result database.

6. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 4 are implemented.

7. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores machine-executable instructions. When the machine-executable instructions are called and executed by a processor, the machine-executable instructions cause the processor to execute the method according to any one of claims 1 to 4.

Images