import/ export cad data - minemap pty ltd - mining … - import export... · web viewminemap ims -...

MineMap IMS 2.0

Produced by W.S. Mart and G. MarkeyFor MineMap Pty Ltd

Intelligent Mining Software “Solutions” MineMap IMS - Import/ Export CAD Data

Intelligent Mining Software “Solutions”MineMap IMS - Import/ Export CAD Data

Copyright © 2014 by William Seldon Mart and Geoff Markey. All rights reserved.

Page 1


TABLE OF CONTENTS

INTRODUCTION............................................................................................................................... 5

IMPORT FREE-FORMATTED ASCII FILES................................................................................6

Field expressions........................................................................................................................................................8

IMPORT GEMCOM FILES............................................................................................................... 9

IMPORT VULCAN SOLID FILES................................................................................................. 11

IMPORT CIVILCAD MODEL FILES............................................................................................ 13

IMPORT ECLIPSE TRIANGULATION FILES............................................................................14

IMPORT FORESIGHT FILES....................................................................................................... 15

IMPORT CIVILCAD CONTROL STATIONS..............................................................................17

IMPORT SURVEY DATA RECORDER FILES...........................................................................18

EXPORT TO AN AUTOCAD DXF VERSION 12 FILE..............................................................19

EXPORT TO A SURPAC STRING FILE......................................................................................20

EXPORT TO AN EASIMINE STRING FILE................................................................................21

EXPORT TO A VRML FILE........................................................................................................... 22

EXPORT TO A CSV FILE............................................................................................................... 23

EXPORT TO A DATA RECORDER.............................................................................................. 24

Page 2


APPENDIX A: IMPORTING RAW SURVEY DATA..................................................................25

APPENDIX B: DEALING WITH NEW CONTROL STATIONS...............................................26

APPENDIX C: DATA RECORDER FORMATS...........................................................................28

Geodat Geodimeter System 400...........................................................................................28

Typical data................................................................................................................................................................28

Codes.............................................................................................................................................................................29

Notes.............................................................................................................................................................................30

Husky Hunter Data Recorder..............................................................................................31

Typical data................................................................................................................................................................31

Codes.............................................................................................................................................................................31

Notes.............................................................................................................................................................................32

Example.......................................................................................................................................................................32

Nikon Data Recorder............................................................................................................34

Typical data................................................................................................................................................................34

Codes.............................................................................................................................................................................34

Notes.............................................................................................................................................................................35

Pentax DC-1...........................................................................................................................36

Typical data................................................................................................................................................................36

Codes.............................................................................................................................................................................37

Sokkisha Data Recorders......................................................................................................38

SDR2:............................................................................................................................................................................38

SDR20:..........................................................................................................................................................................38

SDR33:..........................................................................................................................................................................38

Sokkisha Data Format..........................................................................................................39

Typical data................................................................................................................................................................39

Codes.............................................................................................................................................................................39

Notes..............................................................................................................................................................................40

Topcon Raw Data Format....................................................................................................41

Topcon string identification logic...........................................................................................................................41

Page 3


Processing Topcon data............................................................................................................................................41

Typical data................................................................................................................................................................42

Topcon FC2............................................................................................................................43

Typical data................................................................................................................................................................43

Codes.............................................................................................................................................................................44

Example.......................................................................................................................................................................44

Topcon FC5............................................................................................................................46

Typical data................................................................................................................................................................46

Codes.............................................................................................................................................................................47

Notes.............................................................................................................................................................................47

Topcon GTS-6E.....................................................................................................................51

Wild GRE-3...........................................................................................................................52

Typical data................................................................................................................................................................52

Codes.............................................................................................................................................................................52

Wild TPS 1000.......................................................................................................................54

Typical data................................................................................................................................................................54

Codes.............................................................................................................................................................................54

Page 4


INTRODUCTION

MineMap IMS can import and export MineMap IMS files from and to other formats. The supported formats are shown in the tables below:

Table 1: Supported formats for importing CAD data

Input Format Output FormatASCII Reads and extracts point and string data from a free formatted ASCII text file

and writes to a MineMap IMS CAD file.Optionally performs simple calculations on the data extracted.

CivilCAD Reads a CivilCAD Digital Terrain Model (DTM) ASCII file and writes to a MineMap IMS CAD file.

Eclipse Reads an Eclipse triangulation ASCII file and writes to a MineMap IMS CAD file.

Foresight Reads Foresight string files and writes to MineMap IMS CAD files.Gemcom Reads Gemcom string files and writes to MineMap IMS CAD files.Vulcan Reads Vulcan solid body/triangulation files and writes to MineMap IMS

CAD files.Control Stations Reads a CivilCAD control station binary file and writes to a MineMap IMS

control (SYS) file.Data Recorder Reads a variety of formats from some commonly used survey instruments

and writes to a MineMap IMS CAD file.

Table 2: Supported formats for exporting CAD data

Output Format Input FormatAutoCAD DXF Writes a MineMap IMS CAD file to an AutoCAD

file.Surpac Writes a MineMap IMS CAD file to a Surpac file.

Text is not exported.Easimine Writes a MineMap IMS CAD file to an Easimine

file. Text is not exported.VRML Writes a MineMap IMS CAD solid body to a Virtual

Reality Modelling Language (VRML) file. These files are displayed in a Web Browser.

CSV Writes string data of a MineMap IMS CAD file to a CSV format file.

Data Recorder Writes a MineMap IMS CAD file to a supported data recorder file. These files can be uploaded to various data recorders.

Page 5


IMPORT FREE-FORMATTED ASCII FILES

A free-formatted ASCII file contains text data in which the fields from row to row do not necessarily line up in the same columns. There must be at least one space between each field on each line but the fields may start in different columns on each line.

A fixed-formatted ASCII file (such as an MineMap IMS CAD data file) that has at least one space between each field on each line is a special case of a free-formatted ASCII file and can be read as such.

EXAMPLE

Figure 1 shows an input file with three fields per line. Each field is separated by one or more spaces.

56.2 659.87 265.74 98.43 5489.37 125.91 841.95 376.59 6792.35

Figure 1: A typical free-formatted ASCII file

