Process

From raw scan to georeferenced map — here's exactly how

Everything you need to know before submitting a project: the three-step workflow, what formats we accept, what we need from you, and what you'll receive.

The process, step by step

Two paths converge into the same three-step delivery. Your starting point is determined at step one.

1
Submit your project inquiry

Use the contact form on the homepage to tell us about your project. We respond within 24 hours — no commitment required at this stage. We'll confirm compatibility with your files or site conditions, ask any necessary clarifying questions, and agree on scope before anything moves forward.

If you have GPR data
You receive a secure upload link

Files are transferred over an encrypted channel. Never via email. We confirm compatibility (format, frequency, RTK presence) before you send.

If you need a survey
We schedule a scoping call

We agree on area, surface type, antenna frequency, and output requirements. A timeline and cost indication is provided before any commitment.

2
Processing & analysis

Our AI pipeline runs detection, classification, and depth estimation on your B-scan data. Uncertain detections are explicitly marked with a confidence score — we do not present borderline results as reliable. Our team applies a manual QA pass on flagged areas before delivery.

Tier 1
Within 24 hours of file receipt

Automated processing plus QA review. You receive annotated outputs the same day in most cases.

Tier 2 & 3
Agreed timeline from scoping

Typically 1–2 weeks for Tier 2. Tier 3 runs on a phased schedule agreed at scoping — you'll have specific milestone dates.

3
You receive your deliverables

All outputs are delivered via the same secure channel used for file transfer. Every deliverable includes confidence scoring and explicit flagging of low-quality zones so you can evaluate reliability for each detection independently.

Standard outputs
Annotated B-scan + depth table

Every project receives annotated B-scan images with each detection labelled by type and depth, plus a structured depth table.

With RTK data
Georeferenced GIS map

When your data includes RTK GNSS positioning, a full utility map is produced in your preferred GIS format plus a formal PDF report.

Supported input formats

We accept all major professional GPR file formats. If your equipment isn't listed, contact us before sending — we may be able to support it or convert your files.

Format Manufacturer Compatible equipment
.DZT GSSI SIR series (SIR-3000, SIR-4000, SIR-30), UtilityScan, StructureScan and most current GSSI units.
.RD3 Sensors & Software / Mala Noggin SmartCart, Conquest, Mala GPR Pro, Mala RTA. Includes most Sensors & Software units from 2005 onward.
.SGY / .SEGY Industry standard SEG-Y is supported by most modern GPR systems as an export option. Check your unit's export settings.
.DT1 Sensors & Software (legacy) Older Noggin series units (Noggin 250, Noggin 500, Noggin 1000). Common in government and academic archives.
.IDS IDS GeoRadar Stream C, Stream EM, RIS K2, and Ris Hi-Mod series. Widely used in utility and pavement survey applications.
Input formats accepted → Output formats delivered
.DZT .RD3 .SGY .DT1 .IDS .SHP .KMZ .KML .DXF .DWG .GeoTIFF GeoJSON .CSV .PDF
Coordinate Reference Systems: We deliver output in any CRS — WGS84, ED50, ITRF, or your national grid. Specify your required CRS in the project inquiry.
Field equipment & technical specs

For Tier 2 and 3 projects, we conduct the field survey using professional-grade GPR equipment. Here's exactly what that means for your project outcomes.

Antenna frequency range
100–900 MHz, selected based on your target depth and surface conditions. Lower frequency for deeper targets with lower resolution; higher frequency for shallow utilities with greater detail.
RTK GNSS positioning
Centimeter-level accuracy on all survey work we conduct — essential for producing a georeferenced utility map. Standard GPS (3–5m error) is never used for mapping work.
Detection depth
Up to 5m in favorable dry or sandy conditions. Depth penetration is reduced in wet clay, saline soils, or high-conductivity fill — we assess on-site and advise upfront.
Transect planning
Survey lines are planned based on target utility orientation and depth expectations. We use parallel transects at spacings appropriate to your antenna frequency and required detection confidence.
What you receive

