Visualizing a GSM in 2D on a Fence Diagram or Non-Orthogonal Section

Introduction

In

the current version of MineSight 3-D (MS3D), creating a cross-section of a model view is possible only along an orthogonal orientation. This article presents a method of viewing model data on a fence diagram or non-orthogonal plane utilizing a composite file drillhole view. This method of viewing model data as drillhole data, in 2D on a fence diagram or on a non-orthogonal grid plane, can also be used to view a 3D block model (3DBM), as was demonstrated at the 2009 Annual Mintec Seminar (see 2009 Seminar workshop paper, MineSight 3-D: Tips & Tricks). This newsletter article demonstrates how to view Gridded Seam Model (GSM) data, in 2D on a fence diagram and on a nonorthogonal, non-vertical section using a composite file drillhole view. This method should only be used as a visualization tool. The basic methodology is: MineSight Compass (MSCompass): export the model data to an ASCII file. MineSight Data Reformat Tool (MSDART): create drillhole IDs (DHIDs). MSCompass: create a dummy composite file containing the ASCII model data. MS3D: create a drillhole view with the composite file and use the drillhole strips option to simulate the block display in a fence diagram or non-orthogonal plane.

Export the Model Data from the GSM

Using MSCompass, export data from your existing GSM to ASCII via the procedure, p60301.dat (Figure 1). Table 1 summarizes which items from the model will be used later in the composite file (File 9). Toggle on the option to export the X, Y, Z locations rather than the model column, row, and bench values. And, since this is a Gridded Seam project rather than a 3D block model project, toggle on the option to omit the block centroid Z value in the output file. We will use the ZTOP and ZBOT values instead. Then output any quality items (i.e., BTU, MOIST, SULF, etc.) you might want to query or display in the resulting drillhole view.

Figure 1 shows the first two panels from procedure, p60301.dat. Choose the model items to export and toggle the option to export the mid-block X, Y, Z values rather than column/row/bench, as well as the option to export just the X and Y values (omit Z).

June 2009

Model items X (block centroid) Y (block centroid) ZTOP ZBOT Quality items (BTU, Moist, etc.)

Composite file items EAST NORTH ZTOP ZBOT Quality items (BTU, Moist, etc.)

Figure 2 shows a portion of the resulting output file from procedure p60301.dat. From left to right, the values for X (Easting), Y (Northing), ZTOP, and ZBOT are shown for a few blocks.

Table 1 shows the association between the model items and the items in the composite file. Note the first four items in the composite file column are also required items in a composite file.

Figure 2 shows a portion of the ASCII file output from procedure p60301. dat; Easting, Northing, ZTOP, and ZBOT.

Use MSDART to Create DHIDs

The next step is assigning a DHID to each line of data so we can use MSCompass procedure p50001.dat to load the data into a temporary composite file. Each line of data will correspond to one drillhole having a single composite. Assigning the DHID is easily accomplished via MSDART, using the Counter option on the Output Options panel (Figure 3). On the Load Options page, the source file is the resulting output file from procedure p60301.dat, and the destination file will be used as input to p50001.dat. The Counter option will add a field called Counter that contains integer values that are incremented for every line in the destination output file. As an option, you can use the Reorder function to place this field in the first data column in the output file.

Figure 3 shows the Load Options and Output Options panels from MSDART. On the Load Options panel specify both the input file and output file names. On the Output Options panel, use the Counter option to create a field called Counter. You can optionally use Reorder to put the Counter field in the first column in the output data file.

Figure 4 shows a portion of the resulting output file from MSDART. From left to right, the values for Counter (to be used as DHID later on), X (Easting), Y (Northing), ZTOP and ZBOT are shown for a few blocks. Compare this to Figure 2. The only difference between the files is the addition of the Counter field in the first column.

Figure 4 shows a portion of the ASCII file output from MSDART; counter (will be used as DHID), Easting, Northing, ZTOP and ZBOT).

June 2009

Create a Composite File (dummy File 9)

