Damage diagram creation support device

The damage diagram creation support device addresses the inefficiencies and inaccuracies in conventional inspection methods by using color analysis to create structured damage diagrams, enhancing the precision and efficiency of damage assessment.

JP7830404B2Active Publication Date: 2026-03-16FUJIFILM CORP
View PDF 9 Cites 0 Cited by

Patent Information

Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2023-09-21
Publication Date
2026-03-16

AI Technical Summary

Technical Problem

Conventional inspection methods for structures, such as bridges, result in a high burden on inspection technicians and are prone to mistakes in creating damage diagrams due to the lack of standardized use of chalk colors for marking damage, making it difficult for third parties to interpret the information accurately.

Method used

A damage diagram creation support device that includes an image acquisition unit, marking detection unit, and damage diagram creation unit, which analyzes color markings to create structured damage diagrams by referring to stored information on marking colors, degrees of damage, and other inspection parameters.

Benefits of technology

Enables efficient and accurate creation of damage diagrams by detecting and classifying markings by color, reducing human error and allowing for standardized interpretation of inspection results.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007830404000001
    Figure 0007830404000001
  • Figure 0007830404000002
    Figure 0007830404000002
  • Figure 0007830404000003
    Figure 0007830404000003
Patent Text Reader

Abstract

To provide a damage diagram creation support device capable of efficiently creating a damage diagram by using color of marking.SOLUTION: A color-photographed image of a surface of a structure is acquired. The acquired image is analyzed, and marking applied to a damaged portion on the surface of the structure is detected for each color. A damage diagram is created based on detection results of the marking for each color. The damage diagram is configured by a diagram that traces the marking and has a layer structure for each color.SELECTED DRAWING: Figure 13
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to a damage diagram creation support device, and more particularly to a damage diagram creation support device that supports the creation of a damage diagram based on the inspection results of a structure.

Background Art

[0002] Structures such as bridges are inspected regularly. The inspection work is divided into field work (on-site work) and office work (office work). In field work, inspection technicians go to the site and perform work such as close visual inspection (approaching the inspection location to a distance close enough to touch the focused part and visually inspecting it) (so-called close visual inspection). At this time, based on the visual confirmation results, the inspection technician performs operations such as marking (drawing a line with chalk along the damage (also called deformation)), sketching, and taking pictures (taking pictures of the on-site situation). In office work, a report is created based on the sketches and photos obtained at the site. The report includes a damage diagram (also called a deformation diagram), and the inspection technician writes the damage location into the drawing for each inspection location (for example, a drawing of industrial data such as CAD (Computer-Aided Design)) based on the sketches and photos to create a damage diagram.

[0003] However, the conventional inspection work performed in such a procedure has problems that the burden on inspection technicians is large, and mistakes (such as omissions) are likely to occur in the creation of damage diagrams.

[0004] Therefore, in Patent Document 1, a technique for automatically detecting markings, cracks, etc. from an image of the surface of a concrete structure is proposed. In addition, in Patent Document 2, a technique for making it easier to detect the marked locations from the photographed image by spraying a water retention agent on the surface of the concrete structure after marking is proposed.

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

[0006] Incidentally, marking is generally done using chalk, and inspection technicians sometimes use different colors of chalk for marking. For example, they may use different colors depending on the extent of the damage, the type of damage, and the timing of the inspection. On the other hand, since there are no specific regulations regarding the colors of chalk to be used, a drawback is that if a third party tries to create a damage diagram based on the results of on-site work, they cannot utilize the information from the marking colors.

[0007] This invention has been made in view of these circumstances, and aims to provide a damage diagram creation support device that can efficiently create damage diagrams using marking colors. [Means for solving the problem]

[0008] The means to solve the above problems are as follows:

[0009] (1) A damage diagram creation support device comprising: an image acquisition unit that acquires a color image of the surface of a structure; a marking detection unit that analyzes the image and detects markings applied to damaged areas on the surface of the structure by color; and a damage diagram creation unit that creates a damage diagram based on the detection results of the markings by color.

[0010] (2) The damage drawing creation support device of (1) above, further comprising a storage unit for storing information specified for each marking color, wherein the damage drawing creation unit creates a damage drawing by referring to the information stored in the storage unit.

[0011] (3) The damage diagram creation support device described in (2) above, wherein the memory unit stores information on the degree of damage defined for each marking color, and the damage diagram creation unit creates a damage diagram that classifies the degree of damage by referring to the information stored in the memory unit.

[0012] (4) The storage unit stores information on the degree of cracking defined for each marking color, and the damage diagram creation unit creates damage diagrams that classify the degree of cracking, as described in (3) above.

[0013] (5) The storage unit stores information on the degree of water leakage and / or free lime specified for each marking color, and the damage diagram creation unit creates damage diagrams that classify the degree of water leakage and / or free lime, as described in (3) or (4) above, a damage diagram creation support device.

[0014] (6) A damage diagram creation support device according to any one of (3) to (5) above, wherein the memory unit stores information on the degree of peeling and / or reinforcement exposure defined for each marking color, and the damage diagram creation unit creates a damage diagram classified by the degree of peeling and / or reinforcement exposure.

[0015] (7) A damage diagram creation support device according to any one of (2) to (6) above, wherein the memory unit stores information on the type of damage defined for each marking color, and the damage diagram creation unit creates a damage diagram classifying the type of damage by referring to the information stored in the memory unit.

[0016] (8) A damage diagram creation support device according to any one of (2) to (7) above, wherein the memory unit stores information on the inspection timing specified for each marking color, and the damage diagram creation unit refers to the information stored in the memory unit and creates damage diagrams classified by inspection timing.

[0017] (9) A damage diagram creation support device according to any one of (2) to (7) above, wherein the memory unit stores information on the inspection timing specified for each marking color, and the damage diagram creation unit refers to the information stored in the memory unit and creates damage diagrams for each inspection timing.

[0018] (10) A damage diagram creation support device according to any one of (2) to (9) above, wherein the memory unit stores information on at least one of the degree of cracking, the degree of corrosion, and the degree of deterioration of the corrosion protection function of the steel member, as defined for each marking color, and the damage diagram creation unit creates a damage diagram that classifies at least one of the degree of cracking, the degree of corrosion, and the degree of deterioration of the corrosion protection function of the steel member by referring to the information stored in the memory unit.

[0019] (11) A method for creating a damage diagram, comprising the steps of: acquiring a color image of the surface of a structure; analyzing the image and detecting markings applied to damaged areas on the surface of the structure by color; and creating a damage diagram based on the detection results of the markings by color.

