Duct estimation system, duct estimation method and duct estimation program

Abstract

To estimate the actual location of a duct with high reliability by making management data and estimation data based upon measurement data precisely consistent with the actual location of a buried duct.SOLUTION: A duct estimation system has: a distance data calculation unit which inputs, for ducts buried in the ground, estimation part duct data having an estimation part duct estimated based upon measurement data, and duct management data including positions of a plurality of ducts recorded as management data, and outputs distance data in which the distance to the position of a candidate duct as at least one duct that the duct management data has is calculated and associated with the estimation part duct that the estimation part duct data has respectively; and a duct estimation unit which inputs the estimation part duct data and the distance data and performs first processing to extract estimation duct data satisfying a predetermined distance for each candidate duct and second processing to estimate the actual location of a duct based upon the extracted estimation part duct data, and outputs the actual location of the duct estimated through the second processing as estimation duct data.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a technique for estimating the actual location of a pipeline buried underground. [Background technology]

[0002] Traditionally, when planning or constructing pole installations or pole removals, design drawings and construction drawings that compile information on buried objects and surrounding objects in the relevant locations are used. These drawings are managed, edited, and viewed using computer-aided design (CAD) technology. However, the various managed data may diverge from the actual conditions of the relevant locations due to differences in the timing of preparation between the planning and construction periods. Therefore, surveys of buried objects in the relevant areas are generally conducted. In surveys of buried objects, information including the location of buried objects measured using various methods is obtained based on actual measurements. This eliminates discrepancies between managed data such as design information and the actual conditions, reducing rework in planning and construction.

[0003] Patent Document 1 discloses a technique for automatically estimating buried objects using a buried object learning model based on underground exploration images acquired by a ground-penetrating radar device as a measurement method for investigating buried objects. The buried object learning model is an artificial intelligence (AI) model configured by a neural network that has learned underground exploration data of the detection target.

[0004] Furthermore, Patent Document 2 discloses a support system that corrects design information based on actual measurement data and design information. The support system discloses a method for automatically correcting design data when a discrepancy occurs between the design data and the actual measurement data so that the design data approaches the actual measurement data. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Japanese Patent Publication No. 2022-1203327 [Patent Document 2] Japanese Patent Publication No. 2020-149386 Summary of the Invention [Problem to be solved by the invention]

[0006] The invention disclosed in Patent Document 1 uses underground exploration images as actual measurement data. Various actual measurements, not limited to underground exploration methods, can only obtain partial information about the location of the buried pipeline in the relevant location. Therefore, for a certain survey area, there will be a discrepancy between the management data and the actual measurement data, or between the estimated data estimated from the actual measurement data alone.

[0007] The invention disclosed in Patent Document 2 calculates the discrepancy between design data and measured data, and then applies a correction process based on the calculated discrepancy. However, this method cannot be applied to design and measured data that include multiple objects not anticipated by this invention. Furthermore, depending on the method for acquiring the measured data, there may be areas that cannot be measured due to the measurement principle, for example, due to the presence of obstructions, or depending on when the management data was created, new pipelines may exist in the area. Therefore, the correspondence between the management data and measured data, or between data estimated from the measured data, cannot be determined by calculating the difference between the entire data.

[0008] Therefore, there is an efficiency problem in that it is necessary to manually check the consistency of the estimation results based on the actual measurement data with the management data and reflect the results in the design and construction of the area.In other words, there is a need for a highly reliable technology for estimating the actual location of buried pipelines while maintaining the consistency between the management data and the estimation data based on the actual measurement data.

[0009] The present invention aims to provide a pipeline estimation system, a pipeline estimation method, and a pipeline estimation program that can accurately match management data and estimated data based on actual measurement data regarding the actual location of buried pipelines, and estimate the actual location of the pipelines with high reliability. [Means for solving the problem]

[0010] The pipeline estimation system according to the present invention is configured as a pipeline estimation system characterized by having: a distance data calculation unit that inputs estimated partial pipeline data having estimated partial pipelines estimated based on actual measurement data for pipelines buried underground, and pipeline management data including the positions of multiple pipelines recorded as management data, designates at least one pipeline included in the pipeline management data as a candidate pipeline, calculates the distance to the position of each estimated partial pipeline included in the estimated partial pipeline data, and outputs corresponding distance data; a first process that inputs the estimated partial pipeline data and the distance data, and extracts the estimated partial pipeline data that satisfies a predetermined distance for each candidate pipeline; a second process that estimates the actual position of the pipeline based on the extracted estimated partial pipeline data; and a pipeline estimation unit that outputs the actual position of the pipeline estimated by the second process as estimated pipeline data. [Effects of the Invention]

[0011] According to the present invention, the actual location of a buried pipeline can be estimated with high reliability by accurately matching management data with estimated data based on actual measurement data. [Brief explanation of the drawings]

[0012] [Figure 1] FIG. 2 is a diagram illustrating an example of functional blocks of the pipeline estimation system according to the first embodiment. [Figure 2] 1 is a diagram illustrating an example of a hardware configuration of a pipeline estimation system according to a first embodiment. [Figure 3] FIG. 10 is a diagram showing an example of a schematic diagram of a calculation target in a pipeline estimation unit. [Figure 4] FIG. 10 is a diagram illustrating an example of estimated partial pipeline data. [Figure 5] FIG. 10 is a diagram illustrating an example of pipeline management data. [Figure 6] FIG. 10 is a diagram illustrating an example of distance data. [Figure 7] FIG. 10 is a diagram illustrating an example of estimated pipeline data. [Figure 8] FIG. 4 is a diagram illustrating an example of a flowchart of a pipeline estimation method according to the first embodiment. [Figure 9A] FIG. 10 is a diagram illustrating an example of a flag list. [Figure 9B] FIG. 10 is a diagram showing an example of a display screen on which a flag list is displayed. [Figure 10] FIG. 4 is a diagram illustrating an example of a flowchart of a process of a pipeline estimation unit in the first embodiment. [Figure 11] FIG. 10 is a diagram illustrating an example of a block diagram of a pipeline estimation system according to a second embodiment. [Figure 12] FIG. 11 is a diagram showing an example of estimated partial pipeline data in the third embodiment. [Figure 13] FIG. 10 is a diagram showing an example of actual measurement data in Example 2. [Figure 14] FIG. 13 is a diagram illustrating an example of functional blocks of a pipeline estimation system according to a fifth embodiment. [Figure 15] FIG. 20 is a diagram illustrating an example of a flowchart of a process of a pipeline estimation unit in the sixth embodiment. [Figure 16] FIG. 23 is a diagram showing an example of a schematic diagram of a calculation target in a pipeline estimation unit in the sixth embodiment. [Figure 17] FIG. 20 is a diagram illustrating an example of a flag list in a pipeline estimation unit according to the sixth embodiment. [Figure 18] FIG. 20 is a diagram illustrating an example of functional blocks of a pipeline estimation system according to a sixth embodiment. [Figure 19] FIG. 20 is a diagram illustrating an example of functional blocks of a pipeline estimation system according to a seventh embodiment. [Figure 20] FIG. 20 is a diagram showing an example of object management data in the seventh embodiment. [Figure 21] FIG. 20 is a diagram illustrating an example of a flowchart of a process performed by a correction unit in the seventh embodiment. [Figure 22] FIG. 20 is a diagram showing an example of a schematic diagram of a calculation target of a correction unit in the seventh embodiment. [Figure 23] FIG. 20 is a diagram illustrating an example of functional blocks of a pipeline estimation system according to an eighth embodiment. [Figure 24]FIG. 20 is a diagram illustrating an example of functional blocks of a pipeline estimation system according to an eighth embodiment. [Figure 25A] FIG. 10 is a diagram showing an example of a buried object management screen displayed on the display device (pipe information screen). [Figure 25B] FIG. 10 is a diagram showing an example of a buried object management screen displayed on the display device (estimated partial pipeline information screen). [Figure 25C] FIG. 10 is a diagram showing an example of a buried object management screen displayed on the display device (estimated pipeline information screen). [Figure 25D] FIG. 10 is a diagram showing an example of a buried object management screen displayed on the display device (pipe management screen). [Figure 26] FIG. 11 is a diagram illustrating an example of a flag list according to the third embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0013] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. The following description and drawings are examples for explaining the present invention, and some omissions and simplifications have been made as appropriate for clarity of explanation. The present invention can be implemented in various other forms. Unless otherwise specified, each component may be singular or plural.