When the file is imported MineMap IMS produces the CAD file shown in Figure 2.

56.20 659.87 265.740 198.43 5489.37 125.910 2841.95 376.59 6792.350 3 /* /* /* /* /* /*

Figure 2: The MineMap IMS CAD file

The slash-asterisk (/*) combination is used by MineMap IMS to denote the end of a data section.PIC0000002E

To import a free-formatted ASCII file:

1. Select <File><Import/Export><Import CAD File><ASCII...> to display the import file dialog box (Figure 3).

Page 6


Figure 3: Importing an ASCII file

2. Enter the name of the input file. This file must exist prior to selecting this option.

3. Enter the name of the output file. By default, this will be automatically allocated the MineMap IMS CAD file extension.

4. Specify the field expressions for easting, northing and elevation. See Table 3 for the valid syntax.

5. Specify which field (if any) should be used as the point number for each line of data. E.g. to specify that field 2 is used as the point number for each line of data enter [2]. If this field is left blank then the point numbers will be allocated automatically in ascending order (starting from 1).

6. Specify which field (if any) should be used as the comment for the line of data. This can be done by reading the comment from:

i. a given field only (e.g. [5] to read from field 5) orii. a given field to the end of the line. E.g. to specify that the comment begins in field 5

and continues to the end of the line, enter [5]$ or [5]>.

7. Specify up to three fields on which strings or polygons should be connected.

The general format for specifying that strings should be connected based on the contents of field number field is [field]. E.g. to specify that strings should be connected based on the contents of fields 2 and 4, enter [2][4].The general format for specifying that polygons should be connected based on the contents of field number field is *[field] or [-field]. E.g. to specify that polygons should be connected based on the contents of field 3, put *[3] or [-3].

Page 7


All the points that lie on lines with the same value in the specified field will be connected into the string or polygon until the value of the field changes. Every time the values in the designated fields change, a new string or polygon is created.

8. If there is a number in the comment field that is consistent (i.e. the same as used for connecting strings) it can be incorporated into this field. Alternatively, you can specify a number here for the line type.

If there is no number specified, the line type defaults to line type 1.

9. Press the <OK> button to import the file.

Field expressions

Simple field expressions can be used to specify how the easting, northing and elevation of each point are derived (Table 3).

Table 3: Field expressions

Specification Meaning[field] Read from field field in the file.[field] + value Take whatever is in field field and add value.[field] - value Take whatever is in field field and subtract value.value Set all values to value.

For example, to specify that the easting coordinate should be read from field 2 and that 150.0 should be added to it, enter the following as the easting expression:

[2] + 150.0

Page 8


IMPORT GEMCOM FILES

To import a Gemcom file:

1. Select <File><Import/ Export><Import CAD File><Gemcom...> to display the import file dialog box (Figure 4).

2. Enter the name of the input file (Vulcan solids) or browse for the file.

3. Enter the name of the output file (MineMap IMS CAD).


Figure 4: Importing a Gemcom CAD file

Page 9


NOTES:

Figure 5 shows a typical Gemcom file.

S_9600E INDICAT2 10163.582 9600.000 -329.076S_9600E INDICAT2 10168.041 9600.000 -279.011S_9600E INDICAT2 10195.917 9600.000 -321.101S_9600E INDICAT2 10190.696 9600.000 -369.598S_9600E INDICAT2 10163.582 9600.000 -329.076

Figure 5: A typical Gemcom CAD file

1. Each point line has the following format:

<comment> <northing> <easting> <RL>

Spacing is not important.

2. An index line lists the indices of the three points comprising a triangle, separated by commas. Again, spacing is not important.

3. There is a blank line between point groups depicting a polygon.

Page 10


IMPORT VULCAN SOLID FILES

To import a Vulcan solid file:

1. Select <File><Import/Export><Import CAD File><Vulcan...> to display the import file dialog box (Figure 6).




Figure 6: Importing a Vulcan CAD file

Page 11


NOTES:

Figure 7 shows a typical Vulcan file. There is a header section followed by a vertex section and an index section.

_AU_1_00GT.00T C: (12:17:03 No Points: 4, No Triangles: 2Vertex: 1997.6438, 1028.2014, 75.0001Vertex: 1997.6438, 1030.8597, 75.0001Vertex: 1998.7070, 1030.3280, 70.0001Vertex: 1999.2386, 1027.6697, 70.0001Index : 000001, 000002, 000003Index : 000001, 000002, 000004

Figure 7: An example for a Vulcan CAD file

1. The header lines are ignored by MineMap IMS and can be omitted.

2. A vertex line has the format:

Vertex: <easting>, <northing>, <RL>

There can be multiple spaces between the fields.

3. An index line lists the indices of the three points that make up a triangle and has the format:

Index: <point1>, <point2>, <point3>

There can be multiple spaces between fields. Each index refers to a corresponding vertex number.

Page 12


IMPORT CIVILCAD MODEL FILES

To import a CivilCAD DTM file:

1. Select <File><Import/Export><Import CAD File><CivilCAD...> (Figure 8).

2. Enter the name of the input file (a CivilCAD DTM) or browse for the file.



Figure 8: Importing a CivilCAD file

Page 13


IMPORT ECLIPSE TRIANGULATION FILES

To import an Eclipse triangulation file:

1. Select <File><Import/Export><Import CAD File><Eclipse...> to display the import file dialog box (Figure 9).

2. Enter the name of the input file (an Eclipse triangulation) or browse for the file.



PIC00000036Figure 9: Importing an Eclipse CAD file

Page 14


IMPORT FORESIGHT FILES

To import a Foresight file:

1. Select <File><Import/Export><Import CAD File>< Foresight...> to display the import file dialog box (Figure 10).




Figure 10: Importing a Foresight CAD file

Page 15


NOTES:

Figure 11 shows a typical Foresight point file.

1 3985.000 1735.000 72.500 15 3970.000 1660.000 71.060 16 3970.000 1675.000 71.010 17 3970.000 1690.000 70.790 18 3970.000 1705.000 71.150 19 3970.000 1720.000 71.450 20 3970.000 1735.000 71.440 21 3955.000 1735.000 70.500 22 3955.000 1720.000 70.480 23 3955.000 1705.000 70.350 24 3955.000 1690.000 70.090 ...

Figure 11: A typical Foresight point file

1. This file contains one line per point.

2. Each line has the following format:

<point number> <easting> <northing> <RL>

Spacing is not important.

Figure 12 shows a typical Foresight string file.

LOT 1,P1,L1,1,19.15,27,34.32,53.60,ELOT 2,P1,L1,119.122,115,103.100,118,119,E

Figure 12: A typical Foresight string file

1. This file contains one line per string.

2. Each line represents the points that make up the string and has the following format:

<field1>, <field2>, <field3>, <point1>, <point2>, …, <pointN>, E

A sequence of points can be specified by using, for example, <point1.point2>. In the example file the first line defines a string through points 1, 19, 18, 17, 16, 15, 27, 34, 33, 32, 53, 54, 55, 56, 57, 58, 59 and 60.

3. If the ‘E’ at the end of a line is omitted, the string continues with points on the next line, as shown in the second string of the example above.

4. MineMap IMS looks only for commas so spaces will be ignored.

Page 16


IMPORT CIVILCAD CONTROL STATIONS

To import a CivilCAD control station file:

1. Select <File><Import/Export><Import Control Stations...> to display the import control stations dialog box (PIC00000030Figure 13).

2. Enter the name of the input file (CivilCAD control station) or browse for the file.



PIC00000030Figure 13: Importing control stations

Page 17


IMPORT SURVEY DATA RECORDER FILES

To import a survey data recorder file:

1. Select <File><Import/Export><Import Data Recorder...> to display the import data recorder dialog box (Figure 14).

Figure 14: Importing a data recorder

2. Select the required data recorder. MineMap IMS currently recognises the following recorders (see APPENDIX C for details of the supported recorders).

3. Enter the name of the input file or browse for the file.

4. Enter the name of the control station file or browse for the file.



Page 18


EXPORT TO AN AUTOCAD DXF VERSION 12 FILE

To export a MineMap IMS CAD file to an AutoCAD DXF file:

1. Drag the MineMap IMS CAD file from File Explorer Pane to either the 3D Pane or the Loaded File Pane.

2. Select <File><Import/ Export><Export CAD File><AutoCAD DXF...> to display the “Save As” dialog box (Figure 15).

3. Enter the name of the output (DXF) file.

Figure 15: Exporting to an AutoCAD DXF

Page 19


EXPORT TO A SURPAC STRING FILE


2. Select <File><Import/Export><Export CAD File><Surpac...> (Figure 16).

3. Enter the name of the Surpac (DTM) file.

Figure 16: Exporting to a Surpac file

PIC0000003A

Page 20


EXPORT TO AN EASIMINE STRING FILE


2. Select <File><Import/Export><Export CAD File><Easimine...> (Figure 17).

3. Enter the name of the Easimine ASCII file.

Page 21


Figure 17: Exporting to an Easimine ASCII file

Page 22


EXPORT TO A VRML FILE


2. Select <File><Import/Export><Export CAD File><VRML...> (Figure 18).

3. Enter the name of the VRML file.

Figure 18: Exporting to a VRML file

Page 23


EXPORT TO A CSV FILE


2. Select <File><Import/Export><Export CAD File><CSV (Strings Only)...> (Figure 19).

3. Enter the name of the CSV file to convert the string data of the loaded MineMap IMS CAD file.

Figure 19: Exporting to a CSV file

Page 24


EXPORT TO A DATA RECORDER


2. Select <File><Import/Export><Export Data Recorder...> (Figure 20).

Figure 20: Exporting to a data recorder

3. Select the required data recorder (see APPENDIX C for details on the supported recorders).

4. Enter the name of the output file.

5. Select the method by which the point label is generated.

NOTE: Only points are exported to the data recorder file. This file is used in conjunction with a control station file that needs to be independently uploaded to the data recorder.

Page 25


APPENDIX A: IMPORTING RAW SURVEY DATA

To import raw survey data from a supported survey instrument:

1. Download the survey instrument data to the computer. There are many ways in which this can be done so check with your equipment supplier.

2. Check the data for bad points and include any extra string information as required.

3. Import the final data to MineMap IMS by selecting the appropriate function from the <File><Import/ Export><Import Data Recorder...> menu. The output from this step is a MineMap IMS CAD file.

Page 26


APPENDIX B: DEALING WITH NEW CONTROL STATIONS

Control station names are saved in an ASCII text file named "survey.sys". This file also contains the control stations' coordinates and optional comments such as the station name, date, surveyor name, etc. New control stations, therefore, can be added to the system by adding a new line to the file. This new line should contain the name and coordinate information for the control station. Figure 21 shows an example “survey.sys” file using a fixed with format.

1 5000.000 14500.000 198.720 10 5000.000 15100.000 203.620 11 5000.000 15300.000 200.700 8 5000.000 14400.000 198.750 50 54641.490 65010.510 196.870 51 54263.890 64682.380 196.623 52 54697.730 64261.720 197.540 53 54195.930 62908.640 203.297 66 46295.160 57494.540 245.005 67 45970.150 57226.390 244.368 68 45197.390 56567.560 233.916 69 44831.680 56131.960 230.398

Figure 21: Fixed width format for the survey.sys file

The file can also use a CSV format as shown in Figure 22.

"5 ", 5038.276, 15257.673, 202.653," ","5","6 ", 5183.960, 15117.861, 204.915," ","6",

Figure 22: An example of MineMap IMS format for a control station file

If MineMap IMS cannot find a control station in the current "survey.sys" file it issues a warning stating that a station is not included in the control point file. Once you have confirmed this message, the required information for the control file can be entered directly using the Entry of Control Station Details dialog box as follows:

Easting, Northing and ElevationEnter the easting, northing elevation of the control station.

CodeEnter the code for the control station. This code is typically used for identifying the control station in the data recorder. It may be up to 7 characters in length.

DescriptionEnter a complete description of the control station. This description is included in any reports that are generated during the import. It may be up to 31 characters in length.

Page 27


Permanent? Indicate whether this is a permanent control station (i.e. you will probably use it again and you would like its details to be recorded), or a temporary one. If it is permanent, the details that you enter into this dialog box will be saved to the control station file, "survey.sys".

In some cases you may not know the control station coordinates because it is part of the current run, (e.g. you may have started from a known control point, and then sighted to a new control point from which you complete the survey). In cases like this, you will need to split the processing into two runs of MineMap IMS: the first run to establish the coordinates of the new station and the second to complete the processing. In the first run, only the points calculated before the new station will be correct, so when prompted, enter dummy values for the new station. In the second run, enter the newly established coordinates for the second station and the positions of all the following points will be calculated from that point.

It is good practice to perform a back-sight to the original station so that you can check the coordinates in the final MineMap IMS survey file.

Page 28


APPENDIX C: DATA RECORDER FORMATS

Geodat Geodimeter System 400

Typical data

50=112=21078813=1.62337=038=039=062=22

21=06=1.64=25=120=.036=1.69=52.628=90.11527=288.074=25=26=1.89=49.368=90.10187=286.16044=25=36=1.69=45.78=90.14227=285.4058

Figure 23: Typical Geodat data

Page 29


Codes

Table 4: Geodat codes

Identifier Description2 First station.

This is the station from which the measurements are taken and is a known point stored in the SURVEY.SYS file or added during the execution of MineMap IMS.

3 Instrument height.4 New point.

This is followed by a comment that is used to create strings. The comment is normally used for grade control but all consecutive points with the same comment (except for '1') can also be used to form a string. The comment '1' is used for entering point data otherwise it forms the string number.

5 Point number.

This identifies the point and is appended to the comment mentioned in code 4 above to form the MineMap IMS comment stored with the points. Note that MineMap IMS adds its own point numbers to ensure that point numbers are unique.

6 Reflector height.7 Horizontal angle.8 Vertical angle.9 Slope distance.

This is used in conjunction with codes 7, 8 and 9 to generate the coordinates of the point.

20 Slope distance adjustment.21 Back sight station 1 - offset bearing.

This assumes that a previous station is used as a reference direction from which all following bearings are taken.

37 Northing.38 Easting.39 Elevation.50 Job number.

This code is ignored by MineMap IMS.62 Back sight station 2 - offset position.

Here a previous station or other known object is specified then related via the SURVEY.SYS file to calculate the coordinates. This information is then used to calculate a back bearing. Horizontal angles are taken from this station in a clockwise direction.

Page 30


Notes

MineMap IMS assumes the following:

1. A number or an alphanumeric string usually follows each identifier. For example: 20=1.4 indicates a slope distance adjustment of 1.4 metres.

2. The horizontal angle is taken from the back sight station (if one exists) in a clockwise direction. If there is no back sight station then it is taken from north.

3. The vertical angle is measured from a vertical line.

4. The maximum number of strings imported from a single file is 390. If there are more than 390 strings in a single file then try splitting the file at an appropriate point before importing it.

5. The maximum number of points for each string is 400. Strings of more than 400 points are automatically split into two or more strings.

Page 31


Husky Hunter Data Recorder

Typical data

000100prmdr10_11.0000000011089DM000281VA.SD -0900.000000331md202 01550dpy00040100010061.47200513510916100146000000W1/14001/0200050100020065.44220024010805500146000000E1/14002/0200060100030077.71197052010503300146000000E1/14003/0400070100040073.86205215010557200146000000W1/14006/04

Figure 24: Typical Husky Hunter data.

Codes

Table 5: Husky Hunter codes

ColumnCode Meaning

1-4 #### Record Number5-6 31 Station code (reference)

11 Back sight station - NOT USED01 Radial survey (one point)

Table 6: Husky Hunter fields for code 31.

Column Abbreviation Description7-14 SNo Station number15-19 IH Instrument height20-21 *22 FIN Last slot read

Table 7: Husky Hunter fields for code 01.

Column Abbreviation Description7-10 PNo Sequential point number11-17 SD Slope distance18-24 H Horizontal angle

(ddmmss)25-31 V Vertical angle (ddmmss32-36 RH Reflector height37-41 *42-55 COM Comment (14 characters

maximum)56 FIN Last slot read (possibly

empty)

Page 32


Notes

The comment field is used by MineMap IMS to create strings from point data. It is assumed that all points will be joined into the same string until the codes SP or ST are found.

SP indicates a spot height (single point). ST indicates that the current string is now closed and that a new string will commence. A number following the ST will set the line type for the string as used by MineMap IMS.

Example

For this example we assume the following base values:

Base easting: 1000Base northing: 1200Base elevation: 300Prism height: 155

Consider the line of data shown in Figure 25.

00040100010061.47200513510916100146000000W1/141/02_

Figure 25: Example for Husky Raw data

The line is interpreted as shown in Figure 26.

00040100010061.47200513510916100146000000W1/141/02_ 0001 PNo = 1 0061.47 SD = 61.47m 2005135 H = 200.51'35" 1091610 V = 109.16'10" 01460 RH = 1.460m W1/141/02_ COM = "W1/141/02_"

Figure 26: Coding for the Husky Raw data example

Using the values from Figure 26 and Equation 1, Equation 2 and Equation 3 we get the following result:

Elevation = BaseElevation - (SD * sin(V)) + (IH - prism_height)Equation 1: Calculating the elevationEasting = BaseEasting+ sin(H)* (SD * cos(V))Equation 2: Calculating the eastingNorthing = BaseNorthing + cos(H) * (SD * cos(V))

Equation 3: Calculating the northing

E = 979.34N = 1145.78Elev = 279.804

Page 33


The result is output to the MineMap IMS CAD file as show in Figure 27.

979.34 1145.78 279.804 1 W1/141/02_ 1

Figure 27: Final MineMap IMS survey file format for Husky raw data example

Page 34


Nikon Data Recorder

Typical data

25 B,1.585,000.0000 2 C,1.585,0059.613,000.0000,090.4730,ST1 001 3 C,1.585,0026.941,357.1555,090.1235,PEG 4 C,1.585,0041.385,008.0450,090.2935,TB 5 C,1.585,0024.084,016.0850,090.2415,TB 6 C,1.585,0025.924,018.5905,092.5650,BB 7 C,1.585,0040.289,010.1910,091.5720,BB 8 C,1.585,0038.583,015.5720,092.1020,BLD 9 C,1.585,0029.829,021.0135,092.4530,BLD 10 C,1.585,0034.760,071.3250,092.4350,TK 11 C,1.585,0032.445,083.3810,092.4115,TK 12 C,1.585,0040.721,086.4310,092.3750,TK 13 C,1.585,0041.792,079.0255,092.3440,TK 14 C,1.585,0057.129,087.1635,092.5220,SP 17 C,1.585,0063.737,119.4830,093.2545,ST22 BB 18 C,1.585,0064.565,117.3335,093.3050,BLD 19 C,1.585,0060.703,109.3710,093.4205,BLD 20 C,1.585,0069.411,126.2935,093.0330,ST 21 C,1.585,0053.252,147.5050,092.3820, 23 C,1.585,0027.836,181.1010,090.4825, 24 C,1.585,0036.854,126.1845,092.4740, 2 B,2,180.0000 30 C,2.000,0033.933,357.2750,091.0145,SP 31 C,2.000,0067.040,358.1910,090.4245,ST PEG 32 C,2.000,0078.178,358.3405,090.4905, 33 C,2.000,0062.446,033.4245,093.0220,FNC 34 C,2.000,0070.626,032.2425,092.5255, EOF

Figure 28: Typical Nikon data

Codes

Nikon station data has the following format:

<station #> B,<instrument height>,<bearing>

Figure 29 shows an example of data for a station with the following properties:

Station number: 30Instrument height: 1.585mBearing : 0

25 B,1.585,000.0000

Figure 29: The format of a line of station data

Nikon point data has the following format:

Page 35


<point #> C,<reflector height>,<slope distance><HAng><VAng><comment>

Figure 30 shows an example of data for point 3 which has the following properties:

Point number: 3Reflector height: 1.585mSlope distance: 26.941mHorizontal angle: 357.1555Vertical angle: 90.1235Comment: PEG

3 C,1.585,0026.941,357.1555,090.1235,PEG

Figure 30: The format of a line of point data

NOTE: Note that MineMap IMS adds its own point numbers to ensure that point numbers are unique. The point number produced by the data recorder is added as the last part of the comment stored with the point for reference.

Notes

The comment field is used to either:

1. Indicate the start of a new string, or

2. Isolate points such that they are not included in the current string.

If the first two letters of a comment are "ST", then a new string is started with all following points becoming members of this string. The string is terminated when a new one is started The exception is where a comment starts with "SP", in which case the point is excluded from the current string and treated as an isolated spot height.

If the "ST" in a comment is immediately followed by a one or two digit number then the number is taken to be the line type. For example, a comment of "ST22" would indicate the start of a string with a line type of 22. If no number follows the "ST", a line type of 01 is assumed.

Note that additional comment information can be placed after the "SP" or "ST" information.

Page 36


Pentax DC-1

Typical data

STL:BUS403DAT:5.7.90STA:1STC:504INH:1.525TEM:17.0000PRS:762.0000PSM:0.000PPM:1.0000PPT:1PPC:CNTL505RTH:201.1325PPT:2PPC:STDSPPH:1.500RTH:262.4250RTV:90.1420RTD:51.4300

PPT:3PPC:DSPPH1.500RTH:242.2435RTV:90.0905RTD:58.4500

PPT:4PPC:SPPPH:1.500RTH:227.2830RTV:90.0250RTD:68.7100

Figure 31: Typical Pentax data

Page 37


Codes

Table 8: Pentax codes

Pentax Meaning Geodat Equiv. COMMENTSTL:BUS403 Job number 50= NOT USEDDAT:5.7.90 Date 51= NOT USEDSTA:1 Station sequence number **** NOT USEDSTC:504 Station code 2=INH:1.525 Instrument height 3=TEM:17.0000 Time 52= NOT USEDPRS:762.0000 Atmos. pressure 74= NOT USEDPSM:0.000 Prism. constant **** NOT USEDPPM:1.0000 Atmos. coefficient 30= NOT USED

PPT:1 Target point number 5=PPC:505 Target point code 4= ?? NOT USEDRTH:201.1325 Horizontal angle 7=

PPT:2 Target point number 5=PPC:DS Target point code 4= ?? COMMENTPPH:1.500 Target height 6=RTH:262.4250 Horizontal angle 7=RTV:90.1420 Vertical angle 8=RTD:51.4300 Slope distance 9=

Page 38


Sokkisha Data Recorders

A Sokkisha data recorder can be configured for a variety of output formats. The formats that MineMap IMS recognise are described in the topics below. To effectively import your data, you should configure your Sokkisha to match one of these formats as closely as possible.

Following is a summary of the differences in MineMap IMS options to import from SDR2, SDR20 and SDR33 data recorders. These options are so named for historical reasons; since most data recorders can export in a range of formats, in many cases these formats are interchangeable to suit the individual surveyor’s style.

SDR2:

This option uses the Sokkisha Data Format. It expects the setup station to be nominated before the backsight.

When processing points this option looks to the comment field to indicate how the points should be connected into strings. A comment beginning with “ST” indicates the start of a new string while a comment beginning with “SP” indicates a spot height that is not to be included in the current string. If neither of these comment codes is found then no strings are created.

Use the manual option to ignore the data file and provide information on the fly.

SDR20:

This option uses the same format as the SDR2 option but differs in the way it connects strings. A new string is started every time the comment field differs from that of the previous point.

SDR33:

This option is provided for cases where data reduction has been performed by the data recorder. The only record recognised is a ‘08’ record which contains easting (columns 9-18), northing (19-28) and RL (29-38) information.

Page 39


Sokkisha Data Format

Typical data

02TP00156064.639 5972.778 273.798 0.735 STN 15 08KI00116169.770 6053.850 286.662 STN 11 03NM1.160 09F100150011 84.78333 0.00000 STN 11

Figure 32: Typical Sokkisha data

Codes

Table 9: Primary Sokkisha codes

Column Code Meaning1-2 02 Station details

08 Backsight details03 Reflector/prism height09 Radial survey (one point)

3-4 ** Derivation code (NOT USED)

Table 10: Sokkisha fields for code 02

Column Abbreviation Description5-8 PNo Point number9-17 N Northing18-27 N Easting28-38 RL Elevation39-48 IH Instrument height49-64 Desc Station Code (16 chars)65 FIN


Column Abbreviation Description5-8 PNo Point number9-17 N Northing18-27 E Easting28-38 RL Elevation39-48 IH Instrument Height49-64 Desc Station Code (16 chars)65 FIN

Page 40



Column Abbreviation Description5 RH Reflector height14 FIN


Column Abbreviation Description5 - 8 PNo Sequential point number9 - 12 TPN Target point number

(NOT USED) 13 - 22 SD Slope distance 23 - 32 V Vertical angle 33 - 42 H Horizontal angle 43 - 57 COM Comment (15 chars) 58 FIN

Notes

The comment field is used by MineMap IMS to create strings from point data. It is assumed that all points will be joined into the same string until the codes SP or ST are found.

SP indicates a spot height (single point). ST indicates that the current string is now closed and that a new string will commence. A number following the ST will set the line type for the string as used by MineMap IMS.

Page 41


Topcon Raw Data Format

This option reads in raw data from the TOPCON FC2/2C (ver.153) data recorder working in conjunction with the Total Geodetic Station TOPCON GTS-3B/4B. A pre-processor is used to convert the unpunctuated characters in the raw data file into data that is capable of being checked by the user.

Topcon string identification logic

The comment field is used to either:

1. Indicate the start of a new string, or 2. Isolate points such that they are not included in the current string.

If the first two letters of a comment are "ST", then a new string is started with all following points becoming members of this string. The string is terminated when a new one is started. The exception is where a comment starts with "SP" in which case the point is excluded from the current string and treated as an isolated spot height.

If the "ST" in a comment is immediately followed by a one or two digit number, the number is taken to be the line type. For example, a comment of "ST22" would indicate the start of a string with a line type of 22. If no number follows the "ST" a line type of 01 is assumed.

Note that additional comment information can be placed after the "SP" or "ST" information.

Example:'CNTL504 Control Station*ST05 Start of string 5+05 String continued*SP Spot Height

Processing Topcon data

The Topcon option requires pre-processing of the raw data file to convert it to a useable format for MineMap IMS. The procedure is:

1. Import the raw data into the computer.2. Pass this data through the pre-processor "topconi": topconi.raw topconi.dat3. Check for bad points and include any extra string information necessary.4. Import the data file into MineMap IMS.

Page 42


Typical data

1) __!01_"MINE MAP_#GTS-4B_$MAY-07-91_%21_&750_'9000_(_)1.65_+9001_ a+0000000d_ b0845923d_ c+00012920m_*BS_,1.65_+100 `100_ a+1230140081_2) _1d_ b0845923d_ c+00012920m_*01_,1.65_+101 `101_ a+1452548d_ b0845924d_ c+00012920m_*01_,1.65_+102 `102_ a+2365210d_ b0845923d_ c1061_3) _+00012920m_*01_,1.65_+103 `103_ a+0102540d_ b0845923d_ c+00012930m_*01_,1.65_+104 `104_ a+3592010d_ b0845924d_ c+00012920m_*01_,2115_4) _1.65_'9001_(_)1.65_+9000_ a+1800001d_ b0845924d_ c+00012920m_*BS_,1.65_+105 `105_ a+1800000d_ b0845924d_ c+00012930m_*01_,1.65_+3111_5) _106 `106_ a+1423627d_ b0845923d_ c+00012930m_*01_,1.65_+107 `107_ a+2150143d_ b0845924d_ c+00012930m_*01_,1.65_ 4063_6) _

Figure 33: Typical Topcon raw data

NOTES1. The line length is 134 characters.

2. The initial character is _ (0x02), character position 1.

3. The final character is _ (0x03), character position 134.

4. The EOF character is _ (0x04), character position 1.

Page 43


Topcon FC2

Typical data

!4.8_"SURVEYOR_'1007.470_(1007.475_)1.5_+125_ R+00500001m0894345+0000000d+00002380t21+98+33012_*BS_,1.5_+126_ R+00422221m0900930+1464800d-00001155t23+98+33011_*4.8STN01_,1.5_'4.8STN01_(1007.470_)1.5_+127_ R+00422226m0895510+0000000d+00000606t23+98+33003_*BS_,1.5_+128_ R+00234352m0894200+0990555d+00001231t27+98+33000_*ST01_,1.5+129_ R+00238660m0894110+0892640d+00001311t27+98+33004_*01_,1.59005EOF_

Figure 34: Typical pre-processed FC2 data

Codes

Page 44


Table 14: FC2 codes

Topcon Meaning COMMENT!4.8_ Job number or name NOT USED"SURVEYOR_ Name of observer NOT USED#1_ Instrument serial number NOT USED$NOV-20-90_ Date NOT USED'1007.470_ Station code (reference)(1007.475_ Back sight station(reference))1.5_ Instrument height+125_ Target point codeR+00500001m... Horizontal/vertical distance

mode [R]<0904230+32... V/H angle mode (rpt inf) NOT USED*BS Comment indicating back sight,1.5 Reflector height+126_ Target point codeR+00422221m... Horizontal/vertical distance

mode [R]*4.8STN01_ Point comment info. NEW STRG,1.5_ Reflector height'4.8STN01_ Station code(1007.470_ Back sight station(reference))1.5_ Instrument height..... ..... .....

9005 Block check numberEOF_ END OF FILE MARKER

Example

R+00022067m0904230+3212340d-00000273t40+14+33013|| || | || || | |ID HD m V H d VD t L P O

Figure 35: Example for horizontal/ vertical mode record

Page 45


Table 15: Details of horizontal/ vertical mode record

ID R Hori/Vertical dist modeHD +00022067 Horizontal Distance +22.067mm m/f metres/feet metresV 0904230 Vertical Angle 90.42'30"H +3212340 Horizontal Angle +321.23'40"d d/g/m degrees/radians/mills degreesVD 00000273 Vertical Distance -0.273mt t/* with/without tilt correction NOT USEDL 40 EDM return signal level (2 digits) NOT USEDP +14 Atmos Correction (+/- 2 digits) NOT USEDO +33 EDM instr. offset +25mm (+/- 2 dig.) NOT USED

013 Block check char (3 digits) NOT USED_ End of line (record) character ESSENTIAL

Page 46


Topcon FC5

Typical data

!01_"MINE MAP_#GTS-4B_$MAY-07-91_%21_&750_'9000_(HILL12_)1.65_+9001_ a+0000000d_ b0845923d_ c+00012920m_*BS_,1.65_+100_ a+1230141d_ b0845923d_ c+00012920m_*01_,1.65_+101_ a+1452548d_ b0845924d_ c+00012920m_*01_,1.65_+102 `102_+102_ a+2365210d_ b0845923d_ c+00012920m_*01_,1.65_EOF_

Figure 36: Typical pre-processed FC5 data

Codes

Page 47


Table 16: FC5 codes

Topcon Meaning COMMENT!FG200591_ Job number or name NOT USED"MINE MAP_ Name of observer NOT USED#GTS-4B_ Instrument serial number NOT USED$MAY-07-91_ Date NOT USED%21_ Temperature NOT USED&750_ Pressure NOT USED'9000_ Station code (x,y,z base)(HILL12_ Backsight station (rel ang))1.65_ Instrument height+9001 Target point numbera+0000000d_ Horizontal angleb0845923d_ Vertical anglec+00012920m_ Slope distance*BS_ Point code comment (Backsight),1.65_ Reflector height+100 `100_ Target point number (Correction)a+12301400811d_ Horizontal angle (140 08'11")b0845923d_ Vertical angle (084 59'23")c+00012920m_ Slope Distance (12.920m)*00_ Point code comment (00 Sample, 01 Crest, 02 Toe, 03 Spot Height),1.65_ Reflector height9005 Final number (block check characters)EOF_ End of file marker

NOTES1. The block check characters are four digits found at the end of each line (record) of raw Topcon

data (before any processing). The first three characters are a binary check code while the last digit is the sequential record number (0 through 9).

2. It is possible that the surveyor has moved from one control station to the next in the course of recording the data. See APPENDIX B: DEALING WITH NEW CONTROL STATIONS for details on how to handle this situation.

Notes

It is preferred that you take the reading in SD (Slope distance) mode, (prefix "?" to the data line; "<" indicates "Vertical/Horizontal Angle" mode, and "R" indicates that "Horizontal / Vertical Distance" mode is being used on the instrument).

MineMap IMS has standardised on two methods of setting up the data recorder (see the Topcon Manual: "Data selection mode for storage"). The two methods are described in the sections that follow.

Method: [FUNC][7]

Page 48


TIME REC Y/N Choose NO (don't store time)

SELECT Y/N Choose NO i) across page

Choose YES ii) down page

This question is only applicable with the older Topcon versions (FC2 & FC5) as the FC6 only allows the across page format.

1. ‘Across the page’ format (FC2, FC5, FC6)

This format is common to all Topcon data recorders but may be affected by the mode on the survey instrument when the reading is taken. The data line has the format:

R+00022067m0904230+3212340d-00000273t40+14+33013|| || | || || | | ID HD m V H d VD t L P O

Figure 37: ‘Across the page’ format

2. ‘Down the page’ format (FC2, FC5)

In this format we standardise on horizontal /vertical angles and slope distance data. The settings are as follows for the data recorder:

WARNING Y/N Choose YES (want warning if data incomplete)H,V=11 Select Horizontal. and Vertical anglesSD,HD,VD=100 Only require Slope DistanceN,E,Z=000 Not working in absolute coordsHM,HT=00T,P,O,B,L=00000

Table 17: Typical data

Output data Meaning+100_ Target point numbera+1400811d_ H Horizontal Angle (140 08'11")b0845923d_ V Vertical Angle (084 59'23")c+00012920m_ SD Slope distance (12.920m)*00_ Point code information,1.65_ Reflector height

Method: [FUNC][1]

This is a far more powerful method than function 7 because it provides a comment field which can be used to automatically join the points to create strings. The format here is:

MODE 01 <01>

Page 49


REC:PT# Point number

PCODE Point code

R.HT Reflector height

The point code allows recording of strings. A suitable convention would be:

+100 Sequential point number*ST 01 Start string no. 01+101*01+102*SP Spot height (apart from string 01)+103*01

+104*ST 02 Start string no. 02 (string 01 now terminates)+105*02+106*02

The following contains two suggested methods for carrying the back sight station control:

1. In the header format. This format requires less work in the field.

[F3] '100700.47000_ Occupied Station

(100700.47500_ Back sight Station

2. In the first point recorded

This provides more security on back checking and is more complete but does require an extra step at the first recording on each station in the field. Station setup is normal but the first recorded point will contain the back sight ID and bearing.

Table 18: Station setup data

Page 50


Data Meaning'100700.47000_ Station code (x,y,z base)(XXX_ Optional field now)1.65_ Instrument height+100700.47500_ Back sight station (rel ang) - Special point

number a+0000000d_ H (Horizontal angle) - should be 0.0b0845923d_ V (Vertical angle)c+00012920m_ SD (Slope distance)*BS_ Point code information (BACKSIGHT),1.65_ Reflector height

NOTE: This system is more flexible because it allows a non-zero initial offset if necessary.In the field recording of data is controlled by pressing the [ENTER] key on the data recorder. Do not use the [SCAN REC] key on the survey instrument since the [ENTER] key is still required to advance through the cycle and would result in duplicated data.

When recording use the [SKIP] or [ENTER] keys on a blank field to avoid recording data under that category.

The very first reading can be a back sight – this will not affect anything adversely.

Start the point numbers from an agreed upon convention (e.g. A4-8 100). These may be pre-set on recording the first point; from then on it will automatically increment by one.

Page 51


Topcon GTS-6E

This is simply a TOPCON FC5 data recorder with a later model survey instrument (GTS-6E). The option is a combination of the FC2 and FC5 options.

Page 52


Wild GRE-3

Typical data

410082+00000000 42 +00241191 410083+00000003 42 +00001600 410084+00000008 42 +00006565 43 +00001600 410085+00000005 42 +00002185 110086+00002185 21.104+33733270 22.104+08905070 31 00+00079363 51 +0000+000 410087+00001100 110087+00002008 21.104+07439160 22.104+09024560 31 00+00000000 51 +0000+000 110088+00002004 21.104+30018410 22.104+08948090 31 00+00000000 51 +0000+000 410089+00011101

Figure 38: Typical Wild GRE-3 data

Codes

Each line in the raw data has the format shown in Table 19.

Table 19: Wild GRE-3 codes

Column Description1- 2 The type of information contained on the line (process code / measurement)3- 6 Line number from GRE3

7 +8-15 Code (if it is a code line) or observation number (if it is a measurement)16 Blank

17-22 Ignore23-> Information associated with the code

Or if it is a measurement line :23-31 Reading 1 (typically horizontal angle)39-47 Reading 2 (typically vertical angle: 0=vertical, 90=horizontal)55-63 Reading 3 (typically slope distance)

The process code is either "11" or "41". See Table 20 for details.

Page 53


Table 20: Wild GRE-3 process codes

Col. 1-2

Col. 8-15

Column Description

11 Ident. # 23--> Measurement Line23-31 Horizontal angle39-47 Vertical angle55-63 Slope distance

41 Code line00000000 26-31 Date of survey (dd/mm/yy)00000003 23-31 Reflector (prism) height 00000005 23-31 Backsight station number (-ve ==> remote station calculation,

where next measurement line is bearing to backsight)00000008 23-31 39-47 Set-up station number and instrument height 00000010 23-31 Perpendicular offset from line of sight for last reading

(- = left; + = right)00000011 23-31 Vertical offset for last reading (- = down, + = up)00000012 23-31 Offset along line of sight for last reading

(- = backwards, + = forwards)00000100 12 Series of spot heights follow (if "1" values are contourable)00000101 12 string (if "1" values are contourable)

8-11 string number

A report will be automatically generated in the file GRE3.RPT. Figure 39 shows an example report.

SETUP DETAILS:

Date of Survey ------: 24/11/91Reflector height ----: 1.600

Setup station -------: 6565Location ------------: 272437.000 E, 56.700 N, 341.650Comments ------------: SurveyorInstrument height ---: 1.600

Back sight station ---: 2185Location ------------: 303599.448 E, 14.731 N, 125.265Comments ------------: C.R.118 V0 BENCHInstrument height ---: 1.600Observed angle ------: 337 33'27"True bearing --------: 1 15'56"

Figure 39: Report file - GRE3.RPT

The comments and point locations in the above example are derived from the control station file.

NOTES1. Bearing is with respect to the back sight.2. Dip is measured from the horizontal.3. Distance is resolved slope distance (i.e. in the horizontal plane).

Page 54


Wild TPS 1000

Typical data

410082+000000000000000 42 +0000000000241191 410083+000000000000003 42 +0000000000001600 410084+000000000000008 42 +00000000006565 43 +000000000001600 410085+000000000000005 42 +0000000000002185 110086+000000000000002185 21.104+0000000033733270 22.104+0000000008905070 31 00+000000079363 51410087+000000000001100 110087+000000000000002008 21.104+0000000007439160 22.104+0000000009024560 31 00+000000000000 51110088+000000000000002004 21.104+0000000030018410 22.104+0000000008948090 31 00+000000000000 51410089+000000000000011101

Figure 40: Typical Wild TPS 1000 data

Codes

Table 21: Wild TPS 1000 codes

Column Description1- 2 The type of information contained on the line (process code / measurement)3- 6 Line number from TPS 1000

7 +8-23 Code (if it is a code line) or observation number (if it is a measurement)24 Blank

25-30 Ignore30-> Information associated with the code

Or if it is a measurement line :31-39 Reading 1 (typically horizontal angle)40-48 Reading 2 (typically vertical angle: 0=vertical, 90=horizontal)49-57 Reading 3 (typically slope distance)

The process code is either "11" or "41". See Table 22 for details.

Page 55


Table 22: Wild TPS 1000 process codes

Col. 1-2

Col. 8-15 Column Description

11 Ident. # 30--> Measurement Line31-39 Horizontal angle40-48 Vertical angle49-57 Slope distance

41 Code line00000000 34-39 Date of survey (dd/mm/yy)00000003 34-39 Reflector (prism) height 00000005 34-39 Backsight station number (-ve ==> remote station calculation,

where next measurement line is bearing to backsight)00000008 34-39 47-55 Set-up station number and instrument height 00000010 34-39 Perpendicular offset from line of sight for last reading

(- = left; + = right)00000011 34-39 Vertical offset for last reading (- = down, + = up)00000012 34-39 Offset along line of sight for last reading

(- = backwards, + = forwards)00000100 20 Series of spot heights follow (if "1" values are contourable)00000101 20 string (if "1" values are contourable)

16-19 string number

A report will be automatically generated in the file TPS1000.RPT. Figure 41 shows an example report.

SETUP DETAILS:

Date of Survey ------: 24/11/91Reflector height ----: 2.300

Setup station -------: BLU36Location ------------: 102093.670 E, 110147.570 N, 141.651Comments ------------: 4136Instrument height ---: 2.300

Back sight station ---: CONE2Location ------------: 101130.240 E, 110952.200 N, 103.708Comments ------------: 4442Instrument height ---: 1.000Observed angle ------: 0 00 '00"True bearing --------: 309 52'03"

Figure 41: Output file- TPS1000.RPT

The comments and point locations in the above example are derived from the control station file.

Page 56


NOTES1. Bearing is with respect to the back sight.2. Dip is measured from the horizontal.3. Distance is resolved slope distance (i.e. in the horizontal plane).

Page 57

import/ export cad data - minemap pty ltd - mining … - import export... · web viewminemap ims -...

Documents