Skip to main content

Voxel Models Context Menu

Commands available when right-clicking Voxel Model objects in the Data Tree. Voxel models are 3D volumetric grids (voxels = volume pixels) representing continuous 3D data such as seismic volumes, geological property distributions, or interpolated subsurface models. Each voxel stores attribute values at regular grid positions.

Voxel Model Group Operations​

Commands available when right-clicking a Voxel Model Group (folder containing voxel model collections).

New​

Menu name: New Tooltip Create new voxel model in this group.

What it does Creates a new, empty voxel model within the group. The new model is a 3D grid container that can be populated with imported data, interpolated from point measurements, or computed from analytical functions. Requires specification of grid dimensions (I,J,K cell counts), cell sizes, and spatial extent.

When to use it

  • Creating voxel models for interpolation
  • Preparing containers for seismic data import
  • Setting up 3D property grids for modelling
  • Establishing structured grids for simulation

Notes The created voxel model is initially empty (all cells have no-data or default values). Grid parameters (dimensions, cell size, origin, orientation) must be defined during creation or immediately after. Memory requirements can be substantial for high-resolution grids - a 500×500×500 grid with 32-bit float attributes requires ~500 MB per attribute.

Import​

Menu name: Import Tooltip Import voxel model from file.

What it does Opens file dialogue to import voxel model data from external formats including SEGY (seismic), GRDECL (petroleum reservoir), VTK structured grids, and custom binary formats. Imports grid geometry (dimensions, cell sizes, coordinate system) and associated volumetric attributes. Multiple attributes may be imported simultaneously.

When to use it

  • Loading seismic volumes
  • Importing reservoir property models
  • Bringing in interpolated subsurface grids
  • Loading voxel data from geological modelling software

Notes

Large Data Volumes

Voxel models can be very large (gigabytes). Import may be time-consuming and memory-intensive. Consider data resolution and spatial extent before importing full-scale volumes.

SEGY is a standard seismic format - import reads trace headers for positioning and samples as voxel values. GRDECL format (Eclipse simulator) contains grid geometry and multiple properties. Coordinate system may need manual specification if not embedded in file format. Imported models may require memory management settings for large volumes (streaming, level-of-detail, compression).

Export​

Menu name: Export Tooltip Export all voxel models in group to files.

What it does Opens export dialogue to save all voxel models in the group to external formats. Supports formats including VTK structured grids, raw binary, and custom voxel formats. Each model is typically exported as a separate file with grid geometry and attribute data.

When to use it

  • Exporting models to simulation software
  • Creating deliverables from interpolation results
  • Sharing voxel data with collaborators
  • Archiving volumetric models

Notes Export format determines file size and compatibility. Binary formats are compact but may have endian-ness issues across platforms. ASCII formats (VTK) are larger but more portable. Grid geometry (dimensions, spacing, origin) is embedded in most formats. Multiple attributes may require separate files or format-specific multi-attribute support.

Empty List​

Menu name: Empty List Tooltip Remove all voxel models from group.

What it does Removes all voxel models from the group, clearing the model list whilst preserving the group container itself. This is a batch deletion operation affecting all models simultaneously. Source files on disk are not affected - only project references and loaded data are removed.

When to use it

  • Clearing temporary voxel data
  • Freeing memory from large volumetric datasets
  • Starting fresh with new model imports
  • Cleaning up after analysis workflows

Notes

Large Data Release

Removing voxel models can free substantial memory (potentially gigabytes for high-resolution volumes). Ensure important results are exported before clearing the list.

The group container remains and can be repopulated with new imports. This is the fastest way to release memory from multiple large voxel models.

Voxel Model Operations​

Commands available when right-clicking individual Voxel Model objects.

Goto​

Menu name: Goto Tooltip Move the 3D view to frame the voxel model.

What it does Centres and zooms the 3D view on the selected voxel model, positioning the camera to show the full 3D extent of the volumetric grid. The view is adjusted to frame the voxel model's bounding box, providing an overview of its spatial coverage.

When to use it

  • Locating voxel models in 3D space
  • Reviewing model spatial extent
  • Verifying model positioning and georeferencing
  • Navigating to areas covered by volumetric data

