Underground pipeline management system

Abstract

This invention relates to an underground pipeline management system, belonging to the field of pipeline management technology, and solves the problem of time-consuming and labor-intensive manual calibration and updating of pipeline data in existing technologies. The management system includes: a data acquisition unit for acquiring newly added inflection points and cross points; a data storage unit for storing original pipeline data and updated pipeline data; a data processing unit for updating the original pipeline data to obtain updated pipeline data; and a data comparison unit for obtaining newly added pipeline data based on the original pipeline data and the updated pipeline data. This achieves automatic calibration and update management of pipeline data.

Description

Technical Field

[0001] This invention relates to the field of pipeline management technology, and more particularly to an underground pipeline management system. Background Technology

[0002] Urban underground pipelines are a crucial component of urban municipal infrastructure. Their construction is a vital foundation for the safe and orderly operation of cities and an important aspect of high-quality urban development. Urban underground pipelines mainly include water supply, rainwater, sewage, and gas lines, as well as ancillary facilities. Pipeline data is the basis for pipeline analysis and visualization applications.

[0003] Urban underground pipe networks can be abstracted as a "pipeline point-pipeline segment" mathematical model, and existing technologies mainly adopt a "two-point-one-line" data structure. Pipeline vector data consists of lines with pipeline segment attributes and coordinate information, and node data with pipeline point attributes and coordinate information. For the two-dimensional vector data of urban underground pipelines, there are cases where key inflection points are not marked, that is, when dividing pipeline segments, multiple continuous directed lines are sometimes divided into one pipeline segment; at the same time, there are cases where key nodes at crossing points are not marked.

[0004] In existing technologies, to address the issue of unmarked nodes in the aforementioned pipeline data, unmarked points are typically ignored, or manual calibration is performed line by line. Ignoring certain key nodes directly inevitably affects modeling effectiveness and analysis results, while manual calibration is time-consuming, labor-intensive, and inefficient. Furthermore, using a new set of data is equivalent to starting everything anew, thus manual calibration line by line lacks scalability. Summary of the Invention

[0005] Based on the above analysis, the present invention aims to provide an underground pipeline management system to solve the problem of time-consuming and labor-intensive manual calibration and updating of pipeline data in the prior art.

[0006] This invention provides an underground pipeline management system, which includes:

[0007] The data acquisition unit is used to acquire newly added vertices and cross points;

[0008] The data storage unit is used to store the original pipeline data and the updated pipeline data; the pipeline data includes pipeline segment vector data and pipeline point vector data.

[0009] The data processing unit is used to re-divide the pipeline segments in the original pipeline segment vector data using newly added inflection points and cross points, and renumber all the divided pipeline segments to obtain first line vector data; based on the first line vector data, it generates data corresponding to the two endpoints of each pipeline segment, i.e., second point vector data; it numbers the pipeline points in the first line vector data according to the original pipeline point vector data to obtain third point vector data; and it determines the start and end directions corresponding to each pipeline segment in the second point vector data according to the third point vector data to obtain the updated pipeline data.

[0010] The data comparison unit is used to obtain new pipeline data based on the original pipeline data and the updated pipeline data.

[0011] Based on further improvements to the above system, the management system also includes:

[0012] A visualization platform is used to display the newly added pipeline data for users to view; it is also used to receive pipeline query information from users and send the pipeline query information to the data query unit; it is also used to receive pipeline data sent by the data query unit and display it.

[0013] The data query unit is used to search for the corresponding pipeline data in the data storage unit based on the pipeline query information and send it to the visualization platform for display.

[0014] Based on further improvements to the above system, the management system also includes:

[0015] The data editing unit is used to delete or modify the corresponding pipeline data in the data storage unit according to the deletion or modification instructions sent by the visualization platform.

[0016] Based on further improvements to the above system, the re-division of pipeline segments in the original pipeline segment vector data using newly added inflection points and cross points includes:

[0017] Using the crossing point as the dividing point, the original pipeline segment vector data containing the crossing point is divided into pipeline segments;

[0018] Using the inflection point as the dividing point, the pipeline segments in the original pipeline segment vector data that have inflection points are divided;

[0019] Assign the line attribute values ​​of each pipeline segment before division to each pipeline segment after division; the line attribute values ​​include the start number and the end number.

[0020] Based on a further improvement to the above system, the step of assigning the line attribute values ​​of each pipeline segment before division to each pipeline segment after division includes:

[0021] If a pipeline segment is not divided after partitioning, its line attribute value remains unchanged;

[0022] If a pipeline segment is divided into multiple pipeline segments after partitioning, the line attribute values ​​of the pipeline segment before partitioning are assigned to the multiple pipeline segments obtained after partitioning.

[0023] Based on a further improvement to the above system, the step of numbering the pipeline points in the first line vector data according to the original pipeline point vector data to obtain the third point vector data includes:

[0024] Based on the first line vector data, data of all pipeline points in the first line vector data are generated using network analysis tools to obtain the first point vector data;

[0025] Based on the original pipeline point vector data, the first point vector data is numbered to obtain the third point vector data.

[0026] Based on a further improvement to the above system, the step of numbering the first point vector data and obtaining the third point vector data based on the original pipeline point vector data includes:

[0027] In the first point vector data, find the pipeline points whose position coordinates are the same as those in the original pipeline point vector data, and use them as old pipeline points. Assign the point attribute values ​​of each point in the original pipeline point vector data to the corresponding old pipeline points. The point attribute values ​​include the geophysical point number.

[0028] The pipeline points other than the old pipeline points in the first point vector data are taken as new pipeline points, and the geophysical point numbers of the new pipeline points are assigned to obtain the third point vector data.

[0029] Based on further improvements to the above system, the step of determining the start and end directions corresponding to each pipeline segment in the second point vector data according to the third point vector data to obtain the updated pipeline data includes:

[0030] Find the pipeline points in the second point vector data whose position coordinates are the same as those in the third point vector data, and map the point attribute values ​​of the pipeline points with the same position coordinates in the third point vector data to the corresponding pipeline points in the second point vector data to obtain the geophysical point numbers of each mapped pipeline point.