Create a dummy composite file. In our example, this file will be called coal09.gsm. Open MSCompass and click on the Project tab, then open the Project File Editor (PCF) (Figure 5). In the PCF Editor, either click on the New File button , or go to File | New... (Ctrl+N) and create a new 9 - Composite file. The required items in a File 9 are displayed in blue; they cannot be edited and are always included (i.e., REF#). Add any additional quality items (match the model items that you exported), then save and name the new composite file.

WARNING: Make sure your REF# maximum is at least as large as the number of blocks in your model. The limits on the other items should match the limits in your GSM file.

Figure 5 shows the use of the PCF Editor in MSCompass to create a composite file (File 9). The items with blue highlight are required and cannot be changed.

Load Data to the Composite File (File 9) via Procedure, p50001.dat

Load the data that was output from MSDART into the new composite File 9 using MSCompass procedure p50001.dat (Figures 6 and 7). Note the order of the data columns in the input file; in the procedure, the composite file items must be listed in the same order they occur in the input file. Since there is no corresponding survey file (File 12), choose the option to load data to File 9 only, and then specify which composite file items to use for the collar geometry (EAST, NORTH, and ZTOP for elevation).

June 2009

Figure 6 shows the first panel in procedure p50001.dat. The composite file items must be listed in the order they occur in the input file. Load the Counter data created in MSDART to item REF# it will serve as the DHID.

Figure 7 shows panels 2 and 3 from procedure p50001.dat. Since there is no corresponding survey file (File 12), choose the option to load the data to File 9 only. On the last panel, choose the GSM elevation item to use for defining the drillhole collars (this is required in a GSM project regardless of whether you are loading data to a survey file [File 12] or not). Finally, toggle on DH-IDENT is a numeric ref# value option.

Before proceeding further, check to ensure that the data was loaded properly. Use procedure p50301.dat (List Composite Data). If the data was successfully loaded, proceed to the next step. If not, review the steps described previously. Review the ASCII data files as well as the new composite file (File 9, i.e., do the data item descriptors (min/max/precision) in the file match the input data? etc.).

June 2009

Create a Composite File Drillhole View

In MS3D, create a Drillhole View of the new composite file (Figure 8). Each drillhole has a single interval that corresponds to a block in the GSM. Composite items EAST, NORTH, ZTOP, and ZBOT are used to define the location. To create a Drillhole View in MS3D, choose File or click right in the Data Manager and then select New | DH View | MineSight.

Figure 8 shows drillhole view creation dialogs from MS3D. In the dialog on the left, choose Composite File (File 9) and select the new composite file (coal09.gsm, in this example). Then, click on the toggle for no survey since there is no survey file associated with this composite file. Composite items were previously selected for the collar geometry when the data was loaded to the composite file. The dialog shown on the right is where the start and end point geometry items are defined as well as the item that contains the DHID.

Open the Model View and Drillhole View and use the same display item in each to visually verify that the composite drillhole data was loaded to the proper location (Figure 9).

Warning: You have created a drillhole for every model block. Therefore, viewing the model blocks and drillhole data at the same time can be resource intensive. Opening, closing, and changing the orientation of the Viewer may be slow.

Figure 9 shows a 3D vertically exaggerated view of a GSM Model View (in Surface/Slab display mode) overlaid with the Drillhole View of the composite data. This confirms there is a drillhole interval for each model block.

June 2009

You can also visually verify that the data was loaded properly by viewing a Drillhole and Model View on an orthogonal cross section as shown in Figure 10.

Figure 10 shows an EW slab of GSM blocks and composite Drillhole View data on an Edit Grid. The composite data occurs in the center of the model blocks, and the length of the composite intervals is equal to the thickness of the model blocks which are outlined.

Add Strips and Projection Volume to the Drillhole View

In order to view the data on a fence diagram or nonorthogonal section, you will need to switch to 2D mode. Simulate model blocks on section by turning on Drillhole Strips (Figure 11) in the Drillhole Properties dialog. On the Strips tab, click on the button to Add a Color Strip , then click on the Color Strip Properties button to specify the color display item and the strip width. In the example used in this article, we specified a width of 45m (which equals 90% of the model block size). Use the option to center the strip over the drillhole trace, this simulates a mid-block location.

Figure 11 shows the Drillhole Properties | Strips tab, and the Strip Definition dialog for Color Strips.

June 2009

Set the projection volume for the drillhole data on the Drillhole Properties | Display tab (Figure 12). In this example, we use +25 m and -25 m to simulate the projects model block size (50 m). Because the method we are presenting in this article is for visualization purposes only, you may want to experiment with different projection volume values to see what works best for you.

Figure 12 shows the Drillhole Properties | Display tab, where you can set the 2D projection volume for drillhole data.

View the Data in 2D on a Fence Diagram

Attach a fence polyline to the Viewer by clicking on the Set Fence geometry button . Choose an existing polyline to use for the fence and then switch to 2D mode. In this example, our polyline exists on the horizontal plane, well above the highest level in the model, has an attributed name Fence1, and traverses across the project area. Figures 13, 14, and 15 show this fence in three different views.
Figure 13 is an oblique view across the model area showing the model blocks, drillhole data, and the fence diagram. The model blocks are shown as Filled polygons, and the drillhole data is located in the center of the model blocks. The fence polyline is defined by the polyline with circular nodes and Easting and Northing labels at each fence post. The white fence plane is only for illustrative purposes to show how the fence section bends across the project area.

Figure 14 is a plan view showing the model blocks and the fence polyline with its nodes labeled with their Easting and Northing values. The dashed lines are 25m on either side of the fence polyline to show the projection volume.

June 2009

Figure 15 is a fence diagram cross-section of pseudo GSM data. Drillhole data is displayed using a strip width of 45m centered on the +/-25m projection volume to simulate a GSM block (xy block size in this project is 25 x 25), and a strip width of 45m centered on the drillhole.

View the Data in 2D on a Non-Orthogonal, Non-Vertical Grid Plane

The same method is used to display GSM data on a non-orthogonal section (vertical or non-vertical). Attach an existing non-orthogonal grid plane to the Viewer using the Set a grid set to the Viewer button , and then switch to 2D mode. In the example in this article, we are using a non-vertical, non-orthogonal grid plane (Figures 16 and 17). The pseudo model blocks appear offset from one another because of the Grid plane orientation, the projection volume, and Strip width. Tweaking the projection volume and/ or the Strip width may create a more acceptable view.

Figure 16 shows the non-orthogonal, non-vertical Grid plane in relation to a GSM Model View and the composite drillhole data.

June 2009

Figure 17 shows a portion of the 2D section view on the non-orthogonal, non-vertical grid plane shown in Figure 16 displaying pseudo GSM data (composite drillhole data). Drillhole data is displayed using a strip width of 45m centered on the +/-25m projection volume to simulate a GSM block (xy block size in this project is 25 x 25).

Conclusions
In summary, until the option is available to view a 2D cross section of your GSM in any orientation in MS3D, you can use the following methodology as a visualization tool: 1. MSCompass: export X, Y, ZTOP, ZBOT, and any quality items of interest from the GSM using procedure, p60301.dat. 2. MSDART: create DHIDs. 3. MSCompass: create a dummy composite file (File 9) and load the data into the composite file (File 9) via procedure p50001.dat. 4. MS3D: create a Composite Drillhole View. 5. MS3D: add strips and set the Projection Volume in the Drillhole View. 6. MS3D: view the data on a fence diagram. 7. MS3D: view the data on a non-orthogonal, non-vertical Grid Plane.

June 2009