Notes View extent matches the voxel model's 3D bounding box. Voxel models are typically displayed as volume renderings, cross-sections, or isosurfaces. The "Goto" view provides context for the full model extent before zooming into specific regions or slices.

Export​

Menu name: Export Tooltip Export voxel model to file.

What it does See Export in Shared Commands for complete documentation. Opens export dialogue to save the voxel model to external volumetric formats (VTK, SEGY, binary grid files). Exports grid geometry, coordinate system, and attribute data.

When to use it

  • Exporting individual models to simulation software
  • Creating deliverables for specific volumes
  • Sharing interpolation results
  • Archiving model data

Notes Export includes all active attributes in the model. File size can be substantial for high-resolution volumes. Consider export format compatibility with target software (e.g., SEGY for seismic interpretation, GRDECL for reservoir simulation).

Delete​

Menu name: Delete Tooltip Permanently remove voxel model from project.

What it does See Delete in Shared Commands for complete documentation. Permanently removes the voxel model from the project, freeing associated memory. Source files on disk are not affected - only the project reference and loaded data are removed.

When to use it

  • Removing unwanted voxel models
  • Freeing memory from large volumetric datasets
  • Cleaning up after analysis
  • Managing project resources

Notes Operation cannot be undone and may free substantial memory. Ensure important results are exported before deletion. The original data file remains intact and can be re-imported if needed.

Insert Intersection​

Commands for creating cross-sectional slices through the voxel model along grid-aligned planes.

I Intersection​

Menu name: I Intersection Tooltip Create cross-section perpendicular to I-axis (along J-K plane).

What it does Extracts a 2D cross-sectional slice from the voxel model perpendicular to the I-axis (the first grid dimension). The intersection plane shows a J-K slice through the volume at a specified I-index position. The resulting cross-section displays voxel attribute values as a 2D image or surface, useful for inspecting internal volumetric structure.

When to use it

  • Inspecting internal structure along primary grid direction
  • Creating cross-sections through seismic volumes
  • Visualising property distributions in slice view
  • Extracting 2D slices for interpretation or export
  • Quality control of volumetric interpolation

Notes

Grid Axes

Voxel models use I,J,K indexing:

  • I-axis: Typically easting or inline direction (columns)
  • J-axis: Typically northing or crossline direction (rows)
  • K-axis: Typically depth or elevation direction (layers)

I-intersections are vertical slices perpendicular to I-axis, showing variation in J and K.

Position of the slice is specified by I-index (e.g., I=250 extracts the 250th column). The slice can be moved interactively or positioned at specific index values. Multiple I-intersections can be created to examine different positions. Useful for seismic interpretation (inline slices), reservoir modelling (column sections), or any volumetric data inspection.

J Intersection​

Menu name: J Intersection Tooltip Create cross-section perpendicular to J-axis (along I-K plane).

What it does Extracts a 2D cross-sectional slice from the voxel model perpendicular to the J-axis (the second grid dimension). The intersection plane shows an I-K slice through the volume at a specified J-index position. Displays voxel attribute values as a 2D image, useful for inspecting variations along the J-direction.

When to use it

  • Viewing cross-sections along secondary grid direction
  • Creating crossline slices in seismic data
  • Inspecting property variation perpendicular to I-direction
  • Quality control from different viewing angles

Notes J-intersections are perpendicular to J-axis, showing variation in I and K. For seismic data, these are typically crossline slices (perpendicular to inlines). Position is specified by J-index. Multiple J-intersections complement I-intersections for comprehensive volumetric inspection. Together, I and J intersections provide orthogonal views through the volume.

K Intersection​

Menu name: K Intersection Tooltip Create cross-section perpendicular to K-axis (along I-J plane).

What it does Extracts a 2D cross-sectional slice from the voxel model perpendicular to the K-axis (the third grid dimension, typically depth/elevation). The intersection plane shows an I-J slice through the volume at a specified K-index position. This creates horizontal or depth slices showing map views of volumetric attributes.

When to use it

  • Creating depth slices or horizontal sections
  • Viewing map-view patterns in volumetric data
  • Extracting horizon slices for mapping
  • Analysing spatial patterns at specific depths
  • Creating time slices in seismic volumes

Notes K-intersections are typically horizontal or depth slices, showing spatial variation in the I-J plane (map view). For subsurface models, these are depth slices showing property distribution at constant elevation/depth. For seismic, these are time slices. Position is specified by K-index (e.g., K=100 might represent 1000m depth depending on grid spacing and origin).

Particularly useful for identifying spatial trends, anomalies, or patterns that extend laterally. Multiple K-intersections at different depths reveal vertical variation in properties. Together with I and J intersections, provides complete 3D volumetric inspection capability.

Additional Operations​

Import​

Menu name: Import Tooltip Import additional data into existing voxel model.

What it does Opens dialogue to import additional attribute data into the existing voxel model grid. The grid geometry (dimensions, cell sizes) remains unchanged; new attribute channels are added with values read from imported files. Useful for adding multiple properties to the same volumetric grid or updating attribute values.

When to use it

  • Adding new attributes to existing voxel model
  • Updating property values from new data
  • Importing multiple properties to same grid
  • Combining attributes from different sources

Notes Imported data must match the existing grid dimensions and spatial extent. Mismatched grids will produce errors or require resampling. Common workflow: create grid from first property, then import additional properties to the same grid structure.

Make Active​

Menu name: Make Active Tooltip Set this voxel model as the active volumetric dataset.

What it does Designates the selected voxel model as the "active" volumetric dataset. The active model is used as a reference by various operations and may receive special display treatment. Only one voxel model can be active at a time.

When to use it

  • Before operations requiring a reference volume
  • When working with multiple voxel models
  • For workflows that reference the active model
  • Setting primary volume for intersection operations

Notes Active status affects which model receives new intersections, attribute operations, or queries. Some analysis tools automatically apply to the active voxel model. Useful when multiple volumetric datasets are loaded simultaneously.

Create TriMesh​

Menu name: Create TriMesh Tooltip Extract triangulated mesh surface from voxel model isosurface.

What it does Generates a triangulated mesh surface (isosurface) from the voxel model at a specified attribute threshold value. Uses marching cubes or similar algorithm to extract a 3D surface where the voxel attribute equals the threshold. The resulting mesh can be edited, refined, and analysed using standard mesh tools.

When to use it

  • Extracting surfaces from volumetric data (e.g., geological horizons)
  • Creating mesh representations of seismic reflectors
  • Generating surface models from interpolated volumes
  • Visualising specific property value boundaries
  • Converting volumetric to surface representations

Notes

Isosurface Extraction

An isosurface is a 3D surface of constant attribute value in a volume. For example, extracting isosurface at density=2.5 g/cm³ creates a mesh where all points have that density value.

Threshold value determines which surface is extracted (e.g., seismic amplitude=0 for zero-crossings, porosity=0.2 for 20% porosity boundary). Mesh resolution depends on voxel grid resolution - finer voxel grids produce more detailed meshes. Large voxel models may produce very large meshes requiring decimation. Multiple isosurfaces can be extracted at different threshold values to represent layered structures.

Connected Volume​

Menu name: Connected Volume Tooltip Identify and extract connected volumetric regions.

What it does Performs connected component analysis on the voxel model, identifying contiguous 3D regions where voxel values meet specified criteria (e.g., above/below threshold, within range). Connected voxels (sharing faces, edges, or corners) are grouped into discrete volumetric bodies. Each connected volume can be labelled, measured, and extracted separately.

When to use it

  • Identifying discrete geological bodies in property models
  • Segmenting seismic facies into separate units
  • Finding isolated high/low value regions
  • Quantifying disconnected reservoir compartments
  • Separating touching or overlapping features

Notes Connectivity can be defined as:

  • Face connectivity (6-connected): Voxels share a face (most restrictive)
  • Face+edge connectivity (18-connected): Voxels share face or edge
  • Face+edge+corner connectivity (26-connected): Voxels share face, edge, or corner (most permissive)

Results include connected volume count, volume measurements for each body, and optional labelling where each voxel is assigned its connected component ID. Useful for reservoir characterisation (identifying separate reservoir compartments), ore body analysis (discrete mineralized zones), or any application requiring volumetric segmentation. Small isolated regions may be noise and can be filtered by minimum volume threshold.