Every project delivers the same core outputs. Additional outputs depend on whether RTK positioning data was present in your scans or collected during our survey.

Annotated B-scan
All tiers

Every detected utility is marked on the B-scan image with its classification, depth estimate, and confidence score. Low-confidence detections are explicitly labelled — never silently dropped or presented as confirmed.

Soil-limited or signal-congested zones are flagged on the image so you always know where detection quality was reduced by site conditions.

.PNG.PDF
Depth & detection table
All tiers

A structured table listing every detection: utility type, depth, scan position, and confidence level. Ready to hand to your engineering team for planning or to import into a site management system.

Includes per-detection notes on any limiting factors — pipe diameter uncertainty, material ambiguity, or scan quality issues.

.CSV.XLSX.PDF
Georeferenced utility map
RTK required

When your data includes RTK GNSS positioning, we produce a full utility map with each detected line georeferenced to centimeter accuracy. Utility type and depth at detection points are embedded as attributes in the GIS file.

Deliverable in any CRS you require — WGS84, ED50, ITRF, or your national grid. Specify in the inquiry and we'll match your team's software.

.SHP.KMZ.KML.DXF.DWGGeoJSONGeoTIFF
Formal PDF report
Tier 2 & 3

A professional report including methodology statement, equipment used, survey conditions, accuracy caveats, and CRS documentation. Formatted for regulatory submission where required.

If you have specific submission requirements — agency format, required disclaimers, additional sections — specify these upfront and we'll format accordingly from day one.

.PDF
Technical requirements & accuracy

Key technical details that affect what outputs are possible and how reliable the results will be.

To produce a georeferenced utility map (SHP, KMZ, DXF, DWG…), your survey must include RTK GNSS positioning — not standard GPS. RTK provides centimeter-level accuracy; standard GPS has a 3–5m error margin, which is insufficient for utility mapping at the precision construction and engineering work requires.

RTK data is typically embedded in the GPR file when the antenna is paired with an RTK GNSS receiver during the survey. If you're unsure whether your data includes RTK positioning, send us a small sample file before the full transfer — we'll confirm.

No RTK data? We still process your B-scans fully — detection, classification, and depth estimation all work. The only output we can't produce without positioning data is a georeferenced spatial map. You'll still receive fully annotated B-scan images and a depth table.

91% detection precision across pilot projects under good survey conditions. Every detection includes a confidence score. Low-confidence detections are explicitly flagged — never silently included as reliable results.

Wet clay / saline soilsHigh electrical conductivity attenuates the GPR signal rapidly. Expect reduced depth penetration and lower confidence scores in these zones.
Deep targets (>3m)Signal quality at depth depends heavily on soil type and moisture content. We flag areas where signal integrity is compromised before that depth.
Closely spaced utilitiesParallel utilities within ~30cm of each other may produce overlapping hyperbolic signatures. Individual separation is not guaranteed in these cases.
100 MHz vs 900 MHz100 MHz gives deeper penetration with lower resolution. 900 MHz gives higher resolution at shallower depth. Frequency choice affects detection quality — tell us your survey conditions and we'll advise.
Surface conditionsAsphalt and concrete produce cleaner signals than grass, gravel, or disturbed fill. Wet surfaces improve coupling but increase clutter. Tell us the surface type in your inquiry.

For a detailed accuracy profile relevant to your specific soil type, antenna frequency, and site conditions — contact us before submitting.

Data security & confidentiality

Infrastructure scan data — utility positions, depths, corridor maps — is operationally sensitive. We apply strict controls at every handling stage, and we document them.

Encrypted transfer & storage

All files transferred over TLS-encrypted channels. Data at rest is encrypted. Files are never sent over email — you receive a secure, expiring upload link specific to your project.

No third-party sharing