[0031] Based on the start point number and end point number of each pipeline segment in the second point vector data before mapping and the geophysical point numbers of the two endpoints of the corresponding pipeline segments after mapping, the final start point number and end point number of each pipeline segment in the second point vector data are determined, and the pipeline segment number and its start point number and end point number of each pipeline segment are obtained. After further processing, they are used as the pipeline segment vector data in the updated pipeline data.

[0032] The third point vector data is used as the pipeline point vector data in the updated pipeline data.

[0033] Based on further improvements to the above system, the step of determining the final start-point and end-point numbers corresponding to each pipeline segment in the second point vector data according to the start-point and end-point numbers of each pipeline segment in the second point vector data before mapping and the geophysical point numbers of the two endpoints of the corresponding pipeline segments after mapping includes:

[0034] If E_Origin[i]=Point[i]_1 and S_Origin[i]=Point[i]_2, then End_Point[i]=Point[i]_1 and Start_Point[i]=Point[i]_2;

[0035] If E_Origin[i]=Point[i]_2 and S_Origin[i]=Point[i]_1, then End_Point[i]=Point[i]_2 and Start_Point[i]=Point[i]_1;

[0036] Where E_Origin[i] represents the end point number of the i-th pipeline segment before mapping, and S_Origin[i] represents the start point number of the i-th pipeline segment before mapping; Point[i]_1 represents the geophysical point number of one end point of the i-th pipeline segment after mapping, and Point[i]_2 represents the geophysical point number of the other end point of the i-th pipeline segment after mapping; End_Point[i] represents the final end point number of the i-th pipeline segment, and Strart_Point[i] represents the final start point number of the i-th pipeline segment.

[0037] Based on further improvements to the above system, the step of determining the final start-point and end-point numbers corresponding to each pipeline segment in the second point vector data according to the start-point and end-point numbers of each pipeline segment in the second point vector data before mapping and the geophysical point numbers of the two endpoints of the corresponding pipeline segments after mapping further includes:

[0038] If E_Origin[i]=Point[i]_1 and S_Origin[i]≠Point[i]_2, then End_Point[i]=Point[i]_1 and Start_Point[i]=Point[i]_2;

[0039] If E_Origin[i]≠Point[i]_1 and S_Origin[i]=Point[i]_2, then End_Point[i]=Point[i]_1 and Start_Point[i]=Point[i]_2;

[0040] If E_Origin[i]≠Point[i]_2 and S_Origin[i]=Point[i]_1, then End_Point[i]=Point[i]_2 and Start_Point[i]=Point[i]_1;

[0041] If E_Origin[i]=Point[i]_2 and S_Origin[i]≠Point[i]_1, then End_Point[i]=Point[i]_2 and Start_Point[i]=Point[i]_1;

[0042] If E_Origin[i]≠Point[i]_2 and S_Origin[i]≠Point[i]_1, then End_Point[i] and Start_Point[i] are determined according to the topological relationship rules.

[0043] Compared with the prior art, the present invention can achieve at least one of the following beneficial effects:

[0044] 1. This invention uses a data processing unit to re-divide the pipeline segments in the original pipeline segment vector data using newly added inflection points and cross points, and re-numbers the pipeline segment number of each segment after division and determines the start and end directions of each segment after division, thereby realizing the calibration and update of the original pipeline data.

[0045] 2. This invention intelligently generates important nodes in the original pipeline data that were not marked, avoiding the need for manual inspection of each pipeline segment, improving data processing efficiency, and providing an intelligent, efficient, replicable, and scalable underground pipeline management system.

[0046] In this invention, the above-described technical solutions can be combined with each other to achieve more preferred combinations. Other features and advantages of this invention will be set forth in the following description, and some advantages may become apparent from the description or be learned by practicing the invention. The objects and other advantages of this invention can be realized and obtained from what is particularly pointed out in the description and drawings. Attached Figure Description

[0047] The accompanying drawings are for illustrative purposes only and are not intended to limit the invention. Throughout the drawings, the same reference numerals denote the same parts.

[0048] Figure 1 This is a schematic diagram of the structure of an underground pipeline management system provided in an embodiment of the present invention;

[0049] Figure 2 This is a schematic diagram of a data processing unit acquiring updated pipeline data, provided in an embodiment of the present invention.

[0050] Figure 3 This is one of the schematic diagrams of a pipeline network "node-edge" provided in an embodiment of the present invention;

[0051] Figure 4 This is the second schematic diagram of a pipeline network “node-edge” provided in an embodiment of the present invention;

[0052] Figure 5 This is the third schematic diagram of the pipeline network "node-edge" provided in the embodiments of the present invention;

[0053] Figure 6 This is one of the schematic diagrams for numbering pipeline points provided in an embodiment of the present invention;

[0054] Figure 7 This is a second schematic diagram illustrating the numbering of pipeline points according to an embodiment of the present invention.

[0055] Figure 8 This is a schematic diagram illustrating the correspondence between the updated pipeline segment number and the starting point number, provided in an embodiment of the present invention. Detailed Implementation

[0056] Preferred embodiments of the present invention will now be described in detail with reference to the accompanying drawings, which form part of this application and are used together with the embodiments of the present invention to illustrate the principles of the present invention, but are not intended to limit the scope of the present invention.

[0057] One specific embodiment of the present invention discloses an underground pipeline management system, such as... Figure 1 As shown, the management system includes:

[0058] The data acquisition unit is used to acquire newly added vertices and cross points;

[0059] The data storage unit is used to store the original pipeline data and the updated pipeline data; the pipeline data includes pipeline segment vector data and pipeline point vector data.

[0060] The data processing unit is used to re-divide the pipeline segments in the original pipeline segment vector data using newly added inflection points and cross points, and renumber all the divided pipeline segments to obtain first line vector data; based on the first line vector data, it generates data corresponding to the two endpoints of each pipeline segment, i.e., second point vector data; it numbers the pipeline points in the first line vector data according to the original pipeline point vector data to obtain third point vector data; and it determines the start and end directions corresponding to each pipeline segment in the second point vector data according to the third point vector data to obtain the updated pipeline data.

[0061] The data comparison unit is used to obtain new pipeline data based on the original pipeline data and the updated pipeline data.

[0062] Specifically, the data processing unit acquires the updated pipeline data, such as Figure 2 As shown, it includes:

