Skip to main content
Version: 3.4.20 (unreleased)

Basic Interpretation

Interpretation in VRGS means drawing on the outcrop: tracing a bed, measuring its dip, outlining a channel body. Every tool works the same way — arm the tool from the ribbon, then click on the model — and every tool works on both meshes and point clouds.

This guide covers the tools on the Interpretations ribbon tab. If you are completely new to VRGS, walk the tutorial first; this page is the fuller reference behind it.

How every tool behaves​

Learn these five things once and every tool below makes sense.

ArmingClicking a ribbon tool puts the mouse into that mode. The cursor changes to show which tool is armed.
FinishingSingle-point tools finish on the click. Multi-point tools (polylines, faults, geopolygons, scan lines) finish on a double-click.
Dragging still navigatesLeft-drag orbits the view even with a tool armed, so you can re-frame mid-interpretation without disarming anything.
One object, then back to navigatingWhen a tool finishes it returns you to normal navigation — unless Sticky Interp is on.
UndoCtrl+Z, or Undo on the Edit panel, steps back through digitising.
Sticky Interp is the setting that saves the most time

Structure → Sticky Interp keeps the tool armed after each object, so you can digitise twenty fractures without going back to the ribbon between each one. Turn it off (or press the tool again) when you are done.

Pause Digitising

Mid-polyline and need to fly round the corner of the outcrop? Edit → Pause Digitising suspends the tool so the mouse navigates normally, and pressing it again resumes the same line. It is not the same as finishing.

Before you start: the Active Descriptor​

The Active Descriptor panel sits at the left of the Interpretations tab and carries three dropdowns:

FaciesThe facies assigned to each new object as you create it.
ContactThe contact — a picked boundary, such as a formation top or an unconformity — given to each new polyline.
UnitThe stratigraphic unit — the interval between two contacts — given to each new scan line.

A trace follows a boundary, so polylines and faults take a contact. Things that lie within the rock — orientations measured on bedding, geobodies, scan lines and stratigraphic units — take a unit. The Unit dropdown also lists the project's intervals, so an orientation or a geobody can be given the interval it lies in instead.

Setting these before you digitise is far quicker than editing objects afterwards, and it is what makes the interpretation colour-coded and filterable later. New Contact and New Unit create an entry, and the Apply button beside the contact gives everything currently selected its stratigraphy: the selected traces take the active contact, and everything else takes the active unit. That is how you fix a batch you digitised under the wrong setting. The facies has an apply button of its own.

The lists themselves live in the Collections tree, under Facies, Contacts and Units.

Orientations — Dip Azimuth​

The Dip Azimuth tool records a planar orientation. Five methods, and the choice matters:

MethodHow you drive itUse it when
3 PointsClick three points on the plane. The best-fit plane is built on the third click.The default, and right most of the time — a bedding surface with three clear points on it.
N PointsClick as many points as you like; double-click to finish. In the Vulkan view Space switches to a draw mode, where dragging across a surface lays the points; press it again to go back to clicks, keeping the points so far.The surface is curved or noisy and three points would be unrepresentative.
1 PointClick the location, then type the dip and dip direction.You measured it in the field with a compass-clinometer and want it in the model at the right place.
AreaLasso a region on screen; every point inside is gathered and a plane fitted through all of them.A large, well-exposed surface — the most robust fit available. Point clouds only.
AttributesClick a point on a mesh that has been analysed for dip and azimuth.The mesh already carries per-vertex orientation attributes and you just want to sample one.

Whichever method you use, the result is an orientation object in the Interpretation tree, plotted on the stereonet and usable by every downstream tool.

Area mode needs a point cloud

The lasso gathers points from visible point clouds. On a mesh-only project use N Points, or analyse the mesh for dip and azimuth and use Attributes.

How good is the pick?​

Every orientation VRGS fits for you — 3 Points, N Points, Area, a polyline turned into an orientation with Calculate Best Fit Plane, or a whole-model Best Fit Plane — is graded as it is made, and reports the result in its Orientation properties:

PropertyWhat it says
ErrorRMS scatter of the clicked points about the fitted plane, in degrees. Bigger is worse. A 3-point pick has no scatter, so it reports how thin the triangle is instead, and 90° if the three clicks were collinear
Colinearity / CoplanarityFernández's ratios, as described for attributes
Tavani Collinearityλ₁/λ₂. Lower is better — below 30 excellent, below 100 good
Tavani Coplanarity(λ₁ + λ₂ + λ₃)/λ₃. Higher is better — above 5000 excellent, above 2000 good
Gradeexcellent, good or rejected — the worst of every test below

The grade follows Table 2 of Tavani et al. (2024). They had an experienced geologist digitise bedding traces across seven photogrammetric outcrop models twice over — once with a live preview of the best-fit plane to work against, and once without it, to imitate an unaided or automated pick — and took the difference between the two as their measure of what a good trace looks like.

The grade is a label, not a veto: a rejected pick is still made, still plotted and still exported. It is there so you can sort your measurements by how much they deserve to be believed, rather than discovering the weak ones later on a stereonet.

Grade a whole group at once

The properties panel shows one pick at a time, which is the wrong tool for deciding which of two hundred measurements to trust. Right-click the group → Spreadsheet View puts every one of these columns on screen for the whole group, and clicking a column header sorts by it — so sorting on Grade or Tavani Collinearity brings the weak picks to the top in one go. The same columns cover polylines, faults and geopolygons, and untick Fit Quality in the view's properties to hide the block when you do not need it. Every column it can show is defined in The Interpretation Spreadsheet.

TestExcellentGood
Tavani Collinearitybelow 30below 100
Tavani Coplanarityabove 5000above 2000
Number of nodes12 or more8 or more
Trace length ÷ model resolutionabove 60above 30
Mean node spacing ÷ model resolutionabove 5above 3

The last two compare your digitising against the detail the model actually holds, so they need a figure for the model's resolution. Tavani et al. define that as the square root of the area per triangle, and VRGS estimates it the same way — from the median facet area of a mesh, or, for a point cloud with no facets to measure, converted from its median nearest-neighbour spacing. Both tests skip themselves when the pick has no recorded source model, rather than guessing at a resolution and rejecting good traces on the strength of it.

Treat those two as checks on your digitising style, not as evidence about the plane. Of the nine trace properties the authors measured, only collinearity tracked how far the fitted plane actually ended up from the true bedding; length and node spacing showed no relationship with it at all. Their thresholds simply describe how the expert picked, and are set a standard deviation or two below that. The node-count floor is best read the same way — the paper asks for it to be weighed alongside node spacing rather than applied as a rule on its own.

Traces picked in 3.4.19 or earlier may grade one step better now

Earlier builds divided by a point spacing — a triangle edge or a nearest-neighbour distance — rather than by the square root of the area per triangle. The two differ by about a third, so the length and node-spacing tests ran roughly 50% stricter than Table 2 intends and could cost a pick a grade step the published benchmarks would have allowed it. Both feed the overall grade, so a trace you remember as good may now read excellent. Nothing about the fitted plane, its dip, azimuth or error has changed — only the two normalised style checks.

Why collinearity is the one that matters

It is worth seeing once why this index, of all of them, is the one that predicts a bad measurement.

Where a discontinuity cuts a flat outcrop face, the trace it leaves is a straight line. Infinitely many planes contain that line and all of them fit it equally well, so the fit is settled by your picking scatter rather than by the rock — and it lands on the orientation of the outcrop face, not of the discontinuity you were measuring. The result looks clean and is entirely wrong.

Where the same discontinuity crosses undulating topography, the trace bends out of any one line, and the plane it pins down is the real one. So: favour traces that wander across a rough or convex face, and be suspicious of a beautifully straight trace on a flat wall. That is what the visually-aided digitisers in the study were doing that the unaided ones were not.

A 3 Points pick always grades as rejected

Three nodes is below the eight-node floor, so the grade can never rise above rejected however clean the geometry — and that is the intended reading, not a fault. Three points define a plane exactly: there is no scatter left over to measure, so nothing about them can tell you whether the surface you clicked is really planar. The paper is blunt that a robust error test needs significantly more than three nodes.

3 Points remains the right tool for a clear bedding surface, and is still the default. But when a measurement has to be defensible — an orientation that will drive a DFN, or one you will quote — pick it with N Points or Area so there is enough redundancy to grade.

Earlier versions had this backwards: a 3-point pick passed the quality check unconditionally, including three nearly collinear clicks, which is exactly when a 3-point pick is worthless.

Polylines​

A polyline is the workhorse: a bed trace, a contact, a channel margin, a cross-section line.

ModeHow you drive it
Digitise PointsOne vertex per click. Double-click to finish.
DrawFreehand — hold the left button and drag, and vertices are dropped at the project's minimum digitiser spacing.
Geodesic DistanceClick sparse points; the line follows the shortest path across the surface between them, with a running along-surface length.
Texture TrackClick sparse points along a contact; between clicks the line follows the contact through the photo texture. Vulkan view.

Geodesic Distance is the one worth knowing about. A straight segment between two clicks cuts through the rock; a geodesic stays on it. That makes it the right tool for measuring a distance along an undulating surface, and for tracing a contact across topography with only a handful of clicks.

Texture Track​

Texture Track is an auto-tracker for the outcrop model, in the spirit of a horizon tracker on seismic. You click on a contact, click again a few metres along it, and VRGS finds the contact in the photo texture between the two clicks and lays the line on it. Keep clicking along the contact to extend the line; double-click or Enter finishes it. It is on the Digitise Polyline dropdown beside Geodesic Distance, and it behaves like it in every other respect: Backspace removes the last segment, Ctrl+Z undoes, and the vertices are exact surface positions that are never snapped.

How it finds the contact. The mesh alone cannot do this well: its triangles are centimetres to decimetres across, while a contact is defined by the colour of the rock at the scale of the photo's pixels, and a path that follows triangle edges is jagged by construction. So VRGS does not track on the mesh. It unrolls a strip of the texture along the surface path between your clicks — each column of the strip is the rock's own cross-section, followed over ledges and under overhangs — finds the contact in that image the way a seismic tracker finds a horizon in a section, following a change of colour from one column to the next with a limit on how steeply it may turn, and drapes the result back onto the surface. When the photo texture is finer than about a centimetre it does this twice: once at about 1 cm per pixel across a wide strip to decide where the contact is, then at the texture's own resolution in a narrow strip around that answer to place it precisely. With a coarser texture a single pass at the texture's own resolution does both.

What it looks for is the edge you clicked on. The contrast at your clicks sets the strength it expects: a stronger edge gains nothing over yours, and the line is held near the course described next, so a stronger, parallel bed a few decimetres away does not pull the line onto it, even where your contact fades.

Which way it expects the contact to run. A bed is close to a flat plane over a few metres, so between your two clicks the contact lies where some plane through both clicks cuts the rock. VRGS tries the planes through your clicks, keeps the one whose trace the texture agrees with best, and holds the line near that trace. This matters on rough rock: the shortest path across the surface between two clicks detours round bulges and recesses, often tens of centimetres off the bed, while the plane's trace goes over them as the bed does. Where no plane fits the texture clearly better than the shortest path, usually because the rock is smooth enough for the two to agree, the line is held near the shortest path just as firmly. Either way it can still leave that course where the texture clearly shows the contact elsewhere, so a contact that curves is followed too.

Where the contact is hidden — vegetation, scree, a shadow — there is nothing in the texture to follow. A stretch of 5 cm or more where it finds no convincing edge is drawn as a straight line between the points where the contact is visible either side, which is what you would draw by hand across a covered interval.

The status bar reports each segment's confidence, how clear an edge the line sits on from 0 to 100 %, and the size of the image it tracked in. Where the corridor between the clicks has no texture the segment follows the plain geodesic, and the status bar says so.

Getting good lines
  • Click on the contact itself, not beside it: the edge under your click is what the tracker looks for.
  • Click where the contact is clear. A click in vegetation, scree or a blurred patch of photo gives the tracker a faint target to match along the rest of the segment. Start and end a segment where the contact is crisp, and let the tracker carry it across the poor stretch between.
  • Click every few metres. Between two clicks the tracker has to decide which bed is yours from the texture alone, and over a long span that gets harder. Beyond 5 m the status bar suggests clicking closer together.
  • A wrong segment is one Backspace away. Remove it and click an extra point on the contact where it went astray.
Current limits
  • Texture Track follows a contact: a change of colour or brightness across the line. It is not yet tuned for a thin dark or bright line such as a fracture trace or a vein; use Geodesic Distance for those.
  • It runs in the Vulkan view. In the OpenGL view the button is unavailable.
  • It needs a textured mesh. On an untextured mesh each segment follows the geodesic; on a point cloud the segments are straight.

Editing a line as you build it​

On the Digitise Polyline dropdown:

CommandWhat it does
Split LineClick a vertex to cut the line into two.
Join LinesSelect two or more lines (Ctrl-click), then join them into one.
Add NodeClick anywhere along a line to insert a vertex.
Draw ContourDigitise a contour line.
Close PolylineClose the line into a ring.
Snap To MeshMove the selected line onto the active mesh, adding vertices so that it follows the surface. See Snapping a line to a mesh.
Create GeobodyBuild a geopolygon from the selected polylines.

Snapping a line to a mesh​

Snap To Mesh moves a polyline onto a mesh, for a line that was digitised against something else or has been moved off the surface. It is greyed out unless exactly one polyline is selected and a mesh is active, and the line needs at least two vertices.

  • Every vertex goes to the closest point on the mesh, which is not always straight down.
  • Vertices are added along each segment and snapped as well, so the line follows the surface between the points you digitised. They are no further apart than the polyline's sub-sampling distance, which is 1 project unit by default. No panel changes it in this release, so thin a result that is too dense with Refine by Spacing.
  • The snapped line replaces the old one. It is what the view draws, what picking and measuring use, and what is saved with the project.
  • Undo restores the line as you digitised it. This step has no Redo.

The snap runs in the foreground with a wait cursor, so a long line takes a while: about 17 seconds for a 4 km line on a mesh of 1.2 million vertices, which took the line from 5 vertices to 4045. The messages panel reports the new vertex count and the spacing. A mesh that is busy with another operation is refused.

The Edit panel​

These apply to polylines and faults alike:

CommandWhat it does
Move VerticesClick a line to show its vertices, then drag one. Hold Alt while you drag to move the whole line with it. Click the command again to finish.
3D TranslateMove a vertex along an axis or in a plane, using on-screen handles. Hold Alt while you drag a handle to move the whole line with the vertex. The same tool edits a cross section through the handles on its pillars. See below for how it behaves in the Vulkan view.
Snap VerticesWhile digitising, snap each new vertex onto an existing one — for making traces meet exactly.
Erase VerticesClick vertices to delete them.
Reposition ObjectClick an object to pick it up, then click where it should go.
Pause Digitising / UndoAs described above.

In the Vulkan view 3D Translate keeps its gadget until you put it away:

  • A press that misses the handles keeps the gadget and whatever it was holding, so a near miss does not cost you the object.
  • Shift, or Pause Digitising, hands the left button back to navigation, so you can re-angle the view mid-edit without disarming the tool.
  • Esc, or Move Mode, disarms the tool and removes the gadget.
  • On an orientation, double-click the gadget or press R to switch between the translate arms and the orientation knobs. Ctrl+wheel resizes the gadget.
  • A scale bar moves from its base, where the gadget attaches.

Faults​

Faults digitise exactly like polylines, and get their own tools because a fault is usually built from several sticks rather than one line:

CommandWhat it does
New FaultStart a fault.
Add stickAdd another stick to the existing fault.
Extend FaultContinue a stick from its end.
Split / JoinDivide a fault, or merge two.

VRGS calculates the fault's orientation from its geometry, so a digitised fault plots on the stereonet alongside your measured planes.

Auto Tracker​

Auto Tracker follows a feature across the mesh for you rather than making you click along it — you give it a start and an end and it finds the path between, guided by the mesh's own attributes. Settings puts its parameters in the properties panel.

OpenGL view only

The Auto Tracker digitising tool is handled by the OpenGL view. In a Vulkan view the button is inert — use Texture Track to follow a contact through the texture, Geodesic Distance for other surface-following traces, or switch renderer. (The mesh-following tracker used by measured sections works in both.)

Scan lines​

A scan line samples fracture intensity along a line, the way a tape across the outcrop does in the field. Two ways to build one:

ModeWhat it does
From intersectionsDigitise the line; VRGS intersects it with the orientations already displayed and records where each one crosses.
From PointsDigitise the line, then mark each fracture position along it by hand.

Both finish on a double-click and need at least two points. The result feeds fracture-intensity analysis and DFN work.

Plunge​

The Plunge tool measures a lineation: click the start and end of the line and VRGS returns its plunge and trend. Faults get a plunge calculated automatically.

Geopolygons​

A geopolygon outlines a body on the outcrop and extrudes it into a solid, so you can measure it and attach observations to it.

ModeHow you drive it
Digitise PointsOne vertex per click around the outline; double-click to close and finish.
DrawFreehand around the outline.
Key PillarAdd a pillar that controls the extrusion. Pillars are listed under the geopolygon's Key Pillars branch in the Interpretation tree, where Delete Key Pillar removes one.
Create from polylinesBuild the outline from polylines you have already digitised.

At least three points are needed. The ring is closed for you — you do not have to click back onto the first point.

Working on a geopolygon after you have drawn it​

Right-click it in the Interpretation tree and choose Make Active. A Geobody ribbon tab appears with its editing tools: showing and moving nodes, interpolating new nodes between selected ones, and adding palaeocurrents.

Extract Volume… on the tree menu measures the volume the outline encloses — against a horizontal datum, or against the outline's own best-fit plane where the ground slopes. See the Geopolygons, Fill & Volume guide.

Palaeocurrents​

A geopolygon can carry many palaeocurrent measurements, each with an azimuth, an optional bidirectional flag (for a trend rather than a direction) and a structure type. The types are edited in the Collections tree under Sed Structures.

This is not decoration. An outcrop only exposes a body at whatever angle the cliff happens to cut it, so apparent widths are biased. Palaeocurrents recorded on the body are what let that bias be corrected into a true width.

There is also a standalone Palaeocurrent tool on the Sedimentology panel for a measurement that does not belong to a body.

What to do with an object once you have made one​

Everything below is on the object's right-click menu in the Interpretation tree.

  • Give it meaning — set its facies, its contact or unit (Apply → Active Contact or Unit), or its stratigraphy. Faster still, set the Active Descriptor before digitising.
  • Group it — Group collects selected objects under one tree entry. Groups are the unit almost everything downstream works on: colour-by-group on the stereonet, orientation sets for a DFN, surface gridding inputs.
  • Convert it — a polyline can become an orientation; orientations can become a gridded surface; polylines can become a geopolygon.
  • Clean it up — Refine by Spacing thins vertices to a spacing you choose, Smooth removes digitising jitter, Remove Dip flattens a best-fit dip out of a line.
  • Version it — put an interpretation under version control to keep several admissible interpretations of the same feature side by side.
  • Export it — to file, or as GeoJSON.
  • Re-attach it — see below.

Interpretations stay on their models​

With Keep Interpretations On Their Models on in Project Properties (the default for new projects), each vertex of a polyline, orientation, log or other interpretation records where it lies on its mesh or point cloud. When the model is moved, by a drag, ICP, a correction, a rescale or a change of coordinate system, the picks go with it, and an undo of the move brings them back.

Re-attach to Surface, on the right-click menu of an interpretation or a folder of them, anchors the selection where it lies now. Use it for vertices left behind when a model moved after its triangles changed, once you have put them back on it, and for anything that never had an anchor. It runs in the background with its own progress bar, and refuses while a save is running. The menu item is there only while the project setting is on.

Where interpretation leads​

You haveNext
OrientationsStereonet — plot, contour, cluster into sets
Orientation setsDFN — build a fracture network from them
Polylines / orientationsSurface Gridding — interpolate a surface through them
Traces on photographs2D image interpretation
A measured sectionGeological logging
A distance, height or angleMeasuring

Tips and troubleshooting​

  • The tool disarmed itself after one object. That is the default. Turn on Sticky Interp to keep it armed.
  • Clicking does nothing. The click has to land on a mesh or point cloud — a click on empty sky is discarded. Check the object you are aiming at is visible.
  • My polyline is a mess of vertices. Draw mode drops a vertex every minimum-spacing step. Use Refine by Spacing afterwards, or digitise with Digitise Points.
  • Two traces should meet but do not. Turn on Snap Vertices before digitising the second one.
  • Area dip/azimuth does nothing. It gathers points from point clouds; there is nothing to gather on a mesh-only project.
  • Everything came out with the wrong facies. Select them all, set the facies in the Active Descriptor, and use its apply to selected button.
  • Traces came out on the wrong contact. Select them, choose the contact in the Active Descriptor, and press Apply. The same button gives selected orientations, geobodies and scan lines the active unit.

See also​