Field Files

Field File Types
Copan Field File Format

Field Attribute Codes
Remote Elevation Measurement

To Copan, field survey data consist of measured or reduced angles and distances, and come in field files. Coordinates, however they've been collected or derived, are not yet considered to be field data and can only be imported to Copan via the generic import facility (see § Import and Export)

1. Field File Types

Copan can read field data in various different formats. While the files can have any names, certain extensions are advisable:
- Copan field file — .fld or .f*
- Geodimeter file — .job or .raw
- TDS RAW/RW5 file — .raw or .rw5
- Nikon RAW file — .raw
- Leica GSI-8 file — .gsi
- Leica GSI-16 file — .gsi
- Wild GRE file — .gre
Copan only saves field data in its own format (which is just as it appears in the big edit box).
Field data files are plain text (or ASCII) so can be edited outside of Copan (but be careful to follow the relevant syntax).
Note that while both topographic and geodetic variations of Leica GSI-16 data can be read, some manual editing of the loaded data may be required before calculating.

Let us know ( at support@underhill.ca ) if you'd like Copan to read field data in other formats. Please note the software version and release date (see § Software Version) in all communications.

2. Copan Field File Format

A Copan field file consists of numerous Setup and Observation data lines. It may also contain comment lines, as well as Project, Scale, or Instrument data lines, if required.
Each data line consists of various tab-separated attribute = value pairs.
Typically, observations are indented from setups for readability, but it is not a requirement.
Spaces may be placed either side of equals signs (e.g., HS = 1.56) if desired.
Generally, spaces may replace tabs to separate attribute=value pairs. However, at least one tab character must separate a Code and a Note (e.g., cod=46 [tab] not=timber).
A valid comment line begins with zero or more spaces or tabs, then has two commas (,,), periods (..), slashes (//), semi-colons (;;), or backslashes (\\), which are followed by any character string. Comments are not processed or stored as point notes (but are saved within the field file). Use them to temporarily remove an observation or to log events.

3. Field Attribute Codes

Here are the currently recognized codes representing the attributes in attribute=value pairs. Note that correct case is important.

Attribute code	Attribute meaning	Ignored during calculation
`at`	setup (or station) point number
`az`	azimuth (or bearing)
`bas`	base point number for a REM point
`cod`	point (or feature) code
`dat`	date	*
`DC`	distance correction constant
`DF`	distance correction factor (related to PPM)
`dis`	distance point number for a REM point
`end`	previous line is last leg of traverse or last shot of resection
`FB`	field book number	*
`HC`	horizontal circle reading
`HI`	height of instrument
`HS`	height of signal (or target)
`instr`	instrument number	*
`job`	job/project number	*
`not`	point note
`pgs`	field book pages	*
`ref`	reference (or BS) point number
`rem`	point note (depricated — use `not` instead)
`SD`	slope distance
`SF`	projection (or combined) scale factor
`svr`	surveyor/operator	*
`tim`	time	*
`to`	target point number
`UF`	units conversion factor
`VC`	vertical circle reading (or zenith angle)
`VCC`	vertical circle correction

Let us know ( at support@underhill.ca ) if you'd like Copan to recognize other attributes. Please note the software version and release date (see § Software Version) in all communications.

4. Remote Elevation Measurement

A remote elevation measurement (REM) is an indirect observation of height and position of a topographic point whose slope distance is unobservable. If you can observe a vertical angle to an otherwise inaccessible point (such as the top of a mast) and you cannot get a reflectorless distance, you can determine the 3D coords for that point indirectly, via another point that you can shoot to normally and that is either vertically below the inaccessible point or at the same horizontal distance away. Let's call the high inaccessible point the REM point, an accessible point vertically below it a base point, or an accessible point at the same horizontal distance away a dist point. To insert a REM observation, reference must be made to either a base point or a dist point:

If referencing a base point
1. Enter the observation via the Observation boxes along the bottom, ensuring the SD box is blank.
2. Insert the observation, noting that bas= prev is added to the observation automatically.
3. If the previous side-shot is not the base point, edit the prev with the relevant point number, which can be any normally observed side-shot — even one from an earlier or later setup.
If referencing a dist point
1. Enter the observation via the Observation boxes along the bottom, ensuring the HC and SD boxes are blank.
2. Insert the observation, noting that dis= prev is added to the observation automatically.
3. If the previous side-shot is not the base point, edit the prev with the relevant point number, which must be from the same setup.
As an alternative, add the observation as usual but use dummy values for HC and SD. Then edit the line as appropriate (i.e., delete the HC= and SD= portions and add the bas= or dis= portion).

updated: 18-Jun-2009

Copan for Windows

Field Files

Contents

1. Field File Types

2. Copan Field File Format

3. Field Attribute Codes

4. Remote Elevation Measurement