Skip to main content

GIS Data Context Menu

Commands available when right-clicking GIS (Geographic Information System) objects in the Data Tree. GIS data includes vector layers (shapefiles, GeoJSON), attributes, and components imported from GIS software for integration with 3D geoscience data.

GIS Group Operations​

Commands available when right-clicking a GIS Group (folder containing GIS layers and datasets).

New​

Menu name: New Tooltip Create new GIS layer in this group.

What it does Creates a new, empty GIS layer within the group. The new layer is a container that can be populated with imported vector data (points, lines, polygons), attributes, and georeferencing information. Provides a framework for organising GIS data within the VRGS project.

When to use it

  • Preparing to import GIS vector data
  • Creating placeholders for digitised features
  • Organising multiple GIS datasets
  • Structuring GIS data before import

Notes The created layer is initially empty and requires data import or creation to be useful. Layer type (point, line, polygon) is typically determined during import or creation operations.

Import​

Menu name: Import Tooltip Import GIS data from file.

What it does Opens file dialogue to import GIS vector data from standard formats including shapefiles (.shp), GeoJSON, KML/KMZ, GeoPackage, and other vector formats. Imports geometry (points, lines, polygons), attributes, coordinate reference system, and styling information. Data is added as new layers within the GIS group.

When to use it

  • Loading shapefile vector data
  • Importing geological maps from GIS
  • Adding spatial reference data (faults, contacts, sample locations)
  • Integrating external spatial datasets
  • Bringing in field mapping data

Notes

Shapefile Components

Shapefiles consist of multiple files (.shp, .shx, .dbf, .prj). Import automatically reads all components. Ensure all shapefile files are in the same directory.

Automatically detects coordinate system from .prj file or embedded CRS metadata. If CRS is missing, manual specification may be required. Attributes from attribute table (.dbf) are preserved and can be used for filtering, colouring, or analysis. Large shapefiles may take time to import depending on feature count and complexity.

Import Folder - Shape Files​

Menu name: Shape Files Tooltip Batch import all shapefiles from a folder.

What it does Opens folder dialogue to batch import all shapefiles found in the selected directory. Each shapefile is imported as a separate GIS layer within the group. Subdirectories are typically scanned recursively. Useful for importing entire GIS projects or map series containing multiple shapefile layers.

When to use it

  • Importing complete GIS projects
  • Loading multiple map layers simultaneously
  • Batch processing shapefile collections
  • Importing geological map series (geology, faults, contacts, etc.)

Notes All shapefiles in the folder and subfolders are imported automatically. Ensure shapefiles have consistent coordinate systems for proper alignment. Layer names are derived from shapefile names. Import may take significant time for folders containing many or large shapefiles. Review imported layers to verify correct geometry types and CRS.

Export​

Menu name: Export Tooltip Export all GIS layers to files.

What it does Opens export dialogue to save all GIS layers in the group to external vector formats. Common export formats include shapefiles, GeoJSON, KML/KMZ, GeoPackage, and DXF. Each layer is typically exported as a separate file with geometry, attributes, and coordinate system information preserved.

When to use it

  • Sharing GIS data with collaborators
  • Exporting interpreted features to GIS software
  • Creating deliverables from interpretation work
  • Archiving GIS data
  • Preparing data for GIS analysis

Notes Export preserves geometry, attributes, and coordinate reference system. Styling (colours, symbols) may or may not be preserved depending on target format. Shapefiles support limited attribute types (string, integer, double); complex attributes may be simplified. GeoJSON and KML support embedded styling. For maximum compatibility, shapefile export is most widely supported.

Empty List​

Menu name: Empty List Tooltip Remove all GIS layers from group.

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

When to use it

  • Clearing temporary GIS data
  • Starting fresh with new GIS imports
  • Removing all layers whilst keeping group structure
  • Cleaning up after data review

Notes

Batch Deletion

Removes all layers in the group without individual confirmation. Cannot be undone. Ensure important data is exported before clearing the list.

The group container remains and can be repopulated with new imports. This is faster than deleting layers individually when cleaning up large GIS datasets.

GIS Attribute Operations​

Commands available when right-clicking GIS Attribute objects (attribute fields attached to GIS features).

Set as Z Value​

Menu name: Set as Z Value Tooltip Use this attribute as elevation (Z coordinate) for 2D features.

What it does Designates the selected attribute field as the source for Z (elevation) values for GIS features. For 2D vector data (points, lines, polygons with only X,Y coordinates), this attribute's values are used to position features in 3D space. Essential for draping GIS data onto topography or creating 3D representations from attributed 2D features.

When to use it

  • Draping 2D GIS layers onto elevation surfaces
  • Creating 3D features from attributed points (e.g., sample elevations)
  • Converting 2D contours to 3D elevation lines
  • Positioning geological contacts at measured elevations
  • Integrating survey data with elevation attributes

Notes

2D to 3D Conversion

Many GIS datasets store elevation as an attribute rather than geometry. This command enables 3D visualisation by extracting Z values from the attribute table.

Common attribute names used for elevation: "Z", "ELEV", "ELEVATION", "HEIGHT", "ALTITUDE", "DEPTH" (negative for subsurface). The attribute must contain numeric values. Once set, features are positioned at the specified elevations in 3D space. If attribute values are missing for some features, those features may remain at Z=0 or be flagged as invalid.

Typical workflow:

  1. Import 2D shapefile with elevation attribute
  2. Right-click elevation attribute field
  3. Select "Set as Z Value"
  4. Features are repositioned in 3D based on attribute values
  5. Layer can now be visualised alongside 3D models and point clouds

GIS Component Operations​

Commands available when right-clicking GIS Component objects (individual features or feature collections within layers).

Convert To Point Cloud​

