A municipal sewer network data self-checking system

Abstract

The application discloses a kind of municipal drainage pipe network data self-checking systems, comprising: data acquisition module: for from pipe network field inclusion field data, field data is structured, and facility data is generated;Wherein field data includes element name, element type, element attribute, element relationship;Data self-checking module: for obtaining facility data from data acquisition module and carrying out data self-checking;Data self-checking module includes element checking unit and rule checking unit, element checking unit is used to judge whether facility data meets element basic requirement, if not, define facility data self-checking failure;If it is met, by rule checking unit, pipe network rule is judged, if not meet pipe network rule, define self-checking failure, otherwise define facility data self-checking success;Data storage module: for storing the facility data that has passed data self-checking.According to the above technical scheme, whether the pipe network data collected can be investigated effectively, and the smooth implementation of pipe network investigation project is guaranteed.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of municipal engineering, in particular to a municipal drainage pipe network data self-checking system. BACKGROUND

[0002] Municipal drainage pipe network investigation is an important part of municipal maintenance work, and its work content mainly includes collecting data such as pipe and inspection well material, size, elevation, flow direction, etc. through geophysical prospecting, collecting data through table filling or GIS system database, manually analyzing the collected results and drawing pipe network quality conclusions, and further proposing maintenance schemes. However, the current commonly used method has certain errors in the investigation results, including missing data association, data duplication, data error and other problems, which seriously affect the quality of data results and cannot truly reflect the pipe network situation, thereby increasing the difficulty of pipe network operation and management and affecting the decision-making of managers.

[0003] Therefore, a technical solution is needed to investigate whether the collected data is effective from the collected pipe network data, to ensure the smooth implementation of the pipe network investigation project and the quality of the data results, and to lay a data foundation for later operation and maintenance. SUMMARY

[0004] To achieve the above-mentioned purpose, the present application provides a municipal drainage pipe network data self-checking system, comprising:

[0005] A data collection module is used to collect field data from the pipe network site, structure the field data, and generate facility data; the field data includes element information, and the element information includes element name, element type, element attribute, and element relationship; the element type includes node facilities and pipe facilities; the node facilities include wells, house connection wells, drainage outlets, and rainwater outlets, and the pipe facilities include rain and sewage pipelines; the element attribute includes the x-coordinate, y-coordinate, z-coordinate, diameter, and buried depth of the node facilities, and the length of the pipe facilities; the element relationship refers to the connection relationship between the node facilities and the pipe facilities; the field data structuring refers to generating a unified identifier for the node facilities, generating an identifier for the pipe facilities using the identifier of the node facilities, and converting the element information into structured relational data;

[0006] The data self-checking module is configured to acquire facility data from the data acquisition module and perform data self-checking on the facility data. The node facility is represented as a point element, and the pipeline facility is represented as a line element. The spatial relationship between the point element and the line element constitutes a topological relationship. The data self-checking module includes an element checking unit and a rule checking unit. The element checking unit is configured to determine whether the facility data and the topological relationship meet element basic requirements. If not, the facility data is defined as self-checking failed. If yes, the rule checking unit is configured to determine whether the facility data meets pipeline rules corresponding to a facility type and a pipeline topological structure type according to the facility data and the topological structure. If not, the facility data is defined as self-checking failed. Otherwise, the facility data is defined as self-checking successful.

[0007] The element basic requirements are basic judgments for point, line and other shapes. The rules include:

[0008] The point element represents a node facility such as a manhole, a service connection well, a drainage outlet and a rainwater outlet. Different point elements are not overlapped.

[0009] The line element represents a rainwater and sewage pipeline. The end points of the line element are point elements. Different line elements are not intersected or internally contacted.

[0010] Each point element has an end point of a line element overlapped.

[0011] Each end point of the line element has a point element overlapped.

[0012] Further, the above rules are implemented through topological checking rules of a third-party system and self-defined algorithms. The self-defined algorithms include calculating the distance between two point elements, judging point overlap and point non-overlap of the diameter of the point element, and include:

[0013] The algorithm for judging point overlap is represented as:

[0014] The algorithm for judging point non-overlap is represented as:

[0015] Wherein, D is the distance between two points, d1 is the diameter of point 1, and d2 is the diameter of point 2.

