Quick answer. A damage catalogue turns a photogrammetry or 3D laser scanning survey into a usable list of defects: cracks, spalls and rusted rebar in concrete, corrosion in steel, rutting and potholes in pavement, deterioration in masonry. Each defect gets a unique ID, a position on the 3D model, a type taken from a recognized rating system (such as the Quebec transportation ministry’s for bridges), measured dimensions with their uncertainty, a dated photo and a status. The severity rating, the cause and the recommendation remain the engineer’s judgment. For a defect to be classifiable, the capture must be planned around the smallest defect that needs a rating. And for the catalogue to be useful beyond one report, it must be hosted, viewable in the 3D model and updated at every inspection and every repair.
A parking garage inspection report often comes down to one sentence per defect: “major crack with efflorescence, slab soffit, near column C-4.” Five years later, another engineer looks for the same crack. Which column C-4, on which level? “Major” compared to what? The original photo has no scale. There is no way to tell whether the defect got worse, was repaired or was never found again.
In Quebec, this is not a detail. The Régie du bâtiment’s Safety Code requires an in-depth inspection of multi-storey parking garages by an engineer every five years, with a report that must, among other things, give the location of the defects observed. Facades of buildings with five or more storeys follow the same logic. A 3D survey, whether by drone, from the ground or with a laser scanner, can provide that location, with a known and stated accuracy. But each defect must also be classified according to a common rating system. Otherwise, the owner receives a beautiful model and a folder of photos, and still does not know what to repair first.
Our guide to drone inspection recommends requiring an anomaly register. This article shows how to build one: which rating system to adopt, how to classify each type of failure (concrete, steel, pavement, masonry), which fields to fill in, what 3D data measures and what it does not, how to capture in order to classify, and how to keep the catalogue alive throughout the life cycle of the structure.
What is a damage catalogue, exactly?
A damage catalogue (or defect catalogue) is a database of defects tied to a 3D model. It is not a photo album, a point cloud or a PDF report: it is what connects all three.
A point cloud without a catalogue is a library without an index: everything is there, but nothing can be found. The catalogue is the index. It answers, in seconds, the questions that matter to an asset manager:
- How many severe defects are there on level 2, and exactly where?
- How much spalled area should the repair tender include?
- Which defects affect a load-bearing element?
- What has been repaired since the last inspection, and what is still outstanding?
In practice, each defect is an object: a point, a line or an area placed on the 3D model, with a record attached. Click the defect and you see its record; filter the records and you see the defects in the model.
Which rating system should be used to classify defects?
The first rule is simple: do not invent your own rating system. The catalogue must speak the language of the engineer who will sign the report and of the owner who manages the asset portfolio. Recognized references exist, and the right choice depends on the structure.
| Reference | Structures | What it classifies | Scale |
|---|---|---|---|
| Quebec Ministry of Transportation (MTMD) structure inspection manual | Bridges, culverts, walls, tunnels | Material defects (concrete, steel, timber…) and the behaviour of each element | Material condition A to D (as % of the element); behaviour condition rating 4 to 1, tied to an intervention timeframe |
| AASHTO Manual for Bridge Element Inspection | Bridges (North American reference) | Condition of each element, by quantity | Condition states 1 (good) to 4 (severe) |
| ACI 201.1R | Concrete in service, all structures | Standard terminology: cracking, scaling, spalling, corrosion, efflorescence… | Description, no numerical rating |
| ICOMOS-ISCS illustrated glossary on stone deterioration | Stone masonry, heritage | Deterioration patterns (flaking, alveolization, crusts…) | Illustrated vocabulary, no severity |
| Quebec Ministry of Transportation manual for identifying flexible pavement distress | Asphalt pavements | Cracks, ruts, depressions, potholes, ravelling…, with measurement procedures | Severity levels per distress |
| ASTM D6433 (Pavement Condition Index, PCI) | Roads, streets, outdoor parking lots | About twenty asphalt distress types, each at three severity levels, and their extent | Low, medium, high severity; overall index from 0 to 100 |
In the MTMD system, for example, the inspector splits each element into percentages by material condition, then assigns a behaviour rating. A rating of 1 means an intervention is needed within two years; a rating of 4, none for ten years. The manual also sets thresholds per defect type (depth of disintegration, crack width, loss of rebar section) and a rule for converting cracks into damaged area.
For pavement, the ministry’s distress manual or the ASTM D6433 PCI plays that role. For a parking garage or a building, there is no single provincial rating system. The catalogue then starts from ACI terminology and the severity scale used by the engineer or the asset manager. What matters is to set it before the capture and keep it from one inspection to the next. For a heritage building, the ICOMOS glossary provides the vocabulary for stone deterioration (see also our article on heritage building 3D scanning).
How do you classify each type of failure? Concrete, steel, pavement, masonry
Each defect class depends on an attribute that sets its severity: the width of a crack, the depth of a spall, the depth of a rut. So the right question is not “is the defect visible?” but “does the survey measure the attribute that determines its class?” Here, family by family, are the most common failures, what sets their class and what photogrammetry and 3D scanning can tell you about them. The exact thresholds come from the chosen rating system, not from these tables.
Concrete (bridges, parking garage slabs, walls, wharves, dams)
| Failure | What sets the class | What 3D measures | Complement with |
|---|---|---|---|
| Cracking | Width, length, pattern (isolated, network, map cracking), water or deposits | Photo: length and pattern very well; width only if the crack covers several pixels. Scan: wide cracks and their context | Crack gauge for fine cracks that need a rating |
| Spalling | Area, depth, exposed rebar or not | Scan: depth and volume. Photo: outline and exposed rebar | — |
| Scaling, disintegration | Area and depth (the MTMD grades them by depth) | Scan: depth; photo: extent | — |
| Exposed rebar and rust | Exposed length, loss of bar section | Photo: location and length | Contact measurement of section loss |
| Efflorescence, streaks, leaks | Extent, active water or dry deposit | Photo: extent and colour | On-site check or thermography for moisture |
| Delamination | Hidden extent below the surface | Invisible | Hammer sounding, thermography or GPR |
| Corrosion activity | Potential, resistivity | Invisible | On-site testing by the engineer |
Steel (frames, bridge girders, railings, tanks)
| Failure | What sets the class | What 3D measures | Complement with |
|---|---|---|---|
| Surface corrosion | Extent, coating breakdown | Photo: extent and colour | — |
| Corrosion with section loss | Remaining thickness | Scan: loss of shape visible only when significant | Ultrasonic thickness measurement |
| Deformation, local buckling | Deviation from expected geometry | Scan: very good, over the whole member | — |
| Missing bolts or rivets, fatigue cracks | Presence, location | Close-up photo: location | Hands-on visual inspection or non-destructive testing for fatigue |
Pavement (roads, streets, outdoor parking lots, runways)
| Failure | What sets the class | What 3D measures | Complement with |
|---|---|---|---|
| Longitudinal, transverse, edge cracks | Width, length, edge deterioration | Photo: length and pattern; width depending on resolution | — |
| Alligator (fatigue) cracking | Affected area, open or closed pattern | Photo: extent and pattern | — |
| Rutting | Rut depth and affected length | Scan or mobile LiDAR: cross-sections, depth measured continuously | — |
| Pothole | Diameter and depth, count | Scan: diameter, depth, repair volume | — |
| Depression, heave | Amplitude and extent | Scan: surface model, deviation from a plane or profile | Cause (frost, drainage, pipe) by the engineer |
| Ravelling, bleeding | Affected area | Photo: texture and colour | — |
For rutting, for example, training material based on ASTM D6433 places low severity at roughly 6 to 13 mm of depth, medium at 13 to 25 mm and high beyond 25 mm. A mobile mapping survey measures that depth over kilometres, with no inspector exposed to traffic.

