Creating a Drill Hole Database in Vulcan

Creatin Creating g an Isis Dri llh ole Database Database in Maptek Maptek Vulc an The foundation of any mine model is the drillhole data. In Maptek Vulcan, creating the drillhole database is a prerequisite to creating downhole composites for use in block model grade estimation. As with other tools in Vulcan, there are a number of ways to create the drillhole database but, all the methods require collar location and assay data. Drillhole data can be im ported from Microsoft Access or referenced from an Acquire database but the most common method of creating a drillhole database is from comma separated values (csv) files. Vulcan anticipates separate files for collar location, assay data and survey information (optional, non-surveyed holes are assumed to be vertical). Maptek Vulcan uses a module called ‘Isis’ to maintain drillhole databases. Access the Isis module by clicking on the ‘Start’ icon in the bottom right corner of the Vulcan Workbench and select Isis from the menu.

When the ‘Open Database’ panel pops up click the ‘Cancel’ button.

This seems like an unconventional method to create a drillhole database. I think that Maptek assumes that the majority of times that the end user opens Isis, they will want to edit a database instead of create a new one. The important part here is that we have initiated the Isis module. Notice that the menus at the top of the screen have changed and the toolbars have all become grayed out. There is also a new icon in the bottom right corner of the screen. This Isis icon is shown as a depressed button. We can toggle between Envisage and Isis by clicking on the appropriate button. Next, we want to create a design (*.dsf) file for our new database. To do this click File > New Design.

In the New Database Design panel give your file a three character name and click 'OK'. Common names are ‘dhd’ for drillhole database and ‘ddh’ for diamond drillhole. The three character limit is an data limitation that may or may not be completely removed as newer versions of the software come out. I find that it is best to stick to the old naming limitations as much as possible. I don’t want to be the one to find out that longer names don’t work in the batch plotting (or similar) tool in Vulcan even if Maptek tech support tells me that they will.

In the ‘Design Properties’ menu bar type in a description (Always, always, always use a description). Click on the ‘Attributes’ button to select a database type.

In the Design Type panel select ‘Drilling’ from the Type dropdown list. The Desurvey Style drop down list allows you to specify how the down hole survey was taken. It may seem like a small item but the desurvey style has the potential to dramatically affect the location of the toe of your drillholes. If you are unsure of the desurvey style used during surveying select ‘Tangent’ as this is the most generic method. Click 'OK' to return to the 'Design Properties' menu bar. Leave the Data Source field as the default ‘Isis’ setting. Drillhole collar data and downhole assay data will be stored in tables within Isis. To create an Isis table select the menu option Table > Insert. In the Table Properties toolbar enter ‘Collar’ in the Name field. Type in a description (always use a description). In the Synonyms drop down list select ‘HoleId,Location.’ Leave the ‘Source’ field blank.

Fill out the remaining rows to mimic the columns in your collar file:

•

Name – six characters, all caps. This can be a shortened version of the column name if the original won’t fit.

•

Type – Text: any column that includes a text character. Integer: counting numbers only, no decimals. Single: decimal values up to seven significant characters. Unless you are using full UTM coordinates ‘Single’ decimal values will work. Double: decimal values up to fourteen significant characters, for incredibly accurate numbers (or very low grades).

•

Description – do I really need to say it? (always use a description)

•

Length – maximum number of characters allowed in the field. The default is 12. Memory will be set aside for each character specified so don’t get too carried away.

•

Decimals – only applies to ‘Single’ and ‘Double’ type variables. Entries with more than the specified number of decimals will be truncated to the correct length.

•

Required – if data is mandatory for a field change Required to ‘Yes.’ The HOLEID row should be required.

•

Synonyms – select synonyms for: HoleID, Easting, Northing, Elevation and TotalDepth to correspond with the row names.

•

Default Value – this specified value will be used in the drillhole database if there is no value in the csv files.

•

Type Attributes and Source – leave these fields blank unless you are setting up an outside database connection (ODBC).