[0063] Step S1: Use the newly added inflection points and cross points to re-divide the pipeline segments in the original pipeline segment vector data, and renumber all the divided pipeline segments to obtain the first line vector data;

[0064] Step S2: Based on the first line vector data, generate data for the two endpoint pairs corresponding to each pipeline segment, i.e., the second point vector data;

[0065] Step S3: Number the pipeline points in the first line vector data according to the original pipeline point vector data, and obtain the third point vector data;

[0066] Step S4: Determine the start and end directions of each pipeline segment in the second point vector data based on the third point vector data to obtain the updated pipeline data.

[0067] Specifically, pipeline data includes pipeline segment vector data and pipeline point vector data. The original pipeline data includes original pipeline segment vector data (WSLINE) and original pipeline point vector data (WSPOINT). The original pipeline point vector data consists of nodes in the original pipeline data, and the original pipeline segment vector data consists of edges in the original pipeline data.

[0068] Specifically, a vertices represent nodes in the middle section when multiple consecutive directed line segments in the original pipeline segment vector data are divided into a single pipeline segment. For example, such as... Figure 3 As shown, in the original pipeline segment vector data, P1 to P2 is treated as a pipeline segment, and the newly added inflection points refer to P9 and P10.

[0069] Specifically, a cross point represents the intersection of two directed line segments in the original pipeline segment vector data. That is, in the actual pipeline data, the two pipelines are at different heights and do not actually intersect, but when the two pipelines are projected onto a horizontal plane, an intersection point will appear. For example, as shown... Figure 4 As shown, in the original pipeline segment vector data, P3 to P4 is a pipeline segment, P5 to P6 is a pipeline segment, and the newly added cross point refers to P11.

[0070] Understandably, the data acquisition unit acquires and stores newly added inflection points and cross-points based on pipeline information released by the municipal pipeline management department; the data storage unit stores the original pipeline data and the updated pipeline data. The data processing unit updates the original pipeline data based on the newly added inflection points and cross-points, obtaining the updated pipeline data and storing it in the data storage unit.

[0071] Specifically, in step S1, the pipeline segments in the original pipeline segment vector data are re-divided using inflection points and cross points, and all the re-divided pipeline segments are renumbered to obtain the first line vector data.

[0072] Preferably, the step of re-dividing the pipeline segments in the original pipeline segment vector data using newly added inflection points and cross points includes:

[0073] Using the crossing point as the dividing point, the original pipeline segment vector data containing the crossing point is divided into pipeline segments;

[0074] Using the inflection point as the dividing point, the pipeline segments in the original pipeline segment vector data that have inflection points are divided;

[0075] Assign the line attribute values ​​of each pipeline segment before division to each pipeline segment after division; the line attribute values ​​include the start point number S_POINT and the end point number E_POINT.

[0076] Specifically, such as Figure 3 As shown, pipeline segment P1P2 is a pipeline segment with inflection points in the original pipeline segment vector data. For pipeline segment P1P2 with inflection points, the pipeline segment P1P2 is divided into pipeline segments P1P9, P9P10 and P10P2, with inflection points P9 and P10 as the dividing points.

[0077] During implementation, you can use ArcToolbox's "Data Management" > "Features" > "Split Line at Vertex". In the pop-up "Split Line at Vertex" window, select WSLINE as the input feature and specify the output file save path and name in the output feature class.

[0078] Specifically, such as Figure 4As shown, pipeline segments P3P4 and P5P6 are pipeline segments with crossing points in the original pipeline segment vector data. For pipeline segments P3P4 and P5P6 with crossing points, the crossing point P11 is used as the dividing point to divide pipeline segments P3P4 and P5P6 into pipeline segments P3P11, P11P4, P5P11, and P11P6.

[0079] During implementation, ArcGIS can be used to perform cross-point segmentation on the original pipeline segment vector data WSLINE. First, right-click on the WSLINE layer and select "Edit Feature" > "Start Editing" to make the pipeline layer editable. Then, right-click on the WSLINE layer and select "Select" > "Select All". Use the "Break Intersecting Lines" function in the advanced editing tools to break the lines at the intersections. Click "OK" in the pop-up "Break Intersecting Lines" window to complete the breaking of the intersecting lines.

[0080] Specifically, the line attribute values ​​of the pipeline segment include the start point number S_POINT and the end point number E_POINT. In addition, the line attribute values ​​also include the pipeline segment number PIPEID, the construction time BuildTime, the burial method D_TYPE, the pipe diameter D_S, and the material MATERIAL.

[0081] Assigning the line attribute values ​​of the divided pipeline segments to the divided pipeline segments. Preferably, assigning the line attribute values ​​of the pipeline segments before division to the divided pipeline segments includes:

[0082] If a pipeline segment is not divided after partitioning, its line attribute value remains unchanged;

[0083] If a pipeline segment is divided into multiple pipeline segments after partitioning, the line attribute values ​​of the pipeline segment before partitioning are assigned to the multiple pipeline segments obtained after partitioning.

[0084] For example, such as Figure 3 As shown, before the division, the starting point number S_POINT of pipeline segment P1P2 is 1 and the ending point number E_POINT is 2. After the division, the starting point number S_POINT of pipeline segments P1P9, P9P10 and P10P2 is 1 and the ending point number E_POINT is 2.

[0085] For example, such as Figure 4As shown, before the division, the starting point S_POINT of pipeline segment P3P4 was 3 and the ending point E_POINT was 4; the starting point S_POINT of pipeline segment P5P6 was 5 and the ending point E_POINT was 6. After the division, the starting point S_POINT of pipeline segments P3P11 and P11P4 was 3 and the ending point E_POINT was 4; the starting point S_POINT of pipeline segments P5P11 and P11P6 ​​was 5 and the ending point E_POINT was 6.

[0086] It is worth noting that if a pipeline segment was not divided after the initial division, such as... Figure 5 As shown, there are no crossing points or inflection points in pipeline segment P7P8. The starting point number S_POINT is 7 and the ending point number E_POINT is 8, which remain unchanged.

[0087] Specifically, all pipeline segments are renumbered after the division, and all pipeline segments are summarized to determine the total number of pipeline segments after the division. For example... Figure 3 , Figure 4 and Figure 5 As shown, the pipeline segments P1P9, P9P10, P10P2, P3P11, P11P4, P5P11, P11P6 ​​and P7P8 are numbered PIPEID as 1, 2, 3, 4, 7, 5, 6 and 8 respectively, thus obtaining the first line vector data.