[0016] And: Wherein, y1 is the Y coordinate of point 1, y2 is the Y coordinate of point 2, x1 is the X coordinate of point 1, and X2 is the X coordinate of point 2.

[0017] Furthermore, the rule checking unit includes a facility identification submodule; the facility identification submodule is used to identify the facility type corresponding to the facility data and match the facility identification code; the identification operation includes: extracting facility type definition rules, identifying the facility type to which the facility data belongs, and marking the facility type; identifying the topological relationship of facility data of the same facility type and marking the pipeline topology type; and matching the facility identification code according to the facility type mark and the pipeline topology type mark.

[0018] The facility types include: pipelines, wells, rainwater inlets, and outlets; the network topology types include: pipe segments, pipelines, and networks.

[0019] This includes determining whether facility data conforms to the network rules corresponding to the facility type and network topology, including pipe segment rule self-checking. The corresponding pipe segment rules include:

[0020] The slope limit self-check determines whether the slope is within a reasonable range compared to the average slope of the pipeline. The specific algorithm includes: calculating the slope of a specified pipeline segment using the coordinates and burial depth of the point elements corresponding to the endpoints of the pipeline segment; solving for the range of the average slope with the smallest discreteness in the pipeline based on the slope of each pipeline segment and the number of pipeline segments; calculating the standard deviation of the pipeline segment slope and the allowable range of the pipeline segment slope; and determining whether the slope of the specified pipeline segment is within the allowable range.

[0021] Self-inspection of minimum burial depth limit, that is, determining whether the minimum burial depth exceeds the minimum burial depth limit of the pipe section required by the specification.

[0022] Determining whether facility data conforms to the network rules corresponding to the facility type and network topology type also includes a pipeline rule self-check, the corresponding pipeline rules include:

[0023] Pipeline endpoint type self-check, that is, to determine whether the point element of the upstream starting endpoint of any pipeline is a household well or rainwater inlet, and the point element of the downstream terminal is a sewage treatment plant, drainage outlet or pumping station.

[0024] The pipeline's adjacent pipe segment angle self-check ensures that the included angle between adjacent pipe segments is not less than 90 degrees. The method for determining the included angle is as follows: The point element corresponding to the intermediate inspection well point of the adjacent pipe segment is set as the origin, i.e., O = (x0, y0, z0). The upstream and downstream pipe segments are then set as vectors. and if The included angle between adjacent pipe sections is between 0° and 90°. The included angle between adjacent pipe sections is between 90° and 180°, among which,

[0025] The flow direction self-checking in the pipeline is that the flow direction of the pipe sections in the same pipeline must be consistent and always from the starting point to the terminal point.

[0026] The height difference self-checking is that whether the bottom elevation of the starting point of the gravity pipeline is higher than the bottom elevation of the terminal point of the pipeline.

[0027] Further, the judgment of whether the facility data conforms to the pipe network rules corresponding to the facility type and the pipe network topology type also includes pipe network rule self-checking, and the corresponding pipe network rules include:

[0028] The node external number self-checking is that the point element is acquired, the number of line elements with the point element as the end point is acquired, and whether the data is greater than 4 is judged.

[0029] The special node external number self-checking is that the special node needs to be connected to an equal number of pipe sections.

[0030] The connection relationship self-checking is that only one line element is included between two point elements.

[0031] The facility type definition rule is a facility type library defined in the original database, and the data structure storage mode is a data table; in the data table, the preset data drainage facility type and the drainage facility topology structure type are provided.

[0032] Further, the data self-checking system also includes an information feedback module: used for acquiring problem description data of pipe network system data which fails in self-checking from the data self-checking module, performing information feedback, and the information feedback includes: analyzing the problem description data, extracting data error coordinate points and data error names, and supporting display of the problem description information in the interface of the terminal which displays the topology structure.

[0033] According to the present application, the scheme of pipe network data self-checking processing can be customized according to the data characteristics of the pipe network facilities, the effective rules of the pipe network facilities and the technical implementation of the rules are realized through the logic between the system modules, finally the problems of the drainage pipe network data are accurately, comprehensively and intuitively indicated to the user, the whole process flow loop is formed, and the executable degree and the professionalism of the data maintenance are ensured. BRIEF DESCRIPTION OF DRAWINGS

