Infrastructure Crack Segmentation: Boundary Guidance Method and Benchmark Dataset

Zhili He, Wang Chen, Jian Zhang, Yu-Hsing Wang
6/15/2023
cs.CV

No official code found. Best implementation: hzlbbfrog/BGCrack (10 stars, Apache-2.0, last commit 2024-04-02).

Abstract

Cracks provide an essential indicator of infrastructure performance degradation, and achieving high-precision pixel-level crack segmentation is an issue of concern. Unlike the common research paradigms that adopt novel artificial intelligence (AI) methods directly, this paper examines the inherent characteristics of cracks so as to introduce boundary features into crack identification and then builds a boundary guidance crack segmentation model (BGCrack) with targeted structures and modules, including a high frequency module, global information modeling module, joint optimization module, etc. Extensive experimental results verify the feasibility of the proposed designs and the effectiveness of the edge information in improving segmentation results. In addition, considering that notable open-source datasets mainly consist of asphalt pavement cracks because of ease of access, there is no standard and widely recognized dataset yet for steel structures, one of the primary structural forms in civil infrastructure. This paper provides a steel crack dataset that establishes a unified and fair benchmark for the identification of steel cracks.

View on arXivView PDF

Code Implementations(1)

hzlbbfrog/BGCrackCommunity100%
Apache-2.0

Boundary Guidance Crack Segmentation Model

100May 9, 20232 years agoApache-2.0

Cite this paper

@article{he2023infrastructure,
  title  = {Infrastructure Crack Segmentation: Boundary Guidance Method and Benchmark Dataset},
  author = {Zhili He and Wang Chen and Jian Zhang and Yu-Hsing Wang},
  year   = {2023},
  eprint = {2306.09196},
  archivePrefix = {arXiv},
  url    = {http://arxiv.org/abs/2306.09196v1}
}

Add a badge to your README

Shows whether official code is linked for this paper.

Code of Paper badge
[![Code of Paper](https://codeofpaper.com/badge/2306.09196.svg)](https://codeofpaper.com/paper/2306.09196)

Discussion