[0088] It should be noted that the pipeline segments in the pipeline data are far more than the aforementioned pipeline segments P1P9, P9P10, P10P2, P3P11, P11P4, P5P11, P11P6 ​​and P7P8. This application only uses the aforementioned pipeline segments as examples to illustrate the present invention.

[0089] During implementation, N_WSLINE represents the vector data of all pipeline segments after division. When N_WSLINE is in non-editing mode, right-click on the layer and select "Open Attribute Table". Select the pipeline number field, such as "PIPEID", right-click on "Field Calculator", and in the pop-up Field Calculator window, select the parsing program, such as "VB Script". Then enter "WSL"&[FID] in the code field and click "OK" to complete the renumbering of pipeline segments.

[0090] By adding new inflection points and cross points, the pipeline segments in the original pipeline data are re-divided to obtain more pipeline segments. Then, by determining the line attribute values ​​of each pipeline segment, including the start point number Start_POINT and the end point number End_POINT, a more refined and accurate pipeline network can be obtained.

[0091] It is worth noting that after step S1, we can determine the pipeline segment number PIPEID for each pipeline segment, but we cannot determine the direction of each pipeline segment.

[0092] Specifically, in step S2, based on the first line vector data, data for the two endpoint pairs corresponding to each pipeline segment is generated, namely the second point vector data.

[0093] Specifically, the first line vector data includes pipeline segments P1P9, P9P10, P10P2, P3P11, P11P4, P5P11, P11P6 ​​and P7P8. For each pipeline segment, data corresponding to two endpoint pairs are generated, with the endpoints being the two nodes of each pipeline segment.

[0094] In implementation, the ArcGIS ArcToolbox was used for processing. In the ArcToolbox, go to

Data Management

Features

Feature Turning Point

[0095] Specifically, in step S3, the pipeline points in the first line vector data are numbered according to the original pipeline point vector data to obtain the third point vector data.

[0096] It is understandable that in the first line vector data, there are pipeline points P1, P2, P9, P10, P3, P4, P6, P5, P11, P7 and P8. Based on the original pipeline point vector data WSPOINT, the pipeline points P1, P2, P9, P10, P3, P4, P6, P5, P11, P7 and P8 are numbered to obtain the third point vector data.

[0097] Preferably, the step of numbering the pipeline points in the first line vector data according to the original pipeline point vector data to obtain the third point vector data includes:

[0098] Based on the first line vector data, data of all pipeline points in the first line vector data are generated using network analysis tools to obtain the first point vector data;

[0099] Based on the original pipeline point vector data, the first point vector data is numbered to obtain the third point vector data.

[0100] Specifically, in the first-line vector data, the data exists in the form of pipeline segments, and the endpoints of each pipeline segment are not isolated. Based on the first-line vector data, network analysis tools are used to identify all pipeline points in the first-line vector data, namely pipeline points P1, P2, P9, P10, P3, P4, P6, P5, P11, P7, and P8, thus obtaining the first-point vector data. Then, based on the original pipeline point vector data, WSPOINT is used to number the pipeline points P1, P2, P9, P10, P3, P4, P6, P5, P11, P7, and P8, obtaining the third-point vector data, which includes geophysical point numbers and other point attribute values.

[0101] During implementation, the Network Analysis function in ArcGIS can be used to obtain the first point vector data. Open the "Directory" via the standard toolbar, locate the directory and file containing N_WSLINE, right-click | "New Network Dataset," and enter the name "N_WSLINE_ND." Select "No" for whether to build a turning model in this network; select the default connectivity settings; select "None" for how to model the elevation of network features; do not set any attributes for the network dataset; select "No" for whether to create driving direction settings for this network dataset; the new network dataset has been created. Select "Yes" for whether to build immediately; select "Yes" for whether to add all feature classes involved in "N_WSLINE_ND" to the map.

[0102] The content list now includes three additional layers: a point layer "N_WSLINE_ND_Junctions", a line layer "N_WSLINE", and "N_WSLINE_ND". "N_WSLINE_ND_Junctions" is the file containing all the newly generated pipe point sets, i.e., the first point vector data file.

[0103] Preferably, the step of numbering the first point vector data based on the original pipeline point vector data to obtain the third point vector data includes:

[0104] In the first point vector data, find the pipeline points whose position coordinates are the same as those in the original pipeline point vector data, and use them as old pipeline points. Assign the point attribute values ​​of each point in the original pipeline point vector data to the corresponding old pipeline points. The point attribute values ​​include the geophysical point number.

[0105] The pipeline points other than the old pipeline points in the first point vector data are taken as new pipeline points, and the geophysical point numbers of the new pipeline points are assigned to obtain the third point vector data.

[0106] Specifically, in the first point vector data, pipeline points whose position coordinates are the same as those in the original pipeline point vector data are identified and designated as old pipeline points. All pipeline points in the first point vector data other than the old pipeline points are designated as new pipeline points. For example... Figure 3 , Figure 4 and Figure 5 Pipeline points P1, P2, P3, P4, P6, P5, P7, and P8 are designated as old pipeline points; pipeline points P9, P10, and P11 are designated as new pipeline points.

[0107] For old pipeline points, the point attribute values ​​of each point in the old pipeline points are assigned to the corresponding old pipeline points. The point attribute values ​​include the geophysical point number. For example, the geophysical point numbers of old pipeline points P1, P2, P3, P4, P6, P5, P7 and P8 are 1, 2, 3, 4, 6, 5, 7 and 8, respectively.

[0108] For the new pipeline points P9, P10, and P11, the geophysical exploration points of the new pipeline points P9, P10, and P11 are numbered. For example, after numbering, the geophysical exploration point numbers of the new pipeline points P9, P10, and P11 are 9, 10, and 11, respectively.

[0109] After assigning geophysical point numbers to all pipeline points, this data is used as the third-point vector data. It can be understood that all pipeline points in the third-point vector data have geophysical point numbers.

[0110] During implementation, use the ArcToolbox toolbox's

Analysis Tools

Overlay Analysis

Spatial Connection

