Pipeline detection database logic detection method and device, electronic equipment and medium
By standardizing and logically checking the data from underground drainage pipeline detection, the problem of detecting data in different formats was solved, achieving efficient detection and quality control, and improving the quality of results and production efficiency of underground pipeline detection projects.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- UNDERGROUND SPACE TECHNOLOGY DEVELOPMENT CO LTD OF CNACG
- Filing Date
- 2022-12-19
- Publication Date
- 2026-06-02
AI Technical Summary
Existing technologies cannot effectively detect underground drainage pipeline detection data in different formats, which increases the difficulty of detection and affects the production efficiency and quality of urban underground municipal infrastructure surveys and underground pipeline detection projects.
By standardizing the detection data of different drainage pipelines, converting them into a unified format mdb data table, and performing logical checks, including routine and additional checks, the detection results are output.
This enabled in-depth inspection of underground drainage pipeline detection data, improving production efficiency and data quality, reducing personnel time costs, and enhancing the accuracy and efficiency of detection.
Smart Images

Figure CN115858517B_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of data processing technology, and more specifically, to a pipeline detection database logic detection method, apparatus, electronic device, and medium. Background Technology
[0002] Underground drainage pipeline data describes the spatial location, spatial relationships, and other characteristic attributes of underground drainage pipelines and their ancillary facilities. In recent years, urban underground infrastructure has received increasing attention. As an important carrier of pipeline detection data, the underground drainage pipeline detection database needs to undergo logical testing to improve the efficiency and quality of projects such as urban underground municipal infrastructure surveys, detailed underground pipeline surveys, and specialized underground pipeline detection.
[0003] However, underground drainage pipeline data is constrained by multiple attributes, has complex relationships, and varies depending on the project or standard. This results in complex data types and inconsistent formats stored in pipeline detection databases, increasing the difficulty of detection. Currently, there is no method to detect underground drainage pipeline detection data in different formats. Summary of the Invention
[0004] To address the aforementioned technical problems, embodiments of this application provide a pipeline detection database logic detection method, apparatus, electronic device, and medium.
[0005] In a first aspect, embodiments of this application provide a pipeline detection database logic detection method, the method comprising:
[0006] Obtain multiple drainage pipeline detection data from the pipeline detection database. The initial storage format of different drainage pipeline detection data is different.
[0007] The detection data of each drainage pipeline are standardized to obtain standardized data with a unified format.
[0008] Obtain the detection category of each standardized data and select the corresponding routine logic check item for the detection category;
[0009] Select at least one of the following as an additional logical check item: inspection of the burial depth of drainage pipes and accessories, inspection of drainage professional field attributes, and comprehensive inspection of the safe distance of water supply and drainage pipes and accessories.
[0010] The standardized data is subjected to basic class detection based on the conventional logic check items, and the basic detection results are output. Additionally, the standardized data is subjected to additional class detection based on the additional logic check items, and the additional detection results are output.
[0011] The basic and additional detection results of the drainage pipeline detection data are determined as the combined detection results.
[0012] In one embodiment, the standardization process for the detection data of each drainage pipeline to obtain standardized data with a unified format includes:
[0013] Obtain the data format, data structure, and data table fields of the detection data for each drainage pipeline;
[0014] Convert all the drainage pipeline detection data into an mdb format data table;
[0015] The data structure of the drainage pipeline detection data is divided into point structure, line structure and range structure;
[0016] The names of the data table fields for each drainage pipeline detection data are unified to preset names through field mapping.
[0017] In one embodiment, the detection categories include municipal pipeline detection data and residential pipeline detection data, and the routine logic check items include municipal routine check items and residential routine check items;
[0018] The acquisition of the detection categories for each of the standardized data, and the selection of the corresponding routine logic check items for the detection categories, includes:
[0019] If the detection category is the municipal pipeline detection data, then select the municipal routine inspection item, which includes drainage slope inspection, drainage pipe diameter anomaly inspection, concealed point pipe diameter inspection, drainage well material inspection, rainwater drainage outlet exposure inspection, sewage characteristic attachment name inspection, and well body pipe material consistency inspection.
[0020] If the detection category is the pipeline detection data of the community, then the routine inspection items of the community are selected, wherein the routine inspection items of the community include the inspection of the distance between drainage pipe inspection wells, the inspection of the distance between riser connection inspection wells, and the inspection of the distance between rainwater wells in the community.
[0021] In one embodiment, the step of performing basic class detection on the standardized data based on the conventional logic check items and outputting the basic detection results includes:
[0022] The step of performing basic class detection on the standardized data based on the conventional logic check items and outputting the basic detection results includes:
[0023] Determine whether each of the aforementioned conventional logic check items meets the corresponding preset conditions;
[0024] The preset conditions corresponding to each of the conventional logic check items include:
[0025] The preset condition for the drainage slope check is that the angle between the slope of the drainage pipe section and the horizontal plane is less than a preset angle.
[0026] The preset condition for checking the abnormal drainage pipe diameter is that the drainage pipe diameter meets the first preset range.
[0027] The preset conditions for the hidden point pipe diameter inspection are that the pipe diameters of the connecting pipe sections on both sides of the preset pipeline point or detection point are consistent, and the cross-sectional dimensions of the connecting pipe sections on both sides of the preset pipeline point or detection point are consistent.
[0028] The preset condition for the material inspection of the drainage well is that if the pipe point is an inspection well, the inspection well meets the material standard.
[0029] The preset condition for the rainwater drain outlet exposure inspection is that if the rainwater pipe point is the outlet, the obvious concealed point of the outlet is not a concealed point.
[0030] The preset condition corresponding to the wastewater feature attachment name check is that the wastewater pipe point feature or attachment name is not an outlet or a grate.
[0031] The preset condition for checking the consistency of the manhole body and the pipe material is that if the pipe point is the manhole, the material field of the manhole is the same as the material field of the pipe section connected to the manhole.
[0032] The preset conditions corresponding to the inspection of the distance between the drainage pipe inspection wells are as follows: when the sewage pipe point is a sewage pipe point and the connecting pipe points of the sewage pipe point are all inspection wells, the pipe section diameter of the sewage pipe point meets the second preset range and the coordinate distance between the two pipe points meets the third preset range.
[0033] The preset conditions corresponding to the riser connection inspection well distance inspection are as follows: if the sewage pipe point is a riser and the connecting pipe point of the sewage pipe point is an inspection well, it is determined that the pipe section diameter of the sewage pipe point meets the fourth preset range and the coordinate distance between the two pipe points meets the fifth preset range.
[0034] The preset conditions for checking the spacing between rainwater wells in the community are as follows: if both the rainwater pipe point and the connecting pipe point of the rainwater pipe point are inspection wells, the pipe section diameter of the sewage pipe point is determined to be within the sixth preset range and the coordinate distance between the two pipe points is within the seventh preset range.
[0035] Output routine logic checks and warning messages for detecting anomalies.
[0036] In one embodiment, the inspection of the burial depth of drainage pipes and accessories includes the inspection of the burial depth of rainwater pipes in the community, the inspection of the burial depth of drainage wells, the inspection of the burial depth of concealed points, and the inspection of the burial depth of rainwater inlets;
[0037] The drainage professional field attribute checks include checks on the design service life and structural design safety level, pipe interface type, and number of connected pipes.
[0038] The comprehensive safety distance inspection of water supply and drainage pipes and their accessories includes the inspection of vertical clearance between water supply and drainage pipes, the inspection of horizontal clearance between water supply and drainage pipes, the inspection of septic tank spacing, the inspection of municipal rainwater well spacing, and the inspection of rainwater inlet spacing.
[0039] In one embodiment, the step of performing additional class checks on the standardized data based on the additional logic check items and outputting additional detection results includes:
[0040] Determine whether each of the additional logic check items meets the corresponding preset conditions;
[0041] If any of the additional logic checks does not meet the corresponding preset conditions, it is determined that the additional logic check has a detection anomaly.
[0042] Output additional logical checks and warning messages for detected anomalies.
[0043] Secondly, embodiments of this application provide a pipeline detection database logic detection device, the device comprising:
[0044] The acquisition module is used to acquire multiple drainage pipeline detection data from the pipeline detection database. The initial storage format of different drainage pipeline detection data is different.
[0045] The standardization module is used to standardize the detection data of each drainage pipeline to obtain standardized data with a unified format.
[0046] The first selection module is used to obtain the detection category of each standardized data and select the conventional logic check item corresponding to the detection category;
[0047] The second selection module is used to select at least one of the following as additional logical check items: drainage pipe and appurtenance burial depth inspection, drainage professional field attribute inspection, and water supply and drainage pipe and appurtenance safety distance comprehensive inspection.
[0048] The detection module is used to perform basic class detection on the standardized data according to the conventional logic check items and output the basic detection results, and to perform additional class detection on the standardized data according to the additional logic check items and output the additional detection results.
[0049] The determination module is used to determine the basic detection results and additional detection results of each drainage pipeline detection data into a combined detection result.
[0050] In one embodiment, the standardization module is further configured to:
[0051] Obtain the data format, data structure, and data table fields of the detection data for each drainage pipeline;
[0052] Convert all the drainage pipeline detection data into an mdb format data table;
[0053] The data structure of the drainage pipeline detection data is divided into point structure, line structure and range structure;
[0054] The names of the data table fields for the drainage pipeline detection data are unified to preset names through field mapping.
[0055] Thirdly, embodiments of this application provide an electronic device, including a memory and a processor, wherein the memory is used to store a computer program, and the computer program executes the pipeline detection database logic detection method provided in the first aspect when the processor is running.
[0056] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program that, when run on a processor, executes the pipeline detection database logic detection method provided in the first aspect.
[0057] The pipeline detection database logic detection method provided in this application proposes a solution for logical inspection of drainage underground pipeline detection databases. It innovatively proposes multiple inspection items to achieve in-depth inspection of drainage underground pipeline detection data, improving the quality and efficiency of results from urban underground municipal infrastructure surveys, detailed underground pipeline surveys, and specialized underground pipeline detection projects. This reduces personnel and time costs, quickly and effectively controlling the quality of drainage pipeline detection data. Furthermore, the design and approach of the drainage underground pipeline detection database logic inspection can be widely applied to underground pipeline data acquisition and database construction, underground pipeline information management system platform construction, underground pipeline data processing system development, and the application of underground pipeline detection engineering supervision and quality inspection software, demonstrating broad applicability. Attached Figure Description
[0058] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of the present invention and should not be regarded as a limitation on the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.
[0059] Figure 1 A schematic flowchart of a pipeline detection database logic detection method provided in an embodiment of this application is shown.
[0060] Figure 2This paper illustrates another flowchart of the pipeline detection database logic detection method provided in an embodiment of this application;
[0061] Figure 3 A schematic diagram of the structure of the pipeline detection database logic detection device provided in an embodiment of this application is shown. Detailed Implementation
[0062] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments.
[0063] The components of the embodiments of this application described and illustrated in the accompanying drawings can be arranged and designed in a variety of different configurations. Therefore, the following detailed description of the embodiments of this application provided in the drawings is not intended to limit the scope of the claimed application, but merely to illustrate selected embodiments of the application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.
[0064] In the following, the terms “comprising,” “having,” and their cognates, which may be used in various embodiments of this application, are intended only to indicate a particular feature, number, step, operation, element, component, or combination thereof, and should not be construed as excluding, firstly, the presence of one or more other features, numbers, steps, operations, elements, components, or combinations thereof, or adding the possibility of one or more features, numbers, steps, operations, elements, components, or combinations thereof.
[0065] Furthermore, the terms "first," "second," and "third" are used only to distinguish descriptions and should not be interpreted as indicating or implying relative importance.
[0066] Unless otherwise specified, all terms used herein (including technical and scientific terms) shall have the same meaning as commonly understood by one of ordinary skill in the art to which the various embodiments of this application pertain. Terms (such as those defined in commonly used dictionaries) shall be interpreted as having the same meaning as in their contextual meaning in the relevant technical field and shall not be construed as having an idealized or overly formal meaning, unless clearly defined in the various embodiments of this application.
[0067] Example 1
[0068] This disclosure provides a pipeline detection database logic detection method.
[0069] For details, see Figure 1 The pipeline detection database logical detection method includes:
[0070] Step S110: Obtain multiple drainage pipeline detection data from the pipeline detection database. The initial storage format of different drainage pipeline detection data is different.
[0071] Combination Figure 2 This application demonstrates that in pipeline survey and detection projects, the accuracy of pipelines can be checked by sampling inspections of obvious and concealed pipeline points; and inspections can also be carried out by formulating simple quality inspection rules that meet the requirements of comprehensive pipeline mapping and database construction.
[0072] Different projects and technical procedures and data standards have different requirements, or the data to be checked may come from current surveying or historical data, which may lead to differences in data table fields, database structure, and even database format, making it impossible to directly use the original data for inspection.
[0073] Based on this, the embodiments of this application provide a database conversion process, which can avoid redesigning and recompiling the checking program for external data or database.
[0074] Step S120: Standardize the detection data of each drainage pipeline to obtain standardized data with a unified format.
[0075] In one embodiment, the standardization process for the detection data of each drainage pipeline to obtain standardized data with a unified format includes:
[0076] Obtain the data format, data structure, and data table fields of the detection data for each drainage pipeline;
[0077] Convert all the drainage pipeline detection data into an mdb format data table;
[0078] The data structure of the drainage pipeline detection data is divided into point structure, line structure and range structure;
[0079] The names of the data table fields for each drainage pipeline detection data are unified to preset names through field mapping.
[0080] Database conversion processing includes database format processing, database structure processing, and data table field processing. First, database format processing is performed; if the database formats are different, the existing database format is first converted to an Access .mdb database.
[0081] Secondly, the database structure is processed. The data tables in the mdb database are standardized according to pipeline type + point, pipeline type + line, and pipeline type + range line. This facilitates database checks by pipeline type and object. The data structure standardization process means that each type of pipeline (such as rainwater pipeline, sewage pipeline, and combined pipeline) is organized into three categories: pipeline type + point, pipeline type + line, and pipeline type + range line. For example, rainwater can be represented by three database tables: YSPoint, YSLine, and YSAnnexe.
[0082] Next, the data table fields are processed, and the names of all fields are standardized through field mapping. This standardization facilitates subsequent database classification checks and the fields required by various logical checks. For example, the field mapping method provides a list of fields for the original input and fields for the target output, allowing the user to map and match fields as needed. For instance, the field name for a certain type of pipeline in the database to be logically checked could be "pipe diameter," while the field name for the target pipeline could be "cross-sectional dimensions."
[0083] Step S130: Obtain the detection category of each standardized data and select the regular logic check item corresponding to the detection category;
[0084] Depending on whether the detection is for municipal pipelines or residential pipelines, select the corresponding inspection method, i.e., the inspection item.
[0085] In one embodiment, the detection categories include municipal pipeline detection data and residential pipeline detection data, and the routine logic check items include municipal routine check items and residential routine check items;
[0086] The acquisition of the detection categories for each of the standardized data, and the selection of the corresponding routine logic check items for the detection categories, includes:
[0087] If the detection category is the municipal pipeline detection data, then select the municipal routine inspection item, which includes drainage slope inspection, drainage pipe diameter anomaly inspection, concealed point pipe diameter inspection, drainage well material inspection, rainwater drainage outlet exposure inspection, sewage characteristic attachment name inspection, and well body pipe material consistency inspection.
[0088] If the detection category is the pipeline detection data of the community, then the routine inspection items of the community are selected, wherein the routine inspection items of the community include the inspection of the distance between drainage pipe inspection wells, the inspection of the distance between riser connection inspection wells, and the inspection of the distance between rainwater wells in the community.
[0089] The routine municipal inspection items include the following inspection methods:
[0090] Drainage slope check, also known as municipal drainage back slope check, can calculate the slope of the drainage pipe section by using the coordinates of the start and end points of the pipe section. If the included angle is greater than or equal to 20 degrees, a warning message will be displayed.
[0091] For checking for abnormal drainage pipe diameters, you can use the pipe section table to calculate half of the pipe diameter (or cross-sectional height). If the value is greater than the starting or ending burial depth, a warning message will be displayed.
[0092] The hidden point pipe diameter check can compare and calculate the pipe diameter or cross-sectional dimensions of the connecting pipe sections on both sides of the preset pipeline point (or detection point). If the contents are inconsistent, a warning message will be displayed.
[0093] When inspecting the drainage well material, if the pipe point is an inspection well and the well material is clay brick or brick masonry, a warning message will be displayed.
[0094] When inspecting exposed rainwater drain outlets, if the rainwater pipe point is the outlet, and the content of the obvious concealed point is concealed, a warning message will be displayed.
[0095] Check the names of sewage pipe features and attachments. If the sewage pipe feature or attachment name is an outlet or storm drain, a warning message will be displayed.
[0096] The check for consistency between the manhole body and the pipe material will display a warning message if the material field of the manhole is different from that of the pipe section it is connected to when the pipe point is a manhole.
[0097] The routine inspection items for residential communities include the following inspection methods:
[0098] Inspection of manhole distance for drainage pipes: If there are no manholes for sewage pipe points and their connecting pipe points, and the pipe diameter is less than or equal to 160mm, and the coordinate distance between the two pipe points is greater than 30m, a warning message will be issued; if the pipe diameter is greater than or equal to 200mm but less than 300mm, and the coordinate distance between the two pipe points is greater than 40m, a warning message will be issued; if the pipe diameter is greater than or equal to 300mm, and the coordinate distance between the two pipe points is greater than 50m, a warning message will be issued.
[0099] Riser connection inspection manhole distance check: If the sewage pipe point is a riser and its connection point is an inspection manhole, and the pipe diameter of the pipe section is 50mm, and the coordinate distance between the two pipe points is greater than 10m, a warning message will be issued; if the pipe diameter of the pipe section is 75mm, and the coordinate distance between the two pipe points is greater than 12m, a warning message will be issued; if the pipe diameter of the pipe section is 100mm, and the coordinate distance between the two pipe points is greater than 15m, a warning message will be issued; if the pipe diameter of the pipe section is greater than 100mm, and the coordinate distance between the two pipe points is greater than 20m, a warning message will be issued.
[0100] Inspection of the spacing between rainwater wells in the residential area: If the diameter of the rainwater pipes and their connecting pipes in the residential area are all inspection wells, and the diameter of the pipe section is greater than or equal to 200mm and less than or equal to 315mm, and the coordinate distance between the two pipe points is greater than 40m, a warning message will be issued; if the diameter of the pipe section is equal to 400mm, and the coordinate distance between the two pipe points is greater than 50m, a warning message will be issued; if the diameter of the pipe section is greater than or equal to 500mm, and the coordinate distance between the two pipe points is greater than 70m, a warning message will be issued.
[0101] Step S140: Select at least one of the following as an additional logical check item: drainage pipe and appurtenance burial depth check, drainage professional field attribute check, and water supply and drainage pipe and appurtenance safety distance comprehensive check.
[0102] Because the database inspection and entry requirements differ for different surveying projects, it is not always necessary to inspect all three items in actual production. Instead, one or more items can be inspected based on the actual project requirements and the needs of production personnel. At least one additional inspection can be selected from the following: inspection of the burial depth of drainage pipes and accessories, inspection of drainage professional field attributes, and comprehensive inspection of the safety distance of water supply and drainage pipes and accessories.
[0103] Step S150: Perform basic class detection on the standardized data according to the conventional logic check items and output the basic detection results; and perform additional class detection on the standardized data according to the additional logic check items and output the additional detection results.
[0104] In one embodiment, the step of performing basic class detection on the standardized data based on the conventional logic check items and outputting the basic detection results includes:
[0105] Determine whether each of the aforementioned conventional logic check items meets the corresponding preset conditions;
[0106] If any of the conventional logic check items does not meet the corresponding preset conditions, it is determined that the conventional logic check item has a detection anomaly;
[0107] The preset conditions corresponding to each of the conventional logic check items include:
[0108] The preset condition for the drainage slope check is that the angle between the slope of the drainage pipe section and the horizontal plane is less than a preset angle; wherein, the preset angle can be 20°.
[0109] The preset condition for the abnormal drainage pipe diameter check is that the drainage pipe diameter meets the first preset range; the first preset range can be a value less than or equal to the starting burial depth or the ending burial depth.
[0110] The preset conditions for the hidden point pipe diameter inspection are that the pipe diameters of the connecting pipe sections on both sides of the preset pipeline point or detection point are consistent, and the cross-sectional dimensions of the connecting pipe sections on both sides of the preset pipeline point or detection point are consistent; wherein the preset pipeline point is a general pipeline point.
[0111] The preset condition for checking the material of the drainage well is that if the pipe point is a manhole, the manhole meets the material standard; wherein, the material standard is that it is not clay brick or brick masonry.
[0112] The preset condition for the rainwater drain outlet exposure inspection is that if the rainwater pipe point is the outlet, the obvious concealed point of the outlet is not a concealed point.
[0113] The preset condition corresponding to the wastewater feature attachment name check is that the wastewater pipe point feature or attachment name is not an outlet or a grate.
[0114] The preset condition for the consistency check of the well body pipe material is that if the pipe point is the inspection well, the content of the well material field of the inspection well is the same as the content of the material field of the pipe section connected to the inspection well.
[0115] The preset conditions corresponding to the inspection of the distance between the drainage pipe inspection wells are as follows: when the sewage pipe point is a sewage pipe point and the connecting pipe points of the sewage pipe point are all inspection wells, the pipe section diameter of the sewage pipe point meets the second preset range and the coordinate distance between the two pipe points meets the third preset range.
[0116] The preset conditions corresponding to the riser connection inspection well distance inspection are as follows: if the sewage pipe point is a riser and the connecting pipe point of the sewage pipe point is an inspection well, it is determined that the pipe section diameter of the sewage pipe point meets the fourth preset range and the coordinate distance between the two pipe points meets the fifth preset range.
[0117] The preset conditions for checking the spacing between rainwater wells in the community are as follows: if both the rainwater pipe point and the connecting pipe point of the rainwater pipe point are inspection wells, the pipe section diameter of the sewage pipe point is determined to be within the sixth preset range and the coordinate distance between the two pipe points is within the seventh preset range.
[0118] The second, third, fourth, fifth, sixth, and seventh preset ranges have all appeared in the preceding text and will not be repeated here.
[0119] Output routine logic checks and warning messages for detecting anomalies.
[0120] Output routine logic checks and warning messages for detecting anomalies.
[0121] In one embodiment, the step of performing additional class checks on the standardized data based on the additional logic check items and outputting additional detection results includes:
[0122] Determine whether each of the additional logic check items meets the corresponding preset conditions;
[0123] If any of the additional logic checks does not meet the corresponding preset conditions, it is determined that the additional logic check has a detection anomaly.
[0124] Output additional logical checks and warning messages for detected anomalies.
[0125] In one embodiment, the inspection of the burial depth of drainage pipes and accessories includes the inspection of the burial depth of rainwater pipes in the community, the inspection of the burial depth of drainage wells, the inspection of the burial depth of concealed points, and the inspection of the burial depth of rainwater inlets;
[0126] The drainage professional field attribute checks include checks on the design service life and structural design safety level, pipe interface type, and number of connected pipes.
[0127] The comprehensive safety distance inspection of water supply and drainage pipes and their accessories includes the inspection of vertical clearance between water supply and drainage pipes, the inspection of horizontal clearance between water supply and drainage pipes, the inspection of septic tank spacing, the inspection of municipal rainwater well spacing, and the inspection of rainwater inlet spacing.
[0128] The inspection of the burial depth of drainage pipes and their accessories includes the following inspection methods:
[0129] Rainwater pipe burial depth inspection in residential areas: If the road name in the pipe section table is the name of the residential area or a road in the residential area, and the burial depth at the starting point or the ending point is less than 0.7m, a warning message will be issued.
[0130] Drainage well burial depth check: Combine the flow direction field to determine the inflow and outflow direction of each drainage well. If the burial depth value of the drainage well in the inflow direction is less than the burial depth value of the drainage well in the outflow direction, a warning message will be displayed.
[0131] Concealed point burial depth check: Compare the burial depth of the connecting pipe sections on both sides of the preset pipeline point (or detection point). If the burial depth is inconsistent, a warning message will be displayed.
[0132] Rainwater inlet burial depth inspection: Record the name of the accessory at the beginning or end of the pipe section table as rain grate. If the burial depth of the beginning or end is greater than 1m, a warning message will be issued.
[0133] The field attribute checks for drainage include the following methods:
[0134] Design service life and structural design safety level check: For drainage pipe sections with a diameter of 200mm or greater or a square ditch of 400x400mm or greater in the pipe section table, if the design service life field is less than 50 years or the structural design safety level is less than level two, a warning message will be issued.
[0135] Pipe joint type check: For drainage pipe sections with a seismic fortification intensity of 7 degrees or above in the pipe section table, if the pipe joint type field does not show a flexible joint, a warning message will be displayed.
[0136] Pipe connection count check: The pipe point of the access point is the inspection well. The number of pipe segments connected to the pipe point and the pipe diameter are counted in the pipe segment table. When the pipe diameter is greater than 300mm and the number of connected pipe segments is greater than 3, a warning message is issued.
[0137] The comprehensive inspection of the safety distance of water supply and drainage pipes and their accessories includes the following inspection methods:
[0138] Vertical clearance check of water supply and drainage pipes: Calculate the vertical clearance between each section of drainage pipe and the nearby water supply pipe. When the clearance between the outer wall and the pipe is less than or equal to 0.4m, a warning message will be displayed.
[0139] Horizontal clearance check of water supply and drainage pipes: Calculate the horizontal clearance between each section of drainage pipe and the nearby water supply pipe. When the diameter of the water supply pipe section is less than or equal to 200mm and the clearance between the outer walls is less than or equal to 1m, a warning message will be issued; when the diameter of the water supply pipe section is greater than 200mm and the clearance between the outer walls is less than or equal to 1.5m, a warning message will be issued.
[0140] Septic tank spacing check: When the drainage pipe point is a septic tank, calculate the plane distance between the coordinates of the septic tank point and the coordinates of the underground water intake structure pipe point or water storage tank pipe point. When this distance is less than 30m, a warning message will be issued.
[0141] Municipal storm drain well spacing inspection: If there are no inspection wells for municipal storm drain or combined sewer pipe points and their connecting pipe points, and the pipe diameter or cross-sectional dimension of the pipe section is greater than or equal to 200mm and less than or equal to 400mm, and the coordinate distance between the two pipe points is greater than 50m, a warning message will be issued; if the pipe diameter of the pipe section is greater than or equal to 500mm and less than or equal to 700mm, and the coordinate distance between the two pipe points is greater than 70m, a warning message will be issued; if the pipe diameter of the pipe section is greater than or equal to 800mm and less than or equal to 1000mm, and the coordinate distance between the two pipe points is greater than 90m, a warning message will be issued.
[0142] Rainwater inlet spacing check: For rainwater pipe points with the name of the accessory "rain grate", calculate the pipe section length between its coordinates and the coordinates of the connected pipe point. If the spacing is greater than 25m, a warning message will be displayed.
[0143] Step S160: The basic detection results and additional detection results of each drainage pipeline detection data are determined as a combined detection result.
[0144] Finally, a combined detection result is output, which includes the basic detection result and the additional detection result.
[0145] This application's embodiments focus on in-depth secondary mining of underground drainage pipeline detection data, exploring its inherent logical rules, and studying the content of refined inspection of drainage pipeline data to uncover more hidden errors. Based on data analysis, and taking the underground drainage pipeline detection database as the research object, this application improves and optimizes the inspection content of drainage professional pipeline data, and designs and implements refined inspection content for drainage pipelines. Through the improvement and refinement of the inspection content of the urban underground drainage pipeline detection database, the production efficiency and data quality of underground drainage pipeline detection projects are enhanced.
[0146] By inspecting the drainage pipeline detection database, we can minimize the limitations imposed by data accuracy on the in-depth mining and application of drainage pipeline data in the later stages. Based on this, the inspection can further assist in identifying other issues, such as the quality of drainage pipeline construction and whether it complies with pipeline engineering design specifications. Data analysis can also uncover potential hazards in water supply and drainage pipelines. Drainage pipeline detection data can be further applied to early warning systems for urban underground infrastructure safety and urban road safety. It can also be used to assess the effectiveness of sponge city construction based on pipeline conditions, while better serving the construction of urban underground municipal infrastructure.
[0147] This embodiment provides a logical inspection method for underground drainage pipeline detection databases, offering a solution for logical checks. It innovatively proposes multiple inspection items to achieve in-depth checks on underground drainage pipeline detection data, improving the quality and efficiency of results from urban underground infrastructure surveys, detailed underground pipeline surveys, and specialized underground pipeline detection projects. This reduces personnel and time costs, quickly and effectively controlling the quality of drainage pipeline detection data. Furthermore, the design and approach for in-depth checks on underground drainage pipeline detection databases can be widely applied to underground pipeline data acquisition and database construction, underground pipeline information management system platform construction, underground pipeline data processing system development, and the application of underground pipeline detection engineering supervision and quality inspection software, demonstrating broad applicability.
[0148] Example 2
[0149] Furthermore, embodiments of this disclosure provide a pipeline detection database logic detection device.
[0150] Specifically, such as Figure 3 As shown, the pipeline detection database logic detection device 300 includes:
[0151] The acquisition module 310 is used to acquire multiple drainage pipeline detection data from the pipeline detection database. The initial storage format of different drainage pipeline detection data is different.
[0152] The standardization module 320 is used to standardize the detection data of each drainage pipeline to obtain standardized data with a unified format.
[0153] The first selection module 330 is used to obtain the detection category of each of the standardized data and select the conventional logic check item corresponding to the detection category;
[0154] The second selection module 340 is used to select at least one of the following as an additional logical check item: drainage pipe and appurtenance burial depth check, drainage professional field attribute check, and water supply and drainage pipe and appurtenance safety distance comprehensive check.
[0155] The detection module 350 is used to perform basic class detection on the standardized data according to the conventional logic check items and output the basic detection results, and to perform additional class detection on the standardized data according to the additional logic check items and output the additional detection results.
[0156] The determination module 360 is used to determine the basic detection results and additional detection results of each drainage pipeline detection data into a combined detection result.
[0157] The standardization module 320 is also used for:
[0158] Obtain the data format, data structure, and data table fields of the detection data for each drainage pipeline;
[0159] Convert all the drainage pipeline detection data into an mdb format data table;
[0160] The data structure of the drainage pipeline detection data is divided into point structure, line structure and range structure;
[0161] The names of the data table fields for the drainage pipeline detection data are unified to preset names through field mapping.
[0162] The pipeline detection database logic detection device 300 provided in this embodiment can implement the pipeline detection database logic detection method provided in Embodiment 1. To avoid repetition, it will not be described again here.
[0163] The pipeline detection database logic detection device provided in this embodiment proposes a solution for logical inspection of drainage underground pipeline detection databases. It innovates multiple inspection contents to achieve in-depth inspection of drainage underground pipeline detection data, improving the quality and production efficiency of projects such as urban underground municipal infrastructure surveys, detailed underground pipeline surveys, and specialized underground pipeline detection. This reduces personnel and time costs, quickly and effectively controlling the quality of drainage pipeline detection data. Furthermore, the design and concept of in-depth inspection of drainage underground pipeline detection databases can be widely applied to underground pipeline data acquisition and database construction, underground pipeline information management system platform construction, underground pipeline data processing system development, and the application of underground pipeline detection engineering supervision and quality inspection software, demonstrating broad applicability.
[0164] Example 3
[0165] Furthermore, this disclosure provides an electronic device, including a memory and a processor, wherein the memory stores a computer program, and the computer program, when run on the processor, executes the pipeline detection database logic detection method provided in Embodiment 1.
[0166] The electronic device provided in this embodiment of the invention can implement the pipeline detection database logic detection method provided in Embodiment 1. To avoid repetition, it will not be described again here.
[0167] The electronic device provided in this embodiment proposes a solution for logical inspection of drainage underground pipeline detection databases. It innovates multiple inspection methods to achieve in-depth inspection of drainage underground pipeline detection data, improving the quality and efficiency of results from urban underground municipal infrastructure surveys, detailed underground pipeline surveys, and specialized underground pipeline detection projects. This reduces personnel and time costs, quickly and effectively controlling the quality of drainage pipeline detection data. Furthermore, the design and approach for in-depth inspection of drainage underground pipeline detection databases can be widely applied to underground pipeline data acquisition and database construction, underground pipeline information management system platform construction, underground pipeline data processing system development, and the application of underground pipeline detection engineering supervision and quality inspection software, demonstrating broad applicability.
[0168] Example 4
[0169] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the pipeline detection database logic detection method provided in Embodiment 1.
[0170] In this embodiment, the computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, etc.
[0171] The computer-readable storage medium provided in this embodiment can implement the pipeline detection database logical detection method provided in Embodiment 1. To avoid repetition, it will not be described again here.
[0172] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or terminal that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or terminal. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or terminal that includes that element.
[0173] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.
[0174] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.
Claims
1. A pipeline detection database logic detection method, characterized in that, The method includes: Obtain multiple drainage pipeline detection data from the pipeline detection database. The initial storage format of different drainage pipeline detection data is different. The detection data of each drainage pipeline are standardized to obtain standardized data with a unified format. Obtain the detection category of each standardized data and select the corresponding routine logic check item for the detection category; Select at least one of the following as an additional logical check item: inspection of the burial depth of drainage pipes and accessories, inspection of drainage professional field attributes, and comprehensive inspection of the safe distance of water supply and drainage pipes and accessories. The standardized data is subjected to basic class detection based on the conventional logic check items, and the basic detection results are output. Additionally, the standardized data is subjected to additional class detection based on the additional logic check items, and the additional detection results are output. The basic and additional detection results of each drainage pipeline detection data are determined as a combined detection result; The detection categories include municipal pipeline detection data and residential pipeline detection data, and the routine logic check items include municipal routine check items and residential routine check items; The acquisition of the detection categories for each of the standardized data, and the selection of the corresponding routine logic check items for the detection categories, includes: If the detection category is the municipal pipeline detection data, then select the municipal routine inspection item, which includes drainage slope inspection, drainage pipe diameter anomaly inspection, concealed point pipe diameter inspection, drainage well material inspection, rainwater drainage outlet exposure inspection, sewage characteristic attachment name inspection, and well body pipe material consistency inspection. If the detection category is the pipeline detection data of the community, then the routine inspection items of the community are selected, wherein the routine inspection items of the community include the inspection of the distance between drainage pipe inspection wells, the inspection of the distance between riser connection inspection wells, and the inspection of the distance between rainwater wells in the community.
2. The pipeline detection database logic detection method according to claim 1, characterized in that, The standardization process is performed on the detection data of each drainage pipeline to obtain standardized data with a unified format, including: Obtain the data format, data structure, and data table fields of the detection data for each drainage pipeline; Convert all the drainage pipeline detection data into an mdb format data table; The data structure of the drainage pipeline detection data is divided into point structure, line structure and range structure; The names of the data table fields for each drainage pipeline detection data are unified to preset names through field mapping.
3. The pipeline detection database logic detection method according to claim 1, characterized in that, The step of performing basic class detection on the standardized data based on the conventional logic check items and outputting the basic detection results includes: Determine whether each of the aforementioned conventional logic check items meets the corresponding preset conditions; The preset conditions corresponding to each of the conventional logic check items include: The preset condition for the drainage slope check is that the angle between the slope of the drainage pipe section and the horizontal plane is less than a preset angle. The preset condition for checking the abnormal drainage pipe diameter is that the drainage pipe diameter meets the first preset range. The preset conditions for the hidden point pipe diameter inspection are that the pipe diameters of the connecting pipe sections on both sides of the preset pipeline point or detection point are consistent, and the cross-sectional dimensions of the connecting pipe sections on both sides of the preset pipeline point or detection point are consistent. The preset condition for the material inspection of the drainage well is that if the pipe point is an inspection well, the inspection well meets the material standard. The preset condition for the rainwater drain outlet exposure inspection is that if the rainwater pipe point is the outlet, the obvious concealed point of the outlet is not a concealed point. The preset condition for checking the names of sewage feature attachments is that the sewage pipe feature or attachment name is not an outlet or a grate. The preset condition for the consistency check of the well body pipe material is that if the pipe point is the inspection well, the content of the well material field of the inspection well is the same as the content of the material field of the pipe section connected to the inspection well. The preset conditions corresponding to the inspection of the distance between the drainage pipe inspection wells are as follows: when the sewage pipe point is a sewage pipe point and the connecting pipe points of the sewage pipe point are all inspection wells, the pipe section diameter of the sewage pipe point meets the second preset range and the coordinate distance between the two pipe points meets the third preset range. The preset conditions corresponding to the riser connection inspection well distance inspection are as follows: if the sewage pipe point is a riser and the connecting pipe point of the sewage pipe point is an inspection well, it is determined that the pipe section diameter of the sewage pipe point meets the fourth preset range and the coordinate distance between the two pipe points meets the fifth preset range. The preset conditions for checking the spacing between rainwater wells in the community are as follows: if both the rainwater pipe point and the connecting pipe point of the rainwater pipe point are inspection wells, the pipe section diameter of the sewage pipe point is determined to be within the sixth preset range and the coordinate distance between the two pipe points is within the seventh preset range. Output routine logic checks and warning messages for detecting anomalies.
4. The pipeline detection database logic detection method according to claim 1, characterized in that, The inspection of the burial depth of drainage pipes and accessories includes the inspection of the burial depth of rainwater pipes in the community, the inspection of the burial depth of drainage wells, the inspection of the burial depth of concealed points, and the inspection of the burial depth of rainwater inlets. The drainage professional field attribute checks include checks on the design service life and structural design safety level, pipe interface type, and number of connected pipes. The comprehensive safety distance inspection of water supply and drainage pipes and their accessories includes the inspection of vertical clearance between water supply and drainage pipes, the inspection of horizontal clearance between water supply and drainage pipes, the inspection of septic tank spacing, the inspection of municipal rainwater well spacing, and the inspection of rainwater inlet spacing.
5. The pipeline detection database logic detection method according to claim 4, characterized in that, The step of performing additional class checks on the standardized data based on the additional logic check items and outputting additional detection results includes: Determine whether each of the additional logic check items meets the corresponding preset conditions; If any of the additional logic checks does not meet the corresponding preset conditions, it is determined that the additional logic check has a detection anomaly. Output additional logical checks and warning messages for detected anomalies.
6. A pipeline detection database logic detection device, characterized in that, The device includes: The acquisition module is used to acquire multiple drainage pipeline detection data from the pipeline detection database. The initial storage format of different drainage pipeline detection data is different. The standardization module is used to standardize the detection data of each drainage pipeline to obtain standardized data with a unified format. The first selection module is used to obtain the detection category of each standardized data and select the conventional logic check item corresponding to the detection category; The second selection module is used to select at least one of the following as additional logical check items: drainage pipe and appurtenance burial depth inspection, drainage professional field attribute inspection, and water supply and drainage pipe and appurtenance safety distance comprehensive inspection. The detection module is used to perform basic class detection on the standardized data according to the conventional logic check items and output the basic detection results, and to perform additional class detection on the standardized data according to the additional logic check items and output the additional detection results. The determination module is used to determine the basic detection results and additional detection results of each drainage pipeline detection data into a combined detection result; The detection categories include municipal pipeline detection data and residential pipeline detection data, and the routine logic check items include municipal routine check items and residential routine check items; The acquisition of the detection categories for each of the standardized data, and the selection of the corresponding routine logic check items for the detection categories, includes: If the detection category is the municipal pipeline detection data, then select the municipal routine inspection item, which includes drainage slope inspection, drainage pipe diameter anomaly inspection, concealed point pipe diameter inspection, drainage well material inspection, rainwater drainage outlet exposure inspection, sewage characteristic attachment name inspection, and well body pipe material consistency inspection. If the detection category is the pipeline detection data of the community, then the routine inspection items of the community are selected, wherein the routine inspection items of the community include the inspection of the distance between drainage pipe inspection wells, the inspection of the distance between riser connection inspection wells, and the inspection of the distance between rainwater wells in the community.
7. The pipeline detection database logic detection device according to claim 6, characterized in that, The standardization module is also used for: Obtain the data format, data structure, and data table fields of the detection data for each drainage pipeline; Convert all the drainage pipeline detection data into an mdb format data table; The data structure of the drainage pipeline detection data is divided into point structure, line structure and range structure; The names of the data table fields for the drainage pipeline detection data are unified to preset names through field mapping.
8. An electronic device, characterized in that, The system includes a memory and a processor, wherein the memory stores a computer program that executes the pipeline detection database logic detection method according to any one of claims 1 to 5 when the processor is running.
9. A computer-readable storage medium, characterized in that, It stores a computer program that, when run on a processor, executes the pipeline detection database logic detection method according to any one of claims 1 to 5.