Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                

GPR-SLICE Road Bridgedeck Module

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 6

GPR-SLICE v7.

0
Ground Penetrating Radar Imaging Software

Road + Bridgedeck Module


(updated June 2014)
GPR-SLICE v7.0 Bridgedeck and Road Module

Since 2010 GPR-SLICE has been continually developed for advanced analysis
of bridgedeck and road surveys. Bridgedeck options in the software
include:

 Automatic hyperbola search and detection


 Easy manual assist editing of detected rebar
 Mapping of peak rebar radar reflections on bridgedecks
 Multichannel and single channel capabilities
 Batch operations

The GPR-SLICE Hyperbola Search menu has several detection algorithms


available and is highlighted by an effective 5pt method. The auto-detection
operation compiles the detected rebar along with a real time dialog that
includes the peak response of the detected amplitude on the rebar (Figure
1).

Figure 1. GPR-SLICE Menu for auto-detection of rebar in bridgedeck


surveys. Peak responses of the detected rebar are reported in a real time
dialog and compiled to *.dat files for import to gridding operations.
Raw and normalized amplitudes corrected for depth variations of the
detected rebar are provided during compilation operations.

Once the peak responses are found for all the radargrams in the project,
these amplitudes are compiled and gridded directly in the Grid menu in GPR-
SLICE Software to show the distribution of amplitude response on the rebar
(Figure 2). The distribution of the peak recorded response of the rebar
reflections may help to indicate areas in the bridgedeck where varying
degrees of weathering and corrosion may exist.

Figure 2. Amplitude distribution of the peak response found on the detected


rebar over a bridgedeck.
Details of the auto-hyperbola 5 point search function

An improved algorithm to automatically detect hyperbola on


radargrams has been advanced (Figure 3). The Autosearch2 button will
engage a 5 point search. The search will look along a horizontal line from
the mouse location which is typically placed near the apex of the
hyperbola. Placing the 5pt search line on the 2nd pulse of the return and
centering it, will set amplitude thresholds centered across the hyperbola
apex at 1/4 and points 1/2 the total migrator width on each side. With
choosing a proper migrator width, the outside points (#4 and #5) will have
the opposite signs then the inner 3 points.

Figure 3. Location of the automatic hyperbola detection operation for


examining 5 points across the hyperbola apex.

Searching the hyperbola with this algorithm has proven to work


significantly better than the older scan/threshold method which is still in the
menu. The operations are to click the Help 5pt button, move the
hyperbola/line to the desired location, then left click the mouse. This will
update the search parameters dx1-5 which are the nearby scan locations
from the center, dy1-5 are the horizontal samples on the pulse, and a1-5
are the amplitudes at the 5 points. The amplitudes a1-5 are decreased from
the actually amplitudes at those locations. The point a1 is stored as .8 of
the detected value, a2-3 are recorded as .5 and a4-5 are recorded as .25
the actual recorded values to insure that amplitudes of slightly weaker
hyperbola can be detected. These slots can be manually adjusted as
well. The dy1-5 slots are always shown as 0 for the help 5pt
search. However, these can also be adjusted by the user for a more
customized search. For instance, searching a Hilbert transform-migrated
radargram, one might one to have a vertical search on the pulse to isolate a
strong anomaly etc.

Note: Autosearch2 requires setting the N-Skip and the N-Nearby


settings. The N-Nearby setting will automatically look N scan to the left and
right, and N samples up and down from the first detection location to find
the peak response from the initial detection. The N-Nearby functionality is
also engaged should the user want to manually insert hyperbolas into the
detection window. A value of 0 on the N-Nearby would yield exactly the
detected location; values of 2-4 can assist in making the detected hyperbola
more centered on the feature. There is also new setting call S-Backup. S-
Backup will move the drawn hyperbola N samples on the pulse. S-backup is
used to predict the first arrival of the wave and not the peak response, to
give a better estimate of the depth to the top of the rebar. Even though the
S-backup is engaged, the value of the peak response is reported and not the
value where the hyperbola is drawn if this options is set to other than 0.

Road Module - CALTRANS Standard for road layer evaluation

Bridgedeck license also include specialized reporting for layer evaluation


in road surveys. Along with the advanced layer calculation capabilities in
GPR-SLICE, an operation to provide reporting all the layer thickness into a
standardized format for road evaluation including GPS information, highway
marker information, road types and host of other information are now
included to Bridgedeck/Road advanced licenses. The information for
reporting is contained in a California Department of Transportation
publication and what is called the CALTRANS Standard (California
Department of Transportation. A button called CALTRANS Standard in the
Horizon Detection and Mapping menu will open up a dialog and allow for
manual insertion of the necessary header items to go along with the
required automatic layer detection information that needs to be reported
(Figure 4).

Figure 4. CALTRANS Standard – California Department of Transportation –


reporting of detected layer thickness for road evaluation surveys.

Specialized options to report road layer thicknesses have been tested and
further developed to meet the CALTRANS Standard. The module contains all
the necessary analytical operations for road layer horizon mapping and to
report these results in the CALTRANS Standard file format. An operational
button to recompile the road layer results to any desired density on the
ground was implemented to complete the CALTRANS Standard reporting.

You might also like