[0111] Open the N_WSPOINT attribute table and delete redundant fields such as Join_Count, TARGET_FID, JOIN_FID, and ID. Then sort by EXP_NO using a calculator or by opening the dbf file with WPS and numbering the unnumbered data in the EXP_NO field.

[0112] like Figure 6 , Figure 7As shown, taking WPS processing of a dbf file as an example, open N_WSPOINT.dbf with WPS, insert a column to the left of column A, and enter 1 in cell A2; double-click the crosshair in the lower left corner of cell A2 to complete the sequence filling; sort in descending order using the column containing EXP_NO as the key to filter out data with empty numbers; enter a number (the maximum value among the existing numbers + 1, ensuring that the new number is not a duplicate of the existing number) in the first empty cell of the EXP_NO data column, in this example, WSP1165; double-click the crosshair in this cell to complete the filling of subsequent data; sort in ascending order using column A as the key; delete the newly added serial numbers in column A and save the file. This yields the processed pipe point set data file N_WSPOINT, which is the third point vector data file.

[0113] Preferably, the point attribute value further includes one or more of the following:

[0114] Ground elevation SURF_H;

[0115] Features;

[0116] Subsidiary;

[0117] Location.

[0118] In the third point vector data, new pipeline points and old pipeline points are determined by position coordinates, thus keeping the attribute values ​​of old pipeline points unchanged, while newly added pipeline points are sequentially numbered. The numbering of pipeline points can reflect the time attribute of pipeline points, which is convenient for subsequent analysis of the pipeline network.

[0119] Specifically, in step S4, the start and end directions of each pipeline segment in the second point vector data are determined based on the third point vector data to obtain the updated pipeline data. It can be understood that the points in the second point vector data are generated based on each pipeline segment in the first line vector data. Each pipeline segment generates two corresponding pipeline points, meaning the position information of the two endpoints of each pipeline segment can be obtained from the second vector data. However, at this point, the correspondence between the two endpoints and the start and end points cannot be distinguished. In particular, the point attribute values ​​in the second point vector data inherit the pipeline segment number PIPID, end point number E_POINT, and start point number S_POINT from the first line vector data. The end point number E_POINT and start point number S_POINT are the end point number E_POINT and start point number S_POINT corresponding to the pipeline segments in the original pipeline data. However, the start and end point numbers of each pipeline segment in the second point vector data are inaccurate and need to be corrected based on the third point vector data to obtain the final start and end point numbers of each pipeline segment.

[0120] Preferably, the step of determining the start and end directions of each pipeline segment in the second point vector data based on the third point vector data to obtain the updated pipeline data includes:

[0121] Find the pipeline points in the second point vector data whose position coordinates are the same as those in the third point vector data, and map the point attribute values ​​of the pipeline points with the same position coordinates in the third point vector data to the corresponding pipeline points in the second point vector data to obtain the geophysical point numbers of each mapped pipeline point.

[0122] Based on the start point number S_POINT and end point number E_POINT of each pipeline segment in the second point vector data before mapping, and the geophysical point numbers of the two endpoints of the corresponding pipeline segments after mapping, the final start point number S_POINT and end point number E_POINT of each pipeline segment in the second point vector data are determined, and the pipeline segment number of each pipeline segment and its start point number Start_POINT and end point number End_POINT are obtained. After further processing, it is used as the pipeline segment vector data in the updated pipeline data.

[0123] Understandably, in the second point vector data, each row represents a pipeline point vector data, and every two pipeline point vector data form a pipeline segment data. After determining the start point number Start_POINT and end point number End_POINT for all endpoint pairs in the second point vector data, further processing is needed to convert the endpoint pair data in the second point vector data into pipeline segment vector data. Each endpoint pair data corresponds to one pipeline segment vector data, and the pipeline segment vector data obtained after further processing is used as the pipeline segment vector data in the new pipeline data.

[0124] It is worth noting that the final pipeline segment number PIPEID corresponds to the final start point number S_POINT and end point number E_POINT in the second point vector data. Further processing is needed to use this correspondence as the pipeline segment vector data in the updated pipeline data. For example, ArcGIS's field connection tool can be used to associate the correspondence between PIPID and S_POINT, E_POINT in the second point vector data with the pipeline segment vector data.

[0125] The third point vector data is used as the pipeline point vector data in the updated pipeline data.

[0126] It is worth noting that after mapping based on the third point vector data, each pipeline point in the second point vector data has a geophysical point number.

[0127] Specifically, in the second point vector data, find the pipeline points whose position coordinates are the same as those in the third point vector data. Map the point attribute values ​​of the pipeline points with the same position coordinates in the third point vector data to the corresponding pipeline points in the second point vector data to obtain the geophysical point numbers of each mapped pipeline point.

[0128] It is understandable that if pipeline points with the same location coordinates are considered as the same pipeline point, the number of pipeline points in the second point vector data and the third point vector data will be the same. The point attribute values ​​of pipeline points with the same location coordinates in the third point vector data will be mapped to the corresponding pipeline points in the second point vector data. After the mapping, all pipeline points in the second point vector data will have a geophysical point number.

[0129] for example Figure 3 , Figure 4 and Figure 5 In the pipeline segment P1P9, the geophysical points at the two endpoints P1 and P9 are numbered 1 and 9, respectively; the geophysical points at the two endpoints P9 and P10 of the pipeline segment P9P10 are numbered 9 and 10, respectively; the geophysical points at the two endpoints P10 and P2 of the pipeline segment P10P2 are numbered 10 and 2, respectively; the geophysical points at the two endpoints P3 and P11 of the pipeline segment P3P11 are numbered 3 and 11, respectively; the geophysical points at the two endpoints P11 and P4 of the pipeline segment P11P4 are numbered 11 and 4, respectively; the geophysical points at the two endpoints P5 and P11 of the pipeline segment P5P11 are numbered 5 and 11, respectively; the geophysical points at the two endpoints P11 and P6 of the pipeline segment P11P6 ​​are numbered 11 and 6, respectively; and the geophysical points at the two endpoints P7 and P8 of the pipeline segment P7P8 are numbered 7 and 8, respectively.

[0130] During implementation, a spatial connection tool is used to compare the positions of the endpoint pair data turning_point obtained in step S2 with the points in the pipeline point vector data N_WSPOINT obtained in step S3. Points with the same geographical location, i.e., coordinates, are regarded as the same point, that is, the pipeline point number in N_WSPOINT is mapped to turning_point.