[0014] In order to facilitate understanding of the invention, the position, size, shape, range, etc. of each component shown in the drawings may not represent the actual position, size, shape, range, etc. Therefore, the present invention is not necessarily limited to the position, size, shape, range, etc. disclosed in the drawings.

[0015] In the following explanation, various types of information may be described using expressions such as "database," "table," and "list," but the various types of information may also be expressed in data structures other than these. To indicate that the information is not dependent on the data structure, "XX table," "XX list," etc. may be referred to as "XX information." When describing identification information, expressions such as "identification information," "identifier," "name," "ID," and "number" are used, and these are interchangeable.

[0016] When there are multiple components with the same or similar functions, they may be described using the same reference numeral with different subscripts. However, when there is no need to distinguish between these multiple components, the subscripts may be omitted.

[0017] Furthermore, in the following description, processing performed by executing a program may be described, but the program is executed by a processor (e.g., a central processing unit (CPU) or a graphics processing unit (GPU)) to perform the specified processing while appropriately using storage resources (e.g., memory) and / or interface devices (e.g., communication ports), and therefore the processor may be the subject of the processing. Similarly, the subject of the processing performed by executing a program may be a controller, device, system, computer, or node having a processor. The subject of the processing performed by executing a program may be any computing unit, and may include a dedicated circuit (e.g., a field-programmable gate array (FPGA) or an application-specific integrated circuit (ASIC)) that performs specific processing.

[0018] A program may be installed on a device such as a computer from a program source. The program source may be, for example, a program distribution server or a computer-readable storage medium. If the program source is a program distribution server, the program distribution server may include a processor and storage resources for storing the program to be distributed, and the processor of the program distribution server may distribute the program to be distributed to other computers. Also, in the following description, two or more programs may be realized as one program, and one program may be realized as two or more programs.

[0019] In addition, although the following description may refer to a system configured from a single computer, similar functions may be realized by distributing all or part of the functions of the computer across one or more computers, such as a cloud, and communicating with each other via a network. [Example]

[0020] (1-1) Configuration of the pipeline estimation system according to this embodiment 1, S1 indicates the entire pipeline estimation system according to this embodiment. This pipeline estimation system S1 is configured to include a distance data calculation unit P2 and a pipeline estimation unit P3.

[0021] The pipeline estimation system S1 may be executed by a server H1 having the hardware configuration shown in Fig. 2. The server H1 is configured from a general-purpose computer having a processor A01 such as a CPU, and information processing resources such as a memory A02, a storage A03, and a communication I / F (Interface) A04. The storage A03 stores a pipeline estimation program M1 that causes a computer to execute a pipeline estimation method, and the program is executed by the information processing resources.

[0022] The pipeline estimation system S1 inputs estimated partial pipeline data D2 estimated based on actual measurement data (not shown) and pipeline management data D3 including the positions of multiple pipelines recorded as management data such as design information, estimates the actual position of the pipeline based on the estimated partial pipeline data D2 and the pipeline management data D3, and outputs it as estimated pipeline data D5.

[0023] The measured data is data obtained by excavating the area to expose a portion of the buried pipeline, and then obtaining point clouds using distance measuring devices such as laser range finders, or by non-destructive measurement that does not require excavation using electromagnetic induction, radio waves in various bands, or elastic waves. The signals recorded in the data include information about the location of the portion of the buried pipeline.

[0024] The estimated partial pipeline data D2 is data obtained by manually estimating the partial position of a buried pipeline based on actual measurement data or by using a predetermined estimation device (not shown). As an example, FIG. 4 shows the estimated partial pipeline data D2. Here, for each estimated partial pipeline (EstPipeSeg A, EstPipeSeg B, etc.), the position is input as three-dimensional coordinates of the start point (Start X position), start Y position, start Z position, end X position, end Y position, and end Z position, respectively. The horizontal position, i.e., the X and Y coordinates, may be recorded as geospatial coordinates based on latitude and longitude or various coordinate systems, or may be recorded as an offset from a reference point. The vertical position, i.e., the Z coordinate, may be recorded as a depth from the ground surface or as an elevation. Although the partial positions are recorded as the coordinates of the start and end points of a line segment in the example described above, they may also be recorded as a point cloud, a curve, a curved surface, or a three-dimensional structure.

[0025] The pipeline management data D3 includes the positions of multiple pipelines recorded as management data such as design information. Figure 5 shows an example of the pipeline management data D3. Here, similar to the estimated partial pipeline data D2, the position of each pipeline (PipeA, PipeB, etc.) is input as three-dimensional coordinates of its start point (Start) and end point (End), respectively, recorded as Start X position, Start Y position, Start Z position, End X position, End Y position, and End Z position. The horizontal position, i.e., the X and Y coordinates, may be recorded as geospatial coordinates based on latitude and longitude or various coordinate systems, or may be recorded as an offset from a reference point. The vertical position, i.e., the Z coordinate, may be recorded as a depth from the ground surface or as an elevation. While the example described here uses the coordinates of the start and end points of a line segment to record the pipeline position, it may also be recorded as a point cloud, a curve, a curved surface, or a three-dimensional structure.

[0026] Next, the pipeline estimation method in the pipeline estimation system S1 will be described. FIG. 8 shows a flowchart of the pipeline estimation method. First, in a data input step F101, the pipeline estimation system S1 inputs estimated pipeline segment data D2 and pipeline management data D3. Next, in a distance calculation step F102, a distance data calculation unit P2 calculates the distance between the position of a candidate pipeline in the pipeline management data D3 and the estimated pipeline segment, and outputs distance data D4 to the pipeline estimation unit P3. The pipeline estimation unit P3 then executes the next pipeline position estimation step F103. The pipeline position estimation step F103 consists of a first step F105 of extracting an estimated pipeline segment that satisfies a predetermined distance for each candidate pipeline, and a second step F106 of estimating the actual position of the pipeline. The pipeline position estimated in the pipeline position estimation step F103 is output from the pipeline estimation system S1 in a data output step F104. Pipeline estimation is performed through the above steps.

[0027] The distance calculation step F102 will now be described in detail. Figure 3 shows a schematic diagram of the relationship between the positions of candidate pipelines in the pipeline management data D3 input to the distance data calculation unit P2, the estimated pipeline segments, and the distance between them. Here, the start and end positions are indicated by black circles, the estimated pipeline segments (EstPipeSeg A, EstPipeSeg B) are connected by solid lines, and the candidate pipelines (PipeA, PipeB) in the pipeline management data are connected by dashed lines, with the distance d between them indicated by double-headed arrows. The distance d is the distance between the estimated pipeline segment p and the candidate pipeline q, and is written as d(p, q).

[0028] The distance d(p, q) is calculated using equation (1) when the estimated partial pipeline p and the candidate pipeline q are expressed as n-dimensional points. Even when the estimated partial pipeline p and the candidate pipeline q are line segments, the distance between the start point and end point, or the distance between midpoints or internal division points at a predetermined ratio, may be calculated using equation (1). Furthermore, when the estimated partial pipeline p and the candidate pipeline q are three-dimensional objects such as cylinders or curved surfaces, representative points such as the center point, center of gravity, or end points of each object are calculated in advance, and the distance is calculated by calculating equation (1) between the representative points. Alternatively, multiple internal division points may be set within a line segment, or multiple representative points may be set within an object, and then the distance calculated for each point using equation (1) may be calculated using predetermined calculation processing such as the average, median, or integral to calculate a representative value, which is then used as the distance.

[0029]

number

[0030] Here, equation (1) represents the so-called Euclidean distance, but the distance may be calculated based on the definition of the Mahalanobis distance, the Chebyshev distance, the Manhattan distance, or the like.