Your raw files, processed outputs, and project details are never shared with third parties. Files are only accessible to the team members directly working on your project — no exceptions.

Defined retention & deletion

Raw input files are deleted after project completion. Processed outputs are retained for 30 days for re-delivery, then deleted — unless you request extended storage in writing.

NDA on request

For sensitive infrastructure or government projects, we sign a mutual NDA before any data is shared. Request it in your inquiry — it's sent before you send a single file.

Strict access control

Projects are fully siloed — no cross-project data access, no shared processing environments between clients. Your data stays within your engagement only.

Data processing agreement

All projects are covered by a DPA defining scope, purpose, and constraints of how your data is used. Shared and signed before work begins on any project.

What GPR can and can't do

GPR is the most effective non-destructive method for subsurface utility detection — but it has real physical constraints. We're transparent about both so you can plan with accurate expectations.

Soil conditions affect detection quality
Wet, clayey, or high-conductivity soils reduce GPR signal penetration significantly. Saturated fine-grained soils absorb the signal quickly — we evaluate on-site and factor this into our approach.
False negatives exist
Some utilities may not be detected — when pipe material has low dielectric contrast with surrounding soil, pipes are very small diameter, or soil conditions limit depth. We flag areas of reduced confidence explicitly, never present uncertain detections as confirmed.
Heavily congested corridors
In zones with many closely spaced utilities — typical of dense city centers — individual utilities can be difficult to separate. We report congested zones as such rather than attempting unreliable delineation.
With good input data, our AI performs well
When GPR data is collected under favorable conditions — dry or sandy soils, correct trace interval, appropriate antenna frequency — our AI achieves high precision and accuracy. Garbage in, garbage out: we are only as good as the data we receive.

AI performance — good survey conditions

Metrics from our validated pilot dataset. Performance varies with input data quality and site conditions.

Detection Precision91%
Classification Accuracy88%
Depth Estimation (±10%)84%
Honest caveat: These numbers reflect near-ideal conditions. In challenging environments — wet clay, metallic debris, rocky subsurface — accuracy will be lower. We always communicate site-specific limitations before you commit.
How we report uncertain detections

Every detection carries a confidence score. Where detections are ambiguous, we mark them low confidence rather than dropping them silently or presenting them as confirmed. Soil-limited and congested survey areas are flagged explicitly in the deliverables.

What to prepare before you reach out

A few details upfront let us give you an accurate timeline and cost indication immediately — and avoid back-and-forth.

If you have GPR data (Tier 1)
What to check before submitting
1
Confirm your file format

We accept DZT, RD3, SGY, and DT1. If your format differs, contact us before sending — we may be able to convert it.

2
Check for RTK / GPS positioning data

If your GPR was paired with an RTK GNSS receiver during the survey, position data should be embedded in the file. This determines whether we can produce a georeferenced utility map.

3
Note the survey conditions

Antenna frequency used, surface type (asphalt, grass, gravel, concrete), and suspected utility depth range. Soil type is helpful if known — it helps us flag likely accuracy limitations before we begin.

If you need a survey (Tier 2 & 3)
What to have ready for the scoping call
1
Define the area to be surveyed

Approximate dimensions in m² or km for linear projects. A rough sketch or map outline is helpful — formal drawings are not required at this stage.

2
Surface type and suspected conditions

Surface material, expected utility depth range, and soil type all affect antenna frequency choice and survey planning. Any existing utility records or site maps are valuable context.

3
Share your deliverable requirements

Which GIS software do you use — QGIS, ArcGIS, AutoCAD? Is it for internal use or regulatory submission? The more detail you give, the better we can scope from day one.

4
Geographic coverage

Our primary operations are in Turkey. For other regions, contact us with your location — we coordinate with select local survey partners and will confirm coverage and timeline.

Ready to submit your project?

Use the contact form — tell us your situation and we'll respond within 24 hours with a clear path forward.