[0020] (12) A damage diagram creation support program that enables a computer to perform the following functions: acquiring color images of the surface of a structure, analyzing the images to detect markings applied to damaged areas on the surface of the structure by color, and creating a damage diagram based on the detection results of the markings by color.

[0021] (13) A damage diagram creation support system including a user terminal and a server, wherein the user terminal comprises a terminal-side image input unit for inputting color images of the surface of a structure, a terminal-side transmission unit for transmitting images to a server, and a terminal-side receiving unit for receiving damage diagrams created based on the images from the server, and the server comprises a server-side receiving unit for receiving images from the user terminal, a marking detection unit for analyzing the images and detecting markings applied to damaged areas on the surface of the structure by color, a damage diagram creation unit for creating damage diagrams based on the detection results of markings by color, and a server-side transmission unit for transmitting damage diagrams to the user terminal. [Effects of the Invention]

[0022] According to the present invention, the color of markings can be detected from color images of the surface of a structure, and damage diagrams can be efficiently created by performing image analysis. [Brief explanation of the drawing]

[0023] [Figure 1] System configuration diagram showing an embodiment of a damage diagram creation support system [Figure 2] Block diagram showing an example of the hardware configuration of a user terminal [Figure 3] Block diagram of the main functions of a user terminal [Figure 4] Block diagram showing an example of the hardware configuration of a server [Figure 5] Block diagram of the main functions of a server [Figure 6] Perspective view of a bridge seen from below [Figure 7] Diagram showing an example of marking [Figure 8] Diagram showing an example of the shooting procedure of a floor slab [Figure 9] Diagram showing an example of the shooting procedure in one compartment [Figure 10] Flowchart showing the processing procedure for creating a damage diagram using the damage diagram creation support system of the present embodiment [Figure 11] Diagram showing an example of a photographed image of a compartment marked with multi - colored chalk [Figure 12] Diagram showing the detection result of marking [Figure 13] Diagram showing an example of a damage diagram [Figure 14] Block diagram of the main functions of the user terminal of the damage diagram creation support system of the present embodiment [Figure 15] Block diagram of the main functions of the server of the damage diagram creation support system of the present embodiment [Figure 16] Diagram showing an example of a damage diagram classified according to the degree of cracking [Figure 17] Table showing an example of the evaluation criteria for cracking [Figure 18] Diagram showing an example of a damage diagram classified according to the degree of water leakage [Figure 19] Diagram showing an example of a damage diagram classified according to the degree of free lime [Figure 20] Table showing an example of the evaluation criteria for water leakage and free lime [Figure 21] This diagram shows an example of damage diagrams classified according to the degree of reinforcement bar exposure. [Figure 22] Table showing an example of evaluation criteria for peeling and reinforcement bar exposure. [Figure 23] A diagram showing an example of the structure of a damage diagram. [Figure 24] A diagram showing an example of how damage is represented on a damage diagram. [Figure 25] This diagram shows an example of damage diagrams classified by type of damage. [Figure 26] This diagram shows an example of how damage diagrams are structured, categorized by inspection timing. [Modes for carrying out the invention]

[0024] Preferred embodiments of the present invention will be described in detail below with reference to the attached drawings.

[0025] 《First Embodiment》 [System Configuration of the Damage Diagram Creation Support System] Figure 1 is a system configuration diagram showing one embodiment of a damage diagram creation support system.

[0026] The damage diagram creation support system 10 of this embodiment consists of a user terminal 20 that performs front-end processing and a server 30 that performs back-end processing. The user terminal 20 and the server 30 are connected to each other via a network 40 so that they can communicate with one another. For example, the internet is used for the network 40.

[0027] [User terminal] The user terminal 20 consists of a general-purpose computer such as a personal computer, tablet computer, or smartphone.

[0028] Figure 2 is a block diagram showing an example of the hardware configuration of a user terminal. As shown in the figure, the user terminal 20 is configured with a CPU (Central Processing Unit) 21, RAM (Random Access Memory) 22, ROM (Read Only Memory) 23, HDD (Hard Disk Drive) 24, communication IF (Interface) 25, input device 26, output device 27, and optical disk drive 28, etc. The HDD 24 stores the program necessary for front-end processing and various data necessary for that processing. The input device 26 consists of, for example, a keyboard, mouse, touch panel, etc. The output device 27 consists of, for example, a display, printer, etc. The user terminal 20 is connected to the network 40 via the communication IF 25.

[0029] Figure 3 is a block diagram of the main functions of the user terminal.

[0030] The user terminal 20 performs front-end processing such as receiving input images of the structure to be inspected, sending (uploading) the input images to the server 30, receiving (downloading) the processing results from the server 30, outputting the received processing results, and recording the received processing results. To this end, as shown in Figure 3, the user terminal 20 has the functions of a terminal-side image input unit 20A that receives image input, a terminal-side transmission unit 20B that sends the input images to the server 30, a terminal-side reception unit 20C that receives processing results from the server 30, a terminal-side output unit 20D that outputs the received processing results, and a terminal-side recording unit 20E that records the received processing results. These functions are realized by the computer constituting the user terminal 20 executing a predetermined program.

[0031] The terminal-side image input unit 20A processes the input of an image taken of the object to be inspected. The terminal-side image input unit 20A receives an image from an external device such as a digital camera via the communication IF 25. This image is a color image of the surface of the structure to be inspected. Therefore, it is a color image. Specifically, it is an image (a so-called RGB image) that has intensity values ​​(luminance values) for R (red), G (green), and B (blue) at the pixel level.

[0032] The terminal-side transmission unit 20B processes the input image to be sent (uploaded) to the server 30. The terminal-side transmission unit 20B sends the image to the server 30 via the network 40.

[0033] The terminal-side receiving unit 20C performs processing to receive processing results from the server 30. The terminal-side receiving unit 20C receives processing results from the server 30 via the network 40. As described later, the server 30 creates a damage diagram (also called a deformation diagram) based on the image transmitted from the user terminal 20. The created damage diagram is transmitted to the user terminal 20 as a processing result. The terminal-side receiving unit 20C receives (downloads) this damage diagram transmitted from the server 30.

[0034] The terminal output unit 20D performs processing to output the processing results. Specifically, it outputs the damage diagram, which is the processing result, to the display, which is the output device 27. In addition, if necessary, it outputs the input image to the display, which is the output device 27.

[0035] The terminal-side recording unit 20E performs processing to record the processing results. Specifically, it records the damage diagram, which is the processing result, to the HDD 24. At this time, it records the original image in association with the diagram.

[0036] [server] Server 30 consists of a general-purpose server computer. Server 30 essentially constitutes a damage diagram creation support device.