[0034] Figure 1 is a municipal drainage pipe network data self-checking system function structure schematic diagram provided according to an embodiment of the present application;

[0035] Figure 2 is a municipal drainage pipe network data flowchart provided according to an embodiment of the present application;

[0036] Figure 3 is a municipal drainage pipe network data self-checking system logic flowchart provided according to an embodiment of the present application;

[0037] Figure 4It is a municipal drainage pipe network data self-checking system overall structure schematic diagram provided according to the embodiment of the application. DETAILED DESCRIPTION

[0038] The application establishes a municipal drainage pipe network data self-checking system, customizes the pipe network data self-checking processing scheme according to the data characteristics of pipe network facilities, formulates the processing flow from the data form collected on site to the topological structure and data relationship of application analysis, and realizes the effective rule definition and rule confirmation of pipe network facilities through the logic between system modules, finally accurately, comprehensively and intuitively indicates the problems of drainage pipe network data to the user, forms a whole process flow closed loop, and ensures the executable degree and professionalism of data maintenance.

[0039] The specific implementation of the application will be described in detail below with reference to the accompanying drawings.

[0040] The overall system structure of the municipal drainage pipe network data self-checking system provided by the application is shown in Figure 4 On the hardware, at least a terminal part and a server part are included, the terminal part is a mobile device with GPS positioning, input device, display screen, can be positioned and connected to the Internet, such as mobile phone, tablet computer and the like, the server part mainly includes an application server, a data server and a third party server, the third party server is a GIS server for publishing map service, the application server can provide application service to the mobile device, receive and process mobile device data, and send data to the terminal part for data display, the data server can store data at each stage, on the software, the client application program of the pipe network data self-checking system and the application service of the server part are deployed, and the complete functions of information collection, data checking and analysis, information feedback and data storage are realized.

[0041] The function implementation structure of the pipe network data self-checking system is shown in Figure 1 The pipe network data self-checking system includes a P100 data collection module, a P110 data self-checking module, a P130 information feedback module and a P120 data storage module, wherein the P110 data self-checking module includes a P111 element checking unit and a P112 rule checking unit, which are used to realize data self-checking of different data and different rules, and the specific description is as follows:

[0042] P100: data collection module: used for collecting field data from pipe network field, structuring field data, and generating facility data;

[0043] The field data collected from the pipe network field mainly includes element information, which includes element name, element type, element attribute and element relationship;

[0044] The element types include node facilities and pipeline facilities: the node facilities include facilities such as wells, access wells, drainage outlets, rainwater outlets, pumping stations, sewage plants and the like involved in the municipal drainage network, and the pipeline facilities refer to pipelines connecting the node facilities, including rainwater and sewage pipelines and the like.

[0045] The element attributes refer to characteristics and characteristic values obtained by positioning, measuring and judging the node facilities and the pipeline facilities by the staff through the mobile device, including x coordinates, y coordinates, z coordinates, diameters, materials and burial depths of various node facilities, lengths and materials of pipeline facilities and the like, for example, x coordinate values, y coordinate values and z coordinate values of a certain access well in a simulation coordinate system.

[0046] The element relationship refers to the mutual connection relationship between the node facilities and the pipeline facilities due to the pipeline facilities laid between two node facilities, for example, a certain access well is connected with a certain drainage outlet through a rainwater and sewage pipeline.

[0047] The field data structuring refers to generating a unified identification for the node facilities, generating an identification for the pipeline facilities by using the identification of the node facilities, the identification can be used to correspond to specific element information one by one, and the element information including the attributes, characteristics and relationships of the elements is abstracted into structured relational data. Figure 2 As shown in the above formula, in step S200, the field data is input and positioned by the staff using the mobile device, vector points and lines are drawn, attribute tables are filled in the line, and the field data is uploaded to the server in real time, and the data is output as structured facility data in step S210 through the data acquisition module, for subsequent calculation and analysis in the system.

[0048] It should be noted that, in actual application, the pipeline facilities have directionality, for example: a certain access well is identified as A, a certain drainage outlet is identified as B, and the rainwater and sewage pipeline from A to B is a vector data with direction, and is identified as AB.