[0031] The distance data calculation unit P2 outputs each calculated distance as distance data D4 as shown in Fig. 6. The distance data D4 has a header containing a candidate pipeline and an index containing a label specifying an estimated partial pipeline, with the distance between the two recorded in the corresponding cell.

[0032] Next, the pipeline position estimation step F103 will be described in detail. FIG. 10 shows a detailed flowchart of the pipeline position estimation step. First, the pipeline estimation unit P3 receives the estimated partial pipeline data D2 input to the pipeline estimation system S1 and the distance data D4 output from the distance data calculation unit P2 (F301). Next, the pipeline estimation unit P3 extracts a list of candidate pipelines included in the distance data D4 as Pipe_list (F302). This is equivalent to obtaining a list of headers of the distance data D4 shown in FIG. 6. Next, the pipeline estimation unit P3 sequentially obtains candidate pipelines q from pipe_list (F303, F304). Next, the pipeline estimation unit P3 extracts a list of estimated partial pipelines as EstPipeSeg_List (F305). This is equivalent to obtaining a list of indexes of the distance data D4 shown in FIG. 6.

[0033] Next, the pipeline estimation unit P3 sequentially acquires the estimated pipeline segment p in EstPipeSeg_List (F306, F307). Next, the pipeline estimation unit P3 references the distance between the candidate pipeline q and the estimated pipeline segment p from the distance data D4 and determines whether the distance is less than a predetermined distance threshold (F308). If the pipeline estimation unit P3 obtains a positive result for the determination (F308; Yes, F309), it stores True at the position [p, q] in the flag list. If the pipeline estimation unit P3 obtains a negative result for the determination (F308; No, F310), it stores False at the position [p, q] in the flag list (F311). When the process for all estimated pipeline segments stored in EstPipeSeg_List (F312, F313) has been completed (F313; No), the flag list becomes, for example, table data such as that shown in FIG. 9A. If F313 is Yes, the process returns to F307 and the subsequent processes are repeated.

[0034] The flag list is a table that stores the determination results of whether the distance between the candidate pipeline q and the estimated partial pipeline p satisfies a predetermined distance threshold. The flag list may be displayed on an information display device (not shown), for example, as shown in FIG. 9B. The displayed flag list screen may be displayed together with the screens shown in FIGS. 25A to 25D (described later) by switching tabs, or may be displayed as a separate screen. In FIG. 9B, True is set for the candidate pipeline q and estimated partial pipeline p that satisfy the predetermined distance threshold, while False is set for the candidate pipeline q and estimated partial pipeline p that do not satisfy the predetermined distance threshold, and the two are displayed in different ways on the screen. At a glance at the screen displaying such a flag list, the user can easily identify the combination of the candidate pipeline q and estimated partial pipeline p that satisfy the condition of being less than the predetermined distance threshold.

[0035] Next, the pipeline estimation unit P3 determines whether the distance threshold determination results for all estimated pipeline segments in the column direction of the flag list, i.e., for candidate pipeline q, are False (F314). If the pipeline estimation unit P3 obtains a positive result for this determination (F314; Yes), it determines that there is no estimated pipeline segment that is close to candidate pipeline q in terms of distance. Therefore, the pipeline estimation unit P3 selects the next candidate pipeline q in accordance with the candidate pipeline list Pipe_list (F315, F316) and performs the same steps (F304-F314) again. If the pipeline estimation unit P3 obtains a negative result for this determination (F314; No), it determines that there is an estimated pipeline segment that is close to candidate pipeline q in terms of distance. Therefore, the pipeline estimation unit P3 extracts the corresponding estimated pipeline segment for which the flag list is True (F317) and calculates the data range of the extracted estimated pipeline segment (F318). The data range is defined as the region occupied in position space by the group of extracted estimated pipeline segments. In the schematic diagram of Figure 3, for example, assume that d(B,A) and d(A,A) satisfy the distance threshold for candidate pipeline Pipe A. In this case, estimated pipeline segments EstPipeSeg A and EstPipeSeg B are extracted. The data range is then defined as the smallest range that can contain a total of four points indicated by black circles.

[0036] Next, the pipeline estimation unit P3 performs regression analysis based on the extracted estimated pipeline group within the data range and finds a regression line (F319). One method for finding a regression line is to use the least squares method (LSM). The pipeline estimation unit P3 finds a line segment so that the sum of the distances between the coordinates of the four points that make up EstPipeSeg A and EstPipeSeg B and the line segment to be found is minimized. For example, if the line segment to be found is a line segment on the xy plane, the straight line passing through the line segment is modeled using equation (2).

[0037]

number

[0038] where a and b are regression coefficients. Next, the pipeline estimation unit P3 calculates the sum of the squares of the differences between the coordinates (xi, yi) of point n and the straight line modeled by equation (2) as Error. This operation is generalized and shown in equation (3).

[0039]

number

[0040] The pipeline estimation unit P3 calculates the regression coefficients a and b that minimize the error expressed by equation (3) and substitutes them into equation (2) to obtain a reasonable straight line. Examples of methods for calculating the regression coefficients a and b that minimize the error include analytical methods using partial differentials or matrix operations, and numerical calculations that search by changing the values ​​of the regression coefficients a and b from their initial values ​​and calculating the error each time. Alternatively, a regression line in three-dimensional space can be obtained by modeling a linear equation on the zx and zy planes, as with equation (2), and calculating each regression coefficient based on the three-dimensional coordinates (xi, yi, zi) of n points. The aforementioned data range is applied to the line segment area of ​​the line. While the calculation method for line segments is illustrated here, objects other than line segments, including curves, cylinders, and curved surfaces, can also be estimated by modeling the target using a specified method and optimizing based on a specified error (error) between the model and the extracted estimated pipeline segment. An optimization method such as Random Sample Consensus (RANSAC) can also be used.

[0041] An example of the line segment obtained by this process is shown as EstPipe A in the dashed line in Figure 3. The estimated pipeline is recorded in estimated pipeline data D5 (F320), and then the same process (F304-F316) is performed for the next candidate pipeline. Once this process has been performed for all candidate pipelines in the list Pipe_list (if a negative result is obtained in F316, F316; No), the pipeline estimation unit P3 outputs estimated pipeline data D5 (F321) and ends the process. On the other hand, if a positive result is obtained in F316 (F316; Yes), the process returns to F304, and the subsequent processes are repeated.

[0042] An example of estimated pipeline data D5 is shown in Fig. 7. Here, similar to the estimated partial pipeline data D2, for each estimated pipeline (EstPipe A,,,,), the position is recorded as the three-dimensional coordinates of the start point (Start) and end point (End) as Start X position, Start Y position, Start Z position, End X position, End Y position, and End Z position, respectively.

[0043] The estimated pipeline data output from the pipeline estimation system S1 is displayed on an information display device (not shown), allowing a user to confirm the estimated pipeline data D5. The information display device is configured, for example, with a display device having a liquid crystal display or an organic EL (Electro-Luminescence) display. The information display device generates a predetermined screen showing the position of the estimated pipeline based on the estimated pipeline data D5 provided from the pipeline estimation system S1, and displays the generated screen. As an example of the generated screen, an estimated pipeline information screen 25CM is shown in FIG. 25C. Within the screen, a pipeline 25CP in the estimated pipeline data is displayed as a line object in two-dimensional space.

[0044] According to the pipeline estimation system S1 and method of this embodiment, it is possible to realize a pipeline estimation system and method that can reliably estimate the actual position of a pipeline while ensuring maximum consistency between the pipeline management data D3 and the estimated partial pipeline data D2 based on actual measurement data regarding the actual position of a buried pipeline. [Example]

[0045] Fig. 11 shows a pipeline estimation system S2 according to Example 2. In Fig. 11, parts corresponding to those in Fig. 1 are denoted by the same reference numerals. This pipeline estimation system S2 is configured in the same manner as the pipeline estimation system S1 of Example 1, except that the input data to the system is actual measurement data D1 instead of estimated partial pipeline data D2, and that it has a partial pipeline estimation unit P1 that outputs estimated partial pipeline data D2 from the input actual measurement data D1.

