Skip to main content
Mining module

GeoMine Studio

Drillhole data, implicit geological models, kriged block models, conditional simulation, and grade–tonnage reporting — every result carrying the job, parameters, and inputs that produced it.

Request DemoExplore Mining Solutions
Drillholes to a kriged resourceFull narrated demo

Product screenshots

GeoMine Studio in action

Ordinary kriging on a 20 × 20 × 10 m lattice inside the vein shell, coloured by grade (g/t Au).
The ground surface interpolated from 113 collar elevations, with the drillholes and vein shell beneath it.
Groundrush, a public open-file gold project: 113 drillholes in 3D around the vein shell solved from their logged contacts.
Groundrush, a public NTGS open-file gold project: drillholes, the interpolated ground surface and an ordinary-kriged block model in the vein shell.
P10, P50 and P90 tonnes and grade across the conditional simulations, at the recorded cut-offs.
The review dossier: what ran, with what and by whom — and the decisions it was bound to.

Product positioning

Resource Estimation and Geological Modelling on a Certified Compute Foundation

Key capabilities

Drillhole desurveying from collars, surveys, and logged intervals
Sample compositing and content-addressed input preparation
Implicit geological modelling of contacts and stratigraphic columns
Isosurface extraction into watertight grade and boundary shells
Ordinary kriging with anisotropic variograms and declared search neighbourhoods
Sequential Gaussian simulation with realization stacks
Exceedance probability models against a stated cut-off
Grade–tonnage reporting with P10–P90 uncertainty bands
3D block, mesh, scalar-field, and drillhole visualization with sections and A/B comparison
Content-addressed artifacts with full lineage back to the source records
Structured, four-category refusals instead of silent bad numbers
Reproducibility guarantees — the same job returns the same result identity

Target users

Resource geologists
Mining geostatisticians
Exploration geologists
Mine planning engineers
Competent Persons and technical reviewers
Corporate technical services teams
Auditors and due-diligence reviewers

Component ecosystem

One chain, from logged hole to reported tonnage

GeoMine Studio connects the stages that normally live in separate desktop packages — and keeps the artifact each stage produced, so the next one consumes evidence rather than a re-keyed copy.

Drillhole desurveying

Compositing & inputs

Implicit modelling

Isosurfaces & shells

Kriging & variance

Conditional simulation

Grade–tonnage reporting

Provenance & lineage

Connected resource workflow

Each stage consumes the artifact the last one produced

No stage starts from a re-keyed spreadsheet, and every result names the inputs it came from.

Step 1

Log

Step 2

Desurvey

Step 3

Composite

Step 4

Model

Step 5

Estimate

Step 6

Simulate

Step 7

Report

Key capabilities

Resource estimation and geological modelling

Start from the drilling, not from an export

Collars, surveys, logged intervals, and assays are read from the governed project database. Desurveying returns traces in the mine's own coordinate reference and vertical datum, and the exporter refuses rather than guesses — a station with no bearing on a deviated hole, or lithology logged below the deepest survey, stops the run instead of quietly becoming an assumption.

Make the geological reading geometric

Logged contacts become anchors, an implicit field fits the declared stratigraphic column through them, and isosurfaces contour that field into shells. Nested shells from one field render as layers of a single model, ordered by isovalue — because artifacts that declare identical inputs are lineage siblings, not unrelated objects that happen to share a project.

Estimate, then quantify what the estimate hides

Ordinary kriging returns estimate and variance per block inside a declared search neighbourhood. Sequential Gaussian simulation then produces a realization stack, and an exceedance model converts it into the probability each block clears a stated cut-off — so a single kriged number is never the only thing on the table.

Report a quantity, and say that it is one

Grade–tonnage curves carry a P10–P90 band, contained metal is averaged across realizations rather than multiplied from two means, and the report states explicitly that it is not a resource classification. Classification under a reporting code stays a Competent Person's judgement, and no category label is emitted.

Hand a reviewer something they can check

Every artifact is identified by the hash of its own content and carries the kernel digest, input identities, parameter hash, randomness root, acting identity, and toolchain pins. Lineage is walked from manifests alone, stored results are re-verified on every read, and an invalid job is refused with a code, a category, and a stage rather than answered with a plausible number.

What it deliberately does not do

Being explicit about the boundary is part of what makes the rest defensible.

It does not classify

No Measured, Indicated, or Inferred label is emitted. Classification under a reporting code is a Competent Person's judgement.

It does not interpret for you

The stratigraphic column, contact polarity, and anisotropy orientation are the geologist's reading, recorded as their claim.

It does not guess

Missing assumptions, uninformed blocks, and unsurveyed ground produce a structured refusal, not a plausible number.

A module of the platform

GeoMine Studio runs on the shared geoscience foundation

Explore the platform

Request demo

Make your resource model reproducible

Talk to us about product fit, implementation scope, integrations, and deployment support.

Request DemoExplore the technology
GeoMine Studio | Mineral Resource Estimation & Geological Modelling | SpatialTechSolutions