[0049] The P110 data self-checking module is used for acquiring facility data from the data acquisition module, generating topological relationships and performing data self-checking of the facility data.

[0050] In the application, the node facilities are represented as point elements, and the pipeline facilities are represented as line elements, and the spatial relationships of different point elements and line elements constitute topological relationships.

[0051] Based on the layout specification of the municipal drainage network, firstly, the basic requirements of the node facilities and the pipeline facilities are pre-self-checked, and the data not meeting the basic conditions is not required to be judged subsequently, so as to reduce invalid data calculation and improve the self-checking efficiency of the system.

[0052] The data self-checking module includes a P111 element checking unit and a P112 rule checking unit.

[0053] The P111 element checking unit is used to perform a pre-self-check to determine whether the facility data and its topological relationship meet the element basic requirements, and if not, define the facility data self-check as a failure.

[0054] The element basic requirements mainly perform basic judgment on points, lines and other shapes, wherein a node facility corresponds to a point element, and a pipe facility corresponds to a line element, and a specific judgment process is shown in Figure 3

[0055] Step S310: Element data preparation, first identify the element types in the facility data, and extract relevant information: including the identification, x coordinate value, y coordinate value, z coordinate value of each facility, the diameter of the node facility, the length of the pipe facility, etc.

[0056] Step S311: Determine the numerical rules and topological rules of the element data, and determine whether they meet the element basic requirements, and the determination method includes GIS topological checking rules and self-defined algorithm calculation.

[0057] The rules of the element basic requirements include:

[0058] 1) The point element represents a node facility such as a manhole, a service connection well, a drainage outlet, a rainwater outlet, etc., and different point elements are not overlapped;

[0059] 2) The line element represents a rain and sewage pipeline, and the end points of the line element are point elements; different line elements are not intersected or internally contacted;

[0060] 3) Each point element has an end point of the line element overlapped;

[0061] 4) Each end point of the line element has a point element overlapped.

[0062] These rules can be realized by calculating the distance between two point elements and the diameter of the point element.

[0063] For example, the point elements include A (1, 5, 1), B (2, 3, 1), C (5, 2, 1) and D (4, 4, 1), and the diameters are 1, 1 and 1 respectively, and the line elements include AB, AC and CE.

[0064] In the present application, the relationship between the elements is determined by the coordinate values of the point elements:

[0065] The algorithm for point overlap is expressed as:

[0066] The algorithm for judging that the points are not overlapped is expressed as:

[0067] Wherein, D is the distance between two points, d1 is the diameter of point 1, and d2 is the diameter of point 2.

[0068] And: ​Wherein, y1 is the Y coordinate of point 1, y2 is the Y coordinate of point 2, x1 is the X coordinate of point 1, and x2 is the X coordinate of point 2.

[0069] Through the above calculation, it can be calculated that the point element D does not overlap with the end point of the line element, which does not meet the rule 3); the line element AE includes the end-to-end and does not overlap with the point element, which does not meet the rule 4), the two places do not meet the requirements of the element checking unit, the judgment result is generated problem description data, encoded mark, and the problem description data and the code are sent to the information feedback module (such as Figure 3 in step S330).

[0070] The remaining facility data and topological relationship data that meet the basic requirements of the elements can enter the rule checking unit (such as Figure 2 in step S220).

[0071] On the other hand, for the rules of non-intersection or internal contact between different lines, it can be judged by the topological checking rules of the third party system, such as GIS system.

[0072] P112 rule checking unit: judging whether the facility data meets the pipe network rule of the facility type and the pipe network topological structure type, if not, defining the facility data self-checking failure, otherwise defining the facility data self-checking success;

[0073] In the rule checking unit, different pipe network rules are determined according to different facility types and pipe network topological structure types, therefore, before the rule checking, the facility identification submodule is used to identify the facility type and the pipe network topological structure type corresponding to the facility data:

[0074] The rule checking unit includes P113 facility identification submodule, when the type identification is realized, the operation steps include: extracting the facility type definition rule, identifying the facility type to which the facility data belongs, marking the facility type; identifying the topological relationship of the facility type data, marking the pipe network topological structure type; according to the facility type mark and the pipe network topological structure type mark, matching the facility identification code, which is used for the rule checking unit to refer to the corresponding algorithm for data checking.

