Vulcan Driver Category

Current driver status: Import available, export available.

Drag and drop supported? Yes

Support status: Supported.

To access this driver:

1. Display the Data Import screen. This screen is displayed when import-loading and when adding a file association to the current project. In all cases, functions are found on the Data ribbon.
2. Select the SurpacData Category and an item in the Data Type list.

 

About Vulcan Data Formats

Note: the Vulcan .bmf block model export driver cannot generate a .bmf file larger than 4gb in size. This is a restriction of a 3rd party driver over which Datamine has no direct control.

The import and export of block model data from the Vulcan software is achieved using a customized ASCII text file.  This text file contains a separate record for each block or sub-block in the model.  Information about the origin, dimensions and rotation of the model are stored in a separate block model definition file (.bdf).

The Vulcan Block Model Data Source Driver (DSD) can be used to import a block model that has been exported from Vulcan using the appropriate option.  

The DSD can also be used to create an ASCII text file and an accompanying .bdf file by exporting any block model that has be loaded into or created. These two files can then be used to transfer the block model into the Vulcan application.

Vulcan block models can contain alphanumeric fields, that is, fields that contain text data such as lithological names.  In the Vulcan software these fields are referred to as ‘name type variables’. A limitation of the Vulcan software’s export option is that when an ASCII data file is created integer values are substituted for the actual text.  In order to solve this problem the Vulcan Block Model DSD uses a look-up table to match the integers to the correct text value.  The resulting block model therefore contains the actual text and not an integer substitute.

The look-up table of integers and text value pairs is stored in a separate text file. Vulcan does not create this file during the export process, you must create it yourself using a text editor or spreadsheet program.

The look-up table text file should consist of a set of comma separated records. Each record contains a variable name, an integer value and a look-up string.  For example, the text file for a block model containing two alphanumeric fields called “Rock” and “Stope” may look like this:

Rock, 1, Limestone

Rock, 2, Dolomite

Rock, 3, Basalt

Rock, 4, Alluvium

Stope, 1, P235

Stope, 2, P237

Stope, 3, S452

The order of the records in the file is not important. Text strings that contain spaces and commas do not have to be enclosed in quotes. Any lines that do not begin with the name of one of the data fields in the block model will be ignored.

If, when importing a Vulcan block model data file, an integer value is encountered for which there is no corresponding text string in the look-up table then the Datamine software will create an integer instead of a text string.

When exporting a block model a look-up table text file with the format described above can be created.  This is useful when transferring a block model to Vulcan from another mining software package.

In addition to block model files, this driver also supports the import and export of Design Database files and Wireframe files.

HARP Model Format

Vulcan's HARP model format is supported by your driver. If you choose to import the necessary fields (ZBOT... and ZTOP...), your Studio application will detect these fields and automatically generate a prism model in memory, as opposed to a standard block model. All HARP models must be imported using the Block Model BMF Files driver.

For more information on prism vs. block model formats, refer to your application's help file.