[0046] The measured data D1 input to the partial pipeline estimation unit P1 is generated by irradiating a buried pipeline with radio waves from above ground and acquiring the reflected signals. Figure 13 shows an example of the measured data D1. The vertical axis represents the delay time (t) from when the radio waves are irradiated to when they are reflected underground and received again on the ground, while the horizontal axis represents the distance (x) from the direction of travel of the irradiated point. Furthermore, brightness represents signal strength. The signal strength may be a positive or negative value, or even an imaginary number. Furthermore, three-dimensional measured data may be obtained by shifting the radio waves along the axis (y) perpendicular to the x-axis. Figure 13 shows the position of the buried pipeline as a simulated dotted line on the delay time axis. When radio waves are reflected at the interface between the material constituting the buried pipeline and the underground medium, measured data D1 with strong signal strength is acquired near the top end of the buried pipeline, as shown in Figure 13.

[0047] The partial pipeline estimation unit P1 detects reflected signals from buried pipelines included in the input actual measurement data D1, estimates a portion of the position of the buried pipeline, and outputs the estimated partial pipeline data to the distance data calculation unit P2 and the pipeline estimation unit P3. As a method for estimating a portion of the position of a buried pipeline from reflected signals from the buried pipeline, the method described in Patent Document 1 and, in addition to this method, various techniques for detecting the position of an object by irradiating ultrasonic waves, lasers, etc. may be used. [Example]

[0048] In the third embodiment, the pipeline management data D3" input to the pipeline estimation system S1 records at least one piece of information from among pipe type, pipe diameter, and pipe material for each of the recorded pipelines as pipe information. Then, the pipeline estimation unit P3 estimates the actual position of the pipeline using the pipe information as well. Except for these points, the system is carried out in the same manner as in the first embodiment.

[0049] An example of pipeline management data D3" containing pipe information is shown in Figure 12. As shown in Figure 12, pipe information such as pipe type, pipe diameter, and pipe material is recorded for each pipeline (Pipe A, Pipe B, etc.) recorded in the pipeline management data D3".

[0050] A method for estimating the actual location of a pipeline in the pipeline estimation unit P3 using pipe information will be described in detail. FIG. 26 shows an example of a flag list in Example 3. In Example 1, since pipe information is not necessarily included, the known distance determination results are stored in the flag list, and an estimated pipeline segment is extracted for each pipeline in the pipeline management data D3. In the flag list shown in FIG. 26, for two estimated pipeline segments, EstPipeSeg A and EstPipeSeg B, the flags for two pipelines, Pipe A and Pipe B, are set to True. Here, it is possible to evaluate the appropriateness of which pipeline to associate based on the distance, but the actual measurement data D1, which is the original data for the estimated pipeline segment data D2, has measurement errors derived from the actual measurement method.

[0051] That is, when the distance threshold shown in FIG. 10 is equal to or smaller than the measurement error resulting from the actual measurement method, the pipeline estimation unit P3 determines which pipeline the estimated partial pipeline corresponds to based on other information. Here, the explanation will be given using pipe material as an example of pipe information. Assume that information indicates that pipeline PipeA is made of ductile iron (DI) pipe and pipeline PipeB is made of polyethylene (PE) pipe, and that the actual measurement data D1 was obtained using an electrical method for the pipelines. In this case, it is clear that pipeline PipeA, which is made of metal, has a higher detection rate than pipeline PipeB, which is made of non-metal.

[0052] Therefore, as an example, the pipeline estimation unit P3 updates the flag list of estimated pipeline portions classified within the distance threshold for multiple pipelines based on whether the pipe material in the pipe information is metal or non-metal. Here, the pipeline estimation unit P3 leaves the column for Pipe A, which is made of metal, as True, and updates the column 2601 for Pipe B, which is made of non-metal, from True to False. In addition to this example, if a wavy signal is used to acquire the actual measurement data D1, the pipeline estimation unit P3 may update the flag list for pipelines that are unlikely to be measured based on the relationship between pipe diameter and wavelength, or may update the flag list based on the curvature or inclination of the pipe type. The above updating process may be performed, for example, after it is determined in step (F314) shown in FIG. 10 that all candidate pipelines in the flag list are not False (F314; No), and before the extraction of estimated pipeline portions in step (F317). By performing the above-described update process at this timing, it is possible to remove in advance pipelines that are unlikely to be correct, thereby making it possible to efficiently perform extraction in step (F317).

[0053] These pipe information items are usually recorded together with the pipeline management data, as they are determined at the time of construction planning. In Example 3, the pipeline estimation system S1 outputs estimated pipeline data D5 corresponding to the pipe information recorded in the pipeline management data D3". In other words, each estimated pipeline is recorded with its pipe information. Therefore, by displaying the estimated pipeline D5 on a display device not shown, the user can display not only the position of the estimated pipeline, but also the pipe information (25CST) corresponding to the pipeline management data D3" on the supplementary information screen (25CST), as shown in Figure 25C. [Example]

[0054] Example 4 is carried out in the same manner as pipeline estimation using the pipeline estimation system S1 described in Example 1, except that in the second process (step) F106, the pipeline estimation unit P3 calculates a weight based on the distance data D4 and performs weighted regression analysis using the weight and the estimated partial pipeline data D2.

[0055] In the weighted regression analysis, the pipeline estimation unit P3 performs regression analysis using a weighted error as explained in equation (4) instead of the error explained in equation (3).

[0056]

number

[0057] Here, wi is the weight at each point i. From equation (4), the weight is multiplied by each error, and the sum of these is Error. Therefore, by calculating and using the importance of each point i as a weight, more reasonable regression results can be obtained.

[0058] One method of calculating the weight is to take the reciprocal of the distance d(pq) recorded in the corresponding distance data D4. The distance d(p,q) is the distance from the estimated partial pipeline p to the pipeline q recorded in the pipeline management data D3, and represents the degree of deviation from the management data based on distance. In other words, the reciprocal of the distance represents the degree of agreement with the management data, so a higher importance is set. In addition to the reciprocal of the distance, a linear or nonlinear gradient can be intentionally applied to the importance by calculating the difference from a predetermined value or the power of the reciprocal.

[0059] The measured data D1 contains position errors due to the measurement means. Therefore, even if the pipeline management data D3 contains highly accurate information about the pipeline position, the estimated partial pipeline data D2 estimated from the measured data D1 may be misaligned. It is not realistic in terms of the amount of work required for a user to manually match the vast amount of pipelines contained in each data set and evaluate their validity to address this positional misalignment. In the pipeline estimation system S1 of the fourth embodiment, when the estimated partial pipeline meets a predetermined distance between the multiple pipelines recorded in the pipeline management data, the system automatically calculates the estimated pipeline by taking into account the likelihood of the estimated partial pipeline corresponding to each pipeline based on the distance.

[0060] Furthermore, because estimated pipeline segments based on actual measurement data contain position errors due to actual measurement, even if the positions of actual pipelines in the area match the positions recorded in the pipeline management data, the positions may vary. In such cases, the pipeline estimation system S1 of the fourth embodiment performs estimation by relatively increasing the weight of estimated pipeline segments that are closer to the true value, i.e., the position recorded in the pipeline management data, in terms of distance. In other words, the pipeline estimation system S1 of the fourth embodiment determines that estimated pipeline segments closer to the positions recorded in the pipeline management data from the above-mentioned perspective are more valid and important. Therefore, estimation can be achieved that automatically reflects the influence of data with high validity. From the above, the pipeline estimation system S1 of the fourth embodiment has the effect of maximizing the accuracy of the estimated pipeline position based on the distance between the estimated pipeline segment and the pipeline recorded in the pipeline management data. [Example]