[0131] Using the ArcToolbox toolbox, go to **Analysis Tools** | **Overlay Analysis** | **Spatial Joins**. In the pop-up Spatial Joins window, select "turning_point" for "Target Feature," and "N_WSPOINT" for "Join Features." Choose the output file save path and file name as "Line_to_Point" for "Output Feature Class." Select "JOIN_ONE_TO_ONE" for "Join Operation," and check "Keep All Target Features." In "Field Mapping of Join Features," select to retain the PIPEID, E_POINT, S_POINT, and EXP_NO fields. Select "HAVE_THEIR_CENTER_IN" for "Match Options." Click OK to generate the Line_to_Point file. Open the attribute table of this file, click **Table Options** | **Export**, and in the pop-up Export Data window, select the save path and file name in the output table.

[0132] Preferably, determining the final start point number S_POINT and end point number E_POINT corresponding to each pipeline segment in the second point vector data based on the start point number S_POINT and end point number E_POINT of each pipeline segment in the second point vector data before mapping and the geophysical point numbers of the two endpoints of the corresponding pipeline segments after mapping includes:

[0133] If E_Origin[i]=Point[i]_1 and S_Origin[i]=Point[i]_2, then End_Point[i]=Point[i]_1 and Start_Point[i]=Point[i]_2;

[0134] If E_Origin[i]=Point[i]_2 and S_Origin[i]=Point[i]_1, then End_Point[i]=Point[i]_2 and Start_Point[i]=Point[i]_1.

[0135] If E_Origin[i]=Point[i]_1 and S_Origin[i]≠Point[i]_2, then End_Point[i]=Point[i]_1 and Start_Point[i]=Point[i]_2;

[0136] If E_Origin[i]≠Point[i]_1 and S_Origin[i]=Point[i]_2, then End_Point[i]=Point[i]_1 and Start_Point[i]=Point[i]_2;

[0137] If E_Origin[i]≠Point[i]_2 and S_Origin[i]=Point[i]_1, then End_Point[i]=Point[i]_2 and Start_Point[i]=Point[i]_1;

[0138] If E_Origin[i]=Point[i]_2 and S_Origin[i]≠Point[i]_1, then End_Point[i]=Point[i]_2 and Start_Point[i]=Point[i]_1.

[0139] If E_Origin[i]≠Point[i]_2 and S_Origin[i]≠Point[i]_1, then End_Point[i] and Start_Point[i] are determined according to the topological relationship rules.

[0140] Where E_Origin[i] represents the end point number E_POINT of the i-th pipeline segment before mapping, and S_Origin[i] represents the start point number S_POINT of the i-th pipeline segment before mapping; Point[i]_1 represents the geophysical point number of one end point of the i-th pipeline segment after mapping, and Point[i]_2 represents the geophysical point number of the other end point of the i-th pipeline segment after mapping; End_Point[i] represents the final end point number E_POINT of the i-th pipeline segment, and End_Point[i] represents the final start point number S_POINT of the i-th pipeline segment.

[0141] Specifically, for example, such as Figure 5 As shown, in Figure 5 Before mapping, the starting point number S_POINT for the 8th pipeline segment P7P8 was 7, and the ending point number E_POINT was 8. After mapping, the position coordinates of the two endpoints of the 8th pipeline segment P7P8 are the same as the position coordinates in the third point vector data. Therefore, the geophysical point numbers of the two endpoints of the 8th pipeline segment P7P8 after mapping are still 7 and 8. Comparison shows that the final starting point number S_POINT for the 8th pipeline segment P7P8 is 7, and the ending point number E_POINT is 8.

[0142] For example, such as Figure 3 and Figure 4 As shown. In Figure 3Before mapping, the starting point number S_POINT for the first pipeline segment P1P9 is 1, and the ending point number E_POINT is 2. After mapping, the geophysical point numbers at the two endpoints of the first pipeline segment P1P9 are 1 and 9. Comparison shows that the final starting point number S_POINT for the first pipeline segment P1P9 is 1, and the ending point number E_POINT is 9. Similarly, before mapping, the starting point number S_POINT for the third pipeline segment P10P2 is 1, and the ending point number E_POINT is 2. After mapping, the geophysical point numbers at the two endpoints of the third pipeline segment P10P2 are 10 and 2. Comparison shows that the final starting point number S_POINT for the third pipeline segment P10P2 is 10, and the ending point number E_POINT is 2.

[0143] exist Figure 4 In the diagram, before mapping, the starting point S_POINT of the fourth pipeline segment P3P11 is 3, and the ending point E_POINT is 4. After mapping, the geophysical point numbers of the two endpoints of the fourth pipeline segment P3P11 are 3 and 11. Comparing these, we can see that the final starting point S_POINT of the fourth pipeline segment P3P11 is 3, and the ending point E_POINT is 11. Furthermore, we know that the final starting point S_POINT of the fifth pipeline segment P5P11 is 5, and the ending point E_POINT is 11; the final starting point S_POINT of the sixth pipeline segment P11P6 ​​is 11, and the ending point E_POINT is 6; and the final starting point S_POINT of the seventh pipeline segment P11P4 is 11, and the ending point E_POINT is 4. These details will not be elaborated further.

[0144] For example, such as Figure 3 As shown, before mapping, the starting point number S_POINT of the second pipeline segment P9P10 is 1, and the ending point number E_POINT is 2. After mapping, the geophysical points at the two endpoints of the second pipeline segment P9P10 are 9 and 10. At this time, according to the topological relationship, the final starting point number S_POINT of the second pipeline segment P9P10 is determined to be 9, and the ending point number E_POINT is determined to be 10.

[0145] The specific steps involved in implementation include:

[0146] Select from the second point vector data the pipeline segment number PIPID, the starting point number S_POINT before mapping, the ending point number E_POINT, and the geophysical point number EXP_NO of the pipeline point, and then perform further processing.

[0147] 1) Input Description: The data consists of 4 columns. The first column, PIPEID, is the pipeline segment number; the second column, E_Origin, is the endpoint number before mapping, E_POINT; the third column, S_Origin, is the starting point number before mapping, S_POINT; and the fourth column, EXP_NO, is the geophysical point number of the two endpoints after mapping (the correspondence between the starting and ending points is unknown). Figure 8 As shown.