Masonry and stone (buildings, heritage, retaining walls)
| Failure | What sets the class | What 3D measures | Complement with |
|---|---|---|---|
| Cracks, open or eroded joints | Width, length, pattern | Photo: length, pattern, joints | — |
| Flaking, alveolization, material loss | Area and depth | Scan: depth; photo: deterioration pattern | — |
| Bulging, out-of-plumb | Deviation from vertical or plane | Scan: very good | — |
| Crusts, soiling, vegetation | Extent | Photo: colour and extent | — |
Crack width is the most telling case. A study presented at ISPRS in 2025 on concrete facades found that, with a pixel size of about 0.3 mm on the structure, crack length was measured with a relative error of about 5%, but crack width with an error close to 150%. Super-resolution processing was needed to bring the width error down to around 10%. Another study, published in Sensors in 2026, shows that cracks covering only two or three pixels give the most unstable detection results. The practical conclusion: a photo can locate and measure the length of a fine crack without making it possible to rate it if the class depends on its width. You need to know that before the capture, not after.

The two techniques are therefore complementary: photogrammetry reads the surface, laser scanning reads the shape. To choose or combine them, see our comparison of drone photogrammetry and LiDAR.
What is measured, and what the engineer judges
This is what separates a useful catalogue from a misleading one. A defect record holds two kinds of information that must never be mixed:
- Measured attributes: position, apparent type, length, width, area, depth, photo, date. They come from the survey and carry an uncertainty.
- Judged attributes: severity rating, probable cause, active or stable, recommendation, priority. They belong to the engineer.
A 3D survey can say “spall of 0.42 m², 35 mm maximum depth, exposed rebar over 0.6 m.” It cannot say whether corrosion is active or whether the element has lost load-bearing capacity. The Safety Code in fact requires parking garage reports to address the state of rebar corrosion activity: that is measured on site, with tests, not in a 3D model.
Here are the fields of a well-built defect record:
| Field | Example | Source |
|---|---|---|
| Unique ID | N2-D-0147 | Catalogue (permanent, never changes) |
| Asset and element | East garage, level 2, slab, bay C4-C5 | Owner’s naming system |
| Position | X, Y, Z coordinates and reference system | 3D survey |
| Type | Spall with exposed rebar (rating system code) | Specialist, per the chosen system |
| Dimensions | Area 0.42 m², max. depth 35 mm (± uncertainty) | Measured in the model |
| Source photo | Original image, date, resolution | Capture |
| Method | Terrestrial photogrammetry, pixel size on the structure | Capture plan |
| Detection status | Proposed by AI · validated by a specialist | Quality control |
| Severity rating | Per the rating system, with the engineer’s name | Engineer |
| Cause, recommendation, priority | Text and timeframe | Engineer |
| History | Previous inspection record, repair, date | Catalogue |
The detection status field matters more than it seems. AI tools now propose candidate defects within minutes across thousands of images, but they produce false positives and miss what the images do not show (see what AI really sees). A record must therefore always state whether a specialist has confirmed the defect.
Capturing to classify: start from the smallest defect to rate
A catalogue is prepared before anyone sets foot on site. The method comes down to four questions:
- Which rating system, and which thresholds? If the system distinguishes cracks by width, the finest threshold sets the minimum resolution.
- What pixel size on the structure? It follows from that threshold, with a margin of several pixels across the defect. It determines shooting distance, lens and, for drones, flight height.
- Which areas are critical? Slab soffits, joints, bearings, drainage areas, load-bearing elements. They get denser coverage and multiple angles. A shadow or obstruction creates a hole in the catalogue, which should be flagged as an uninspected area rather than an area without defects.
- Which reference system? For a defect’s position to still be valid in five years, the survey must be tied to a stable control network. And its accuracy must be stated, not assumed (see the true accuracy of a point cloud).
This is often where an inspection is won or lost. A flight that is too high produces a fine model in which fine cracks are visible but impossible to rate. A scan without close-up photos gives the geometry of a spall, but not the condition of the rebar.
Which format keeps the catalogue alive?
A catalogue locked into proprietary software dies with the licence. A few guidelines:
- The record table should export to an open format (CSV, GeoJSON) into the owner’s maintenance management system (CMMS) or GIS, with the unique ID as the key.
- In a BIM model, the IFC 4.3 standard already provides a “defect” type for the surface features of an element (a corroded or eroded area, for example). For exchanging issues between stakeholders, buildingSMART’s BCF format is designed for exactly that.
- On the research side, ontologies such as the Damage Topology Ontology separate the defect from its geometry: damage can be recorded in the field and its 3D shape attached later. That is the direction infrastructure digital twins are taking.
- The source data (photos, E57 point cloud, textured model) are delivered and archived: they make it possible to revisit a defect with another rating system or another tool.
Hosting and viewing: the catalogue across the asset’s life cycle
An inspection report is a snapshot. The structure lives thirty, fifty or a hundred years. A damage catalogue shows its value when it follows the asset instead of sleeping in a PDF.
In practice, the 3D model and the catalogue are hosted on a web viewing platform: they open in a browser, with no specialized software, and access rights by role. Each stakeholder finds what they need:
- The engineer rates defects in the model rather than in a spreadsheet, with the photo and the measurement in front of them.
- The asset manager filters by class, level or element, and sees a map of what is urgent.
- The estimator and the repair contractor extract quantities (spalled areas, crack lengths) and locate each repair before mobilizing a crew.
- The owner keeps dated evidence of the structure’s condition and of the work done, useful for the insurer, a potential buyer or the next mandatory inspection.
The catalogue then follows the asset’s cycle: inspection, prioritization, repair tender, acceptance of the work (the defect moves to “repaired” status, with the date and an after photo), then the next inspection. At that point, the same ID makes it possible to tell whether a defect has progressed, is stable, or whether new ones have appeared. That is the subject of our article on tracking damage between two 3D surveys.
Streaming platforms display very large surveys in a browser and let maintenance information be attached to them. The choice of platform matters less than the structure of the catalogue: with stable IDs and open formats, you can change tools without losing the history.
Typical case: a three-level parking garage
Representative, anonymized case.
Context. A property manager must have the five-year in-depth inspection of a three-level concrete parking garage carried out. The previous report contains about forty photos and a table of defects described in words, with no precise location.
Challenge. The engineer must locate the defects, assess how they have evolved and recommend a repair program that can be priced, without closing the garage for more than a weekend.
Approach. Before the capture, the engineer and the survey team set the rating system (ACI terminology, the engineer’s severity scale) and the smallest defect to rate. Slabs and soffits are laser scanned for geometry, spalls and deflections. Critical areas are photographed up close for cracks and exposed rebar. Everything is tied to permanent benchmarks. AI tools propose candidate defects; a specialist validates, measures and fills in the records. The engineer rates each defect in the hosted model, then completes the picture with on-site corrosion testing.
Logical outcome. The report gives the location of each defect, as the Safety Code requires. The repair estimate is built from measured rather than estimated quantities. After the work, repaired defects change status. In five years, the next inspection will start from the same catalogue, on the same benchmarks.
Why work with a geomatics partner
The damage catalogue sits at the boundary of two professions: the engineer, who judges, and the measurement specialist, who captures, locates and structures. A partner such as Topo3D steps in on three specific points:
- Guiding the capture. Translating the engineer’s rating system into a capture plan: pixel size, coverage of critical areas, combining laser scanning and photogrammetry, permanent benchmarks. We do not capture “everything”: we capture what is needed to rate. Depending on the structure, we use drone-based aerial surveys, terrestrial or mobile 3D scanning, or a combination of both.
- Building the catalogue. Detecting (our AI agents propose candidates, under a specialist’s supervision), measuring with a stated uncertainty, structuring the records according to the chosen rating system. The technical lead validates the data before delivery. The severity rating remains the engineer’s: we provide the measurement, not the diagnosis.
- Hosting and keeping it alive. Putting the model and catalogue online for all stakeholders, recording repairs, preparing the next campaign on the same benchmarks, and exporting records to the owner’s tools.
In the field. In 2018, Topo3D scanned the Port-Daniel–Gascons rail tunnel in Gaspésie, with cross-sections every 25 ft, to simulate the passage of wind turbine blades. Circa 2005-2006, it surveyed the complete structure of the Laviolette Bridge for the rehabilitation carried out for the MTQ.
Conclusion
An inspection 3D survey is only as good as its damage catalogue. A recognized rating system, chosen before the capture; records that separate what is measured from what is judged; a capture sized for the smallest defect to rate; open formats; hosting that follows the structure from one inspection to the next. With these five elements, the model stops being a pretty picture: it becomes the tool that says what to repair, where, and in what quantity.
FAQ
It is a database of defects tied to a 3D model. Each defect has a unique ID, a position, a type based on a recognized rating system, measured dimensions, a dated photo, a status and, once judged by the engineer, a severity rating and a recommendation. In Quebec, it directly meets the Safety Code requirement to give the location of the defects observed for parking garages and facades.
For bridges and structures in Quebec, the system in the Ministry of Transportation’s structure inspection manual (material condition A to D, behaviour rating 4 to 1). Elsewhere in North America, AASHTO condition states 1 to 4. For a building or parking garage, ACI 201.1R terminology with the engineer’s scale. The key is to set it before the capture and keep it from one inspection to the next.
Yes, if the crack covers several pixels in the image. When the pixel size is of the same order as the crack width, length is still measured well, but width becomes highly uncertain. Capture resolution must therefore be planned from the finest crack width that needs a rating.
No. The survey locates and measures visible defects; the engineer judges their severity, cause and urgency, and performs the tests that 3D cannot replace (delamination, corrosion activity). The survey makes that work faster, more complete and verifiable.
With a pavement rating system: the Quebec Ministry of Transportation’s flexible pavement distress manual, or the ASTM D6433 Pavement Condition Index, which gives each distress a low, medium or high severity level. Rutting is classified by its depth, a pothole by its diameter and depth. A scanning or mobile mapping survey measures both attributes continuously, with the position of each defect.
The model and catalogue can be hosted on a web viewing platform, accessible according to each stakeholder’s role. The data belongs to the owner of the structure: it should be delivered in open formats so the owner can change tools without losing the history.
Preparing a parking garage, facade or bridge inspection? Let’s talk about the capture and the damage catalogue your engineer will need.
References
- Quebec Ministry of Transportation and Sustainable Mobility (2026). Matériel d’inspection des structures et des tunnels (consistent with the Manuel d’inspection des structures, 2017 ed.). https://www.transports.gouv.qc.ca/fr/projets-infrastructures/structures/documentation-structures/Documents/Mat%c3%a9riel%20d%e2%80%99inspection%20des%20structures/Mat_insp_livret_recto.pdf
- Government of Quebec. Safety Code, Chapter Building (B-1.1, r. 3), s. 371 to 400. https://www.legisquebec.gouv.qc.ca/en/document/cr/B-1.1,%20r.%203
- Federal Highway Administration. Specification for the National Bridge Inventory — Bridge Elements (AASHTO MBEI condition states 1 to 4). https://www.fhwa.dot.gov/bridge/nbi/131216_a1.pdf
- American Concrete Institute (2008). ACI 201.1R-08 — Guide for Conducting a Visual Inspection of Concrete in Service. https://www.concrete.org
- ICOMOS-ISCS (2008). Illustrated glossary on stone deterioration patterns. https://openarchive.icomos.org/id/eprint/434/
- Jang, Park and Jeon (2025). Crack measurement on drone facade orthomosaics with super-resolution. ISPRS Archives, XLVIII-2/W11-2025. https://isprs-archives.copernicus.org/articles/XLVIII-2-W11-2025/139/2025/
- Lee, Lee and Kim (2026). Effect of shooting distance and pixel size on crack segmentation. Sensors, 26(3), 1031. https://pmc.ncbi.nlm.nih.gov/articles/PMC12900104/
- buildingSMART International. IFC 4.3 — IfcSurfaceFeatureTypeEnum (DEFECT); BCF-XML. https://github.com/buildingSMART
- ASTM International. ASTM D6433 — Standard Practice for Roads and Parking Lots Pavement Condition Index Surveys. https://www.astm.org
- Quebec Ministry of Transportation. Manuel d’identification des dégradations des chaussées souples. BAnQ digital copy. https://collections.banq.qc.ca/document/s/t/L82Id2udGC57r4uk5eXzOw
- Hamdan, Bonduel and Scherer (2019). An ontological model for the representation of damage to constructions (Damage Topology Ontology). LDAC 2019. https://ceur-ws.org/Vol-2389/05paper.pdf