[0061] FIG. 14 shows a pipeline estimation system S3 according to a fifth embodiment. In FIG. 14, parts corresponding to those in FIG. 1 are denoted by the same reference numerals. This pipeline estimation system S3 further includes an alignment unit P4, which aligns the geographical spatial position of the estimated partial pipeline data D2, the pipeline management data D3, or both. When the geographical space of the estimated partial pipeline data D2 is transformed by this alignment, the alignment unit P4 outputs aligned estimated partial pipeline data D2' to the distance data calculation unit P2 and the pipeline estimation unit P3. Similarly, when the geographical space of the pipeline management data D3 is transformed, the alignment unit P4 outputs aligned estimated partial pipeline data D3' to the distance data calculation unit P2. In addition, when both data are converted into a predetermined reference geographical space, the alignment unit P4 outputs position matching estimated partial pipeline data D2' to the distance data calculation unit P2 and the pipeline estimation unit P3, and outputs position matching estimated partial pipeline data D3' to the distance data calculation unit P2.

[0062] The alignment is achieved by processing the data using a predetermined method selected from at least one of the following: scale conversion, adding or subtracting a position offset, rotation, and coordinate reference system conversion.

[0063] (1) Scale conversion The pipeline management data D2 may have a scale that is suitable for management. Therefore, the alignment unit P4 refers to the scale and performs processing to align the ranges of the horizontal and vertical axes of the estimated partial pipeline data. Specifically, the alignment unit P4 calculates a conversion ratio ScaleB / ScaleA between the scale ScaleA of the pipeline management data D2 and the scale ScaleB of the estimated partial pipeline data D3. Furthermore, the alignment unit P4 multiplies the position (coordinates) of the pipeline management data D2 by the conversion ratio. The reciprocal of the above-mentioned conversion ratio may be multiplied by the estimated partial pipeline data D3.

[0064] (2) Addition and subtraction of position offset If the pipeline management data D2 and the estimated partial pipeline data D3 have recorded reference points (Ground Control Points, GCPs) for aligning the positions, the alignment unit P4 reads them, calculates the difference between the respective reference points, and aligns the coordinates of the data by subtracting it from one of the data. If multiple GCPs are recorded, processing may be performed using statistical values ​​such as the average value of the differences calculated for the multiple points.

[0065] (3) Rotation For example, the pipeline management data D2 is processed so that north is oriented upward for management purposes. On the other hand, the estimated partial pipeline data D3 is data in which, for example, the traveling direction of the measuring instrument is oriented upward for the convenience of actual measurement data. The alignment unit P4 performs a rotation calculation in the opposite direction to account for the difference in orientation between the two pieces of data, thereby aligning the orientations of both pieces of data.

[0066] (4) Coordinate reference system transformation Depending on the settings of the positioning device used during actual measurement, the coordinate reference systems (CRS) may differ. To ensure that the coordinate reference systems match, the two can be aligned to a predetermined standard coordinate reference system, or one can be aligned to the coordinate reference system recorded in the other. Transformations of each coordinate reference system use affine transformations, etc. The alignment unit P4 may perform transformations by using an API (Application Programming Interface) with a calculation module defined in a geographic information system (GIS) (not shown).

[0067] With this configuration, the estimated partial pipeline data D2 and the pipeline management data D3 input to the pipeline estimation system S3 of Example 5 do not need to be consistent in position with each other. In other words, there are no restrictions on the method of acquiring the actual measurement data D1 or the method of recording the positions of the sources of the pipeline management data D3, which has the effect of expanding the range of data that can be used. Furthermore, data that is not managed by the user of the system but is managed by others can also be input to the system, which has the effect of enabling businesses to make maximum use of the data acquired and managed by each business and improving the accuracy of information about the actual location of pipelines. [Example]

[0068] FIG. 18 shows the configuration of a pipeline estimation system S7 according to a sixth embodiment. In FIG. 18, the same reference numerals as those in the pipeline estimation system S1 of FIG. 1 are used. The pipeline estimation system S7 has the same configuration as the pipeline estimation system S1 of the first embodiment, except that unknown portion pipeline data D8 is added to the output of the pipeline estimation unit P3'. FIG. 15, in which the same reference numerals are used to indicate parts corresponding to those in FIG. 10, is a flowchart of the pipeline estimation unit P3' in the pipeline estimation system S8. Except for the addition of the processes F401-404 shown in FIG. 15, the same processes as those in the pipeline estimation unit P3 of the first embodiment are performed.

[0069] The pipeline estimation unit P3' refers to the flag list of Fig. 9 generated based on the distance data D4 to determine whether the distance between the estimated pipeline segment and each candidate pipeline is equal to or greater than a predetermined value. The pipeline estimation unit P3' then extracts a set B of all estimated pipeline segments containing True from the flag list of a predetermined range (F401). For example, the pipeline estimation unit P3' extracts a set B of all estimated pipeline segments containing True (e.g., EstPipeSeg A to EstPipeSeg D) from the estimated pipeline segments p corresponding to candidate pipelines (e.g., Pipe A to Pipe D) within a range specified by the user for the candidate pipeline q included in the flag list of Fig. 9.

[0070] Next, the pipeline estimation unit P3' extracts a difference set C = AB from the set A of estimated partial pipelines in a predetermined range (F402). For example, the pipeline estimation unit P3' extracts set A of estimated partial pipelines (e.g., EstPipeSeg A, EstPipeSeg B) in a range designated by the user as an output target from among the estimated partial pipelines extracted in (F401). The range designated by the user as an output target is, for example, a range of estimated partial pipelines for which all flags are True. Set A of estimated partial pipelines for which all flags in the predetermined range are True in the flag list means pipelines that are recognized as being linked in terms of distance to pipelines recorded in the pipeline management data D3. Therefore, set C means pipelines that are not recognized as being linked in terms of distance to pipelines recorded in the pipeline management data D3. The pipeline estimation unit P3' determines whether these pipelines exist, i.e., whether the set C is an empty set (F403), and if a negative result is obtained (F403; No), it outputs the included estimated partial pipelines as unknown pipeline data D8 (F404).

[0071] 16 and 17 show a schematic diagram of the calculation target and an example of a flag list serving as intermediate data when unknown pipeline data D8 is output in Example 6. In FIG. 16, the estimated pipeline segments EstPipeSeg C and EstPipeSeg D indicate that the distances to the candidate pipelines Pipe A and Pipe B, d(C,A), d(C,B), d(D,A), and d(D,B), are all False in the corresponding rows of the flag list, indicating that the distances to each candidate pipeline are greater than or equal to a predetermined value. Therefore, the estimated pipeline segments EstPipeSeg C and EstPipeSeg D are classified as unknown pipelines, recorded in unknown pipeline data D8, and output from the pipeline estimation system S7.

[0072] The unknown pipeline data D8 can be displayed, for example, as shown in 25CP' in Fig. 25C by using a display device (not shown). The unknown pipeline portion can be intuitively grasped from the pipeline management data shown in Fig. 25A.

[0073] The pipeline management data D2 is data recorded for management purposes and does not necessarily include all information about buried pipes at the time of designing new plans or construction for the area. Furthermore, the estimated partial pipeline data D2 is partial pipeline data estimated based on actual measurement data, as described in Example 1, and therefore may include data about actual pipelines that are not managed in the pipeline management data D2. By using the pipeline estimation system S7 of Example 6, a buried pipeline not listed in the management data can be identified as an unknown pipe and the estimated pipeline can be identified, which allows the user to obtain the effect of reducing construction errors. [Example]

[0074] Fig. 19 shows the configuration of a pipeline estimation system S4 according to a seventh embodiment. In Fig. 19, the same reference numerals as those in the pipeline estimation system S1 of Fig. 1 are used. The pipeline estimation system S4 has the same configuration as the pipeline estimation system S1 according to the first embodiment, except that it further receives object management data D6 including position information of surrounding objects, and that it additionally includes a correction unit P5 that receives estimated pipeline data D5 output by the pipeline estimation unit P3 and the object management data D6, corrects the estimated pipeline data D5 based on the distance between the object position and the estimated pipeline, and outputs corrected estimated pipeline data D5'.