[0037] Figure 4 is a block diagram showing an example of the server's hardware configuration. As shown in the figure, the server 30 is configured with a CPU 31, RAM 32, ROM 33, HDD 34, communication interface 35, input device 36, output device 37, and optical disk drive 38, etc. The HDD 34 stores the programs necessary for backend processing and various data necessary for that processing. The input device 36 consists of, for example, a keyboard, mouse, touch panel, etc. The output device 37 consists of, for example, a display, printer, etc. The server 30 is connected to the network 40 via the communication interface 35.

[0038] Figure 5 is a block diagram of the main functions of the server.

[0039] The server 30 performs backend processing such as receiving images transmitted from the user terminal 20, panoramic stitching of divided image groups when images taken of inspection areas are received, analyzing images to detect markings applied to the surface of structures by color, creating damage diagrams based on the marking detection results, and transmitting the created damage diagrams to the user terminal 20 as processing results. Therefore, as shown in Figure 5, the server 30 has functions such as a server-side receiving unit 30A that receives images from the user terminal 20, a panoramic stitching unit 30B that panoramic stitches the divided image groups, a marking detection unit 30C that detects markings from images, a damage diagram creation unit 30D that creates damage diagrams based on the marking detection results, and a server-side transmitting unit 30E that transmits the created damage diagrams to the user terminal 20. These functions are realized by the computer constituting the server 30 executing a predetermined program. This program essentially constitutes a damage diagram creation support program.

[0040] The server-side receiving unit 30A processes images transmitted from the user terminal 20. The server-side receiving unit 30A receives images from the user terminal 20 via the network 40. The server-side receiving unit 30A is an example of an image acquisition unit. The received images are stored in the HDD 34. Images can also be acquired as images taken by dividing the inspection area. In this case, the panoramic stitching unit 30B performs the following panoramic stitching.

[0041] When the panoramic stitching unit 30B receives images taken by dividing the inspection area into sections, it performs a process to stitch the divided image groups together into a panorama. Since panoramic stitching itself is a well-known technique, a detailed explanation will be omitted. For example, the panoramic stitching unit 30B detects corresponding points between images and stitches the divided image groups together. At this time, the panoramic stitching unit 30B applies corrections such as scaling correction, tilt correction, and rotation correction to each image as necessary.

[0042] When photographing inspection points in sections, the photographer (inspection technician) should ensure that adjacent images overlap.

[0043] The marking detection unit 30C analyzes the image and performs a process to detect markings by color. For example, if markings are made in two colors, white and red, the marking detection unit 30C detects the markings in the image separately for white and red. Various methods can be used to detect markings. For example, a method can be used to detect markings by color using a trained model that has been machine-trained using images containing markings of multiple colors as training data. The type of machine learning algorithm is not particularly limited, and algorithms using neural networks such as RNN (Recurrent Neural Network), CNN (Convolutional Neural Network), or MLP (Multilayer Perceptron) can be used. Alternatively, for example, a method can be used to detect markings by color based on the brightness distribution and RGB value distribution of the image. Since the areas with markings have different brightness distributions and RGB value distributions than other areas, markings can be detected by color from the image by searching for changes in brightness and RGB values.

[0044] The damage diagram creation unit 30D performs a process to create a damage diagram based on the marking detection results. The damage diagram is created as a traced diagram of the markings detected from the image and is created by classifying it by color. For example, it is created in a layer structure with different colors.

[0045] The server-side transmission unit 30E processes the creation of the damage diagram and sends it to the user terminal 20. The server-side transmission unit 30E transmits the damage diagram to the user terminal 20 via the network 40.

[0046] [How to create damage diagrams] Next, a method for creating damage diagrams using the damage diagram creation support system 10 of this embodiment (damage diagram creation support method) will be described. Here, the example will be that of inspecting a bridge, particularly the bridge deck.

[0047] [Bridges] Figure 6 is a perspective view of the bridge from below.

[0048] The bridge 1 shown in the figure has a three-dimensional structure comprising a main girder 2, a transverse girder 3, a bracing 4, a transverse bracing 5, and a deck slab 6, and these members are connected by bolts, rivets, welding, etc.

[0049] A deck slab 6 is poured on top of the main girders 2, etc., for vehicles to run on. The deck slab 6 is generally made of reinforced concrete. The main girders 2 are members that span between abutments or piers and support the load of vehicles, etc. on the deck slab 6. The main girders 2 have a surface (vertical surface) perpendicular to the surface (horizontal plane) of the deck slab 6. The transverse girders 3 are members that connect the main girders 2. The transverse girders 3 are provided to support the load with multiple main girders 2. The bracing 4 and transverse bracing 5 are members that connect the main girders 2 to each other. The bracing 4 and transverse bracing 5 are provided to resist lateral loads from wind and earthquakes, respectively.

[0050] [Bridge inspection] Generally, inspections of the deck slab 6 are carried out in units of corrugations. A corrugation is a section of the deck slab 6 that is divided by the main girders 2 and the transverse girders 3.

[0051] In the inspection using the damage diagram creation support system 10 of this embodiment, field work (on-site work) is performed, which includes marking and taking photographs at the site. Then, based on the photographs (images) obtained during the field work, damage diagrams are created as office work.

[0052] [marking] Marking is the process of drawing lines with chalk along cracks or other damage (also called deformation).

[0053] Figure 7 shows an example of marking. This figure illustrates an example of marking cracks that appear on the surface of a structure.

[0054] As shown in Figure 7, marking is done by drawing a line M with chalk along the cracks that appear on the surface of the structure. In addition, damage such as water leakage, free lime, spalling, and exposed rebar is marked by drawing a line along the outer edge of the damaged area. Furthermore, information (letters and symbols, etc.) indicating the state of the damage is added as needed.

[0055] [photo shoot] Figure 8 shows an example of the procedure for photographing the deck slab.

[0056] As described above, inspections of the deck slab are carried out on a per-section basis. A per-section GO is one section divided by the main girders 2 and cross girders 3. Therefore, photography is also carried out for each per-section GO. Figure 8 shows how each per-section GO is photographed while moving sequentially in the y and x directions (the arrows in the figure indicate the direction of movement). In Figure 8, the longitudinal direction of the deck slab 6 (direction of the main girders 2) is denoted as x, the direction perpendicular to x within the plane of the deck slab 6 (direction of the cross girders 3) is denoted as y, and the direction perpendicular to the deck slab 6 (vertical downward direction) is denoted as z.

[0057] Figure 9 shows an example of the shooting procedure in one cell.

