Correlate Bridge Deck GPR Maps with Verification Evidence

A bridge deck GPR survey can produce a detailed map, but the map's colors and interpreted features are not the same kind of evidence as a directly observed condition at a verification location. A useful report keeps those records distinguishable while showing how they are related. Start by identifying the surveyed area, the interpretation being reviewed and the physical evidence available to support or challenge it. The objective is to make the correlation understandable, including its limits, rather than presenting every mapped area as a confirmed defect merely because the output looks precise.

The free digital NDT reporting workspace can organize entered map references, verification observations and review decisions in a structured PDF. It does not process native GPR data, select a dielectric velocity, create a condition map or authorize intrusive work on a bridge. Those activities belong to the approved survey and engineering process. This guide supplies a correlation worksheet for the records produced by that process. The examples are fictional and provide no universal signal threshold, sampling requirement or condition-rating rule. Use the owner's actual scope, technical requirements and responsible review for the project.

State what the GPR survey was intended to investigate and which interpreted output the correlation record addresses. A survey may be used to describe different subsurface features or condition-related responses, and one map should not be assumed to answer every question about the deck. Identify the source report, processing version and legend associated with the selected output. Keep the wording of the interpretation accurate. A map described as indicating likely deterioration should not become a report column labeled confirmed deterioration without additional evidence and an appropriate technical decision.

FHWA's GPR information page describes interpretation that relates radar coordinates and travel time to estimated or calibrated quantities, and shows condition-related mapping examples. This supports keeping the interpretation basis visible in the report. It does not supply a project-specific acceptance rule or prove that a particular colored area represents one physical defect type. Ask the responsible analyst to identify the meaning and limitations of the delivered map. The report author should preserve that explanation rather than infer it from a screenshot or a familiar color scale.

Identify the bridge, carriageway or deck area and the coordinate convention used by the survey. Record the origin, directions and units needed to locate the mapped observations. FHWA's archived LTBP bridge deck coordinate protocol, published in 2016, provides an example of a defined deck grid and coordinate system. It is a reference example, not an instruction to replace an owner's existing convention. Use the approved project system and document any supported transformation between survey coordinates and verification-location references.

Check that the physical verification locations can be matched to the intended map positions. A lane description or an approximate offset may not be sufficient when the interpretation changes over a short distance. Preserve the original location record and the evidence used to establish the correlation. If the match is uncertain, state that limitation rather than moving the verification point on the map until it agrees with the expected result. The worksheet should distinguish the recorded position from any interpreted relationship, allowing a reviewer to see what is directly supported and what requires further clarification.

Retain the identity of the source dataset, survey event and processing output used for the map. A revised processing approach can change the presentation without adding new field acquisition. Keep those events separate so that a later report does not imply the deck was surveyed again when only the analysis changed. The reporting workspace can reference files and versions, but it does not store or analyze native GPR datasets. Maintain those files in the approved evidence system and identify the exact output supporting each correlation row.

Ask the analyst to provide the relevant interpretation assumptions and review status in the form required by the project. Do not reconstruct technical settings from an image when the original record is available. If a parameter or correction affects how a result is interpreted, preserve its source reference and the responsible decision. A report preparer should not choose a new processing value merely to make the map agree with a verification observation. Differences between evidence sources are useful review information and should remain visible until the appropriate analysis explains their significance.

Record the type, date and location of the physical evidence used for correlation. This may involve an authorized direct observation, sample or other approved verification activity, depending on the project. Identify what was actually observed and the source record supporting it. Do not call an assumed condition ground truth merely because it appears in another spreadsheet. The verification evidence also has scope and limitations. A local observation may establish a condition at that location without proving that every surrounding mapped area has the same condition.

Any intrusive verification must follow the owner's authorization and technical process; this worksheet does not select locations for drilling or supply instructions for accessing a deck. The reporting task begins with the evidence produced through that approved work. Preserve the relationship between the proposed verification location and the location actually examined. If the activity was moved or could not be completed, record the change and its effect on the intended correlation. Do not substitute a nearby observation silently or mark a planned verification as completed because a row was created for it.

Check whether the survey and verification records refer to the same physical area and relevant condition. Time between events, maintenance work, changes in surface condition or a different coordinate basis may need consideration by the responsible reviewer. These factors do not automatically make the evidence unusable, but they should not disappear from the report. Record the dates and any known intervening event. Where the relationship is uncertain, describe the question rather than presenting a simple agreement or disagreement as if the records were directly interchangeable.

Keep the extent of each observation clear. A point verification, a small exposed area and a mapped zone have different spatial meanings. Avoid treating a point as if it confirms every part of a larger polygon. Conversely, a local difference should not be extrapolated automatically to invalidate an entire survey. The technical reviewer determines how the evidence affects the interpretation. The correlation table should provide the necessary location, scope and source context so that decision can be understood and revisited, rather than hiding the differences behind one overall percentage.