[0075] FIG. 20 shows an example of object management data D6 input to the pipeline estimation system S7. As shown in FIG. 20, the management position of an object (here, a potted plant) is recorded as three-dimensional coordinates. The correction unit P5 calculates the distance between the estimated pipeline recorded in the estimated pipeline data D5 and the object recorded in the object management data D6. If this distance is below a certain value, the correction unit P5 considers the object and the estimated pipeline to be in contact. However, the area where the potted plant is present and the area where the estimated pipeline is located should not actually be in contact. Therefore, the correction unit P5 performs a calculation to shift the position of the estimated pipeline so that the distance between the object and the estimated pipeline is equal to or greater than a certain value, thereby correcting the position of the estimated pipeline. The correction unit P5 outputs the corrected estimated pipeline as corrected estimated pipeline data D5'. When correcting the position of the estimated pipeline, the correction unit P5 may calculate and output multiple patterns for the estimated pipeline that avoid the object. The correction method may be to shift either the start or end point of the pipeline, or to translate the entire pipeline. Alternatively, only the interfering portion may be recorded as partial data extracted from the estimated pipeline.

[0076] Users who do not use the pipeline estimation system S4 must manually associate the pipeline management data D3 with the estimated partial pipeline data D2, overlay the object management data D6, and interpret the pipeline interference and connections to make sense, which is time-consuming. The correction process in the pipeline estimation system S4 of Example 7 automates this interpretation, reducing the user's workload. Furthermore, by retaining partially extracted data for areas that interfere with surrounding objects, the user can perform a primary screening of inconsistencies between the management data and the actual measurement data D1 using the corrected estimated pipeline data D5'. This has the effect of enabling decisions to be made for secondary investigations, such as re-measurements, test drilling, or referencing other management data, based on the inconsistencies.

[0077] Furthermore, the correction method of the correction unit P5 will be described using the flowchart of FIG. 21 and FIG. 22. First, the correction unit P5 reads the input estimated pipeline EstPipe and the extrapolation range range (F201). The extrapolation range is a parameter that defines the surrounding area to which the estimated pipeline is extrapolated. Next, the correction unit P5 calculates the extrapolated estimated pipeline ext_seg by extrapolating the estimated pipeline EstPipe (y=ax+b, xs<x<xe) from the end within the range range (y=ax+b, xs-range<x<xe+range) (F202). Here, the estimated pipeline represented by a two-dimensional line segment arranged on the yx plane has been described, but this does not depend on the number of dimensions or the plane on which it is arranged. Regarding the recalculation method in the surrounding area, the extrapolation of line segments has been described in this embodiment, but this is not limited to this. Recalculation based on the surrounding area may also be performed by position shifting, rotation, interpolation, estimation, or interpolation. Furthermore, the object is not limited to the above-mentioned two-dimensional line segment (y=ax+b), but may be a three-dimensional line segment, a group of points, a curve, a curved surface, or other three-dimensional structure.

[0078] Next, the correction unit P5 reads the position of object i from the object management data D6 (F203). Here, the correction unit P5 may read only objects that exist in an area obtained by expanding the extrapolation range "range" from the area inscribed in the estimated pipeline. Next, the correction unit P5 calculates the distance between object i and the extrapolated estimated pipeline as d(i,ext_seg) (F204).

[0079] Next, the correction unit P5 determines whether the calculated distance is less than a predetermined distance threshold (F205). If the determination is negative (F205; No), the correction unit P5 reads the next object and performs the same process (F209-F204). If the determination is positive (F205; Yes), the correction unit P5 reads the estimated pipeline segment EstPipeSeg that constitutes the estimated pipeline (F206). Here, the estimated pipeline data D5 is previously recorded in association with the estimated pipeline segment data D2 used by the pipeline estimation unit P3.

[0080] Next, the correction unit P5 instructs the pipeline estimation unit P3 to re-estimate the estimated pipeline EstPipe based on the estimated partial pipeline and the position of object i. The pipeline estimation unit P3 re-estimates the estimated pipeline EstPipe in accordance with the instruction (F207). The aforementioned regression analysis method can be used for the estimation. At this time, if an area is recorded for the position of object i, a representative point within the area, such as the center of gravity or center point, may be used. Alternatively, the area may be divided into several segments, and multiple constituent points of each segment may be used. Furthermore, re-estimation may be performed with constraints to ensure that the pipeline passes through object i. Next, the correction unit P5 adds the estimated pipeline obtained by re-estimation to the corrected estimated pipeline data D5'. The correction unit P5 then reads the next object and performs the same process (F209-F204). When it is determined that calculations have been completed for all objects recorded in the object management data (if a negative result is obtained in F209, F209; No), the process ends.

[0081] Buried pipelines are used to transport water, sewage, electricity, gas, and other commodities. In the process, they typically have connection points for various processing, branching, and management. These connection points may house separately managed objects. The locations of these objects can sometimes be managed with greater accuracy than buried pipelines. For example, utility poles can serve as routes for electrical wiring from underground to aboveground, but their locations can be determined because they are exposed aboveground. Therefore, their locations can be managed with greater accuracy than buried pipelines. By correcting the estimated results of buried pipelines based on this information, more accurate estimates can be obtained. This ultimately reduces rework and improves efficiency when users use this information to plan construction projects. [Example]

[0082] Fig. 23 shows the configuration of a pipeline estimation system S6 according to an eighth embodiment. In Fig. 23, the same reference numerals as those in the pipeline estimation system S1 of Fig. 1 are used. The pipeline estimation system S6 has the same configuration as the pipeline estimation system S1 according to the first embodiment, except that it includes a drawing generation unit P6 that receives as input the estimated pipeline data D5 and pipeline management data D3 output from the pipeline estimation unit P3, generates and outputs the pipeline data to be recorded as drawing data D7.

[0083] The drawing generation unit P6 references the estimated pipeline data D5 (shown in FIG. 7) and the pipeline management data D3 (shown in FIG. 5) stored in the system's memory to generate drawing data D7 in a predetermined format. As an example, we will explain DXF (Drawing Exchange Format), which is commonly used for data exchange between different CAD software. When recording the pipelines, i.e., line segments, of the estimated pipeline data D5 (shown in FIG. 7) in DXF, the drawing generation unit P6 records the information as LINE entities. At this time, the information of each entity is recorded with an integer value called a group code. Furthermore, the drawing generation unit P6 uses the group code to specify layer names in order to classify and record the estimated pipeline data D5 and the pipeline management data D3 in a single DXF file.

[0084] Although the generation of drawing data in DXF format has been described as an example here, the data format is not limited to this. Furthermore, the drawing generation unit P6 may record the data as entities other than LINE, such as polylines, rectangles, cylinders, etc., depending on the shape of the pipeline recorded in the estimated pipeline data D5 and the pipeline management data D3.

[0085] This has the effect that, by utilizing the drawing data D7 output from the pipeline estimation system S6, the user can easily handle the estimated pipeline data D3 estimated by the pipeline estimation system D6 and the pipeline management data managed by the user himself / herself directly, i.e., by superimposing them, using CAD software (not shown) and a computer that runs it.

[0086] Furthermore, as in Example 3, when the pipeline management data D3 input to the pipeline estimation system S6 includes at least one of pipe type, pipe diameter, and pipe material information for each of the recorded pipelines, the pipeline estimation unit P3 also uses the pipe information to estimate the actual location of the pipeline. At this time, the estimated pipeline data D5 input to the drawing generation unit P6 includes pipe information corresponding to each estimated pipeline. Therefore, when recording the estimated pipeline as an entity, the drawing generation unit P6 acquires the corresponding pipe information and adds it as a comment or explanation using a predetermined group code. Alternatively, a predetermined group code may be used as layer information, and the pipe information may be recorded in the layer name. Alternatively, a predetermined group code may be used, and the thickness calculated based on the pipe diameter from the pipe information may be recorded in the line thickness information. While the method of generating the drawing data D7 as a DXF file has been illustrated here, the data format is not limited to this, and the pipe information may be recorded and output according to the supplemental information assignment method of each format.

[0087] This pipe information is usually recorded together with the pipeline management data, as it is determined at the time of construction planning. Using the drawing data D7 output by the pipeline estimation system S6, a user can use CAD software (not shown) and a computer running it to handle the estimated pipeline data D3 estimated by the pipeline estimation system D6, along with the pipe information. The pipe information can be displayed on a display device (not shown) in addition to the estimated pipeline location, as shown in Figure 25C, and the corresponding pipe information (25CST) can be displayed on a supplementary information screen (25CST).

[0088] Furthermore, Fig. 24 is a diagram showing another example of a pipeline estimation system S6. In Fig. 24, the same reference numerals as those in the pipeline estimation system S2 in Fig. 11 are used. In this example, the pipeline estimation system S6 is implemented as described in the second embodiment, and generates and outputs drawing data D7 by a drawing generation unit P6 not shown in Fig. 11.

[0089] The user can import and display management data for surrounding objects (e.g., buildings, roads, etc.) using CAD software (not shown) and a computer running the software. As shown in FIG. 25D, the drawing generation unit P6 stores each piece of information as a layer and switches the display accordingly (25DSL) and displays it in an overlapping manner (25DM). This effectively allows the user to efficiently grasp the pipeline management data, estimated pipeline data based on actual measurements, and surrounding object data for the relevant area. Furthermore, by using a display method that allows switching between FIGS. 25A-25D using tabs, buried object management can be performed by switching between the pipeline information screen 25AM, which displays pipeline management data, the estimated partial pipeline information screen 25BM, which displays estimated partial pipeline pipeline data, the estimated pipeline information screen 25CM, which displays the pipelines within the estimated pipeline data, and the pipeline management screen 25DM, which displays the overlapping management data for surrounding objects, on the buried object management screen 25.

[0090] In FIG. 25A, a pipeline 25AP in the pipeline management data is displayed on a pipeline information screen 25AM, and pipeline information 25AST is displayed on a supplementary information screen 25AS. In FIG. 25B, an estimated pipeline portion BP in the estimated pipeline portion data is displayed on an estimated pipeline portion information screen 25BM, and an estimation execution button 25BSB is displayed on a supplementary information screen 25BS, for example, to execute processing for implementing the pipeline estimation method shown in FIG. 8. In FIG. 25C, an estimated pipeline information screen 25CM displays a pipeline 25CP and an unknown pipeline 25CP' in the estimated pipeline data, and a supplementary information screen 25CS displays estimated pipeline information 25CST. In FIG. 25D, in addition to the above-mentioned pipeline 25AP and pipeline 25CP, a surrounding object 25DB is superimposed on a pipeline management screen 25DM, and a supplementary information screen 25DS displays pipeline information 25DST and a layer display switching panel 25DSL. The layer display switching panel 25DSL is an area for displaying or hiding each piece of information shown in Figures 25A to 25C (for example, the above-mentioned pipeline 25AP, pipeline 25CP, or partial pipeline BP). By switching the display of such information, the user can more easily manage buried objects.

[0091] Each embodiment has been described above with reference to the drawings. According to this system, as described in the first embodiment, for a pipeline buried underground, estimated partial pipeline data (for example, estimated partial pipeline data D2 shown in FIG. 4) having an estimated partial pipeline estimated based on actual measurement data and pipeline management data (for example, pipeline management data D3 shown in FIG. 5) including the positions of a plurality of pipelines recorded as management data are input, and at least one pipeline included in the pipeline management data is identified as a candidate pipeline (for example, Pipe A) includes a distance data calculation unit P2 that calculates the distance between each of the estimated partial pipelines contained in the estimated partial pipeline data and the position of each of the candidate pipelines and outputs corresponding distance data (e.g., distance data D4 shown in FIG. 6), a first process (e.g., first step F105 in FIG. 8) that inputs the estimated partial pipeline data and the distance data and extracts the estimated partial pipeline data that satisfies a predetermined distance for each of the candidate pipelines, a second process (e.g., second step F106 in FIG. 8) that estimates the actual location of the pipeline based on the extracted estimated partial pipeline data, and a pipeline estimation unit P3 that outputs the actual location of the pipeline estimated by the second process as estimated pipeline data (e.g., estimated pipeline data D5 shown in FIG. 7). With this configuration, it is possible to accurately match management data and estimated data based on actual measurement data regarding the actual location of a buried pipeline, and to estimate the actual location of the pipeline with high reliability.

[0092] 13 and the like, the actual measurement data is generated by irradiating radio waves from above ground to the pipeline buried underground and acquiring the reflected signals, and the partial pipeline estimation unit P1 inputs the actual measurement data and detects the reflected signals from the actual measurement data to output the estimated partial pipeline data that estimates a portion of the position of the pipeline buried underground. With this configuration, it becomes possible to estimate the position of the buried pipeline based on the reflected signals from the buried pipeline.

[0093] As explained in Example 3, FIG. 12, etc., the pipeline management data includes at least one piece of pipe information (for example, pipeline management data D3″ shown in FIG. 12) among pipe type, pipe diameter, and pipe material for each of the recorded pipelines, and the pipeline estimation unit estimates the actual position of the pipeline using the pipe information as well. With this configuration, the position of the buried pipeline can be estimated with even higher accuracy.

[0094] Furthermore, as explained using the formula (4) in Example 4, in the second processing of the pipeline estimation unit, a weight is calculated based on the distance data, and the actual position of the pipeline is estimated by weighted regression analysis using the weight and the estimated partial pipeline data. With this configuration, the position of the buried pipeline can be estimated with even greater accuracy based on the distance between the estimated partial pipeline and the pipeline recorded in the pipeline management data.

[0095] 14 and the like, the system includes a position alignment unit P4 that aligns the geographical spatial positional consistency of the pipeline management data, the estimated partial pipeline data, or both of them using at least one of scale conversion, adding / subtracting a position offset, rotation, and coordinate reference system conversion. With this configuration, there are no restrictions on the method of recording positions, and data that do not maintain positional consistency with each other can be accepted, thereby expanding the range of data that can be used with this system.

[0096] 15 to 18, the pipeline estimation unit determines whether the distance between the estimated pipeline segment and each candidate pipeline is equal to or greater than a predetermined distance, classifies a set of estimated pipeline segments for which a positive result is obtained in the determination as unknown pipeline segment data (for example, unknown pipeline segment data D8), and further outputs the unknown pipeline segment data. With this configuration, the user can easily recognize buried pipelines that are not listed in the management data as unknown pipes, thereby reducing construction errors.

[0097] 19 and 20, etc., the system further includes a correction unit P5 that inputs object management data including position information of surrounding objects (for example, object management data D6 shown in FIG. 20) and corrects the estimated pipeline data based on the distance between the object positions recorded in the object management data and the estimated pipeline. With this configuration, it is possible to obtain highly accurate estimation results that are more in line with the actual situation, allowing the user to efficiently plan construction work.

[0098] 21 and 22, the correction unit recalculates the estimated pipeline for a predetermined surrounding area, calculates the distance between the recalculated estimated pipeline and the object recorded in the object management data (for example, the distance d(i, ext_seg) shown in FIG. 22), and if there is an object whose distance from the recalculated estimated pipeline is less than a predetermined value, re-estimates the estimated pipeline from the position of the object and the partial estimated pipelines that make up the estimated pipeline. With this configuration, it is possible to obtain more accurate estimation results by taking into account the predetermined surrounding area and the positions of objects in the surrounding area.

[0099] 23 and 24, the system includes a drawing generation unit P6 that receives the estimated pipeline data and the pipeline management data, generates pipeline data recorded in the various data as drawing data, and outputs the drawing data. With this configuration, it becomes possible to represent various pipeline data recorded in the various data as drawings.

[0100] 25A to 25D, the system includes a drawing generation unit P6 that receives the estimated pipeline data and the pipeline management data, generates and outputs the pipeline information recorded in the various data as drawing data, and the drawing generation unit associates the pipe information (e.g., pipe information 25CST in FIG. 25C) with each estimated pipeline recorded in the estimated pipeline data and records it in the drawing data. With this configuration, the estimated pipeline data D3, including the pipe information, can be easily understood.