[0058] If the entire area of ​​the GO grid cannot be captured in a single shot, or if a high-resolution image cannot be obtained even if it can be captured, the shooting area is divided and captured in multiple shots. In Figure 9, the frame indicated by symbol A represents the area to be captured in a single shot. The example shown in Figure 9 shows how each area within the GO grid is captured while sequentially moving in the y and x directions.

[0059] The photographer (inspection technician) faces the floor slab being inspected and takes photographs from a fixed distance. Furthermore, adjacent areas are photographed so that they partially overlap (for example, overlapping by 30% or more). This allows for high-precision stitching when creating a panoramic image.

[0060] The photography will be done using a digital camera capable of color photography.

[0061] [Creating damage diagrams] Here, we will explain using the example of creating a damage diagram for a single GO (Gate Assembly).

[0062] Figure 10 is a flowchart showing the processing procedure for creating a damage diagram using the damage diagram creation support system of this embodiment.

[0063] First, images are input on the user terminal 20 (step S1). If a single GO is divided into multiple images and captured, all captured images are input.

[0064] Next, the input image is sent (uploaded) to the server 30 (step S2). If one GO is divided into multiple parts for shooting, for example, all the captured images are stored in one folder and sent.

[0065] Server 30 receives the image sent from user terminal 20 (step S3). The received image is stored in HDD 34.

[0066] Server 30 determines whether panoramic stitching is necessary based on the received images (step S4). If multiple images have been received, it determines that panoramic stitching is necessary.

[0067] When server 30 determines that panoramic stitching is necessary, it performs the panoramic stitching process (step S5). Panoramic stitching yields a single image of the GOs taken between each section.

[0068] Next, the server 30 detects markings from the captured images of the interlocking GOs (step S6). The markings are detected by color.

[0069] Figure 11 shows an example of a photograph taken between cells marked with multiple colors of chalk.

[0070] In the image I shown in the figure, the grid GO is marked using two different colors of chalk depending on the degree of damage. Specifically, cracks with a width of less than 0.2 mm are marked with white chalk, and cracks with a width of 0.2 mm or more are marked with red chalk. In Figure 11, the code MR indicates a marking made with red chalk, and the code MW indicates a marking made with white chalk. Server 30 analyzes image I and detects markings for each color.

[0071] Figure 12 shows the results of marking detection.

[0072] The figure shows the detected markings traced with lines. In the figure, the code LR represents the line tracing the marking detected as a red marking, and the code LW represents the line tracing the marking detected as a white marking. For convenience, in the figure, the line LR tracing the red marking is shown as a thick line, and the line LW tracing the white marking is shown as a thin line, to make it easier to distinguish between the two.

[0073] After detecting the markings, as shown in Figure 10, the server 30 creates a damage diagram based on the detection results (step S7). The damage diagram is created as a traced diagram of the markings detected from the image. In this embodiment, a damage diagram with a layered structure classified by color is created.

[0074] Figure 13 shows an example of a damage diagram.

[0075] The figure shows an example of a damage diagram between cells marked in two colors, white and red. In this case, a damage diagram DF is created, comprising a first layer L1 and a second layer L2. The first layer L1 consists of a damage diagram traced from the white markings. The second layer L2 consists of a damage diagram traced from the red markings. Damage diagram DF is composed of a diagram created by superimposing the first layer L1 and the second layer L2.

[0076] Furthermore, it is preferable to use different line types and / or different colors for the lines traced by the markings in each layer so that they can be distinguished from each other when the layers are superimposed. For example, the same color as the detected color can be used.

[0077] By constructing the damage diagram DF with a layered structure for each color, the markings applied to the inspection points (in this example, the spaces between the gates) can be identified by color.

[0078] After creating the damage diagram, the server 30 sends the created damage diagram to the user terminal 20, as shown in Figure 10 (step S8).

[0079] The user terminal 20 receives (downloads) the damage diagram sent from the server 30 as a processing result (step S9). Then, it outputs the received damage diagram to the output device 27 (step S10). Specifically, it displays it on the display, which is the output device 27. It also records the received damage diagram to the HDD 24 (step S11). At this time, the user terminal 20 records the damage diagram in association with the photographic data that was used to create the damage diagram.

[0080] The process of creating damage diagrams based on the captured images is completed through the above series of steps. The user (inspection technician) then creates an inspection report based on the acquired damage diagrams. At this time, since data for damage diagrams for each marking color is obtained, reports can be created efficiently if each marking color has a specific meaning. For example, if different chalk colors are used for marking according to the degree of damage, individual damage diagrams corresponding to the degree of damage can be obtained (by switching layers, damage diagrams for each degree of damage can be obtained). On the other hand, the color of the chalk used for marking may also be changed according to the color of the concrete. For example, a chalk color that stands out against the color of the concrete may be selected for marking (for example, red chalk may be used on light-colored concrete, and white chalk on dark-colored concrete). In such cases, a damage diagram with each layer superimposed is used. This allows for the creation of damage diagrams without being affected by color. On the other hand, during marking, the marking work can be carried out efficiently without being affected by the color of the concrete. Furthermore, when detecting markings from images, markings can be detected with high accuracy.

[0081] 《Second Embodiment》 This embodiment describes a case in which damage diagrams are automatically classified using marking color information.

[0082] In this embodiment of the damage diagram creation support system, information on the meaning of each color in the color-coded markings is obtained from the user, and this information on the meaning of each color is used to create a damage diagram that classifies the damage information.

[0083] [User terminal] Figure 14 is a block diagram of the main functions of the user terminal of the damage diagram creation support system of this embodiment.

[0084] As shown in the figure, the user terminal 20 of this embodiment differs from the user terminal 20 in the damage diagram creation support system 10 of the first embodiment in that it further has the function of a marking color information input unit 20F. Therefore, only the differences will be explained here.

[0085] The marking color information input unit 20F processes the input of information about the meaning of each marking color (marking color information) when the markings are color-coded. The marking color information input unit 20F inputs information about the meaning of each marking color via the input device 26. For example, if cracks with a width of less than 0.2 mm are marked with white chalk and cracks with a width of 0.2 mm or more are marked with red chalk, the information input would be that "white" represents "cracks with a width of less than 0.2 mm" and "red" represents "cracks with a width of 0.2 mm or more".

[0086] When the terminal-side transmitting unit 20B transmits the input image to the server 30, it also transmits the marking color information to the server 30 at the same time.

[0087] [server] Figure 15 is a block diagram of the main functions of the server of the damage diagram creation support system in this embodiment.

[0088] As shown in the figure, the server 30 (damage diagram creation device) of this embodiment differs from the server 30 of the damage diagram creation support system 10 of the first embodiment in that it further has the function of a marking color information storage unit 30F. Therefore, only the differences will be explained here.