Menu name: Point Cloud Tooltip Convert GIS features to point cloud format.

What it does Converts GIS vector features to point cloud representation. Points are created at feature vertices (for lines/polygons) or at feature locations (for points). The resulting point cloud can be processed using point cloud tools (filtering, meshing, analysis). Attribute values can optionally be transferred as point cloud attributes.

When to use it

  • Converting GPS tracks or sample points to point cloud format
  • Densifying vector features for point cloud processing
  • Integrating vector and point cloud workflows
  • Creating point clouds from digitised features

Notes Point density depends on vertex spacing in original features. Complex polygons with many vertices produce dense point clouds; simple lines produce sparse points. Consider whether attribute transfer is needed - attributes become point cloud attributes accessible for filtering and colouring.

Convert To Polylines​

Menu name: Polylines Tooltip Convert GIS features to VRGS polyline objects.

What it does Converts GIS vector features to native VRGS polyline interpretation objects. Line features become polylines directly; polygon features are converted to their boundary polylines; point features may create single-vertex polylines or be skipped. The resulting polylines can be edited, refined, and analysed using VRGS polyline tools.

When to use it

  • Converting GIS line data to editable interpretations
  • Importing fault traces for 3D modelling
  • Converting geological contacts to interpretation polylines
  • Bringing GIS digitised features into VRGS interpretation workflow

Notes Conversion enables use of VRGS polyline editing and analysis tools (refinement, smoothing, 3D operations). Polylines inherit coordinate system and elevation from source GIS data. Attributes may be preserved as polyline metadata depending on configuration. Multi-part features create multiple polylines.

GIS Layer Operations​

Commands available when right-clicking GIS Layer objects (complete vector layers containing features).

Goto​

Menu name: Goto Tooltip Move the 3D view to frame the GIS layer.

What it does Centres and zooms the 3D view on the selected GIS layer, adjusting the camera to show the full spatial extent of all features in the layer. The view is positioned to provide a clear overview of the layer's geographic coverage.

When to use it

  • Locating GIS layers in 3D space
  • Reviewing layer spatial extent
  • Navigating to areas covered by specific layers
  • Verifying layer positioning and georeferencing

Notes View extent matches the layer's bounding box. Useful for understanding layer coverage relative to other datasets. For large-extent layers (regional maps), the view may be very zoomed out. For point layers with sparse features, the zoom may encompass large empty areas.

Export​

Menu name: Export Tooltip Export GIS layer to file.

What it does See Export in Shared Commands for complete documentation. Opens export dialogue to save the GIS layer to external vector formats (shapefile, GeoJSON, KML, etc.). Exports geometry, attributes, and coordinate system information for the layer.

When to use it

  • Exporting individual layers to GIS software
  • Creating deliverables for specific map layers
  • Sharing interpreted features
  • Archiving layer data

Notes Export preserves original geometry type (point, line, polygon). Coordinate system is embedded in export format (shapefile .prj, GeoJSON CRS property). Attributes are exported to attribute table format supported by target format.

Convert To Point Cloud​

Menu name: Point Cloud Tooltip Convert entire GIS layer to point cloud.

What it does Converts all features in the GIS layer to point cloud format. See GIS Component "Convert To Point Cloud" for details on conversion process. This operates on the entire layer at once rather than individual components.

When to use it

  • Batch converting all layer features to point cloud
  • Creating point clouds from entire shapefile layers
  • Integrating full GIS datasets into point cloud workflows

Notes Same conversion rules as component conversion, applied to all features in layer. Resulting point cloud contains points from all features, potentially mixed geometry types if layer contains diverse feature types.

Convert To Polylines​

Menu name: Polylines Tooltip Convert entire GIS layer to VRGS polylines.

What it does Converts all features in the GIS layer to VRGS polyline interpretation objects. See GIS Component "Convert To Polylines" for details on conversion process. This operates on the entire layer at once.

When to use it

  • Batch converting all layer features to polylines
  • Importing complete fault trace or contact layers
  • Converting entire geological map layers to interpretations

Notes Each feature becomes a separate polyline. Layer with 100 fault traces creates 100 polyline objects. Useful for importing complete interpreted datasets from GIS into VRGS interpretation framework.

Convert To Faults​

Menu name: Faults Tooltip Convert GIS layer to VRGS fault interpretation objects.

What it does Converts GIS vector features (typically lines or polygons) to VRGS fault interpretation objects. Line features become fault traces; polygon features may become fault surfaces or their boundaries become fault traces. The resulting faults can be analysed and modelled using VRGS fault tools, including fault surface construction and kinematic analysis.

When to use it

  • Importing mapped fault traces from GIS
  • Converting structural geology layers to fault interpretations
  • Bringing external fault databases into VRGS
  • Creating fault models from GIS digitised features

Notes

Geological Interpretation

Conversion creates fault interpretation objects with geological context, not just generic polylines. Faults can have attributes like dip/azimuth, displacement, and fault type assigned after conversion.

Particularly useful when importing regional fault maps or structural interpretation from GIS software. Converted faults can be extended into 3D fault surfaces using VRGS fault modelling tools. Attributes from GIS (fault name, type, movement sense) may be preserved as fault metadata. For best results, source GIS layer should contain linear fault traces rather than complex polygons.

Delete​

Menu name: Delete Tooltip Permanently remove GIS layer from project.

What it does See Delete in Shared Commands for complete documentation. Permanently removes the GIS layer and all its features from the project. Source files on disk are not affected - only the project reference is removed.

When to use it

  • Removing unwanted GIS layers
  • Cleaning up after data review
  • Deleting incorrectly imported layers
  • Managing project organisation

Notes Operation cannot be undone. All features, attributes, and layer configuration are removed from the project. The original shapefile or vector file remains intact on disk and can be re-imported if needed.