[0075] The facility type definition rule is the facility type library defined in the original database, and the data structure storage mode is data table; in the data table, the data drainage facility type and the drainage facility topological structure type are preset, which specifically includes the definition of drainage facility type: pipe type, well type, rainwater inlet type and outlet type; the pipe network topological structure type is also predefined, including: single line segment (pipe segment), multi-segment line (pipe line), network structure (pipe network).

[0076] Corresponding to the preset defined facility type library, the facility types of which facility data can be recognized in the facility recognition submodule include: pipeline type, well type, rainwater inlet type, and drain outlet type; and the topological structure types of the pipe network include: pipe section, pipeline, and pipe network, wherein one or more pipe sections constitute a pipeline, and one or more pipelines constitute a pipe network.

[0077] The facility recognition code in the application is a unique identifier based on the above facility types and the above topological structure types, which can indicate the topological structure type, facility type, and element information to which the facility belongs, for calculation and analysis of the self-checking system.

[0078] It should be noted that the self-checking operation performed in the data self-checking module of the application has a hierarchical definition. The element checking is directed to point elements and line elements, and its rules are relatively independent and the calculation process is relatively simple. The rule checking needs to comprehensively consider the relationship of all point elements and line elements, and the calculation amount is relatively large and the rules are relatively complex. Therefore, after confirming that the element checking is passed, the next step of rule checking is performed, so that the data of the facilities participating in the rule checking all meet the basic requirements, thereby effectively avoiding invalid and resource-wasting data operations.

[0079] The step of performing data self-checking by the rule checking unit includes:

[0080] 1) Recognizing the facility recognition code and extracting the related values of each element in the facility data corresponding to the facility recognition code;

[0081] 2) Judging whether the facility type corresponding to the facility recognition code, the related values of each element, and the topological relationship meet the pipe network rules.

[0082] Corresponding to the topological structure type of the pipe network, the pipe network rules include three parts:

[0083] 1. Pipe section rule self-checking:

[0084] The pipe section is composed of two point elements and a line element between the two point elements;

[0085] The pipe section rule mainly includes:

[0086] 1) Slope limit value self-checking, i.e., the slope is kept within a reasonable range compared to the average slope of the corresponding pipe section, and the specific algorithm is as follows:

[0087] Step a: Calculate the slope of the specified pipe section through the coordinates and burial depth of the point elements corresponding to the endpoints of the pipe section: Wherein, i is the pipe section slope, h is the height difference between the starting point and the ending point of the pipe section, and l is the horizontal projection length of the pipe section,

[0088] Wherein: y1 is the starting point Y coordinate, y2 is the ending point Y coordinate, x1 is the starting point X coordinate, and x2 is the ending point X coordinate,

[0089] And: h = H2 - H1, H1 is the starting depth, H2 is the end depth;

[0090] Step b: according to the slope of each pipe section in the pipeline, the number of pipe sections, solve the discrete minimum slope average value range in the pipeline: Where μ is the average value of the slope of the pipe section, X i is the slope of each pipe section of the same pipeline, N is the number of pipe sections of the same pipeline;

[0091] Step c: calculate the standard deviation of the slope of the pipe section: Where σ is the standard deviation of the slope of the pipe section, μ is the average value of the slope of the pipe section, X i is the slope of each pipe section of the same pipeline, N is the number of pipe sections of the same pipeline;

[0092] Step d: determine the allowable range of the slope of the pipe section: I = μ ± 3σ, where I is the allowable range of the slope of the pipe section;

[0093] Determine whether the slope of the pipe section is within the allowable range, when: The slope limit value does not meet the pipe section rule, and the problem description data is "pipe section slope anomaly, please check the pipe section end depth", record the problem description data and code mark, and send the problem description data and code to the information feedback module;

[0094] 2) Minimum depth limit self-check, numerical determination method as follows:

[0095] Step a: determine the minimum depth of the pipe section: H1 < H2, H min <H1, where H1 is the starting depth, H2 is the end depth, H min is the minimum depth of the pipe section;

[0096] Step b: determine whether the minimum depth is over limit: H min ≤ H lim , where H lim is the minimum depth limit value required by the specification;

[0097] When the pipe section does not meet the formula of step b, the system determines that the self-check fails, and the problem description data is "pipe section depth anomaly, please check the minimum depth of the pipe section";