[0089] The marking color information transmitted from the user terminal 20 is received by the server-side receiving unit 30A and stored in the marking color information storage unit 30F. The marking color information storage unit 30F is composed of, for example, an HDD 34.

[0090] When creating a damage diagram, the damage diagram creation unit 30D refers to the information stored in the marking color information storage unit 30F to create a damage diagram that classifies the damage information.

[0091] [Example of creating a damage diagram] (1) When different marking colors are used depending on the degree of damage. In this case, a damage diagram is created that classifies the damage according to its degree. The user inputs information on the degree of damage for each color (marking color information) into the user terminal 20. The input marking color information is sent to the server 30 and stored in the marking color information storage unit 30F of the server 30. The server 30 refers to this marking color information and creates a damage diagram that classifies the damage according to its degree.

[0092] (A) When different marking colors are used depending on the degree of cracking. In this case, the color of the chalk used is determined by the degree of the crack. For example, cracks with a width of less than 0.2 mm are marked with white chalk, and cracks with a width of 0.2 mm or more are marked with red chalk. The user inputs the color of the chalk used (the color of the marking) and the meaning of that color (information about the degree of the crack) into the user terminal 20. For example, the user inputs into the user terminal 20 that "white" represents "cracks with a width of less than 0.2 mm" and "red" represents "cracks with a width of 0.2 mm or more".

[0093] As described above, markings are detected by color. Server 30 creates a damage diagram based on the detection results of markings by color and the color information of the markings. The damage diagram creates, for example, a damage diagram with a layered structure classified by the degree of damage.

[0094] Figure 16 shows an example of a damage diagram classified according to the degree of cracking.

[0095] The figure shows an example of a damage diagram between cells where cracks with a width of less than 0.2 mm are marked with white chalk, and cracks with a width of 0.2 mm or more are marked with red chalk. In this case, a damage diagram DF is created, comprising a first layer L1 and a second layer L2. The first layer L1 consists of a damage diagram with cracks with a width of less than 0.2 mm marked. This damage diagram consists of a damage diagram traced from the white markings. The second layer L2 consists of a damage diagram with cracks with a width of 0.2 mm or more marked. This damage diagram consists of a damage diagram traced from the red markings. Damage diagram DF is composed of a diagram with the first layer L1 and the second layer L2 superimposed.

[0096] Each layer is labeled with information about the classified damage. For example, the first layer L1 is labeled with If1, indicating that it is the result of detecting cracks with a width of less than 0.2 mm. The second layer L2 is labeled with If2, indicating that it is the result of detecting cracks with a width of 0.2 mm or more. Damage diagram DF, which is a composite of the first layer L1 and the second layer L2, is labeled with If0, indicating that it is the result of detecting all cracks.

[0097] Furthermore, it is preferable to use different line types and / or different colors for the lines tracing the markings on each layer so that they can be distinguished from each other when the layers are superimposed. For example, the same color as the detected color can be used.

[0098] In this example, by using different marking colors according to the degree of cracking, the information from these marking colors can be used to automatically create damage diagrams classified by the degree of cracking. This allows for the efficient creation of inspection reports.

[0099] Regarding cracks, damage can also be evaluated according to predetermined evaluation criteria, and the cracks can be marked using different colors according to that evaluation. In this case, based on the detection results of the markings detected for each color, a damage diagram classified by color (a damage diagram layered by color) can be created, thereby automatically generating a damage diagram classified according to the evaluation criteria. In addition to criteria established independently, criteria established by the national government, local governments, and companies can be used for judgment criteria. For example, regarding bridge inspections, the criteria stipulated in the Bridge Periodic Inspection Guidelines prescribed by the Ministry of Land, Infrastructure, Transport and Tourism can be used.

[0100] Figure 17 is a table showing an example of criteria for evaluating cracks.

[0101] In the example shown in the figure, the degree of crack damage is evaluated on a five-point scale (a, b, c, d, e) by combining the degree of maximum crack width (large, medium, small) and the degree of minimum crack spacing (large, small).

[0102] When marking, use different colors of chalk according to the evaluation category (a, b, c, d, e). For example, use white chalk for category b, blue chalk for category c, yellow chalk for category d, and red chalk for category e to mark the damaged area.

[0103] When creating damage diagrams, create diagrams categorized by marking color. This allows for the automatic creation of damage diagrams categorized by damage evaluation category.

[0104] (B) When different marking colors are used depending on the degree of water leakage. In this case, the color of the chalk used will vary depending on the degree of water leakage. For example, normal water leaks will be marked with white chalk, and water leaks accompanied by rust stains will be marked with red chalk. The user inputs the color of the chalk used (the marking color) and the meaning of that color (information about the degree of water leakage) into the user terminal 20. For example, the user inputs into the user terminal 20 that "white" means "normal water leakage" and "red" means "water leakage accompanied by rust stains".

[0105] Server 30 creates a damage diagram of the layer structure classified according to the degree of water leakage, based on the detection results of markings for each color and the information of the marking colors.

[0106] Figure 18 shows an example of a damage diagram classified according to the degree of water leakage.

[0107] The figure shows an example of a damage diagram between sections where normal leak locations are marked with white chalk and leak locations accompanied by rust stains are marked with red chalk. In this case, a damage diagram DF is created, comprising a first layer L1 and a second layer L2. The first layer L1 consists of a damage diagram marking normal leak locations. This damage diagram consists of a traced white marking. The second layer L2 consists of a damage diagram marking leak locations accompanied by rust stains. This damage diagram consists of a traced red marking. Damage diagram DF is composed of a diagram in which the first layer L1 and the second layer L2 are superimposed.

[0108] Each layer is labeled with information about the classified damage. For example, the first layer L1 is labeled with If1, indicating that it is a normal water leak. The second layer L2 is labeled with If2, indicating that it is a water leak accompanied by rust stains. The damage diagram DF, which is a combination of the first layer L1 and the second layer L2, is labeled with If0, indicating that it is the detection result for all water leak locations.

[0109] In this example, by using different marking colors according to the degree of water leakage, the information from these marking colors can be used to automatically create damage diagrams classified by the degree of leakage. This allows for the efficient creation of inspection reports.

[0110] (C) When marking colors are used differently depending on the degree of free lime. In this case, the color of the chalk used is determined by the degree of free lime. For example, areas with normal free lime are marked with white chalk, while areas with free lime accompanied by rust stains and icicle-shaped free lime are marked with red chalk. The user inputs the color of the chalk used (marking color) and the meaning of that color (information on the degree of free lime) into the user terminal 20. For example, the user inputs into the user terminal 20 that "white" represents "normal free lime" and "red" represents "free lime accompanied by rust stains and icicle-shaped free lime".