[0101] Furthermore, in the first process, the pipeline estimation unit may output data (for example, the flag list shown in FIGS. 9A and 9B) that stores the determination result of whether or not the distance between the candidate pipeline and the estimated partial pipeline satisfies a predetermined distance threshold, and display the data on a display device. With this configuration, the user can easily grasp the combination of the candidate pipeline and the estimated partial pipeline that satisfies the condition that the distance is less than the predetermined distance threshold, and can efficiently and intuitively estimate the position of the buried pipeline.

[0102] The present invention is not limited to the above-described embodiments, but includes various modifications and equivalent configurations within the spirit and scope of the appended claims. For example, the above-described embodiments have been described in detail to clearly explain the present invention, and the present invention is not necessarily limited to configurations including all of the described configurations. Furthermore, part of the configuration of one embodiment may be replaced with the configuration of another embodiment. Furthermore, the configuration of another embodiment may be added to the configuration of one embodiment. Furthermore, part of the configuration of each embodiment may be added, deleted, or replaced with other configurations. [Explanation of symbols]

[0103] D1: Actual measurement data, D2: Estimated partial pipeline data, D3, D3": Pipeline management data, D2': Position-matched estimated partial pipeline data, D3': Position-matched pipeline management data, D4: Distance data, D5: Estimated pipeline data, D5': Corrected estimated pipeline data, D6: Object management data, D7: Drawing data, D8: Unknown partial pipeline data, P1: Partial pipeline estimation unit, P2: Distance data calculation unit, P3, P3': Pipeline estimation unit, P4: Positioning unit, P5: Correction unit, P6: Drawing generation unit, S1, S2, S3, S4, S5, S6, S7: Pipeline estimation system, H1: Server, A01: Processor, A03: Storage, A02: Memory, A04: Communication I / F, M1: Pipeline estimation program, F101: Data input step, F10 2...Distance calculation step, F103...Pipeline position estimation step, F104...Data output step, F105...First step, F106...Second step, 25...Buried object management screen, 25AM...Pipeline information screen, 25AP...Pipeline in pipeline management data, 25AS...Supplementary information screen, 25AST...Pipeline information, 25BM...Estimated partial pipeline information screen, 25BP...Partial pipeline in estimated partial pipeline data, 25BS...Supplementary information screen, 25BSB...Estimation execution button, 25CM...Estimated pipeline information screen, 25CP...Pipeline in estimated pipeline data, 25CS...Supplementary information screen, 25CST...Estimated pipe information, 25DM...Pipeline management screen, 25DB...Surrounding objects, 25DS...Supplementary information screen, 25DST...Pipeline information, 25DSL...Layer display switching panel

Claims

1. For underground pipelines, estimated partial pipeline data having an estimated partial pipeline estimated based on actual measurement data; Pipeline management data including the positions of a plurality of pipes recorded as management data is input; At least one pipeline included in the pipeline management data is designated as a candidate pipeline; Regarding the estimated partial pipeline included in the estimated partial pipeline data, a distance data calculation unit that calculates the distance to each of the positions of the candidate pipelines and outputs the associated distance data; inputting the estimated partial pipeline data and the distance data; a first process of extracting the estimated partial pipeline data that satisfies a predetermined distance for each of the candidate pipelines; a second process of estimating an actual position of the pipeline based on the extracted estimated partial pipeline data; a pipeline estimation unit that outputs the actual position of the pipeline estimated by the second processing as estimated pipeline data; A pipeline estimation system characterized by:

2. the actual measurement data is generated by irradiating radio waves from the ground to the underground pipe and acquiring the reflected signals; a partial pipeline estimation unit that receives the actual measurement data, detects the reflected signal from the actual measurement data, and outputs estimated partial pipeline data that estimates a portion of the position of the pipeline buried underground; The pipeline estimation system according to claim 1 ,

3. The pipeline management data includes at least one piece of pipe information among a pipe type, a pipe diameter, and a pipe material, in association with each of the recorded pipelines, The pipeline estimation unit estimates an actual position of the pipeline using the pipeline information. The pipeline estimation system according to claim 1 ,

4. In the second processing of the pipeline estimation unit, Calculating a weight based on the distance data; By performing a weighted regression analysis using the weights and the estimated partial pipeline data, Estimating the actual location of the pipeline The pipeline estimation system according to claim 1 ,

5. The geographical spatial positional consistency of the pipeline management data or the estimated partial pipeline data or both is determined by: The device has a registration unit that aligns the data using at least one of the following methods: scale conversion, adding or subtracting a position offset, rotation, and coordinate reference system conversion. The pipeline estimation system according to claim 1 ,

6. The pipeline estimation unit determining whether the distance between the estimated partial pipeline and each candidate pipeline is equal to or greater than a predetermined distance; classifying a set of the estimated partial pipelines for which a positive result is obtained in the determination as unknown partial pipeline data; and further outputting the unknown portion of the pipeline data. The pipeline estimation system according to claim 1 ,

7. Further inputting object management data including position information of surrounding objects; a correction unit that corrects the estimated pipeline data based on the object position recorded in the object management data and the distance of the estimated pipeline; The pipeline estimation system according to claim 1 ,

8. The correction unit recalculating the estimated pipeline for a predetermined surrounding area; Calculating the distance between the recalculated estimated pipeline and the object recorded in the object management data; If there is an object whose distance from the object to the recalculated estimated pipeline is less than a predetermined value, re-estimating the estimated pipeline from the position of the object and the partial estimated pipeline that constitutes the estimated pipeline; The pipeline estimation system according to claim 7,

9. inputting the estimated pipeline data and the pipeline management data; It has a drawing generation unit that generates and outputs the pipeline data recorded in the various data as drawing data. The pipeline estimation system according to claim 1 ,

10. inputting the estimated pipeline data and the pipeline management data; It has a drawing generation unit that generates and outputs the pipeline information recorded in various data as drawing data. The pipeline estimation system according to claim 2 ,

11. inputting the estimated pipeline data and the pipeline management data; A drawing generation unit generates and outputs the pipeline information recorded in the various data as drawing data, The drawing generation unit For each estimated pipeline recorded in the estimated pipeline data, the pipe information is recorded in the drawing data in association with the estimated pipeline. The pipeline estimation system according to claim 3 ,

12. The pipeline estimation unit In the first processing, data storing a determination result as to whether or not the distance between the candidate pipeline and the estimated partial pipeline satisfies a predetermined distance threshold is output, and the data is displayed on a display device. The pipeline estimation system according to claim 1 ,

13. For underground pipelines, estimated partial pipeline data having an estimated partial pipeline estimated based on actual measurement data; a data input step of inputting pipeline management data including positions of a plurality of pipelines recorded as management data; At least one pipeline included in the pipeline management data is designated as a candidate pipeline; Regarding the estimated partial pipeline included in the estimated partial pipeline data, a distance calculation step of calculating distances to the positions of the candidate pipelines and outputting associated distance data; inputting the estimated partial pipeline data and the distance data; a first step of extracting the estimated partial pipeline data that satisfies a predetermined distance for each of the candidate pipelines; a pipeline position estimation step including a second step of estimating an actual position of the pipeline based on the extracted estimated partial pipeline data; a data output step of outputting the actual position of the pipeline estimated by the pipeline position estimation step as estimated pipeline data; A pipe line estimation method including:

14. For underground pipelines, estimated partial pipeline data having an estimated partial pipeline estimated based on actual measurement data; a data input step of inputting pipeline management data including positions of a plurality of pipelines recorded as management data; At least one pipeline included in the pipeline management data is designated as a candidate pipeline; Regarding the estimated partial pipeline included in the estimated partial pipeline data, a distance calculation step of calculating distances to the positions of the candidate pipelines and outputting associated distance data; inputting the estimated partial pipeline data and the distance data; a first step of extracting the estimated partial pipeline data that satisfies a predetermined distance for each of the candidate pipelines; a pipeline position estimation step including a second step of estimating an actual position of the pipeline based on the extracted estimated partial pipeline data; a data output step of outputting the actual position of the pipeline estimated by the pipeline position estimation step as estimated pipeline data; A pipeline estimation program that causes a computer to execute the above.

Images