[0148] 2) Output requirements: Map the start and end point numbers of the pipeline segments to the pipeline segments themselves, as shown in the following example. Figure 8 As shown.

[0149] 3) Logical implementation process:

[0150] i. Extract the two data points Point_1 and Point_2 from the EXP_NO column, which represent the two endpoints of the same pipeline;

[0151] ii. Compare the data E_Origin[i] and S_Origin[i] corresponding to the E_POINT and S_POINT columns of the pipeline with the Point_1 and Point_2 retrieved in the previous step to obtain the start point number Start_Point[i] and end point number End_Point[i] corresponding to pipeline i:

[0152] a. If E_Origin[i]=Point_1 and S_Origin[i]=Point_2, then End_Point[i]=Point_1, Start_Point[i]=Point_2;

[0153] b. If E_Origin[i]=Point_2 and S_Origin[i]=Point_1, then End_Point[i]=Point_2, Strut_Point[i]=Point_1;

[0154] c. If E_Origin[i]=Point_1 and S_Origin[i]≠Point_2, then End_Point[i]=Point_1, Strat_Point[i]=Point_2;

[0155] d. If E_Origin[i]=Point_2 and S_Origin[i]≠Point_1, then End_Point[i]=Point_2, Start_Point[i]=Point_1;

[0156] e. If E_Origin[i]≠Point_1 and S_Origin[i]=Point_2, then End_Point[i]=Point_1, Start_Point[i]=Point_2;

[0157] f. If E_Origin[i]≠Point_2 and S_Origin[i]=Point_1, then End_Point[i]=Point_, Start_Point[i]=Point_1;

[0158] g. In other cases, Start_Point[i] = "To be determined" and End_Point[i] = "To be determined".

[0159] For case g, the determination is based on the rules of topological relationships.

[0160] Using ArcGIS's field connection tool, the updated pipeline segment and pipeline point correspondence is linked to the pipeline segment vector data to obtain the updated pipeline data.

[0161] Specifically, the data comparison unit obtains the newly added pipeline data based on the original pipeline data and the updated pipeline data. It should be noted that the newly added pipeline data refers to the newly added pipeline segments.

[0162] The process of obtaining new pipeline data based on the original pipeline data and the updated pipeline data includes:

[0163] For a pipeline segment in the updated pipeline data, if there exists a pipeline segment in the original pipeline segment vector data, and the position coordinates of the start and end points of that pipeline segment are the same as the position coordinates of the start and end points of the updated pipeline segment, then the updated pipeline segment is the old pipeline segment; otherwise, the pipeline segment is the new pipeline segment, and the new pipeline segment is used as newly added pipeline data.

[0164] Specifically, such as Figure 3 , Figure 4 and Figure 5 As shown, P1 to P8 are old pipeline points, and P9, P10, and P11 are new pipeline points; pipeline segments P1P9, P9P10, P10P2, P3P11, P11P4, P5P11, and P11P6 ​​are new pipeline segments, P7P8 is an old pipeline segment, and pipeline segments P1P9, P9P10, P10P2, P3P11, P11P4, P5P11, and P11P6 ​​are newly added pipeline data.

[0165] Furthermore, the management system also includes:

[0166] A visualization platform is used to display the newly added pipeline data for users to view; it is also used to receive pipeline query information from users and send the pipeline query information to the data query unit; it is also used to receive pipeline data sent by the data query unit and display it.

[0167] The data query unit is used to search for the corresponding pipeline data in the data storage unit based on the pipeline query information and send it to the visualization platform for display.

[0168] The data editing unit is used to delete or modify the corresponding pipeline data in the data storage unit according to the deletion or modification instructions sent by the visualization platform.

[0169] Specifically, the visualization platform can display pipeline data from the data storage unit according to user needs. When new pipeline data is added, the visualization platform displays the new data for user viewing. For example, the visualization platform can display two-dimensional or three-dimensional pipeline data and use different colors to display new and old pipeline segments. When a user clicks on a pipeline segment, the line attribute value of that pipeline segment is displayed on the screen.

[0170] It's worth noting that the visualization platform can serve as an interaction platform with users, and also for receiving users' pipeline query information, deletion commands, and modification commands. When a user inputs pipeline query information through the visualization platform, the data query unit locates the corresponding pipeline data in the data storage unit based on the pipeline query information, and then sends it to the visualization platform for display.

[0171] For example, you can enter the pipeline segment number to find the corresponding pipeline segment, or enter the starting coordinates of the pipeline segment to find the corresponding pipeline segment; you can also enter the geophysical point number of the pipeline point to find the pipeline point.

[0172] The data editing unit is used for routine maintenance of pipeline data. When a certain attribute value in the pipeline data needs to be deleted or modified, the user can input a deletion command or modification command through the visualization platform. The data editing unit can then delete or modify the corresponding pipeline data in the data storage unit according to the command.

[0173] Compared with existing technologies, the underground pipeline management system provided in this invention uses a data processing unit to re-divide the pipeline segments in the original pipeline segment vector data using inflection points and cross points. It then re-numbers each segment and determines the start and end directions of each segment, thus calibrating the original pipeline data. Simultaneously, by intelligently generating important nodes that were not marked in the original pipeline data, it avoids manual inspection of each pipeline segment, improving data processing efficiency. This provides an intelligent, efficient, replicable, and scalable underground pipeline management system.

[0174] Those skilled in the art will understand that all or part of the processes of the methods described in the above embodiments can be implemented by a computer program instructing related hardware, and the program can be stored in a computer-readable storage medium. The computer-readable storage medium may be a disk, optical disk, read-only memory, or random access memory, etc.

[0175] The above description is only a preferred embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any changes or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in the present invention should be included within the scope of protection of the present invention.

Claims