[0111] Server 30 creates damage diagrams of the layered structure classified according to the degree of free lime based on the detection results of markings for each color and the color information of the markings.

[0112] Figure 19 shows an example of a damage map classified according to the degree of free lime.

[0113] The figure shows an example of a damage diagram between sections where areas of normal free lime are marked with white chalk, and areas of free lime with rust stains and icicle-shaped free lime are marked with red chalk. In this case, a damage diagram DF is created, comprising a first layer L1 and a second layer L2. The first layer L1 consists of a damage diagram with areas of normal free lime marked. This damage diagram consists of a traced white marking. The second layer L2 consists of a damage diagram with areas of free lime with rust stains and icicle-shaped free lime marked. This damage diagram consists of a traced red marking. Damage diagram DF is a diagram formed by superimposing the first layer L1 and the second layer L2.

[0114] Each layer is labeled with information about the classified damage. For example, the first layer L1 is labeled with If1, indicating that it is normal free lime. The second layer L2 is labeled with If2, indicating that it is free lime accompanied by rust stains and icicle-shaped free lime. Damage diagram DF, which is a composite of the first layer L1 and the second layer L2, is labeled with If0, indicating that it is the result of detecting all free lime.

[0115] In this example, by using different marking colors according to the degree of free lime, it is possible to automatically create damage diagrams classified by the degree of free lime using the information from those marking colors. This allows for the efficient creation of inspection reports.

[0116] For water leakage and free lime, damage can be evaluated according to predetermined evaluation criteria, and the damage can be marked using different colors according to that evaluation. In this case, based on the detection results of the markings detected for each color, a damage diagram classified by color (a damage diagram layered by color) can be created, thereby automatically generating a damage diagram classified according to the evaluation criteria.

[0117] Figure 20 is a table showing an example of evaluation criteria for water leakage and free lime.

[0118] In the example shown in the figure, the degree of damage is evaluated on a five-point scale (a, b, c, d, e) depending on the amount of water leakage and the amount of free lime generated.

[0119] When marking, use different colors of chalk according to the evaluation category (a, b, c, d, e). For example, use white chalk for category c, yellow chalk for category d, and red chalk for category e to mark the damaged area.

[0120] When creating damage diagrams, create diagrams categorized by marking color. This allows for the automatic creation of damage diagrams categorized by damage evaluation category.

[0121] (D) When different marking colors are used depending on the degree of peeling and reinforcement exposure. In this case, the color of the chalk used is determined by the degree of peeling and rebar exposure. For example, areas with normal rebar exposure are marked with white chalk, while areas with severe rust and rebar exposure are marked with red chalk. The user inputs the color of the chalk used (marking color) and the meaning of that color (information on the degree of rebar exposure) into the user terminal 20. For example, the user inputs into the user terminal 20 that "white" represents "normal rebar exposure" and "red" represents "severe rust and rebar exposure".

[0122] Server 30 creates damage diagrams of the layered structure, classified according to the degree of reinforcement exposure, based on the detection results of markings for each color and the information of the marking colors.

[0123] Figure 21 shows an example of a damage diagram classified according to the degree of reinforcement bar exposure.

[0124] The figure shows an example of a damage diagram of a girder, where areas of normal rebar exposure are marked with white chalk, and areas of severely rusted rebar exposure are marked with red chalk. In this case, a damage diagram DF is created, comprising a first layer L1 and a second layer L2. The first layer L1 consists of a damage diagram marking areas of normal rebar exposure. This damage diagram consists of a damage diagram traced from the white markings. The second layer L2 consists of a damage diagram marking areas of severely rusted rebar exposure. This damage diagram consists of a damage diagram traced from the red markings. Damage diagram DF is a diagram formed by superimposing the first layer L1 and the second layer L2.

[0125] Each layer is labeled with information about the classified damage. For example, the first layer L1 is labeled If1, indicating that it is normal rebar exposure. The second layer L2 is labeled If2, indicating that it is rebar exposure accompanied by severe rust. Damage diagram DF, which is a combination of the first layer L1 and the second layer L2, is labeled If0, indicating that it is a detection result of total rebar exposure.

[0126] In this example, by using different marking colors according to the degree of rebar exposure, it is possible to automatically create damage diagrams classified by the degree of rebar exposure using the information from those marking colors. This allows for the efficient creation of inspection reports.

[0127] For peeling and exposed rebar, damage can be evaluated according to predetermined evaluation criteria, and markings can be made using different colors according to that evaluation. In this case, based on the detection results of the markings detected for each color, damage diagrams classified by color (damage diagrams layered by color) can be created, thereby automatically generating damage diagrams classified according to the evaluation criteria.

[0128] Figure 22 is a table showing an example of evaluation criteria for peeling and reinforcement bar exposure.

[0129] In the example shown in the figure, the degree of damage is evaluated on a five-point scale (a, b, c, d, e) depending on the occurrence of peeling and reinforcement exposure.

[0130] When marking, use different colors of chalk according to the evaluation category (a, b, c, d, e). For example, use white chalk for category c, yellow chalk for category d, and red chalk for category e to mark the damaged area.

[0131] When creating damage diagrams, create diagrams categorized by marking color. This allows for the automatic creation of damage diagrams categorized by damage evaluation category.

[0132] (2) When different marking colors are used depending on the type of damage. In this case, a damage diagram is created that is classified according to the type of damage. The user inputs information about the type of damage for each color (marking color information) into the user terminal 20. The input marking color information is sent to the server 30 and stored in the marking color information storage unit 30F of the server 30. The server 30 refers to that marking color information and creates a damage diagram classified according to the type of damage.

[0133] For example, cracks are marked with white chalk, water leaks with blue chalk, free lime with green chalk, peeling with yellow chalk, and exposed rebar with red chalk. The user inputs the color of the chalk used (the marking color) and the type of damage associated with that color into the user terminal 20. For example, the user inputs into the user terminal 20 that "white" represents "cracks," "blue" represents "water leaks," "green" represents "free lime," "yellow" represents "peeling," and "red" represents "exposed rebar."

[0134] Server 30 creates a damage diagram based on the detection results of markings for each color and the color information of the markings. The damage diagram creates a layered structure classified according to the degree of damage.

[0135] Figure 23 shows an example of the structure of a damage diagram.

