Professional Documents
Culture Documents
Documents - Pub - Surpac Database Tutorial PDF
Documents - Pub - Surpac Database Tutorial PDF
DATABASE
________________________________________________________________
www.cadfamily.com EMail:cadserv21@hotmail.com 1/79
The document is for study only,if tort to your rights,please inform us,we will delete
_______________________________________________________________
Copyright © 2005 Surpac Minex Group Pty Ltd. All rights reserved.
This software and documentation is proprietary to Surpac Minex Group Pty Ltd.
Surpac Minex Group Pty Ltd publishes this documentation for the sole use of
Surpac licenses. Without written permission you may not sell, reproduce, store in
a retrieval system, or transmit any part of the documentation. For such
permission, or to obtain extra copies please contact your local Surpac Minex
Group Office.
While every precaution has been taken in the preparation of this manual, we
assume no responsibility for errors or omissions. Neither is any liability assumed
for damage resulting from the use of the information contained herein.
All brand and product names are trademarks or registered trademarks of there
respective companies.
This manual has been designed to provide a practical guide to the many uses of
the software. The applications contained within this manual are by no means
exhaustive as the possible uses of the software are only limited by the user’s
imagination. However, it will give new users a starting point and existing users a
good overview by demonstrating how to use may of the functions in Surpac
Vision. If you have any difficulties, or questions whist working through this
manual feel free to contact your local Surpac Minex Group Office.
FILES USED................................................................................................................................................. 4
DISCUSSION................................................................................................................................................ 4
DATABASE STRUCTURE......................................................................................................................... 4
COLLAR TABLE................................................................................................................................... 4
SURVEY TABLE ................................................................................................................................... 5
OPTIONAL TABLES............................................................................................................................. 5
MAPPING A DATABASE .......................................................................................................................... 6
Surpac Mapping Detail database tree .................................................................................................. 9
Removing a table and field mapping................................................................................................... 11
Adding an optional database field to a Mandatory table.................................................................... 11
Renaming an optional database field in a table.................................................................................. 12
Mapping Optional Tables (sample or geology) .................................................................................. 12
TASKS........................................................................................................................................................ 14
1. Map the surpac_training.mdb database to create the surpac_training.ddb map link .................... 16
2. Add an interval table called “geology” with an optional field called “lithology” to the “surpac”
database. ............................................................................................................................................. 21
3. Import geology and sample data into the database from the files geology.txt and samples.txt,
respectively. ........................................................................................................................................ 21
4. Display the drillholes and create colour display styles for lithology and assays ........................... 23
5. Manipulation of the drillholes by:................................................................................................... 29
• Display lithological codes on the right-hand side. .................................................................... 29
• Display assays on the left-hand side.......................................................................................... 29
• Display colour-filled bar graphs of the gold assays on the left-hand side and offset them 5m. 29
6. Drillhole Investigation and interrogation ....................................................................................... 32
7. Sectioning by Create E-W sections starting at 7120N to 7600N in steps of 40m............................ 34
8. Interpretation and digitizing of sections on screen ......................................................................... 42
9. Flagging an interval table with 3dm intercepts .............................................................................. 44
COMPOSITING......................................................................................................................................... 47
BENCH ELEVATIONS ....................................................................................................................... 48
DOWNHOLE COMPOSITING........................................................................................................... 52
COMPOSITING DOWNHOLE CONSTRAINED BY INTERCEPT TABLE ....................................... 53
COMPOSITING GRAPHICAL ............................................................................................................... 56
OPTIONAL EXERCISE ........................................................................................................................... 62
Grade Control Activity........................................................................................................................ 62
VERTICAL SECTIONS FOR PLOTTING ............................................................................................ 72
SETTING UP A MAP ENTITY FOR PLOTTING ................................................................................ 76
FILES USED
Files used in this lab exercise are found in the following folder:
C:\GEOLOGY\DATABASES\DATA
DISCUSSION
The Geological Database module in Surpac is one of the most important set of tools you can
learn. Drillhole data are the starting point of all mining projects and constitute the basis on which
feasibility studies and ore reserve estimations are done. A geological database consists of a
number of tables, each of which contains a different kind of data. Each table contains a number
of fields of data. Each table will have many records with each record containing the data fields.
Surpac uses a relational database model and supports several different types including oracle,
paradox and Microsoft access.
We also support Open Database Connectivity for ODBC and can connect to databases across
networks.
A database can contain up to 50 tables and each table can have a max of 60 fields
DATABASE STRUCTURE
Surpac requires 2 mandatory tables within a database: collar and survey.
COLLAR TABLE
The information stored in the collar table describes the location of the drill hole collar, the
maximum depth of the hole and whether a linear or curved hole trace is to be calculated when
retrieving the hole. Optional collar data may also be stored for each drill hole. For example, date
drilled, type of drill hole or project name. The mandatory fields in a collar table are:
The survey table stores the drill hole survey information used to calculate the drill hole trace
coordinates. Mandatory fields include: downhole depth at which the survey was taken, the dip
and the azimuth of the hole. For a vertical hole, which has not been surveyed, the depth would
be the same as the max_depth field in the collar table, the dip as -90 and the azimuth as zero.
The y, x and z fields are used to store the calculated coordinates of each survey. Optional fields
for this table may include other information taken at the survey point e.g., core orientation. The
mandatory fields in a survey table are:
OPTIONAL TABLES
Aside from the mandatory tables, optional tables may be added and used to store such data as
geology and assays. There are 3 different types of optional tables that can be added to a
database:
The interval tables require the depth at the start of the interval and the depth at the end of the
interval, called the depth_from and depth_to fields respectively. The point tables require only the
depth where the sample was taken, called the depth_to field. A sample identifier field is defined
for interval tables but this field is not a key field and so does not require data if not available. The
y, x and z fields are used to store the calculated coordinates of the sample depths. The discrete
sample tables are used for storing data for a point, which has a unique samp_id. All that is
MAPPING A DATABASE
How does Surpac connect to a Database?
Whether connecting to a database which has been created using Surpac or one created
independently, a database definition file is required to read/write to the database.
Put simply, a database definition file (*.ddb) can be described as a header file that describes:
The ddb file is a text file and does no contain any data. It allows Surpac to connect to a backend
relational database and is usually the same name as the database itself.
If connecting to a database that was not created using Surpac Vision, a ddb file has to be created
in order to view drill and manipulate the data in Surpac. This is called “mapping” (or connecting)
a database and
Surpac Vision has a function that allows a ddb file to be created quickly and simply. If the
structure of the database does not change, ie the field and table names do not change, this
process only need to be done once.
Data can be added to a database at any point. This does not change the ddb file, you are simply
adding more data into each table.
For Surpac to read a database, it must know where the geological database and drill hole data
live if the database is not created within Surpac. Surpac knows that certain tables and fields
exist, but the location of these must be “mapped” so that fields can be linked.
The DB MAPPER function is a tool that is used to set up the mappings between the actual
database and the database Surpac expects to have. This function will also allow you to define a
view of your database by specifying which tables and fields you want Surpac to know about. This
is useful if you have a very large database and Surpac only needs to use information from a few
of the tables. It is also possible to add validation information to fields in your tables using the DB
MAPPER so that Surpac will check the integrity of the data that is about to be stored or modified
in your database.
Once you have finished mapping your database, a ddb file will be produced that Surpac can then
use to connect to your database. If you rename or change the configuration of your database, you
can use the DB MAPPER to reflect these new changes.
A process bar may appear. This may appear for a minute or so, depending on the size of
database.
The form is split into two halves. The left hand side, Source Database, shows all tables and
queries contained in the Database. The right and side, Mapping Detail, shows the table and
fields names (explained in the previous section) that Surpac requires to connect to a database. If
you open one of these folders by clicking on the “+” symbol to the left of the folder, a list within
that table will be displayed.
Tip: Surpac can map Queries in a Database. Set up a query to look at specific holes, map the
queries, Only this data is accessible in Surpac.
The mapping detail side of the form shows two folders labelled "Mandatory Tables" and "Optional
Tables". As discussed earlier, Surpac requires mandatory tables within a database to display
and manipulate drillholes. The mandatory tables that Surpac requires are the 'collar'and '
survey'
tables.
The "Interval Tables", "Point Tables" and "Discrete Tables" folders will be used to specify which
non-mandatory tables in your database that you wish to access.
NOTE: Any table names or fields names that have an asterisk (*) next to their name MUST be
mapped.
If the external database has used the same table names and field name conventions as a
database created using Surpac then during the process of mapping the database, Surpac can
identify the collar, survey, interval and point tables automatically (note this is case sensitive).
If other naming conventions have been used, including upper or mixed case, then each table
must be mapped.
Any table names or field names that have not been recognised by the Mapper is highlighted with
an asterix (*).
Drag and drop the collar table from the left hand side over the top of the collar table on the right
hand side. Repeat this process to map each of the Mandatory fields. All optional fields are
mapped automatically.
If you have mapped a Surpac table or field with an incorrect table in your database, you can
remove the mapping by selecting the Surpac table/field folder name and by right clicking on the
mouse. A menu will popup with the option to Remove mapping. Select this item from the menu
and the mapping will be removed
The other option is to follow the mapping procedure using the correct name.
If you have mapped one of your database tables to a Surpac mandatory table and you wish to
access other fields in the database you can map these to the optional fields within that table.
Highlight the database field name with a left mouse click and without releasing the mouse button,
move the mouse pointer over the "Optional Fields" folder in the Surpac database tree and release
it. If you open the "Optional Fields" folder you will see the field name you have just added.
Note: this will not change the actual name of the field in your database.
The interval, point and discrete tables allow you to map tables such as sample, geology,
weathering, geochem etc.
A sample or assay table can be mapped to the “interval table” within Surpac by the same steps
as detailed above.
NOTE: For an interval table, the field samp_id is specified as a mandatory field however you DO
NOT need to map this field if your interval table is a geology table. All other fields with an asterisk
(*) next to their name MUST be mapped.
Connecting to a Database
Once the mapping is complete, it will create a *.ddb file in the same directory as the database
which is the link which you can now open the database. To open a database either, double click
the *.ddb file in the navigator or select DATABASE | OPEN/NEW. A message will be sent to the
message window that the database is connected and the symbol below will appear in the status
bar at the bottom of the screen.
2. Add an interval table called “geology” with an optional field called “lithology” to the
“surpac” database.
3. Import geology data into the database from the files geology.txt.
4. Display the drillholes and create colour display styles for lithology and assays
I. Inquire drillholes
II. Using graphical logs
a. From the database menu, select Map the Database. The following form will be
displayed.
b. The database type: browser will also allow you to map to other forms of
databases, including paradox or oracle. Select the surpac_training.mdb and select Next
c. This will now create the following *.ddb file, select Next to continue with
mapping the database.
The map the database form will now appear. On the left hand side of the form is the source
data, or the access database that we are trying to connect to, and on the right hand side are
the mandatory and optional tables that surpac is looking for.
hole_id
y
x
z
max_depth
Surpac is automatically able to recognize which fields are to be mapped to which table. If this
is not the case, then a * will appear to the right of the table name as shown below:
We will begin with the collar table. Drill down on the collar file on both sides of the form to
expose the fields which require mapping
f. The Optional Tables will include the sample, weathering and any other tables
such as geology. Drill down on the optional table folder on the mapping detail side of the
form to expose the optional tables to map.
Continue this process until all the tables on the source database, have been matched with
tables on the mapping detail and then select Finish. You will now be connect to the database
surpac_training as shown on the status bar and the file surpac_training.ddb will appear in
your directory
a. First you must connect to the drillhole database. To do this simply click and
drag the file “surpac_training.ddb” from the Navigator to the viewport. You will
see in the Status Bar an item appear with the database icon and the name
“surpac_training”. This means you have successfully connected to the
database.
b. From the Database menu choose Database, Administration, Create table.
c. Fill the subsequent forms as follows:
3. Import geology and sample data into the database from the files geology.txt and
samples.txt, respectively.
d. Make sure you are connected to the drillhole database. See step 2geo.a.
e. From the Database menu, choose Database, Import data and fill the
subsequent forms as follows:
Select which table you want to insert the data into in this case it’s the geology table. Review the
text file to check the delimiter of the file.
The form below is what links the text file you will use to import the data into the correct fields
within the database. Open you text file and determine which column each of the fields reside,
then complete the column number.
4. Display the drillholes and create colour display styles for lithology and assays
a) Rescale view to show drillholes? Click to input a tick mark so that the Graphics
window will rescale to show all drillholes.
b) Add constraint to drillholes? Click to input a tick mark so that only drillholes in the
database that satisfy the constraints that are entered on the Define Query Constraints
form once the Draw Holes form is applied.
c) Location for legend This allows the user to select the location for the drillhole legend.
The positions are
b. In the subsequent form, expand the geology folder to find the lithology field.
c. Right-hand click on the lithology field and choose Get field codes from the
context menu:
B Yello
IN Green
MU Blue
QV1 Red
S2 Orange
SH Cyan
ST Magenta
All unique
lithological
codes
i. Before applying the form, expand the sample folder to find the gold field.
j. Right-hand click on the gold field and choose Get min – max range from the
context menu:
0-2 Cyan
2-4 Orange
4-6 Yellow
6-8 Blue
8-10 Red
Hole ID: WRC001, Collar Y: 1682.69, Collar X: 7318.77, Collar Z: 191.48, Depth: 120.00
Note: This function allows you to edit the drillhole database unless permissions have been
set.
a. Ensure that the drillholes are displayed onscreen and zoom to data extents
b. from the Database menu select Database | Section | Define or select
Step Distance = The distance between sections – how far the cutting planes move when the next
and previous functions are used
Off Section Holes – holes within this distance of the section plane will be considered on the
section
Select your section – left click and hold mouse button down and drag to point
Rotate section using mouse and if you wish to go back to the zoom plane select
View | zoom | zoom plane OR Database | Sections | Zoom Plane
to select a exaggeration
d. This will create section starting on 7120N to 7600m, every 40m. Notice in the
status bar the current drillhole section is displayed. To switch to other sections
choose Previous section ( ), and Next section ( ) from the Database,
Sections menu. Now you will need to display certain information along the hole
traces. In order to do this you will need to define the display styles.
1. Reset Graphics
2. Add topo, faults and an open pit outline.
topo1.dtm
fault1.dtm
pit1.dtm
1. Draw the drillholes with trace colours and geology table and sample assays
3. Sections >Define.
Screen now shows the ore outline, to find out the averaged grade of this outline [or segment as
Surpac calls it].
Dilute
If there are gaps or negative assay values in the samples along the drill hole trace, you
must decide how to treat them. If this checkbox is checked the composited grade is
diluted by assuming a value of zero for the blank or negative samples.
If this checkbox is left unchecked, the missing or negative samples are completely
ignored and the composited grade is not affected
This will calculate the length average for the segment and write this value to the D1 field in the
sample table.
Select the segment and it will calculate and display in the message window
REVIEW OF DIGITISING
a. Determine which parts of the drillhole that you wish to be able to select whilst digitizing.
To do this, view the Database | Display menu and select Drillhole trace selectable, Label
tickmarks selectable, geology patterns selectable.
digistise – wherever the cusor sits is where you will get a point – point at
mouse location (snap off) The digitised point will be appended to the end
of the digitiser string
mid point: select a point, select another point and surpac will determine
a mid point. useful when interpolating geological zones from drilling data
Beginning with the section 7120, ensure that this section is on screen
The z-value of the first point will be initialised with either a value of 7120 or if the SELECT mode
is chosen, the z-value will be assigned from the drill hole.
2. Create a New Layer by selecting EDIT | LAYER | NEW and then name your layer
the same as the ore section you are digitizing
4. Use Digitise mode to digitise new points at either end. The z-value will be
assigned based on the z-value of the last selected point.
8. If desired, you can determine the segment grade as shown in the previous
section
9. Complete the ore outlines for each section from 7120 to 7600 northing
Now we have modeled an ore zone for you deposit. We wish carry out some statistical analysis
on the data to determine sample populations and to then use the composited data to estimate the
block model
Go to Database, Administration, Create Table and fill out the forms as shown below.
Fill out the form as shown below. At the very top of the form is an object pick list. Surpac will list
all objects sitting in the active layer. You will have to do each object separately if there are more
than one.
Any drill holes that pass through object three will be written to the '
intersect'table.
A new layer will also be created to visually show intercepts that pass through the 3DM. (shown
below). It is not necessary to save this information. It can be used as a graphics check to ensure
an intercept has been generated for all drillholes passing through the 3DM.
COMPOSITING
Several different ways to composite:
• Composite by grade
Produces bulked samples of different sample lengths based on width and grade constraints.
• Composite by geology
• Composite by elevation
• Composite downhole
Create sample composites by searching up from the end of the hole and maximising one criteria
while minimising a second criteria.
Of these compositing methods, only Composite by elevation and Composite downhole will
produce composited samples of equal length suitable for use in statistical and geostatistical
studies.
BENCH ELEVATIONS
This function creates one or more string files which contain elevation composites of sample data.
It can be weighted by length alone or by other fields in the table containing the sample data and
can be used to weight by specific gravity or recovery.
All samples, or fractions of samples, of a drill hole which are within the nominated elevations for
the composite, are reduced to a single point value. This value has the length weighted average of
all samples which intersected the elevation range of interest. If the total vertical length of the
samples as a percentage of the vertical height of the elevation bounds of the composite is less
than a defined threshold percentage then the hole will be ignored. The reason for this is to give
you some control over whether drill holes which only partially intersect the elevation composite
are included or excluded from the final result.
• -, to composite samples for the required extent below the nominal elevation
• +, to composite samples for the required extent above the nominal elevation
• +-, to composite samples for the required extent above and below the nominal elevation.
Note: If you choose the +- method you should use an extent which is equal to
half the spacing between the required composite elevations since the extent is
applied both below and above the nominal elevation.
d. Define the output class range to determine to colour the string by grade
range for greater impact
Y= the sample will take on an assumed value of 0 (zero) this has the effect of reducing or diluting
the final averages.
N= the sample will be ignored completely and it will have no effect on the final result.
Typically, additional weighting fields used would be specific gravity and/or recovery. A maximum
of 5 additional weighting fields may be used. Enter the field name/s which are to be used to
provide the additional weighting criteria for the creation of the composite intervals.
a. Go to Composite, Downhole and fill out the form as shown. Make sure that
'
Multiple Zones'has been selected on the form.
This is where we use the flagged intercepts created and stored in the ' Intersect'Table. Surpac will
now composite samples that fall inside the intervals stored in this table.
b. Recall the composite string file into graphics and view the results.
To display the strings as markers, select from the display menu, strings and points
c.. The Intersect table can be deleted from the drill hole database when finished as it is a sub-set
of primary data.
I. Graphical Compositing
The dilute option means that if the box is ticked any negative values or missing samples will be
classed as zero and will therefore dilute any composite you create. If it is not ticked the negative
value or missing sample will be ignored and not effect the composite.
This will display the code labels on the left hand side of the drillhole trace, 1 unit high. The code
is a character value suitable for storing in a database table representing an interval.
Change the size and alignment of the composite value so that it is visible.
Setup options .
View the calculated grade and the exact depth to and depth.
Composite >Edit,
You can also edit the depths at this point should you wish. You can also edit the created
composite in two other ways.
1. Composite | Adjust Length and ‘Select and drag an end point’ As you move this it
also changes the calculated composite
2. Composite | Move and ‘Select and drag an end point’ the composite length does
not change. The the calculated grade changes dynamically.
Exercise.
To delete a composite left click on the Delete One composite icon , then left click on
the composite that you wish to delete.
The Group by Composite code will group all the HG_ORE code composites together, should you
have also done some composites for low grade ore, previously in the exercise above these would
also have been presented in the report
Grade control drilling can also be interpreted in section, then the ore zones sliced in plan to
produce flitch bars, these, together with a bench composite file can be re-interpreted in plan
and then a grade assigned to the polygon to form a mining bench plan.
1. Display the drillholes and then section, interpreting each ore zone and saving to a
separate file. A good naming convention is to ensure that the suffix of the file contains
the section name, ie sec7200.str
2. Save all the section into one file. An easy way to do this is to select
FILE | OPEN and nominate the ore sections and the range, don’t forget to specify the
“append” which will place it all in one layer. Now that all the files are in the same layer,
save the files, creating a new file name.
Using the layer maths function, complete the form as shown below:
The result of swapping the Y and Z fields is that the Y field (which was the northing) has now
become the elevation, and the Z field (which was the rl) has now become the northing.
To do this, select:
This outputs the grade results to the message window and also creates a new file
ore_blocks110.str. View this file in graphics to validate the ore grade.
Hole trace for holes which start outside the extraction limits, but finish inside the
2
extraction limits.
Hole trace for holes which start inside the extraction limits but finish outside the
3
extraction limits.
4 Hole trace for holes that start and finish outside the extraction limits.
5 Top, bottom and down hole survey depths with survey data stored in the D fields.
6 The point at which the hole trace crosses the extraction plane.
The first interval sample grade range string, for the first sample table, with different
11 elements stored in the D fields in the order in which they were selected (second table =
111, third = 211 etc).
The second and subsequent interval sample grade range strings, for the first sample
12 table with different elements stored in the D fields in the order in which they were
selected ( second table = 112, third = 212 etc).
The interval sample bar graph strings for the first selected element (or the first sample
21
table), with the grade range in the D field (second table = 121, third = 221 etc).
The interval sample bar graph strings for the second and subsequent selected elements,
22 for the first sample table with the grade range in the D field (second table = 122, third =
222 etc).
The interval bulked sample string for the first selected element, for the first sample table
31
(second table = 131, third = 231 etc)
The interval bulked assay strings for the second and subsequent selected elements, for
32
the first sample table (second table = 132, third = 232 etc).
The first point sample grade range string with different elements stored in the D fields for
41 the first sample table, in the order in which they were selected (second table = 141, third
= 241 etc).
The second and subsequent interval sample grade range strings with different elements
42 stored in the D fields for the first sample table in the order in which they were selected
(second table = 142, third = 242 etc).
The line graph string for the second and subsequent selected elements, in the order in
52
which they were selected (second table = 152, third = 252 etc).
The literal geology string for the first sample table with the different geology fields stored
70 in the D fields in the order in which they were selected (second table = 170, third = 270
etc).
The symbolic geology box strings for each geology field that has been selected with the
71 literal geology codes in the D field, in the order in which they were selected (second table
= 171, third = 271 etc).
81 -
Geology trace for each geology field for the drill hole display module.
90
Strings 1 to 4 contain the drill hole trace strings for all of the holes extracted for plotting. Only the
portion of the hole which lies within the extraction limits is extracted, so that special plot entities
can be used to correctly display those holes which enter or leave the extraction limits.
The number of points defining the drill hole trace is determined by the answer to the question
Downhole datapoint interval given in the EXTRACT SECTIONS FOR PLOTTING form. If you
entered a value for Interval for plotting depths in the same form, the downhole depths will be
stored in the D field of the drill hole trace string.
String 5 contains at least two points for each drill hole that has met the selection criteria. These
points are for the top of the hole or the position where the hole enters the extraction limits, and
the bottom of the hole or the position where the hole leaves the extraction limits. Each point in
this string will have the following information stored in the D fields:
D1 hole_id
D2 depth
D3 dip
D4 azimuth
Strings 11 to 20 will contain interval assay data for the selected elements, with each string
representing a different grade range. If you answered `Y'to the prompt Process each element
separately in the EXTRACT SECTIONS FOR PLOTTING form, then String 11 will contain all the
values for each selected element in the first grade range for each individual element, String 12
will contain all the values for each selected element in the second grade range for each individual
element, and so on. If you answered `N'to the prompt Process each element separately in the
EXTRACT SECTIONS FOR PLOTTING form, then String 11 will contain the values for each
selected element in the first grade range of the first selected element. The second and
subsequent selected elements for the samples in this string will be stored in this string regardless
of their own value. String 12 will contain the values for each selected element in the second grade
range of the first selected element, and so on. The actual data point stored for each of these
strings represents the end point of the selected sample.
Strings 21 to 30 will contain bar graphs for selected elements, with one string number used for
each selected element. These bar graph strings are closed segment boxes with the grade range
number for each box stored in the D field so that fill entities can be applied when using the
plotting module.
Strings 31 to 40 will contain the bulked sample data with one string number for each selected
element. The bulked grades and lengths are stored in the D field at the point at the end of the
bulked interval in the form `10m @ 25' .
Strings 41 to 50 will contain point sample data for the selected elements, with each string
representing a different grade range. If you answered `Y'to the prompt Process each element
separately in the EXTRACT SECTIONS FOR PLOTTING form, then String 41 will contain all the
values for each selected element in the first grade range for each individual element, String 42
will contain all the values for each selected element in the second grade range for each individual
element, and so on. If you answered `N'to the prompt Process each
element separately in the EXTRACT SECTIONS FOR PLOTTING form, then String 41 will
contain the values for each selected element in the first grade range of the first selected element.
The second and subsequent selected elements for the samples in this string will be stored in this
string regardless of their own value. String 42 will contain the values for each selected element in
the second grade range of the first selected element, and so on.
Strings 51 to 60 will contain line graphs for selected elements, with one string number used for
each selected element. If the line graphs are created from interval sample data then the graph
points are located half way along each sample length.
String 70 will contain the literal geology codes with selected geology fields stored in individual D
fields. The actual data point stored for each of these strings represents the end point of the
selected sample.
Strings 71 to 80 will contain the closed box segments for plotting symbolic geology, with one
string number for each selected symbolic geology field. A closed box segment is created for each
geological code, with the literal geology code stored in the D field so that fill entities can be used
in the plotting module. The boxes will be offset from the drill hole trace by the box thickness.
String 92 contains the actual dipmeter line segments as defined on the DEFINE DIPMETER
DATA form with the dip, azimuth and quality value stored in the D1, D2 and D3 fields. These can
be plotted out using a line entity.
copy and paste between fields using the right click mouse or control c and then use the down
arrow to move and control v to paste fields down
To colour the geology boxes – add your codes to the pattern lookup table by going to Plotting,
Plotting colours, Pattern look up file properties.
All you have to know is the simple structure of the procedure and how to insert a variable in to a
macro. Always have a clear plan of what steps you need to do when recordsing a macro.
The first step to creating any batch plotting is to record the steps in a macro and then edit the
macro so it can “loop”, or repeat the steps to do multiple plots.
This must be done so the next section string files can be inserted in to the Map definition.
Make sure the Plot parameters form has display plot ticked.
Save the plot file as a meaningful name, something crazy like “sec7000.pf”
Do some housekeeping and delete the files created when a plot file *.pf is
created.
Type in “EXEC”, Surpac will auto-finish the function name. Hit the enter key to
present the form.
If the map name was SECTION, the files created will be sectio*.pf, sectio*.cf and
sectio*.par
This will delete from the current working directory all the files, except for the
renamed file, created by the Process Map function.
Now the macro can be edited and set up sing a procedure to do multiple plots!