[0098] 2, pipeline rule self-check, including:

[0099] 1) Pipeline endpoint type self-check, that is, determine whether the point element of the upstream starting endpoint on any pipeline is a household well, a rainwater inlet, and the downstream terminal endpoint element is a sewage plant, a drainage outlet, a pump station;

[0100] This rule is determined by topology rule plus field, including the following steps:

[0101] Step a: find the connected pipeline with the connectivity rule and the flow direction consistency rule;

[0102] The connectivity rule is used to judge the end points of the pipeline, and the flow direction consistency rule is used to judge the start point and the end point in the end points of the pipeline;

[0103] Step b: obtain all line elements in the connected pipeline;

[0104] Step c: generate a sequence table for all line elements according to the end points, obtain the identification of the start point element of the line element as the start point identification, and the identification of the end point element of the last line element as the end point identification;

[0105] Step d: extract the facility type corresponding to the start point identification and the end point identification from the facility data;

[0106] Step e: judge whether the facility corresponding to the start point identification is a house entrance well or a rainwater inlet, and whether the facility corresponding to the end point identification is a sewage plant, a drainage outlet or a pump station. If not, the system determines that the self-check fails, and the problem description data is "abnormality of pipeline end point accessory, please check";

[0107] 2) Adjacent pipe segment angle self-checking, i.e. judging that the adjacent pipe segment angle of any pipeline cannot be less than 90 degrees;

[0108] Taking the intermediate inspection well point of the adjacent pipe segment as the origin O=(x0, y0, z0), the upstream pipe segment and the downstream pipe segment are respectively set as vectors and

[0109] Then:

[0110] Then the adjacent pipe segment angle is between 0° and 90°, the system determines that the self-check fails, and the problem description data is "pipe segment angle less than 90°, please check";

[0111] The adjacent pipe segment angle is between 90° and 180°, which is a normal case;

[0112] The intermediate inspection well point is: the point element corresponding to the common end point of the adjacent pipe segments;

[0113] 3) Pipeline flow direction self-checking, i.e. judging that the flow direction of the pipe segment in the same pipeline must be consistent and always from the start point to the end point;

[0114] 4) Height difference self-checking, i.e. judging whether the pipe bottom elevation of the start point of the gravity pipeline is higher than the pipe bottom elevation of the end point of the pipeline.

[0115] 3. Network rule self-checking can be realized by data statistical query operation: including:

[0116] 1) Node external number self-check, that is, get the point element, get the number of line elements with the point element as the endpoint as the node external number, and determine whether the data is greater than 4, so as to realize the rule judgment of whether the number of pipes connected to any node is greater than 4.

[0117] 2) Self-check of the number of external connections of special nodes: If the facility corresponding to the point element is a tee or a cross, then the point element is a special node. Obtain the number of external connections of the special node. When the node is a tee, the number of external connections should be 3. When the node is a cross, the number of external connections should be 4. That is, the special node needs to be connected to an equal number of pipe segments, and the flow direction of the connected pipe segment should have at least one outflow point.

[0118] 3) Connection relationship self-check: Determine whether there is a unique connection relationship between any two point elements in the pipeline network topology, that is, the two point elements are connected by only one line element.

[0119] 4) Self-inspection of mixed pipe network connections, that is, determining whether sewage pipe networks and rainwater pipe networks can be mixed based on whether they are combined systems.

[0120] If the self-check fails during the rule self-check process described above, the system will encode and mark the problem description data and send it to the information feedback module.

[0121] P130: Information Feedback Module: Used to obtain problem description data of pipeline system data that failed self-test from the data self-test module, and perform information feedback. For example... Figure 3 As shown, in step S311, when determining whether the basic requirements of the elements are met, the information of self-test failure is sent to step S330, the information feedback step. Similarly, in step S321, when determining whether the network rules are met, the information of self-test failure is also sent to step S330, the information feedback step. In this invention, the information feedback module centrally processes all information of self-test failure, including problem description data, data error coordinates, data error names, etc. The information feedback module configures codes for various problem description data. The data self-test module only needs to send the error code and specific facility data to the information feedback module for the scenario in which the error occurs. The information feedback module parses the error code, extracts the problem description data, data error coordinates, and data error names, and supports displaying the problem description information in the interface of the terminal displaying the topology structure, displaying the indication of self-test failure at the corresponding coordinate position, or displaying the problem description in text form in the prompt box or bubble box of the corresponding symbol.