[0136] The figure shows an example of the structure of a damage diagram when cracks are marked with white chalk, water leaks with blue chalk, free lime areas with green chalk, delamination areas with yellow chalk, and exposed rebar areas with red chalk. In this case, a damage diagram DF with five layers (Layer 1 L1 to Layer 5 L5) is created. Layer 1 L1 consists of a damage diagram with marked cracks. This damage diagram consists of a traced white marking. Layer 2 L2 consists of a damage diagram with marked water leaks. This damage diagram consists of a traced blue marking. Layer 3 L3 consists of a damage diagram with marked free lime areas. This damage diagram consists of a traced green marking. Layer 4 L4 consists of a damage diagram with marked delamination. This damage diagram consists of a traced yellow marking. The fifth layer, L5, consists of a damage diagram with marked reinforcement bars. This damage diagram is composed of traced red markings. The overall damage diagram DF is composed of all layers superimposed.

[0137] Similarly, each layer is labeled with information about the classified damage. Furthermore, it is preferable that the lines tracing the markings on each layer use different line types and / or different colors so that they can be distinguished from each other when the layers are superimposed. For example, the same color as the detected color can be used. Alternatively, they may be displayed according to pre-defined display rules.

[0138] Figure 24 shows an example of how damage is represented on a damage diagram.

[0139] As shown in the figure, the display method on the damage diagram is set for each type of damage, and the damage is displayed on the damage diagram according to that setting. For example, if a water leak marking (blue marking in this example) is detected, the location of the marking is displayed on the damage diagram with hatching.

[0140] Furthermore, if damage is depicted on the damage diagram in accordance with pre-established display rules, a legend may be displayed or attached to the damage diagram.

[0141] Figure 25 shows an example of a damage diagram classified by type of damage.

[0142] The example shown in the figure illustrates how a damage diagram can be created from images of a girder where cracks, water leakage, and free lime have occurred. In this case, as shown in the figure, white markings are detected where cracks are present, blue markings where water leakage occurs, and green markings where free lime is present. The damage diagram consists of three layers: Layer 1 L1, which shows the crack damage; Layer 2 L2, which shows the water leakage damage; and Layer 3 L3, which shows the free lime damage (Layer 4 L4, which shows the peeling damage, and Layer 5 L5, which shows the reinforcement bar exposure damage, are blank (transparent) layers). The overall damage diagram DF shows all the damage.

[0143] In this example, by using different marking colors depending on the type of damage, the information from those marking colors can be used to automatically create damage diagrams categorized by damage type. This allows for the efficient creation of inspection reports.

[0144] (3) When different marking colors are used depending on the timing of the inspection. For example, the first inspection uses white chalk, the next uses red chalk, and the following uses blue chalk, changing the color of the chalk used for marking each time an inspection is performed. In this case, damage diagrams are created that are classified according to the timing (number of inspections). The user inputs information about the timing (number of inspections) for each color (marking color information) into the user terminal 20. The input marking color information is sent to the server 30 and stored in the marking color information storage unit 30F of the server 30. The server 30 refers to this marking color information and creates damage diagrams that are classified according to the timing of inspections. For example, a damage diagram of a layered structure is created. That is, a damage diagram of a structure that is classified and stacked according to the timing (number of inspections) is created.

[0145] Figure 26 shows an example of the structure of damage diagrams classified by inspection timing.

[0146] The figure shows an example of a damage diagram after three inspections have been conducted. In the first inspection (December 1, 2008), damaged areas were marked with white chalk; in the second inspection (December 1, 2013), damaged areas were marked with red chalk; and in the third inspection (December 1, 2018), damaged areas were marked with blue chalk. In this case, a damage diagram DF is created with three layers (Layer 1 L1 to Layer 3 L3). Layer 1 L1 consists of the damage diagram from the first inspection. This damage diagram consists of damage traced from the white markings. Layer 2 L2 consists of the damage diagram from the second inspection. This damage diagram consists of damage traced from the red markings. Layer 3 L3 consists of the damage diagram from the third inspection. This damage diagram consists of damage traced from the blue markings. The overall damage diagram DF is a diagram made by superimposing all the layers.

[0147] In this example, by using different marking colors depending on the inspection timing (number of inspections), the information from these marking colors can be used to automatically create damage diagrams categorized by inspection timing (number of inspections). This allows for the efficient creation of inspection reports. Furthermore, by creating such damage diagrams, it is possible to check the difference (progression of damage) between past and current inspections.

[0148] Other embodiments and modifications [Items to be inspected] The above embodiment was described using the inspection of a bridge as an example, but the application of the present invention is not limited to this. It can also be similarly applied to the inspection of other structures such as tunnels, dams, and buildings. Furthermore, the structure to be inspected is not limited to concrete structures, but can also be applied to the inspection of other structures. In addition, the surface structure of the inspection area is not limited to concrete, but may be made of tiles or the like. Moreover, the present invention can also be applied when the steel members of a structure are to be inspected. When steel members of a structure are included in the inspection, for example, the marking color can be used according to the degree of cracking, corrosion, deterioration of corrosion protection function, and loosening of bolts of the steel members. For example, regarding cracks, (1) if paint cracks can be confirmed in areas with abrupt changes in cross-section, welded joints, etc., and if cracks have occurred but are not linear, or if they are linear, their length is extremely short and there are few of them, mark with white chalk; and (2) if linear cracks have occurred or if there is paint cracks that cannot rule out the suspicion that cracks are occurring directly underneath, mark with red chalk. Furthermore, regarding corrosion, for example, (1) if the depth of damage is small (rust is superficial and no significant reduction in plate thickness is visible) and the area of ​​damage is small (the area of ​​damage is small and localized), mark it with white chalk; (2) if the depth of damage is small and the area of ​​damage is large (rust has occurred over the entire area of ​​the area of ​​interest or there are multiple areas of widespread rust in the area of ​​interest), mark it with blue chalk; (3) if the depth of damage is large (significant expansion has occurred on the surface of the steel or a clear reduction in plate thickness is visible) and the area of ​​damage is large, mark it with yellow chalk; and (4) if the depth of damage is large and the area of ​​damage is large, mark it with red chalk. Furthermore, regarding the deterioration of the corrosion protection function, in the case of paint, for example, (1) if discoloration occurs or localized lifting occurs in the outermost layer of the corrosion protection coating, mark it with white chalk; (2) if the corrosion protection coating is partially peeled off and the undercoat is exposed, mark it with yellow chalk; and (3) if the deterioration of the corrosion protection coating is widespread and pitting rust has occurred, mark it with red chalk.Regarding deterioration of corrosion protection, in the case of plating and thermal spraying, (1) if the corrosion protection coating deteriorates locally and rust spots occur, mark with white chalk; (2) if the deterioration of the corrosion protection coating is widespread and rust spots occur, mark with red chalk. Regarding deterioration of corrosion protection, in the case of weathering steel, (1) if the rust is coarse and about 1-5 mm in size, mark with white chalk; (2) if the rust is scaly and about 5-25 mm in size, mark with yellow chalk; (3) if there is layered peeling of rust, mark with red chalk. Regarding loose bolts, (1) if bolts are loose or have fallen out and the number is small (less than 5% of the number of bolts per group), mark with white chalk; (2) if bolts are loose or have fallen out and the number is large (5% or more of the number of bolts per group), mark with red chalk. When creating damage diagrams, the diagrams are created according to the detection results for each color of the markings detected from the images. In other words, damage diagrams are created that classify the damage according to the degree of cracking, corrosion, and deterioration of the corrosion protection function of the detected steel members.

