Exploration data integration

The problem

Early-stage projects rarely lack data. They lack data in one place. There is a spreadsheet per drilling campaign, a contractor report per geophysical survey, a geological map that exists only as a scan, and public records nobody has had time to download. Each uses its own coordinate system, units and naming.

Before anyone can rank a target, someone has to make these sources agree with each other. That work is slow, it is rarely documented, and it is usually repeated when the person who did it leaves the project.

What you send

• Collar, survey, assay and lithology tables, as spreadsheets, CSV files or database exports
• Geophysical grids, lines and sections, with the contractor reports that describe them
• Soil, rock-chip and stream-sediment geochemistry
• Geological maps and sections, including scanned paper maps and CAD drawings
• Anything public you already hold: survey sheets, tenure files, elevation models

Send it as it is. Gaps and inconsistencies are part of the brief, not a reason to wait.

What we do

• Bring every layer into one datum and projection, and record each transformation
• Check collars against a terrain model and downhole surveys against what a drill string can physically do
• Find overlapping, missing and out-of-order intervals
• Harmonise units and detection limits, and treat values below detection explicitly instead of as zeros
• Flag duplicate and conflicting assays for your decision; we do not resolve them silently
• Georeference and digitise scanned maps to the level the question needs

Every correction is logged, so each value in the database can be traced back to the file it came from.

What you get

One validated, georeferenced database in open formats that any GIS can read, a browser map showing all layers together, and a validation report: what was checked, what was corrected, and what remains uncertain.

Example: collar, survey and assay spreadsheets from three drilling campaigns, contractor IP and magnetic surveys, a scanned geological map and public geochemistry are merged into one validated database in a single datum, with collars checked against terrain and conflicting assays flagged.

What it cannot say

Integration does not make data better than it is. A collar located with a handheld GPS stays uncertain by metres, and an assay without quality control stays unverified. We mark those limits in the database so that later work, ours or anyone's, can weigh them.