GEODAT
Vulcan can directly interface with most GEODAT instruments, providing you with both uploading and downloading capabilities.
Note The Geodimeter based Trimble Total Stations is also supported by Vulcan. However, not all GEODAT codings and options are supported.
Vulcan supports files of the following types:
- Standard pickups (with either a standard instrument set up or special resection set up) using the Reduction option.
- Special resection record structure for use with the Resection option
- Special traverse record structure for use with the Traverse option
Pickup file format
The format of a pickup file, which is created in the instrument, required by Vulcan is in the standard GEODAT format (that is, with records one per line or space separated).
The following table lists the supported GEODAT codes:
| Code | Description |
|---|---|
| 2 | Instrument station name |
| 3 | Instrument height |
| 4 | Feature code |
| 5 | Point name |
| 6 | Signal height |
| 7 |
Horizontal angle (ddd.mmss)
|
| 8 |
Zenith distance (ddd.mmss)
|
| 9 | Slope distance |
| 21 |
Backsight direction
(ddd.mmss)
|
| 50 | GEODAT job name |
| 51 | Date of survey |
| 53 | Surveyor's name |
| 54 | Project name |
| 62 | Backsight/resected station |
| 90 |
Horizontal offset
Negative = left
|
| 91 |
Perpendicular Horizontal offset
Negative = left
|
| 92 |
Horizontal distance offset
Positive = away from instrument
|
| 93 |
Vertical offset
Negative = down
|
| 94 | Temporary station name |
| 99 | Special (see resection below) |
Example: Standard instrument set up pickup file
50=588 51=18-05-2000 53=JRL 2=5336 3=1.6 62=145 21=0 4=HWL_TOE 5=1 6=2.2 7=130.5712 8=91.122 9=80.73 6=1.6 94=NEW_STN 5=2 6=1.6 7=133.112 8=90.3128 9=93.66 5=3 6=1.6 7=136.301 8=90.0038 9=102.93 4=CREST 5=4 6=1.6 7=136.3356 8=89.5314 9=102.32 5=5 4=CHTRIG21 6=1.6 7=134.2922 8=90.0012 9=93.07
Note We recommend that your pickup file follow the sequence shown in the example above. It is possible to ignore the code 21 records, in which case it is assumed that horizontal angles are bearings. Refer to the Surveying > Reduction option for more information.
The feature code record (4) sets the feature code for the shots that follow. This code is required initially, and then only at a change of feature.
All the required offset records (record types 91,92,93) for a shot should appear BEFORE the compulsory shot records (horizontal angle, vertical angle, and slope distance).
The code 90 record must occur in the raw data file BEFORE, or in the compulsory shot records for which it is related (that is, slope distance, horizontal and vertical angles). The code 90 value consists of 3 digits. The first determines the direction, where 1 is directly back towards the instrument along the line of sight, 2 is at 45 degrees clockwise from the instrument, 3 at 90 degrees etc. up to 8 which is 315 degrees clockwise. The last two digits are the distance of the offset in units from 01 to 99 units.
For example 90=405 means a 5 unit offset from the target at 135 degrees clockwise from the sight line between the target and the instrument.
Note The code 90 record will not be used if there code 91/92 offset records are being used for the same shot.
The temporary station name record (94) should occur BEFORE, or in the compulsory shot records for which it is related. The syntax is
94=stn_name
. Later on in the job you can have a set up on the station with a
2=stn_name, and it will use the calculated coordinates for the station coordinates. In the example above, the coordinates of shot 2 would be used for station
NEW_STN
if the station was used later in the reduction and a station of that name didn't exist in the selected station libraries. Temporary stations only last for the current reduction, although they may be optionally saved into the station library.
Consecutive shots with the same point name are averaged into one shot during the reduction.
Check shots are defined as shots to a known station that produce a misclose line on the reduction report. These are implemented by checking the Report on check shots check box, and providing a prefix that will be used for the feature code of the check shot. In the above example, the last shot (shot 5) has a feature code of
CHTRIG21
. If you chose to report on the check shots, and entered CH as the flagging prefix, then this will mean that this last shot is a check shot to a station called
TRIG21
. An additional line will then be added to the survey report giving the calculated misclose.
Special resection instrument set up for a pickup file
If you are doing a resection rather than a normal instrument set up, then the instrument set up section of the file needs to be in a special format.
Example:
50=JOB1 51=06-06-2000 53=JRL 99=RESECTION_4 2=06902 3=1.005 62=TRIG01 6=2.000 7=0.0000 8=84.3850 62=???? 6=2.000 7=8.5139 8=81.1506 62=???? 6=2.000 7=103.3954 8=70.4030 62=???? 6=2.000 7=149.0650 8=83.0333 5=1 92=4.2 4=TODC 6=2.000 7=61.0929 8=92.5335 9=58.30 5=2 92=4.3 4=TODC 6=2.000 7=77.0612 8=92.3017 9=57.01
This file has a resection with shots to 4 known stations. Note the special 99= record, which contains the keyword
RESECTION_#
where # is the number of resected stations that will be read. If the resected station name is ????, then its name will be prompted for during the resection calculations, which would then require the station coordinates to be read from the station libraries or manually entered. Once the resection information is completed, the rest of the pickup file follows the rules laid out above.
Note This file is reduced by the Reduction option, and does not use the Resection option.
Resection calculation file format
This format is for use with the Resection option. It is designed to support the calculation of a resection only, and cannot continue and perform a reduction. The data file must be structured in a special format, essentially a backsight and a reading set, duplicated for various backsight stations up to a maximum of ten. The minimum number of readings is obviously three.
Example:
62=158......backsight reading 1 7=31.413......horizontal angle 8=97.5316.....zenith angle 62=709......backsight reading 2 7=38.5024 8=94.0936 62=710......backsight reading 3 7=57.1402 8=95.2338 62=145...... backsight reading 4 7=63.4924 8=92.4556
Traverse file format
The Traverse option requires the GEODAT file to be in a special format. You can divide the file format into 'groups' of records.
These groups are :
Code 50 - file name in geodat Code 51 - date Code 2 - instrument station name Code 3 - instrument height Code 62 - backsight station Code 7- back bearing Code 87 - Traverse foresight Code 6- target height Code 7- foresight bearing Code 8- vertical angle (zenith distance) Code 11 - Horizontal distance Code 10 - Vertical distance Code 62 - backsight station Code 6- target height Code 7- back bearing Code 8- vertical angle (zenith distance) Code 11 - Horizontal distance Code 10 - Vertical distance Code 87 - Traverse foresight Code 6- target height Code 7- foresight bearing Code 8- vertical angle (zenith distance) Code 11 - Horizontal distance Code 10 - Vertical distance Code 62 - backsight station Code 6- target height Code 7- back bearing Code 8- vertical angle (zenith distance) Code 11 - Horizontal distance Code 10 - Vertical distance Code 87 - Traverse foresight Code 7- foresight bearing Code 56 - temperature (optional but not used)
All records as mentioned in a 'group'; need to exist in the data. You can have multiple sets of the measurement 'groups' these are meaned for the final result.
Example:
50=JOB1 51=12-02-1999 Job records 2=STN1 3=0.260 Instrument set up records 62=BS1 7=0 87=2251 6=1.595 7=343.1658 8=90.2016 11=484.624 10=-2.838 Initial BS and FS measurements 2=2251 3=1.595 Instrument set up records 62=STN1 6=0.110 7=0.0004 8=89.4144 11=484.627 10=2.592 87=2252 6=0.110 7=105.3724 8=90.3528 11=466.516 10=-4.796 Full back and foresight measurements 2=2252 3=1.575 Instrument set up 62=2251 6=0 7=0 8=89.0540 11=158.256 10=2.501 87=2011 7=160.1232 Closing shot for angle closure
Data Storage - Upload
To use GEODAT instruments for upload data recorders with direct access into Vulcan, you are required to use a standard set of coding functions. Whilst GEODAT supports extensive coding styles Vulcan supports the following.
| Code | Meaning |
|---|---|
| 5 | Point Number |
| 37 | Easting |
| 38 | Northing |
| 39 | RL |
Example: Upload File
5=1 37=10414.244 38=14417.045 39=10000.000 5=2 37=10567.885 38=14775.540 39=10000.000 5=3 37=10446.252 38=15067.885 39=10000.000 5=4 37=10245.666 38=15153.241 39=10000.000 5=5 37=10028.007 38=15023.073 39=10000.000
