Surveying Goal Extraction from 3D Point Clouds to Support Bridge Inspection What does that mean? Why is that important? Currently, bridge inspectors have to manually process point clouds to extract surfaces, edges etc., and calculate a piece of information they are interested in (how much is the minimum vertical under clearance? where does it occur?). That manual approach takes a lot of time, and is error-prone. With my approach, bridge inspectors only interact with components and features in a bridge information model to define what they are interested in, then the computer can report the surveying goal result. The representations developed by me is like a macro language of bridge inspectors, and my algorithms serve as compilers to compile them into operations which can be automatically executed, but right now are executed manually by bridge inspectors. Please look at these two pictures, the left one is a mesh model of a bridge composed of just points and triangles, how boring is manually selecting individual points and triangles to extract geometric features for calculating a surveying goal? Look at the bridge information model at the right side, bridge inspectors can interact with components rather than points and surfaces, so they can specify things like "select all columns" while defining what they are looking for in laser scanned data! BIM (building information modeling) is maturing these days, I expect that such bridge information model will be widely used in practice, and use it for querying laser scanned data can be one great benefit brought by BIM! ![]() Automated BIM supported bridge inspection, that is the future! |