[0122] Furthermore, the information feedback module also supports data verification, providing a data rewriting function within the terminal. Users can verify and troubleshoot data based on the problem type displayed by the information feedback module, and rewrite the data, preventing duplicate data after rewriting. Figure 3In step S300 to S321, after the self-checking is successful, the data is stored in the data storage module.

[0123] P120: data storage module: used for storing the facility data that has passed the data self-checking, and supporting displaying the self-checking result on the terminal, and completing the pipe network data self-checking.

[0124] The application establishes a pipe network data self-checking system framework, determines the core function module, defines the logic architecture between the modules, and supports realizing the data self-checking of the physical facilities from the physical layer to the abstract data layer; the data self-checking method provided by the application realizes the discovery of data errors, and at the same time, the level of the data self-checking is also designed, so that the next complex calculation is only performed under the condition of meeting certain rules, and the invalid and resource-wasting data operation is effectively avoided; in the business, the application adopts the self-defined facility classification and coding method, digitizes the drainage specification, can realize various and complex rule confirmations by measuring the basic attribute values of each facility, and can more accurately, comprehensively and intuitively indicate the problems of the pipe network data to the user, guarantees the smooth implementation of the pipe network checking project and the quality of the data achievement, lays a data foundation for the later operation and maintenance, at the same time, the workflow of the professional personnel and the data self-checking system is combined, a whole-process manual and system process closed loop is formed, and the executable degree and the professionalism of the data maintenance are ensured.

[0125] The above only discloses several specific embodiments of the application, but the application is not limited to this, and any changes that can be thought of by those skilled in the art should fall within the protection scope of the application.

Claims

1. A self-inspection system for municipal drainage pipe network data, characterized in that, include: Data acquisition module: used to collect field data from the pipeline network, structure the field data, and generate facility data; The on-site data includes element information, which includes element name, element type, element attributes, and element relationships. The element types include node facilities and pipeline facilities. Node facilities include wells, service wells, drainage outlets, and storm drains; pipeline facilities include storm and sewage pipelines. The element attributes include the x-coordinate, y-coordinate, z-coordinate, diameter, and burial depth of the node facilities, and the length of the pipeline facilities. The element relationships refer to the connection relationships between the node facilities and the pipeline facilities. The on-site data structuring refers to generating a unified identifier for each node facility, using the identifiers of the node facilities to generate identifiers for the pipeline facilities, and converting the element information into structured relational data. Data self-checking module: Used to acquire facility data from the data acquisition module and perform data self-checking on the facility data; wherein, the node facilities are represented as point elements, the pipeline facilities are represented as line elements, and the spatial relationship between the point elements and line elements constitutes a topological relationship; the data self-checking module includes an element checking unit and a rule checking unit. The element checking unit is used to determine whether the facility data and the topological relationship meet the basic requirements of elements. If they do not meet the requirements, the facility data self-check is defined as failing; if they do meet the requirements, the rule checking unit summarizes the facility type and pipeline topology type based on the facility data and topology structure, and determines whether the facility data conforms to the pipeline rules corresponding to the facility type and pipeline topology structure type. If the data does not conform to the pipeline rules, the facility data self-check is defined as failing; otherwise, the facility data self-check is defined as succeeding. Data storage module: Used to store facility data that has passed the data self-test; The basic requirements for these elements are fundamental judgments on the shape of points and lines, and the rules include: Point elements represent node facilities including: inspection wells, service wells, drainage outlets, and rainwater inlets. Different point elements do not overlap. Line features represent stormwater and sewage pipelines, and the endpoints of line features are point features; different line features do not intersect or have internal contact. Each of the point features overlaps with the endpoints of line features; The endpoints of each line feature overlap with some other features; The rules are implemented through the topology verification rules and custom algorithms of a third-party GIS system. The custom algorithm includes calculating the distance between two point features and the diameter of the point features to determine whether points overlap or not. The algorithm for determining point overlap is expressed as follows: , The algorithm for determining non-overlapping points is expressed as follows: , Where D is the distance between the two points, d1 is the diameter of point 1, and d2 is the diameter of point 2; and: , where y1 is the Y coordinate of point 1, y2 is the Y coordinate of point 2, x1 is the X coordinate of point 1, and x2 is the X coordinate of point 2.