Define practical categories such as supports the stated interpretation, differs from the stated interpretation, location relationship unresolved or verification incomplete. Use the categories approved for the project and explain their meaning. They are working review states, not universal statistical measures or bridge condition ratings. A row should include a short reason and the relevant source references. Avoid labeling a result correct or incorrect when the evidence only addresses a narrower question. The purpose is to show what the comparison actually supports and what remains to be investigated.

Where the evidence differs, preserve both records and identify the next technical question. Possible issues may concern location correlation, interpretation meaning or the scope of the verification, but the report author should not invent a cause. Obtain the analyst's or responsible reviewer's assessment and record its reference. A disagreement can reveal a useful limitation or a need for further work. It should not be removed from the dataset merely to improve the apparent agreement of the final package. Transparent treatment makes the report more useful for planning and engineering review.

Record how the verification set was selected according to the actual project plan. If locations were chosen because they showed strong responses or were easy to access, that context matters when interpreting the resulting comparisons. Do not present a small, deliberately selected set as if it were a representative assessment of every deck area. This guide does not prescribe a sampling design or calculate a confidence level. It helps the report retain the selection basis so the responsible reviewer can determine which conclusions the evidence supports.

Keep unverified areas visible in the map index. A useful report can identify where supporting observations exist and where the interpretation remains unverified, without suggesting that unverified means either sound or defective. If further verification is proposed, describe it as proposed and identify the decision owner. The free quote planner may help organize user-entered costs for additional work, but it does not decide the required technical scope. Maintain the distinction between a commercial scenario, an approved examination plan and evidence that has actually been collected.

Use a stable correlation identifier for each comparison. Include the map and processing reference, deck coordinate, interpreted response, verification event and location, observed condition, relationship assessment and unresolved action. Where the verification location differs from the intended map point, include the actual offset or explanation supplied by the source record. Do not hide the difference in a general note detached from the row. The recipient should be able to follow one comparison from the map to the physical evidence and understand the basis for its treatment.

Separate raw observations from the analyst's interpretation and the owner's decision. These may appear in adjacent columns, but their authorship and meaning should remain clear. If a later analysis revises the map, preserve the earlier correlation record and identify which rows need review against the new output. A document revision should not silently change the source map identity while leaving old comparison conclusions untouched. The worksheet is a manual index, so the author must reconcile those relationships deliberately. The software does not detect that an external map or verification report has changed.

Consider a fictional deck survey with a mapped area described as a suspected condition zone. An authorized verification observation is recorded near its boundary, but the field location uses a different origin from the radar map. The author initially marks the relationship unresolved rather than claiming agreement. A supported coordinate cross-reference is then provided, showing that the actual observation lies outside the intended mapped area. The report preserves the physical observation and explains why it does not directly verify the original target. No point is moved simply to make the comparison fit the plan.

In another fictional row, a verification observation within a supported matching location differs from the map's stated interpretation. The author retains both records and refers the difference to the responsible analyst. The resulting review may clarify the interpretation, identify a limitation or request more evidence, but the report does not invent the answer. These examples provide a documentation pattern, not a technical diagnosis or a sampling rule. Their value is that the final table can show an unresolved location relationship and a genuine interpretive difference as two distinct questions requiring different follow-up.

In the reporting workspace, describe the survey scope, map reference and correlation purpose before presenting the table. Use observations to explain significant differences and limitations. Keep the conclusion at the level supported by the reviewed comparisons. A set of successful local correlations does not automatically establish a complete deck condition rating or quantify all deterioration. If a separate engineering assessment uses the evidence, identify that assessment and its role. Do not let the report's title or summary imply a broader decision than the actual work and review support.

Use company and client logos only as authorized identifiers and keep technical approval references separate. The tool's PDF output is a reporting format, not a certification mark or an endorsement of the interpretation. Reference native data, maps and verification records through the approved evidence system; the current workspace does not automatically embed those external files. Confirm that the intended recipient can retrieve the relevant versions. A report with precise-looking coordinates is still difficult to use if the referenced map cannot be found or its legend has been separated from the image.

Check the rendered PDF for readable coordinates, units, map identifiers and relationship categories. Select one comparison and follow it back to both source records. Then choose an unresolved row and confirm that the required next action is understandable. If a long table becomes difficult to read, split source references and conclusions into connected tables using the stable correlation identifier. Do not remove important location qualifications to make the layout smaller. Save the intended draft after corrections and create a new proof, because earlier downloaded PDFs do not update with the workspace.

Before issuing, retain the required technical review and confirm that the report represents the agreed interpretation and limitations. Issued status preserves the saved document; it does not validate radar analysis, authorize intrusive work or assign an official bridge condition rating. For later surveys or reanalysis, add the new event and identify which comparisons remain applicable. Correct an issued report through a draft revision and the owner's document process. A useful correlation record preserves the distinction between a mapped interpretation, a physical observation and a responsible decision, making the evidence clearer for future inspection and maintenance planning.