Drawing program
The drawing program efficiently generates accurate vector data for conduit networks by using pipe type information from joint labels, automating the connection of point and line data, and includes error detection, addressing inefficiencies in existing methods.
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- TOHO GAS CO LTD
- Filing Date
- 2022-09-14
- Publication Date
- 2026-06-30
AI Technical Summary
Existing methods for generating vector data of conduit networks are inefficient, requiring manual labor and are costly due to the need for machine learning, and are difficult to implement across different companies using varying pipe and fitting materials.
A drawing program that utilizes pipe type information from labels on joints to automatically generate vector data by connecting point data with line data, based on image data from 3D point cloud, 3D mesh, and orthomosaic images, with error detection and correction mechanisms.
The program generates accurate vector data at a lower cost and with easier implementation than traditional methods, reducing the need for manual labor and machine learning, and is adaptable across different companies' pipe and fitting materials.
Smart Images

Figure 0007882728000001 
Figure 0007882728000002 
Figure 0007882728000003
Abstract
Description
Technical Field
[0001] The present invention relates to a drafting program that draws and outputs a completion drawing representing the laying state of a conduit network formed underground by a plurality of conduits and a plurality of joints connecting the conduits, based on pipe type information included in a label attached to the joint, using line data representing the conduits.
Background Art
[0002] Multiple conduits such as gas pipes and water pipes are connected by joints to form a conduit network underground. When the construction of the conduit network is completed, a completion drawing is created. The completion drawing is a drawing obtained by correcting the design drawing based on design changes and the like that occurred during the construction, and represents the position and the like of the actually completed conduit network. As the completion drawing, for example, vector data, 3D CAD drawings, and 2D CAD drawings are created.
[0003] Vector data is a simplified drawing that holds the laying state of the conduit network as attributes of line data for the conduits and point data for the joints. 3D CAD drawings and 2D CAD drawings are completed drawings in which the appearance of the laid conduit network and the surrounding situation (roads, buildings, etc.) are drawn.
[0004] Since there is no limit to the amount of information held in the attributes of vector data, the amount of information is equivalent to that of 3D CAD drawings and 2D CAD drawings. Also, the attributes are easy to process information-wise, and creating statistics, filtering, searching, etc. are more user-friendly than 3D CAD drawings and 2D CAD drawings. Therefore, even though it is vector data with a simple appearance, it is useful drawing data that can be traded on its own.
[0005] Vector data is created, for example, as follows: The state of the pipeline network laid during construction on a given day is photographed using a camera, and multiple digital images (for example, about 200 images for a day's work) are acquired. Then, based on these multiple digital images, 3D point cloud data, 3D mesh data, and orthophotos representing the state of the pipeline network are created. Then, based on the 3D point cloud data, 3D mesh data, or orthophotos, the positions of joints are plotted as point data, and the plotted point data are connected with line data representing the pipelines to create vector data. As described above, a system capable of creating vector data based on digital images is known, for example, the construction drawing creation support system disclosed in Patent Document 1. [Prior art documents] [Patent Documents]
[0006] [Patent Document 1] Japanese Patent Publication No. 2020-160626 [Overview of the Initiative] [Problems that the invention aims to solve]
[0007] However, the conventional techniques described above had the problem that it was difficult to automatically generate vector data, and that it took a long time to create it.
[0008] In the construction drawing creation support system disclosed in Patent Document 1, it is possible to automatically plot point data indicating joints by recognizing the codes attached to the joints. On the other hand, it is difficult to recognize how the conduits are arranged, so it is not possible to automatically and accurately draw line data. This is because computers cannot distinguish between conduit networks appearing in 3D point cloud data, 3D mesh data, and orthomosaic images and other objects (such as the ground).
[0009] Therefore, obtaining accurate vector data requires operators to manually connect point data with line data while referring to 3D point cloud data, 3D mesh data, orthomosaic images, which is inefficient. While it is possible to automatically generate vector data using a machine learning system, it is costly and requires training on a vast amount of data, making implementation difficult. Furthermore, since the pipe and fitting materials used differ from company to company, it is not easy to reuse machine learning data from other companies. For this reason, if multiple companies use the system, multiple rounds of machine learning are required.
[0010] The present invention aims to solve the above-mentioned problems and to provide a plotting program that is low-cost, easy to implement, and capable of generating accurate vector data. [Means for solving the problem]
[0011] To solve the above problems, the drawing program of the present invention has the following configuration.
[0012] (1) A drawing showing the state of the installation of a conduit network formed underground by multiple conduits and multiple joints connecting the conduits. A drawing creation support system for generating drawings Based on the pipe type information contained in the label affixed to the joint, the conduit is drawn using line data. The aforementioned completion drawings output Let In the drawing program, the pipe type information includes at least the number of connection ports for connecting the conduit of the fitting to which the label is to be affixed, and the drawing program is The aforementioned drawing creation support system , acquire image data showing the aforementioned installation status. Let The pipe type information is obtained from the code captured in the image data. Let Based on the position of the code captured in the image data, the positions of the multiple joints are identified. Let , the specific Let Depending on their position, each of the multiple joints is plotted as point data on the completed drawing. Let This involves recognizing the two point data points that are furthest apart from the aforementioned point data, namely the endpoint data. Let The line data is drawn starting from one of the two endpoint data points. Let Based on the pipe type information, the connectable point data are sequentially connected using the line data. Let thing, To generate the aforementioned completion drawings, It is characterized by the following.
[0013] Image data refers to, for example, 3D point cloud data, 3D mesh data, orthomosaic images, and is generated in advance before the creation of the completion drawings (vector data). Furthermore, whether or not point data can be connected can be determined based on the read pipe type information, by checking whether the pipe type of the conduit that can be connected to the connection port 211 is the same for the joints corresponding to each point data, and whether or not the diameter of the connection port is the same.
[0014] (2) The drawing program described in (1) is characterized in that the number m (where m is an integer of 2 or more) of the connection ports of the joint corresponding to the data of both ends included in the pipe type information is set to the number (m-1) and the drawing of the line data is started.
[0015] (3) The drawing program described in (1) or (2) is characterized in that, after drawing the line data from a predetermined first point data to a predetermined second point data among the point data, it is checked whether there is any point data that is closest to the joint corresponding to the second point data and corresponds to a connectable joint, and that is not connected to the second point data by the line data.
[0016] (4) The drawing program described in any one of (1) to (3) is characterized in that it includes an error prevention step for detecting drawing errors before outputting the completed drawing, the error prevention step recognizes the number of conduit network groups drawn in the completed drawing, determines that a drawing error has occurred if the number of groups is two or more, and determines that no drawing error has occurred if the number of groups is one, and outputs the completed drawing. [Effects of the Invention]
[0017] By having the above configuration, the drawing program of the present invention can generate accurate vector data at a lower cost and with easier introduction than the drawing work by an operator or a system using machine learning.
Brief Description of the Drawings
[0018] [Figure 1] It is a block diagram showing the configuration of a drawing creation support system using the drawing program according to this embodiment. [Figure 2] It is a diagram showing an example of a state where a conduit network is photographed using a photographing device. [Figure 3] It is a diagram showing an example of the laying state of a conduit network. [Figure 4] It is a diagram showing the flow in which the drawing program creates a completion drawing. [Figure 5] It is a diagram for explaining the generation process of a completion drawing by the drawing program. [Figure 6] It is a diagram for explaining the generation process of a completion drawing by the drawing program. [Figure 7] It is a diagram for explaining the generation process of a completion drawing by the drawing program. [Figure 8] It is a diagram for explaining the generation process of a completion drawing by the drawing program. [Figure 9] It is a diagram for explaining the generation process of a completion drawing by the drawing program. [Figure 10] It is a diagram for explaining the generation process of a completion drawing by the drawing program. [Figure 11] It is a diagram for explaining the generation process of a completion drawing by the drawing program. [Figure 12] It is a diagram for explaining the generation process of a completion drawing by the drawing program. [Figure 13] It is a diagram for explaining the generation process of a completion drawing by the drawing program. [Figure 14] It is a diagram for explaining the generation process of a completion drawing by the drawing program. ][Modes for carrying out the invention]
[0019] Embodiments of the drawing program of the present invention will be described in detail with reference to the drawings. Figure 1 is a block diagram showing the configuration of a drawing creation support system 1 that utilizes the drawing program according to this embodiment. Figure 2 is a diagram showing an example of photographing the conduit network 2 using the photographing device 11. Figure 3 is a diagram showing an example of the laid state of the conduit network 2. Figure 4 is a diagram showing the flow of the drawing program creating the completion drawing. Figures 5 to 14 are diagrams illustrating the process of generating the completion drawing D11 by the drawing program.
[0020] The drawing creation support system 1 stores a drawing program in the processing unit 16 and is a system for creating completion drawings that show the laid state of the conduit network 2 (see Figure 3).
[0021] Conduit network 2 is, for example, part of a supply network for supplying gas to consumers, and was laid in a single day of construction. As shown in Figure 3, conduit network 2, consisting of conduits 20A-20F and fittings 21A-21F, forms a roughly T-shaped network as a whole, and is laid in an installation trench 30a created in the ground 30 by civil engineering work. Conduits 20 are, for example, gas pipes, and all are of the same type. However, this is merely an example, and multiple types of conduits may be used.
[0022] Fittings 21A, 21B, 21C, 21E, and 21F each have two connection ports 211, allowing for the linear connection of conduits 20. Fitting 21D has three connection ports 211, enabling the branching of the conduit network 2. The diameter of the connection ports 221 of fittings 21A-21F is the same for all of them. A two-dimensional code 40 is affixed to the surface of fittings 21A-21F.
[0023] The two-dimensional code 40 contains information (hereinafter referred to as pipe type information) regarding the number of connection ports for connecting conduits to the fitting to which the two-dimensional code 40 is attached, the type of conduit that can be connected to the connection ports, and the diameter of the connection ports. The processing unit 16, described later, can acquire the pipe type information by recognizing the two-dimensional code 40 captured in the digital image. Note that the two-dimensional code 40 does not necessarily need to include all of the information regarding the number of connection ports for connecting conduits, the type of conduit that can be connected to the connection ports, and the diameter of the connection ports. For example, if it is assumed that all conduits 20 used in the conduit network 2 are of the same type, then vector data can be generated by the drawing program as long as the two-dimensional code 40 contains information regarding the number of connection ports for connecting conduits. Furthermore, the two-dimensional code 40 is not particularly limited, but any code that can include pipe type information is acceptable. For example, the two-dimensional code disclosed in Japanese Patent Application Publication No. 2020-160626 may be used, or a QR code (registered trademark) may be used.
[0024] As shown in Figure 1, the drawing creation support system 1 is connected to a camera 11, a positioning device 12, and a communication terminal 18 via a communication line 19 such as the Internet.
[0025] The imaging device 11 is a digital camera used by workers at a construction site to photograph the laying status of the conduit network 2. As shown in Figure 2, the imaging device 11 is equipped with a handle 11a. This allows workers at the construction site to photograph the conduit network 2 laid in the installation trench 30a from above while standing on the ground 30. This photography acquires digital images showing the laying status of the conduit network 2. Approximately 200 digital images are taken per day of construction. The imaging device 11 can then transmit the captured digital images to the drawing creation support system 1 via the communication line 19.
[0026] Since a two-dimensional code 40 (see Figure 3), which is an example of a code, is affixed to the surface of the joint 21 that constitutes the conduit network 2, the two-dimensional code 40 is also captured in the digital image acquired by the imaging device 11.
[0027] In this embodiment, the worker takes the photographs using the photographing device 11, but the photographing device 11 may also be mounted on a remotely controlled unmanned aerial vehicle such as a drone, and photographs may be taken from above. Furthermore, the worker may take the photographs while holding the photographing device 11 in their hand. In this case, the photographing position will be lower than when using the handle 11a or a drone, and the photographing range will be narrower, so the number of photographs will be greater than when using the handle 11a or a drone.
[0028] The positioning device 12 acquires absolute coordinates within at least the area captured by the imaging device 11 for the purpose of topographic surveying or joint position surveying using GPS or the like. The positioning device 12 can then transmit the information regarding the acquired absolute coordinates to the drawing creation support system 1 via the communication line 19.
[0029] As shown in Figure 1, the drawing creation support system 1 consists of a communication unit 13, a registration unit 14, a database 15, a processing unit 16, and a communication unit 17.
[0030] The communication unit 13 receives digital images and information regarding absolute coordinates transmitted from the imaging device 11 and the positioning device 12. The information received by the communication unit 13 is then registered in the database 15 by the registration unit 14.
[0031] Database 15 contains registered information on digital images and absolute coordinates, as well as pipe type information. This allows the corresponding pipe type information to be retrieved from Database 15 by querying the pipe type information contained in the 2D code 40.
[0032] The processing unit 16 comprises an image determination unit 161 and a drawing generation unit 162. The image determination unit 161 determines whether the digital image captured by the shooting device 11 is usable in the drawing creation support system 1 based on whether the shooting environment is appropriate, and then determines whether the digital image meets predetermined standards.
[0033] The determination of whether the shooting environment is appropriate is made based on five criteria: equipment type, illumination difference, flash guide number, shutter speed, and ISO value. In addition, the predetermined criteria are determined based on the captured digital images, based on six criteria: brightness, sharpness, shooting interval, overlap rate between digital images, and subject position. These determination processes are described in detail, for example, in Japanese Patent Publication No. 2020-160626. While it is desirable that all images taken in a day meet the criteria, in cases where high accuracy in drawing is not required, such as when the drawings are used only as reference drawings, it may be possible to generate drawings even if some digital images do not meet the criteria.
[0034] The drawing generation unit 162 creates 3D point cloud data, 3D mesh data, and orthophotos based on digital images that the image determination unit 161 has determined to meet predetermined criteria. Furthermore, it creates vector data as an as-built drawing based on any of the 3D point cloud data, 3D mesh data, or orthophotos.
[0035] Three-dimensional point cloud data is a three-dimensional image of the conduit network 2 drawn from a collection of points, and can represent the layout of the conduit network 2 with high accuracy. The created three-dimensional point cloud data is stored in database 15.
[0036] 3D mesh data is created by meshing 3D point cloud data and converting it into polygon data, thereby rendering a 3D image of the conduit network 2. Because the data size is smaller than that of 3D point cloud data, the laying status of the conduit network 2 can be easily checked even on a general-purpose computer. The created 3D mesh data is stored in database 15.
[0037] An orthophoto is an image obtained by orthorectification. Since the digital image captured by the imaging device 11 is a central projection, distortion occurs in the image due to differences in distance from the center of the lens of the imaging device 11 to the object being photographed. An orthophoto is obtained by converting such a central projection image to an orthorectification and correcting the distortion. By generating an orthophoto with corrected distortion, it becomes possible to accurately measure the positions of gas pipes 20 and fittings 21 that constitute the conduit network 2 on the orthophoto. The created orthophoto is stored in the database 15.
[0038] Furthermore, the above-mentioned 3D point cloud data, 3D mesh data, and orthomosaic images (hereinafter referred to as image data) are generated with information regarding absolute coordinates obtained by the positioning device 12. Therefore, it is possible to obtain the latitude and longitude information of any point arbitrarily selected in the image data. Furthermore, since the above-mentioned 3D point cloud data, 3D mesh data, and orthophotos are generated by combining multiple digital images, they display the configuration of the conduit network beyond the range that can be captured by a single digital image. For example, since approximately 200 digital images are taken during a day of construction, combining these makes it possible to obtain 3D point cloud data, 3D mesh data, and orthophotos that display the configuration of the conduit network over a wide range (e.g., a range of several meters to tens of meters). Naturally, the number of construction days is not limited to one day, nor is the number of digital images limited to 200.
[0039] Next, vector data is a simplified diagram of the conduit network layout by storing information in the attributes of point data and line data. The drawing generation unit 162 stores the drawing program shown in Figure 4, and generates vector data according to this program as follows. Here, we will explain using an example of generating vector data representing the conduit network 2 shown in Figure 3.
[0040] First, one of the following is obtained from database 15: 3D point cloud data, 3D mesh data, or orthomosaic image (hereinafter referred to as image data) (S1 in Figure 4). The choice of which of the 3D point cloud data, 3D mesh data, or orthomosaic image to obtain can be automatically selected from a predetermined set, or it can be selected by the operator each time.
[0041] From the acquired image data, the 2D code 40 depicted in the image data is recognized, and the pipe type information corresponding to the recognized 2D code 40 is read out (S2 in Figure 4).
[0042] Next, the location of the 2D code 40 in the image data is recognized. This is done based on absolute coordinate information obtained from topographic surveying, which is included in the image data, or based on absolute coordinates obtained from joint location surveying. Then, based on the recognized location, point data PD11-PD16 corresponding to joints 21A-21F are plotted on the as-built drawing D11 (S3 in Figure 4). Figure 5 shows the state where point data PD11-PD16 are plotted on the as-built drawing D11. Point data PD11 corresponds to joint 21A, point data PD12 corresponds to joint 21B, point data PD13 corresponds to joint 21C, point data PD14 corresponds to joint 21D, point data PD15 corresponds to joint 21E, and point data PD16 corresponds to joint 21F.
[0043] The numbers indicated within the circles for point data PD11-PD16 in Figure 5 represent the number of connection ports 211 in the fitting 21A-21F corresponding to point data PD11-PD16. This number of connection ports 211 is obtained by reading the pipe type information from the 2D code 40. Note that, for the sake of clarity, the number of connection ports 211 is shown within the circles for point data PD11-PD16 here, but it is not necessarily required to display it on the completion drawing D11.
[0044] Next, from the point data PD11-PD16 plotted on the as-built drawing D11, the two points furthest apart, which are the endpoint data, are identified (S4 in Figure 4). Among the point data PD11-PD16, the two points furthest apart are point data PD11 and point data PD12, and these two points are the endpoint data.
[0045] In this embodiment, the method for recognizing the endpoint data involves automatically recognizing the two points furthest apart from the positional relationship of the plotted point data PD11-PD16. However, it is not always necessary to automatically recognize the endpoint data; for example, the two-dimensional code 40 attached to the joints 21A and 21B may include information that indicates the endpoint data. Alternatively, the operator may specify the endpoint data each time.
[0046] When the endpoint data is recognized, the number m (where m is an integer greater than or equal to 2) of the connection ports 211 of the joints corresponding to the endpoint data is processed as the number (m-1) (S4 in Figure 4). In other words, although the number of connection ports 211 of the joints 21A and 21B corresponding to the endpoint data (point data PD11, PD12) is actually two, it is processed as one. Accordingly, as shown in Figure 6, the numbers inside the circles for point data PD11 and PD12 on the completion drawing D11 are changed from 2 to 1.
[0047] Next, one of the endpoint data is selected as the source point data from which the line data is to be drawn, and the line data is drawn from that source point data toward the nearest point data that can be connected (destination point data) (S5 in Figure 4). In this embodiment, of the endpoint data points PD11 and PD12, point data PD11 is selected as the source point data. And point data PD13 is selected as the destination point data. Therefore, as shown in Figure 7, the line data LD11a is drawn from point data PD11 toward point data PD13.
[0048] Whether point data PD11-PD16 can be connected to each other is determined based on the read pipe type information, specifically by checking whether the pipe type of the conduit that can be connected to the connection port 211 of each point data PD11-PD16 is the same for the fittings 21A-21F, and whether the diameter of the connection port 211 is the same. In this embodiment, all conduits 20 are of the same type, and the inner diameter of the connection port 211 of the fittings 21A-21F is the same for all. Therefore, when point data PD11 is used as the source point data, based on the pipe type information, it is determined that all point data PD12-PD16 can be connected to point data PD11. Among the connectable point data PD12-PD16, point data PD13 is the closest, so point data PD13 is selected as the destination point data.
[0049] Next, we check for the presence of a point data (second point data) that is the closest and connectable to the destination point data (point data PD13) but is not connected to the destination point data (point data PD13) (S6 in Figure 4). The closest and connectable point data to the destination point data (point data PD13) is point data PD14. Furthermore, since point data PD14 is not connected to the destination point data (point data PD13) by line data, it is an unconnected point data. Therefore, it is determined here that there is a point data that is connectable to the destination point data (point data PD13) and is the closest point data, but is not connected to the destination point data (point data PD13) (S6: YES in Figure 4).
[0050] Next, the connection point data and the second connection point data are connected by line data, and the previous connection is canceled (S7 in Figure 4). Here, as shown in Figure 8, the point data P13, which is the connection point data, and the point data P14, which is the second connection point data, are connected by line data LD12, and the previously made connection between point data PD11a and point data PD13 is canceled (i.e., line data LD11a is deleted).
[0051] Next, we check whether there are any unconnected connection ports 211 in the source point data (S8 in Figure 4). Here, although it is recognized that the number of connection ports in the point data PD11, which is the source point data, is 1, since the line data LD11a has been deleted earlier, it is determined that there are unconnected connection ports in the point data PD11 (S8 in Figure 4: YES).
[0052] Next, a connection is made from the source point data to the nearest point data that can be connected (the destination point data) (S9 in Figure 4). However, this does not apply if it would intersect with line data already drawn on the completion drawing D11, or if a loop would occur in the connection relationship between the point data. In this case, the source point data is point data PD11, and the nearest point data that can be connected is point data PD13. Therefore, point data PD13 is recognized as the destination point data. Even if point data PD11 and point data PD13 are connected, it will not intersect with the already drawn line data LD12, and no loop will occur in the connection relationship between point data PD11-PD16. Therefore, as shown in Figure 9, line data LD11b is drawn from point data PD11 to point data PD13, and point data PD11 and point data PD13 are connected.
[0053] Next, we check whether there are any points that can be connected without intersecting with line data already drawn on the as-built drawing D11 or creating loops in the connection relationships between point data (S10 in Figure 4). Here, as shown in Figure 9, there are point data PD12, PD15, and PD16 that are not connected to any other point data, so it is determined that there are (S10 in Figure 4: YES).
[0054] Next, the system checks for the presence of a second point data (point data PD13) that is connected to the destination point data (point data PD13) and is located at the closest possible position, but is not connected to the destination point data (point data PD13) (S6 in Figure 4). As shown in Figure 9, the point data that is connected to the destination point data (point data PD13) and is located at the closest position is point data PD14, but point data PD14 is already connected to the destination point data (point data PD13) by line data LD12. Therefore, it is determined that there is no second point data (S6 in Figure 4: NO).
[0055] Next, we check whether there are any unconnected connection ports in the source point data (S8 in Figure 4). Here, as shown in Figure 9, the number of connection ports in the source point data, point data PD11, is recognized as one. Since point data PD11 and point data PD13 are already connected by line data LD11, it is determined that there are no unconnected connection ports 211 in point data PD11 (S8: NO in Figure 4).
[0056] Next, check whether there are any unconnected joints among the point data PD11-PD16 plotted on the as-built drawing D11 (S11 in Figure 4). Specifically, check for point data that has no line data connected at all, or point data to which fewer line data than the number of connection ports are connected.
[0057] As shown in Figure 9, point data PD11 is recognized as having one connection port 211, but line data L11b has already been drawn (i.e., the same number of line data as the number of connection ports are connected), so there are no connection ports 211 left that can be connected. Therefore, it does not correspond to an "unconnected joint" in S11 in Figure 4. Similarly, point data PD12 also does not correspond to an "unconnected joint" because there are no connection ports 211 left that can be connected. On the other hand, point data PD12, PD14, PD15, and PD16 either have no line data connected at all, or have fewer line data connected than the number of connection ports 211, so there are connection ports 211 left that can be connected. Therefore, point data PD12, PD14, PD15, and PD16 correspond to "unconnected joints". Thus, it is determined that there are unconnected joints here (S11 in Figure 4: YES).
[0058] Next, a new "source point data" is selected from the "unconnected joints" to begin drawing the line data, and the line data is drawn from this source point data toward the nearest point data (destination point data) that is connectable (S12 in Figure 4). However, this does not apply if it would intersect with line data already drawn on the completion drawing D11, or if a loop would occur in the connection relationships between point data. As the new "source point data," a point data adjacent to the "source point data" up to this point is selected. Since point data PD13, which is adjacent to point data PD11 (the "source point data" up to this point), is already connected, the further adjacent point data PD14 is selected as the new "source point data." The nearest point data that is connectable to the source point data (point data PD14) is point data PD15. Even if point data PD14 and point data PD15 are connected, it will not intersect with the already drawn line data LD11b, LD12, and no loop will occur in the connection relationships between point data PD11-PD16. Therefore, using point data PD15 as the "connection point data," line data LD13 is drawn from point data PD14 to point data PD15, as shown in Figure 10, thereby connecting PD14 and PD15.
[0059] Next, we check whether there are any points that can be connected without creating loops in the connection relationships between point data, or any points that intersect with line data already drawn on the as-built drawing D11 (S10 in Figure 4). Here, as shown in Figure 10, there are point data PD12 and PD16 that are not connected to any other point data, so it is determined that there are (S10 in Figure 4: YES).
[0060] Next, the system checks for the presence of a second point data (point data PD15) that is the closest and connectable point data, but is not connected to the first point data (point data PD15) (S6 in Figure 4). As shown in Figure 10, the closest and connectable point data to the first point data (point data PD15) is point data PD14, but point data PD14 is already connected to the first point data (point data PD15) by line data LD13. Therefore, it is determined that there is no second point data (S6 in Figure 4: NO).
[0061] Next, we check whether there are any unconnected connection ports in the source point data (S8 in Figure 4). Here, as shown in Figure 10, the point data PD14, which is the source point data, is recognized to have 3 connection ports. Two line data LD12 and LD13 are connected to point data PD14, leaving one connection port 211 unused. Therefore, it is determined that there is an unconnected connection port 211 in point data PD14 (S8 in Figure 4: YES).
[0062] Next, the connection is made from the source point data to the nearest point data that can be connected (the destination point data) (S9 in Figure 4). However, this does not apply if it would intersect with line data already drawn on the completion drawing D11, or if a loop would occur in the connection relationships between the point data. In the completion drawing D11, the point data closest to the source point data, point data PD14, is point data PD15. However, since point data PD15 is already connected to point data PD14 by line data LD13, the next closest point data PD12 takes priority, and point data PD12 is recognized again as the "destination point data". Even if point data PD14 and point data PD12 are connected, it will not intersect with the already drawn line data LD11b, LD12, LD13, and a loop will not occur in the connection relationships between point data PD11-PD16. Therefore, as shown in Figure 11, line data LD14 is drawn from point data PD14 to point data PD12, connecting point data PD14 and point data PD12.
[0063] Next, we check whether there are any points that can be connected without creating loops in the connection relationships between point data, or any points that intersect with line data already drawn on the as-built drawing D11 (S10 in Figure 4). Here, as shown in Figure 11, there is point data PD16 that is not connected to any other point data, so it is determined that there are (S10 in Figure 4: YES).
[0064] Next, the system checks for the presence of a second point data (point data PD12) that is connected to the destination point data (point data PD12) and is located at the closest possible position, but is not connected to the destination point data (point data PD12) (S6 in Figure 4). As shown in Figure 11, the point data that is connected to the destination point data (point data PD12) and is located at the closest position is point data PD14, but point data PD14 is already connected to the destination point data (point data PD12) by line data LD14. Therefore, it is determined that there is no second point data (S6 in Figure 4: NO).
[0065] Next, we check whether there are any unconnected connection ports in the source point data (S8 in Figure 4). Here, as shown in Figure 11, the point data PD14, which is the source point data, is recognized to have 3 connection ports. However, since 3 line data LD12, LD13, and LD14 are already connected, it is determined that there are no unconnected connection ports in the point data PD14 (S8: NO in Figure 4).
[0066] Next, we check whether there are any unconnected joints among the point data plotted on the as-built drawing D11 (S11 in Figure 4). Point data PD15 and PD16 either have no line data connected at all, or have fewer line data connected than the number of connection ports, so there are still connectable connection ports. Therefore, they correspond to "unconnected joints". Thus, it is determined that there are unconnected joints here (S11 in Figure 4: YES).
[0067] Next, a new "source point data" is selected from the "unconnected joints" to begin drawing the line data, and the line data is drawn from this source point data toward the nearest point data (destination point data) that is connectable (S12 in Figure 4). However, this does not apply if the line data intersects with line data already drawn on the completion drawing D11, or if a loop occurs in the connection relationships between the point data. As the new "source point data," a point data adjacent to the "source point data" up to this point is selected, and in this case, point data PD15, adjacent to point data PD14, which is the "source point data" up to this point, is selected as the new "source point data." In the completion drawing D11, the point data closest to the source point data (point data PD15) is point data PD14. However, since point data PD14 is already connected to point data PD15 and line data LD13, the next closest point data PD16 takes priority, and point data PD16 is recognized again as the "destination point data." Furthermore, even if point data PD15 and point data PD16 are connected, they will not intersect with the already drawn line data LD11b, LD12, LD13, and LD14, and no loops will be created in the connection relationship between point data PD11 and PD16. Therefore, as shown in Figure 12, line data LD15 is drawn from point data PD15 to point data PD16, and point data PD15 and point data PD16 are connected.
[0068] Next, we check whether there are any points that can be connected without intersecting with line data already drawn on the as-built drawing D11 or creating loops in the connection relationships between point data (S10 in Figure 4). Here, as shown in Figure 12, all point data PD11-PD16 are already connected, and there are still points that can be connected, so it is determined that there are "none" (S10: NO in Figure 4).
[0069] Next, the number of groups formed by the point and line data drawn on the as-built drawing is recognized (S13 in Figure 4). This is a step to prevent drawing errors. If there is one group, it is determined that there are no drawing errors (S13 in Figure 4: 1 group), and the vector data is output (S14 in Figure 4), after which the drawing program terminates. On the other hand, if there are two or more groups, it is determined that there are drawing errors (S13 in Figure 4: 2 or more groups), and the vector data is regenerated.
[0070] Here, as shown in Figure 12, there is one group formed by the point data PD11-PD16 and line data LD11-LD15 on the completion drawing D11. Therefore, the drawing program outputs the vector data in the state shown in Figure 12 (S14 in Figure 4) and terminates its operation. The output vector data (Figure 12) accurately represents the laying state of the conduit network 2 shown in Figure 3.
[0071] Here, we will explain what happens when a drawing error occurs. For example, the completed drawing D12 shown in Figure 13 is the result of a drawing error that occurred when attempting to generate vector data for the conduit network 2 shown in Figure 3. Specifically, the network is configured as two separate groups: one with connected point data PD11 and PD16, and the other with connected point data PD12, PD13, and PD14. This does not accurately represent the laying state of the conduit network 2. When such vector data is generated, a drawing error is detected at S13 in Figure 4 (S13 in Figure 4: 2 or more groups). The cause of the error is insufficient connections between groups, and the error can be suppressed by prioritizing the connection of those missing connections.
[0072] Then, a connection is made from a point data with an unconnected connection port in one of the two or more groups to a connectable point data in another group (S15 in Figure 4). When there are multiple connectable point data, the closest one is prioritized. Specifically, in the two groups in the as-built drawing D12 in Figure 13, in the group formed by point data PD11 and point data PD16, point data PD16 is recognized as having two connection ports based on pipe type information, but since only one line data is connected, it is determined that there is an unconnected connection port. On the other hand, there are multiple point data in the other group that can be connected to point data PD16. Therefore, here, line data LD15 is drawn from point data PD16, which has an unconnected connection port, to point data PD15, which is the closest connectable point data, and point data PD16 and point data PD15 are connected. Next, the process returns to S5 in Figure 4, and the process from S5 to S15 in Figure 4 is repeated until accurate vector data is generated. When returning to S5 in Figure 4, as indicated by "the second round connects in reverse," drawing begins with the point data at each endpoint that was different from the point data used for line data drawing in the first S5 process. In other words, if line data drawing started from point data PD11 in the first S5 process, when returning to S5 from S15 in Figure 4, line data drawing will start from point data PD12. This prevents drawing errors from occurring again.
[0073] Furthermore, in Figure 4, step S15 states "reconnect from the second round onwards." This means that when the process of S5-S15 in Figure 4 is repeated, if S15 in Figure 4 is reached for the second time or later, all line data drawn in the previous S15 will be drawn, and new connections will be made. Specifically, if line data LD15 is drawn in the first S15, in the second S15, line data LD15 will be drawn, and a connection will be made from point data with an unconnected connection port in one group to connectable point data in another group (for example, connecting point data PD11 to point data PD13). Note that this step of drawing all line data drawn in the previous S15 does not necessarily have to be performed in step S15; it may be performed before S15, for example.
[0074] The vector data output by the drawing program is stored in database 15. Note that the layout of the conduit network 2 may also be drawn using not only point data and line data, but also surface data and body data.
[0075] The drawing generation unit 162 may also generate 3D CAD drawings or 2D CAD drawings based on vector data.
[0076] 3D CAD is a method of drawing a 3D image of the conduit network 2 using a 3D function. Based on vector data, fittings are drawn on the point data plotted on the vector data, and conduits 20 are drawn on the line data connecting the point data to generate a 3D CAD drawing. At this time, the types of conduits 20 and fittings 21 to be drawn are identified based on the pipe type information represented by the 2D code 40. Because the drawn content is easy to edit, for example, the drawn conduits 20 and fittings 21 can be moved, enlarged, reduced, short-circuited, extended, etc. on the drawing, and it is possible to consider future renovations on the drawing.
[0077] Two-dimensional CAD drawings refer to plan views, cross-sectional views, and side views that represent the layout of a conduit network. Based on vector data, two-dimensional CAD drawings are generated by drawing joints on point data plotted on the vector data and drawing conduits 20 on line data connecting the point data. At this time, the types of conduits 20 and joints 21 to be drawn are identified based on pipe type information represented by a two-dimensional code 40.
[0078] Furthermore, the drawing generation unit 162 may also be capable of generating geographic information system data by linking 3D CAD drawings and 2D CAD drawings with a geographic information system. Geographic information system data is a visualization of the pipeline network's laying status on a map based on 3D CAD drawings and 2D CAD drawings, and records all the laying status of pipelines and other infrastructure from past construction work. The generation of geographic information system data can be used not only for future pipeline network renovation work, but also for sewer pipe construction and other projects where the location of buried pipelines must be taken into consideration.
[0079] As shown in Figure 1, the drawing creation support system 1 is connected to a communication terminal 18 via a communication line 19. The communication terminal 18 is a tablet or similar device held by a worker on site. The processing unit 16 of the drawing creation support system 1 can transmit the results determined by the image determination unit 161 and the drawings generated by the drawing generation unit 162 to the communication terminal 18 via the communication unit 17. By receiving the determination results from the image determination unit 161 on the communication terminal 18, the worker on site can determine whether or not it is necessary to retake the image using the shooting device 11, depending on the determination result. In addition, by receiving the drawings generated by the drawing generation unit 162, it is also possible to create a construction daily report on the communication terminal 18 using the received drawings.
[0080] As described above, according to the drawing program of this embodiment (S1-S15 in Figure 4), (1) a drawing program that outputs an as-built drawing D11 representing the laid state of a conduit network 2 constructed underground by a plurality of conduits 20A-20G and a plurality of joints 21A-21F connecting the conduits 20A-20G to each other, is drawn using line data LD11-LD15 representing the conduits 20A-20G based on the pipe type information contained in the code (2D code 40) attached to the joints 21A-21F, wherein the pipe type information includes at least the number of connection ports 211 for connecting the conduits 20A-20G of the joint 21A-21F to which the code (2D code 40) is attached, and the drawing program takes image data (e.g., 3D point cloud data, 3D mesh data, orthoimage) that displays the laid state. The method is characterized by obtaining pipe type information from a code (2D code 40) captured in the image data, identifying the locations of multiple joints 21A-21F based on the location of the code (2D code 40) captured in the image data, plotting each of the multiple joints 21A-21F as point data PD11-PD16 on the completion drawing D11 according to the identified location, recognizing the two point data points that are furthest apart from the point data PD11-PD16, which are the endpoint point data (point data PD11, PD12), starting from point data PD11 of the endpoint point data (point data PD11, PD12), starting the drawing of line data LD11-LD15, and sequentially connecting connectable point data PD11-PD16 using line data LD11-LD15 based on the pipe type information.
[0081] The plotting program described in (1) recognizes the endpoint data (point data PD11, PD12) as shown in S4-S5 in Figure 4, for example, and starts drawing the line data LD11-LD15, using one of the point data PD11 as the starting point. By defining a starting point and starting the drawing of line data in this way, drawing errors in the line data are less likely to occur, and accurate vector data can be generated. The plotting program in this embodiment generates vector data by repeating the process in S5-S15 in Figure 4, but by defining a starting point, unnecessary repetitions are avoided, making it possible to generate vector data quickly.
[0082] (2) The drawing program described in (1) is characterized in that the number m (where m is an integer of 2 or more, and in this embodiment it is 2) of the connection ports 211 of joints 21A and 21B corresponding to the end point data (point data PD11 and PD12) included in the pipe type information is set as the number (m-1) and the drawing of line data LD11-LD15 is started.
[0083] The drawing program described in (2) starts drawing line data LD11-LD15 by reducing the number of connection ports 211 of joints 21A and 21B corresponding to the endpoint data (point data PD11, PD12) from m=2 to m-1=1, as shown in S4 in Figure 4 and Figure 6. By reducing the number of connection ports of the endpoint data by one before starting to draw the line data in this way, drawing errors are less likely to occur, and accurate vector data can be generated. The drawing program in this embodiment generates vector data by repeating the process in S5-S15 in Figure 4, but by defining the starting point, unnecessary repetitions are avoided, making it possible to generate vector data quickly.
[0084] (3) The drawing program described in (1) or (2) is characterized in that, after drawing line data LD11-LD15 from a predetermined first point data (connection source point data) to a predetermined second point data (connection destination point data) among the point data PD11-PD16, it checks for the presence or absence of point data (second connection destination point data) that is closest to the joint corresponding to the second point data (connection destination point data) and corresponds to a connectable joint, but is not connected to the second point data (connection destination point data) by line data.
[0085] The drawing program described in (3) checks for the presence of a point data (second connection point data) that is closest to the joint corresponding to the connection point data and corresponds to a connectable joint, and is not connected to the connection point data by line data, as shown in S6 in Figure 4. By checking for the presence of second connection point data in this way, drawing errors are less likely to occur, and accurate vector data can be generated.
[0086] (4) The drawing program described in any one of (1) to (3) includes an error prevention step (S13) for detecting drawing errors before outputting the completed drawing D11, characterized in that the error prevention step recognizes the number of conduit network groups drawn in the completed drawing D11, determines that a drawing error has occurred if the number of groups is two or more, and determines that no drawing error has occurred if the number of groups is one, and outputs the completed drawing.
[0087] The drawing program described in (4) recognizes the number of conduit network groups drawn in the completion drawing D11, for example, as shown in S13 in Figure 4. If the number of groups is two or more, it determines that a drawing error has occurred, and if the number of groups is one, it determines that no drawing error has occurred. The cause of the error is insufficient connections between groups, and it is possible to suppress the error by prioritizing the connection of those groups.
[0088] The above embodiments are merely illustrative and do not limit the present invention in any way. Therefore, the present invention can naturally be improved and modified in various ways without departing from its essence. For example, the pipeline network 2 is not limited to supplying gas to consumers, but may also be for supplying water.
[0089] Furthermore, in S3 of Figure 4, the position of the 2D code 40 is recognized based on absolute coordinates contained in the image data, but this is not necessarily limited to this. For example, the position of the 2D code 40 may be recognized based on relative coordinates based on marks arbitrarily placed on the ground or structures that appear in the image data. In this case, information about the length of a single conduit or the length of a laid conduit network is obtained in advance, or a ruler is projected into the image data. Based on these lengths, the scale of the image data is calculated, and then the point data PD11-PD16 are plotted. [Explanation of Symbols]
[0090] 1. Drawing creation support system 20A-20G conduit 21A-21F Fitting 40. Two-dimensional code (an example of a code) 211 connection ports D11 As-built drawing LD11-LD15 Line Data
Claims
1. In a drawing creation support system for generating a completion drawing that shows the state of installation of a conduit network formed underground by multiple conduits and multiple joints connecting the conduits, a drawing program outputs the completion drawing, which is drawn using line data representing the conduits based on the pipe type information contained in the labels attached to the joints, The pipe type information includes, at a minimum, the number of connection ports for connecting the conduit of the fitting to which the label is to be affixed. The drawing program is provided to the drawing creation support system. Acquire image data showing the aforementioned installation status. From the code captured in the image data, the pipe type information is obtained. Based on the position of the symbols shown in the image data, the positions of the multiple joints are identified, and each of the multiple joints is plotted as point data on the completed drawing according to the identified position. From the point data, the two point data points that are furthest apart are identified as endpoint data, one of the endpoint data points is used as the starting point to begin drawing the line data, and the connectable point data points are sequentially connected using the line data based on the pipe type information. To generate the aforementioned completion drawings, A drawing program characterized by the following:
2. In the drawing program described in claim 1, The number m (where m is an integer of 2 or more) of the connection ports of the joint corresponding to the data of both ends, included in the pipe type information, is set to (m-1) and the drawing of the line data is started. A drawing program characterized by the following:
3. In the drawing program according to claim 1 or 2, After drawing the line data from a predetermined first point data to a predetermined second point data among the point data, To check for the presence or absence of point data corresponding to a joint that is closest to and connectable to the joint corresponding to the second point data, and that is not connected to the second point data by the line data. A drawing program characterized by the following:
4. In the drawing program according to claim 1 or 2, Before outputting the aforementioned completion drawings, an error prevention step is provided to detect drawing errors. The error prevention step recognizes the number of conduit network groups depicted in the as-built drawings. If the number of such groups is two or more, it should be determined that a drawing error has occurred. If there is only one group, it is determined that no drawing error has occurred, and the completed drawing is output. A drawing program characterized by the following: