updated: 26-Nov-2009

 Copan for Windows

Map Checks

Note that if you need to adjust azimuth and distance traverse data or save new points, you should use the § Map Traverses module.

Also, this module cannot be used for field data, involving horizontal or vertical circle readings. For such needs, use the § Field Data Processing module. While there are certain similarities between the Map Check and the Field Data modules, there are various operational differences (other than the type of map/survey data involved). If you are familiar with one and new to the other, please study the appropriate manual and dialog carefully.

To Check Bearing-Distance Traverses

1. If you have a coordfile open, close it.
2. Calculate | Check Brng-Dist Traverse (Map Check)...
3. Optionally Load... a traverse Data file. This may be an older-format loop file or a newer-format map traverse file (see Map Traverse Files below).
4. Optionally enter corrections: an Azimuth Correction, to be added to every bearing; a Units Factor, for converting distance units to coordinate units; a Projection SF, for the map projection scale factor correction.
5. Enter or edit the bearing-distance traverse data in the big edit box. See below for a description of map traverse data for checking.
6. Editing traverse data in the big edit box:
   To move the text cursor within the big edit box, use the Arrow, Tab, or Enter keys, or the mouse pointer. Do not use the Space key to separate fields. To delete a chunk of text, select it with the mouse then click Cut (or type Ctrl-X) but be careful not to delete the embedded tabs within a line. To manually insert a tab, Copy and Paste an existing one. The Ctrl-Insert and Ctrl-Delete key combinations act like the Ins and Del buttons, that is, they insert and delete a line of data. To add a Point number automatically to the next blank line, press Enter when in the Distance column of the previous line.
7. Optionally List the map traverse data.
8. Save the Data for reuse.
9. Calculate (or OK) the traverses.
10. To graphically view the traverses: Close or hide the Info Display window if it is open, and minimize or move aside — but do not close — the Map Traverse window. You may turn off the annotations prior to Calculation if desired.

click for larger view

Map Traverse Data for Checking

• Begin each traverse by a starter line, which must contain the first point number, under Point, and may contain a label, under T-Label, identifying the traverse. Since there is no use of coordfiles, any valid point number may do.
• If you have multiple traverses, when you Calculate you may begin from a specific traverse rather than from the top by entering the start point number or traverse label.
• A traverse must have a sequence of leg lines. Each leg
  • must contain these three items: to Point number, Bearing (or bearing) and Distance,
  • and may contain a Label, P-Code, and a Curve code (Labels and P-Codes are ignored, however).
• For a Bearing or Distance, a bearing or distance expression may be used (see § Bearing Expressions and § Distance and Offset Expressions), except that, because no coordfile is open, no point numbers may be used. If a Bearing or Distance is the same as the previous one, a double-quote character (") may be used for ditto.
• At any point along a traverse you may need to change the scale or distance factors or the azimuth correction. To do this, enter a separate line with
  • SF=value,
  • UF=value, or
  • AC=value
  under Correction. From that point on the new value is used instead of the original head value. Optionally, a relative azimuth correction
  • ac=value
  may be used, where the value is added to the original value for subsequent azimuth corrections. Note that these commands are case-sensitive.
• Blank lines may be used for readability but have no affect on traverse demarcation or calculation.

Map Traverse Files

• The first line must contain only this text:
    Map Traverses
• The next three lines can contain anything as they are not currently used.
• The next three lines must contain the head correction values — Scale factor, Distance factor, and Azimuth correction — one each per line.
• Each subsequent line must be a tab-delimited data line with these six fields:
      Point, Bearing, Distance, Label/Correction, Code, and Curve
  While some or all of those fields may be empty there must be five tabs per line. Which fields can be left blank depends on the purpose of the particular data line (see Map Traverse Data for Checking above).

Example 1: Map traverse file.

Map Traverses
1st dummy line
2nd dummy line
3rd dummy line
1.0000000000
1.0000000000
0.0000000000
1                       Parcel B
2   092.2112    160.40
3   182.0352    160.93
4   "           048.32
5   183.4005    059.19
6   260.5657    160.73
7   000.0812    061.41
8   002.1748    077.60
1   002.1748    161.24      

Notes

• If a traverse is a true loop (i.e., it closes on itself) Copan provides the enclosed area in squared distance units (e.g., m²). Copan does not yet calculate areas enclosed by separate traverses.
• If Copan complains about the data when calculating, and you cannot see what is wrong, visually inspect the data by selecting it all with the mouse. Often, you can see the inconsistency via the selection block outline.
• List All... is equivalent to the sequence List data and Calculate.
• If you List traverse data to the Info Display file,
  • multiple blank lines are ignored, and
  • azimuth (or bearing) and distance expressions or dittos are shown in their interpreted, but not corrected form.

Bugs

• Traverse graphics annotations are not sized properly.

updated: 26-Nov-2009