[0149] [System Configuration] In the above embodiment, the present invention is configured as a so-called client-server type system for damage diagram creation support, but the present invention can also be implemented as a so-called standalone computer, for example, for damage diagram creation support system.

[0150] [Marking work] In the above embodiment, the example of marking with chalk was used, but the marking work can also be done using markers such as felt-tip pens (marking pens). The important thing is that you can use different colors.

[0151] Furthermore, while the above embodiment described the case where inspection and marking of cracks, water leakage, free lime, spalling, and exposed rebar are performed individually, these tasks can be performed in combination. For example, inspection and marking of cracks and water leakage can be performed simultaneously. In this case, different chalk colors can be used for marking depending on the degree of cracking and the degree of water leakage. Also, different chalk colors can be used for marking depending on the type of damage. This makes it possible to create damage diagrams classified by the degree and type of damage.

[0152] [Enter marking color information] In the above embodiment, the user inputs information for each marking color into the user terminal 20. However, if the information for each marking color is predetermined (for example, when an inspection technician marks according to predetermined color usage rules), the server 30 may store this information (stored in the HDD 34 (storage unit), etc.) and create a damage diagram by referring to this information.

[0153] [Structure of the damage diagram] In the above embodiment, a damage diagram with a layered structure separable by marking color is created, but the configuration of the damage diagram is not limited to this. A separate damage diagram may be created for each marking color. Alternatively, a single damage diagram may be created in a form that is separable by marking color (for example, by grouping by marking color and enabling switching between displaying and hiding each marking color).

[0154] [Variations in hardware configuration] The hardware for realizing the damage diagram creation support device of the present invention can be composed of various processors. These various processors include CPUs (Central Processing Units), which are general-purpose processors that execute programs and function as various processing units; Programmable Logic Devices (PLDs), such as FPGAs (Field Programmable Gate Arrays), which are processors whose circuit configuration can be changed after manufacturing; and Dedicated Electrical Circuits, such as ASICs (Application Specific Integrated Circuits), which have a circuit configuration specifically designed to perform specific processing. One processing unit constituting the damage diagram creation support device may be composed of one of the above various processors, or it may be composed of two or more processors of the same or different type. For example, one processing unit may be composed of multiple FPGAs, or a combination of a CPU and an FPGA. Alternatively, multiple processing units may be composed of one processor. An example of composing multiple processing units with one processor is, firstly, a configuration in which one processor is composed of a combination of one or more CPUs and software, as is exemplified by computers such as clients and servers, and this processor functions as multiple processing units. Secondly, there is a configuration that uses a processor that realizes the functions of the entire system, including multiple processing units, on a single IC (Integrated Circuit) chip, as exemplified by System-on-a-Chip (SoC). In this way, various processing units are configured using one or more of the above-mentioned processors as hardware structures. Furthermore, the hardware structure of these various processors is more specifically an electrical circuit (circuitry) that combines circuit elements such as semiconductor elements. [Explanation of Symbols]

[0155] 1 Bridge 2 Main digit 3 crossbeam 4. Opposite leaning structure 5. Horizontal composition 6 Floor slab 10. Damage Diagram Creation Support System 20 User Terminals 20A Terminal-side image input section 20B Terminal-side transmitting unit 20C Terminal-side receiving unit 20D Terminal side output section 20E Terminal side recording unit 20F Marking Color Information Input Section 21 CPU(Central Processing Unit) 22 RAM (Random Access Memory) 23 ROM (Read Only Memory) 24 HDD (Hard Disk Drive) 25. Communication Interface 26 Input devices 27 Output device 28 Optical disc drives 30 servers 30A Server-side receiving unit 30B Panorama stitching section 30C Marking detection unit 30D Damage Diagram Creation Department 30E Server-side transmission unit 30F Marking Color Information Storage Unit 31 CPU(Central Processing Unit) 32 RAM (Random Access Memory) 33 ROM (Read Only Memory) 34 HDD (Hard Disk Drive) 35. Communication Interface 36 Input devices 37 Output device 38 Optical disc drives 40 Networks DF Damage Diagram GO Square Image I If0 Information If1 Information If2 Information L1 First Layer L2 (Second Layer) L3 (Third Layer) L4 (Layer 4) L5 (Layer 5) S1-S11 Procedure for creating damage diagrams

Claims

1. Equipped with a processor, The aforementioned processor, A structure in which lines are drawn along surface damage, and an image of the structure in which the lines are drawn is obtained using different colors. The aforementioned image is analyzed to detect the lines drawn on the surface of the structure and the color of those lines. We obtain information about the meaning of the different colors used for the aforementioned lines. Based on the detection results of the lines and the colors of the lines, and the information on the meaning of the colors of the lines, a damage diagram is created in a layered structure in which layers are separated for each color of the lines, wherein each layer consists of a damage diagram in which the lines of the color of each layer are traced, and each layer is associated with the information on the meaning of the colors. Damage diagram creation support device.

2. The aforementioned processor, The system accepts and obtains information from the user regarding the meaning of the different colors used for the aforementioned lines. The information regarding the meaning of the color of the received line is stored in the memory unit. Based on the detection results of the line and the color of the line, and the information on the meaning of the line's color stored in the storage unit, the damage diagram is created. The damage diagram creation support device according to claim 1.

3. The processor provides information on the meaning of the line colors, including information on the degree of cracking for each color. Obtain information on the degree of water leakage for each color, information on the degree of free lime for each color, or information on the degree of rebar exposure for each color. The damage diagram creation support device according to claim 1 or 2.

4. The processor outputs the damage diagram to the display destination. A damage diagram creation support device according to any one of claims 1 to 3.

Citation Information

Patent Citations

  • Method of detecting air leakage utilizing pressure reduction in silo

    JP1982040628A

  • Surface inspecting and marking mechanism

    JP1992134064U

  • Defect marking method to thin steel sheet

    JP2000051937A

  • Method for inspection, evaluation and repair of concrete structure

    JP2002228642A

  • Measuring method of damaged part of concrete structure

    JP2002340805A