We also want to specify the ‘HOLEID’ as the ‘Key’ field. This is the unifying field that appears in all the csv files to be imported. This is the field which ties them all together. Do this by right clicking on the ‘HOLEID’ row and selecting ‘Primary Key.’ The row should now show the title ‘Key’ to the left of the name column. Use the images below as a guide to fill out the table fields.

If your HOLEID.csv file looks like this:

you should fill out the HOLEID table like this:

Next we want to add tables for the assay and survey data. Do this by selecting Table > Append (the table showing the ‘Key’ field should always be the first table on the left). Synonyms for the Survey and Assay tables are 'Survey' and 'Assay' respectively. You do not need to enter the holeid field in these tables because it is assumed that the key field will appear in each table anyway. If you decide to add it to the table anyway that’s okay too. The images below are examples of how I have entered the table data for the Survey and Assay tables. If your ASSAY.csv file looks like this:

you should fill out the ASSAY table like this:

If your SURVEY.csv file looks like this:

you should fill out the SURVEY table like this:

Note: in the Survey synonyms, when it says bearing it really means azimuth. This is a function of Australian software being halfway backwards. Now that we have defined how the database structure should look we can save the definition using the menu option File > Save. Now exit Isis using File > Quit Isis. This will take you back into Envisage so that we can import the csv files into an Isis database. In Envisage select File > Import > CSV (Databases) > Databases. In the CSV Load – Data Files and Database panel we can leave most of the fields as default. If your csv files have one row of header information you can accept the default settings for the line number fields. If your csv files have more than one row of header data or no lines of header data or if there are any blank rows between the header rows and the start of data you will want to change the fields ‘Line number containing field names’ and ‘Line number where records start’ accordingly.

Under the ‘Database’ section of this panel type in a name for the Isis filename. This name should not contain spaces. To populate the ‘New Database Design field click the ‘Select…’ button (why no dropdown list and ‘Browse…’ button? I don’t know!). In the ‘Select Design from which to Create Database’ panel select your design file from the dropdown list (why do we need an entire separate panel to show a dropdown list and ‘Browse…’ button? I don’t know this either!!). Click ‘OK’ to accept the values on these two panels.

In the ‘Datafile to Record Connections’ panel specify the csv files containing your hole id, assay and survey data either b y selecting them from the dropdown list or by browsing to their remote l ocation. Next click the browse (…) button in the field connections column. In the panel that pops up (I would call it by its name but Maptek has chosen to give this panel the same name as the one that came before it) specify the record connection between the dsf file on the left and the csv column on the right. Field names that are exactly the same will be auto populated by Vulcan. In the panels for assay and survey you will need to specify the index field which is really the key field you specified in the design file. This is usually the hole id field. Click ‘OK’ to exit each of the child panels and click ‘Next’ to move on.

The ‘Specification save’ panel is intended to allow you to save all the settings you have just set to this point in the File > Import > CSV menu option. These settings can be reused to import data as long as you don’t change anything in the import process. In reality, I seldom want to import using the same settings and am often frustrated that the minor alterations I make to the process prevent me from using the saved specifications. I would recommend not saving your specifications. It is just a waste of time.

 After clicking ‘Finish’ your csv files will be imported into a new isis database. Click ‘OK’ to exit the successful import panel and ‘Cancel’ to exit the import panel.

To view your database in Isis click on the ‘Start’ icon in the bottom right corner of the workbench and select Isis. This time you can select your database from the dropdown list in the Isis Filename field. Click ‘OK.’ In the Isis view you can select a specific drillhole from the dropdown field above the database tabs. Each of the tabs (COLLAR, ASSAY and SURVEY) holds different information about the database. The COLLAR field is usually pretty boring with just the x,y,z location information. Take a look at the ASSAY and SURVEY fields for more information.

What’s next? Learn to create a Vulcan colour schema so that you can load your drillholes into Envisage. Learn to composite your drillhole data to use in block model grade estimation.