1. An underground pipeline management system, characterized by, The management system includes: The data acquisition unit is used to acquire newly added inflection points and cross points; the cross point refers to the intersection point of two pipelines at different heights in the original pipeline segment vector data when projected onto the horizontal plane; the inflection point refers to the node in the middle part when multiple continuous directed line segments in the original pipeline segment vector data are divided into one pipeline segment. The data storage unit is used to store the original pipeline data and the updated pipeline data; the pipeline data includes pipeline segment vector data and pipeline point vector data. The data processing unit is used to re-divide the pipeline segments in the original pipeline segment vector data using newly added inflection points and cross points, and renumber all the divided pipeline segments to obtain first line vector data; based on the first line vector data, it generates data corresponding to the two endpoints of each pipeline segment, i.e., second point vector data; it numbers the pipeline points in the first line vector data according to the original pipeline point vector data to obtain third point vector data; and it determines the start and end directions corresponding to each pipeline segment in the second point vector data according to the third point vector data to obtain the updated pipeline data. The data comparison unit is used to obtain new pipeline data based on the original pipeline data and the updated pipeline data.

2. The management system according to claim 1, characterized by The management system also includes: A visualization platform is used to display the newly added pipeline data for users to view; it is also used to receive pipeline query information from users and send the pipeline query information to the data query unit; it is also used to receive pipeline data sent by the data query unit and display it. The data query unit is used to search for the corresponding pipeline data in the data storage unit based on the pipeline query information and send it to the visualization platform for display.

3. The management system according to claim 2, characterized by The management system also includes: The data editing unit is used to delete or modify the corresponding pipeline data in the data storage unit according to the deletion or modification instructions sent by the visualization platform.

4. The management system of claim 1, wherein, The process of re-dividing the pipeline segments in the original pipeline segment vector data using newly added inflection points and cross points includes: Using the crossing point as the dividing point, the original pipeline segment vector data containing the crossing point is divided into pipeline segments; Using the inflection point as the dividing point, the pipeline segments in the original pipeline segment vector data that have inflection points are divided; Assign the line attribute values ​​of each pipeline segment before division to each pipeline segment after division; the line attribute values ​​include the start number and the end number.

5. The management system according to claim 4, characterized by Assigning the line attribute values ​​of each pipeline segment before division to each pipeline segment after division includes: If a pipeline segment is not divided after partitioning, its line attribute value remains unchanged; If a pipeline segment is divided into multiple pipeline segments after partitioning, the line attribute values ​​of the pipeline segment before partitioning are assigned to the multiple pipeline segments obtained after partitioning.

6. The management system of claim 1, wherein, The step of numbering the pipeline points in the first line vector data according to the original pipeline point vector data to obtain the third point vector data includes: Based on the first line vector data, data of all pipeline points in the first line vector data are generated using network analysis tools to obtain the first point vector data; Based on the original pipeline point vector data, the first point vector data is numbered to obtain the third point vector data.

7. The management system according to claim 6, characterized by The step of numbering the first point vector data based on the original pipeline point vector data and obtaining the third point vector data includes: In the first point vector data, find the pipeline points whose position coordinates are the same as those in the original pipeline point vector data, and use them as old pipeline points. Assign the point attribute values ​​of each point in the original pipeline point vector data to the corresponding old pipeline points. The point attribute values ​​include the geophysical point number. The pipeline points other than the old pipeline points in the first point vector data are taken as new pipeline points, and the geophysical point numbers of the new pipeline points are assigned to obtain the third point vector data.

8. The management system of claim 4, wherein, The step of determining the start and end directions of each pipeline segment in the second point vector data based on the third point vector data to obtain the updated pipeline data includes: Find the pipeline points in the second point vector data whose position coordinates are the same as those in the third point vector data, and map the point attribute values ​​of the pipeline points with the same position coordinates in the third point vector data to the corresponding pipeline points in the second point vector data to obtain the geophysical point numbers of each mapped pipeline point. Based on the start point number and end point number of each pipeline segment in the second point vector data before mapping and the geophysical point numbers of the two endpoints of the corresponding pipeline segments after mapping, the final start point number and end point number of each pipeline segment in the second point vector data are determined, and the pipeline segment number and its start point number and end point number of each pipeline segment are obtained. After further processing, they are used as the pipeline segment vector data in the updated pipeline data. The third point vector data is used as the pipeline point vector data in the updated pipeline data.

9. The management system according to claim 8, characterized by The step of determining the final start and end numbers of each pipeline segment in the second point vector data based on the start and end numbers of each pipeline segment in the second point vector data before mapping and the geophysical point numbers of the two endpoints of the corresponding pipeline segments after mapping includes: If E_Origin[i]=Point[i]_1 and S_Origin[i]=Point[i]_2, then End_Point[i]=Point[i]_1 and Start_Point[i]=Point[i]_2; If E_Origin[i]=Point[i]_2 and S_Origin[i]=Point[i]_1, then End_Point[i]=Point[i]_2 and Start_Point[i]=Point[i]_1; Where E_Origin[i] represents the end point number of the i-th pipeline segment before mapping, and S_Origin[i] represents the start point number of the i-th pipeline segment before mapping; Point[i]_1 represents the geophysical point number of one end point of the i-th pipeline segment after mapping, and Point[i]_2 represents the geophysical point number of the other end point of the i-th pipeline segment after mapping; End_Point[i] represents the final end point number of the i-th pipeline segment, and Strart_Point[i] represents the final start point number of the i-th pipeline segment.

10. The management system according to claim 9, characterized by The step of determining the final start and end numbers of each pipeline segment in the second point vector data based on the start and end numbers of each pipeline segment in the second point vector data before mapping and the geophysical point numbers of the two endpoints of the corresponding pipeline segments after mapping also includes: If E_Origin[i]=Point[i]_1 and S_Origin[i]≠Point[i]_2, then End_Point[i]=Point[i]_1 and Start_Point[i]=Point[i]_2; If E_Origin[i]≠Point[i]_1 and S_Origin[i]=Point[i]_2, then End_Point[i]=Point[i]_1 and Start_Point[i]=Point[i]_2; If E_Origin[i]≠Point[i]_2 and S_Origin[i]=Point[i]_1, then End_Point[i]=Point[i]_2 and Start_Point[i]=Point[i]_1; If E_Origin[i]=Point[i]_2 and S_Origin[i]≠Point[i]_1, then End_Point[i]=Point[i]_2 and Start_Point[i]=Point[i]_1; If E_Origin[i]≠Point[i]_2 and S_Origin[i]≠Point[i]_1, then End_Point[i] and Start_Point[i] are determined according to the topological relationship rules.

Images