2. The data self-testing system according to claim 1, characterized in that, The rule checking unit includes a facility identification submodule; The facility identification submodule is used to identify the facility type corresponding to the facility data and match the facility identification code. The identification operation includes: extracting facility type definition rules, identifying the facility type to which the facility data belongs, and marking the facility type; identifying the topological relationship of facility data of the same facility type and marking the pipeline topology structure type; and matching the facility identification code according to the facility type mark and the pipeline topology structure type mark.

3. The data self-testing system according to claim 1, characterized in that, The facility types include: pipelines, wells, rainwater inlets, and drainage outlets; The pipeline network topology types include: pipe segments, pipelines, and pipeline networks; among them, multiple related pipe segments constitute a pipeline, and multiple related pipelines constitute a pipeline network.

4. The data self-testing system according to claim 3, characterized in that, The step of determining whether the facility data conforms to the pipeline rules corresponding to the facility type and pipeline topology type includes a pipeline segment rule self-check, wherein the pipeline segment rules include: The slope limit self-check determines whether the slope is within a reasonable range compared to the average slope of the pipeline. The specific algorithm includes: calculating the slope of a specified pipeline segment using the coordinates and burial depth of the point elements corresponding to the endpoints of the pipeline segment; solving for the range of the smallest discrete average slope in the pipeline based on the slope of each pipeline segment and the number of pipeline segments; calculating the standard deviation of the pipeline segment slope and the allowable range of the pipeline segment slope; and determining whether the slope of the pipeline segment is within the allowable range. Self-inspection of minimum burial depth limit, that is, determining whether the minimum burial depth exceeds the minimum burial depth limit of the pipe section required by the specification.

5. The data self-testing system according to claim 3, characterized in that, The determination of whether the facility data conforms to the pipeline rules corresponding to the facility type and pipeline topology type also includes pipeline rule self-checking, wherein the pipeline rules include: Pipeline endpoint type self-check, that is, to determine whether the point element of the upstream starting endpoint of any pipeline is a household well or rainwater inlet, and the point element of the downstream terminal is a sewage treatment plant, drainage outlet or pumping station. The self-check of the included angle between adjacent pipe segments of a pipeline, that is, to determine that the included angle between adjacent pipe segments of any pipeline cannot be less than 90 degrees, the method for determining the included angle between adjacent pipe segments is: setting the point element corresponding to the intermediate inspection well point of the adjacent pipe segment as the origin, i.e. Set the upstream and downstream pipe segments as vectors respectively. and ,if If the included angle between adjacent pipe sections is between 0° and 90°, The included angle between adjacent pipe sections is between 90° and 180°, among which, ; The pipeline flow direction self-check determines that within the same pipeline, the flow direction of each section must be consistent and always flow from the starting point to the ending point. Height difference self-check, that is, to determine whether the bottom elevation of the starting point of the gravity pipeline is higher than the bottom elevation of the ending point of the pipeline.

6. The data self-testing system according to claim 3, characterized in that, The determination of whether the facility data conforms to the pipeline rules corresponding to the facility type and pipeline topology type also includes pipeline rule self-checking, wherein the pipeline rules include: The node external number self-check is to obtain the number of line elements with the point element as the endpoint, and determine whether the data is greater than 4. Self-check of the number of external connections at special nodes, meaning that special nodes must be connected to an equal number of pipe segments; The connection relationship self-check means that there is only one line feature between two point features.

7. The data self-testing system according to claim 2, characterized in that, The facility type definition rules are a facility type library defined in the form of an original database, and its data structure is stored in a data table; the data table is used to preset the drainage facility type and drainage facility topology type.

8. The data self-testing system according to claim 1, characterized in that, It also includes an information feedback module: used to obtain problem description data of pipeline system data that failed self-test from the data self-test module, and perform information feedback. The information feedback includes: parsing the problem description data, extracting the data error coordinates and data error names, and supporting the display of problem description information in the interface of the terminal displaying the topology structure.

Images