[^1] [^2]

CONTENTS

This help document describes those functions of the GSMAP version 9
system implemented by the GSMCAD program, many new functions, and the
system of menus unique to the Windows implementation. GSMCAD does not
include all the capabilities of the GSMAP system, and this documentation
is not comprehensive. The most complete documentation of the GSMAP
system remains the U.S. Geological Survey Open-File Report 93-411,
SYSTEM 9 ,GSMAP, AND OTHER PROGRAMS FOR THE IBM PC AND COMPATIBLE
MICROCOMPUTERS, TO ASSIST WORKERS IN THE EARTH SCIENCES. by Gary I
Selner and Richard B. Taylor. Users should refer to that document for
questions that are not resolved by the on-line documentation.

GETTING STARTEDgetstart

DRAWING ENTITY TYPES (CODE GROUPS)code0

MAP PROJECTION AND PROJECTION FILESprojectionhelp

FILE FUNCTIONSfiles

EDITING ENTITIESeditm

BLOCK FUNCTIONSblkhead

DRAWING NEW ENTITIESdigitize

DISPLAY OPTIONSdisplay

ZOOMING THE SCREEN WINDOWzoom

PANNING THE SCREEN WINDOWpan

EDITING THE DATABASEdbase

HARD COPY OUTPUToutputm

DATABASE FILE STRUCTURE AND STANDARD DOS FILE EXTENSIONSdosexthelp

SETTING UP A DIGITIZERsetupdig

[^3] [^4]

FILE MENU FUNCTIONS

The file menu is active when the program begins, whereas the other menus
only become active after a database has been opened. File menu functions
are listed below.

Opening a databasefopendb Creating a new databasefmakenew

Opening a background databasefopenback Backing up a databasefdbbak

Opening a projection filefopenprj Opening a plot file fopenplt

Rereading a plot filefirrplt Editing text filesfedit

Importing datafiimport Exporting dataexporthead

Resuming previous sessionslasttime Reporting bugsfibug

Shelling out to DOSshelldos Exiting the programend

[^5] [^6]

Opening a database

Displays a list of database index (.ndx) files. Select a database to
edit by double clicking on the filename or typing in the filename. If
the data base is [geodetic]{.underline}geodeticdef rather than
[cartesian]{.underline}geodeticdef, a projectionprojectionhelp file must
be opened. If a file with the same root as the database and the
extension .prj exists in the same directory as the database, it will be
opened as the default projection file. Otherwise another display appears
offering a choice of projection files from which the user must select
one. Next a plot file file must be opened. If a file with the same root
as the database and the extension .plt exists in the same directory as
the database, it will be opened as the default plot file. Otherwise the
program displays a list of plot (.plt) files from which the user must
select one. If an error is detected in the plot file selected, the
program will report the type of error and the line number where it
occurs, and will load the plot file into the NOTEPAD editor for
correction. This aborts the automatic sequence, so that the user must
select another menu choice to load the corrected plot file.

If the default plot and projection files are automatically loaded, but
the user wants to use other plot or projection files, the other files
can be loaded using other options under the FILESfiles menu.

[^7] [^8]

Coordinates in a geodetic database are stored as latitude and longitude
and projected to map inches using any one of a number of standard
projectionsprojectionhelp according to parameters selected by the user
and stored in the projection file.

Cartesian coordinates can be any orthogonal system of units, including
drawing inches, universal transverse mercator (UTM) ground meters, or
state plane coodinates. They are converted to map inches by simple
scaling.

[^9] [^10] [^11]

Creating a new database:

The FILE menu \<New database\> option should be used to create a new
database when starting a new project. It initiates a step by step
sequence that creates the line segment file (.lsf), index file (.ndx),
and nodenodehelp file (.nod) to hold data, and, optionally, adds a
border line or grid of lines to the database. For a
[geodetic]{.underline}geodeticdef database, a projectionprojectionhelp
file will be automatically created for the most common U.S.G.S. base map
series or the user will be guided in preparing a projection file for
nonstandard maps. Projection parameters can be complicated, so it is
advised to use this option.

Next the user has the option to copy a preexisting plot file or to be
guided through the steps to create a new one. It is usually most
efficient to copy a preexisting plot file, but educational to create
one. Available wall charts provide a good summary of plot file
parameters.

[^12] [^13] [^14]

Opening a background database

After a database has been opened for editing, a second database can be
opened that will be plotted as a background to the first, but that
cannot be edited. For example a topographic basemap might be scanned,
vectorized, converted into GSMAP format, and displayed behind a geologic
map. After background database files are opened under the file menu,
display of the background can be toggled under the display menu. On the
screen the background will be displayed in light gray, but the
background lines will be plotted according to the line code instructions
in the plot file when output to a plotter or printer.

[^15] [^16] [^17]

Backing up a database

The FILE menu \<backup database\> option copies the three database files
(.LSF, .NDX, .NOD) to files with the same root, but extensions .BSF,
.BDX, and .BOD. If the database files are subsequently damaged by some
editing mistake, the data can be recovered by renaming the backup files
to the original extension names. It is advisable to back up the database
at the beginning of each session, and periodically thereafter,
especially prior to any complicated editing procedure. Edits and
additions are written to a GSMAP database immediately, so the option of
not saving mistaken edits does not exist.

[^18] [^19] [^20]

Opening a projection file:

Files menu option that opens a list of projectionprojectionhelp files
and offers opportunity for user of a geodeticgeodeticdef database to
switch to an alternative projection without closing the database. When
digitizing from a map, the projection file must agree with the
projection used to construct the source map base. When plotting or
converting to ground meters, the projection file must agree with the
projection of the target map.

[^21] [^22] [^23]

Opening a plot file:

Files menu option that opens a list of available plot files (.PLT) and
offers opportunity for user to switch to an alternative plot file
without closing the database.

[^24] [^25] [^26]

Rereading the plot file

Option on the FILES menu that reads the selected plot file again. If
changes are made to the plot file by using NOTEPAD or some other editing
program, the file must be read into GSMCAD again for the changes to take
effect. If the changes are made by using NOTEPAD through the edit text
filefedit option on the FILE menu, the plot file will be reread
automatically the next time the screen is redrawn.

[^27] [^28] [^29]

Importing data

A FILES menu option that offers a submenu of options for adding data to
a GSMAP database from various types of preexisting files.

Create a cartesian GSMAP database from a DXF filefidxfin

Append from another GSMAP databasefiappgsmap

Append from a GSPOST or MPS format ascii filefiappost

Paste a cartesian GSMAP database into another GSMAP databasecartin

[^30] [^31] [^32]

Create a new GSMAP [cartesian]{.underline}geodeticdef database from a
DXF file

A new [cartesian]{.underline}geodeticdef GSMAP file will be created from
an autocad data exchange format (.DXF) file. The conversion is partial.
Only polylines, lines, text, and attributes will be converted and all
other entities ignored. Polylines from different layers will be assigned
different line codes between 1 and 99. By this method linework from
other CAD programs and vectorizing programs can be imported so that
scanned data and data digitized directly from air photographs on
photogrammetric plotters can be incorporated in GSMAP drawings.

[^33] [^34] [^35]

Append from a GSMAP database

Data from another GSMAP database can be merged with the data in the open
database. The data types must match. Only
[geodetic]{.underline}geodeticdef data can be added to a geodetic
database.

[^36] [^37] [^38]

Paste a GSMAP [cartesian]{.underline}geodeticdef data base into another
GSMAP database

A GSMAP [cartesian]{.underline}geodeticdef database will be added to the
current [cartesian]{.underline}geodeticdef or
[geodetic]{.underline}geodeticdef database. The user determines the
offset by clicking the mouse on the new position for the lower left
corner of the database to be imported. This can be used for adding
standard scale bars and explanation text.
[Cartesian]{.underline}geodeticdef data added to a
[geodetic]{.underline}geodeticdef database will be transformed into
geodetic format.

[^39] [^40] [^41]

Append from GSPOST or MPS table

A variety of single or two point entity types can be added to a GSMAP
database by reading in data from an ascii text table formatted in
GSMPOST style. The value for P1 will be read from the first column, P2
from the column designated for label rotation angle (col 4 except col 10
for degree, minutes seconds \[GDMS\] format). The line code is either
read from the first data column (column 7 except col 13 for GDMS) or a
single code for every entity in the table is input by the user. GPS
coordinates for sample locations (100 codes)code100, structural
observations (200 codes)code200, or point symbols (300 codes)code300 can
be read in this way so that analytical data is posted or strike and dip
symbols are automatically plotted. The GSPOST file can be used as the
data file for 100 codes. It does not have to be reformatted into GSMAP
data table format.

Generally data tables having [geodetic]{.underline}geodeticdef
coordinates can only be read into a geodetic GSMAP database and data
tables having [cartesian]{.underline}geodeticdef coordinates can only be
read into a cartesian GSMAP database. An exception is UTM ground
coordinates in meters can be read into a
[geodetic]{.underline}geodeticdef database if the UTM projection file
for the correct zone is in use. The UTM coordinates will be transformed
into geodetic (latitude, longitude) coordinates.

MPS files are ascii tables of GPS positions generated by the PLGR GPS
receiver. Both LL/dms and UTM/UPS formats can be read, but the UTM zone
of the projection file or of the cartesian data in the database must be
the same as that of the observations, or the observations will be
misplotted. If a code \<100 (code group for lines and decorated lines)
is assigned when the data is read in, all the points in the file will be
connected to form a single line.

[^42] [^43] [^44]

Export data from GSMAP binary files to other formats

A FILES menu option that offers a submenu of options for extracting data
from a GSMAP database for transfer to another format.

Convert GSMAP to ARC/INFO ascii generate formatfitoarc

Output GSMAP ascii formatfigsm2asc

[^45] [^46] [^47]

Convert GSMAP to ARC/INFO ascii generate format

Writes ASCII coordinate and attribute files in ARC generate format.
Takes instructions from special words included in the comments of the
plot file. Line codes including the word \"contact\" will be added to
the line file used to generate polygons. Text codes in the 500 series
will be used to generate polygon tags if their comment includes the word
\"tag\". Line codes including the word \"line\" will be included in a
coverage of miscellaneous lines that are not polygon boundaries. The
decorations for lines and symbols of the 100, 200, and 300 series will
be included in a symbols coverage if their comments include the word
\"symbol\". Text will be included in a text coverage if the comment
includes the word \"text\". Macro files (.aml) that run under ARC/INFO
are provided to convert the files generated by GSMCAD to the appropriate
ARC coverages.

Unit labels with leaders (500 codes) are a special case. The leader
lines will be brought into the text coverage as arcs, and points at the
second point of each leader (odd numbered points \>1) will be used as
the tag positions if the code comment includes the word tag.

[^48] [^49] [^50]

Output a GSMAP ascii format file from a GSMAP binary database

Combines attribute data from the .NDX binary file and coordinates from
the .LSF binary file and outputs a text file im standard GSMAP ascii
format. The data can be reformated with a word processor to produce
custom formats. Text files can be converted back to binary the GSMUTIL
utilities program, but nodenodehelp data is lost, so the node topology
must be rebuilt. This will occur automatically if the reconstructed
database is read into GSMCAD.

[^51] [^52] [^53]

Edit text file

A FILES menu option that calls the NOTEPAD editor. A sub menu offers
choices to automatically load the plot (.PLT), projectionprojectionhelp
(.PRJ) or rock unit file (.RU) or to start with no file loaded so the
user can select another text file. This is most commonly used to revise
the plot file. If the plot file is revised, it must also be reread for
the changes to take effect. This occurs automatically the next time the
screen is redrawn. If the projection file is revised, the file menu
choice to select another projection file must be used, even if the
revised projection file has the same name as the current projection
file. Under this option there is also a routine to reformat a text list
into a properly formated GSMAP rock units (.RU) file.flist2ru

[^54] [^55] [^56]

Convert text list to GSMAP formatted rock unit file.

GSMAP text entities (code groups 500 - 599code500 and 700-799code700)
store their text information as numbers in the P1 field. These numbers
relate to a text file (named in the plot file) where the same numbers
set next to the words and letters they represent. The text file can have
any name and extension, but have been called rock unit files because
they commonly consist mostly of the letter abbreviations for rock unit
names. It is customary to give them the extension \<.RU\> to distinguish
them from other text files. The format for rock unit files is shown
below:

1,\"Qal\"

\"EOT\"

2,\"Tv\"

\"EOT\"

3,\"Any kind of text\"

\"EOT\"

Because it is tedious to type in all the numbers, commas, quotation
marks, and end of text marks and because of the possibility of typing
errors, this menu option will read in a simple text list without numbers
and write out a rock unit file with numbers and formatting included.
There is an option to begin at a number greater than one and also to
skip numbers to leave space for afterthoughts. Code group 500-599code500
can have several lines of text associated with a single entry, but this
option assumes one line of text per entry. If several lines of text need
to be associated with one entry, edit the created file to remove the
excess numbers and end of text markers.

Please note that certain stand in characters can be used with font 0 to
produce the symbols for Triassic (@), Pennsylvanian (&), Cambrian (\\),
degree ({), and second (}). Other special symbols can also be produced
by entering ASCII characters greater than 127, depending on the font..

The conversion to rock unit file format option is found under the FILE
menu under \<Edit text file\>.

[^57] [^58] [^59]

Recall previous sessions

A record is maintained of the last four databases that were opened, and
the names of the databases are listed in the FILE menu after numbers
from 1 to 4. Any one of those previous sessions can be resumed by
selecting the name or number from the menu.

[^60] [^61] [^62]

Report bugs

A FILE menu option that calls the NOTEPAD editor with a form loaded on
which the user can type reports of problems with the program. The form
includes the address, phone number, fax number, and E-mail address of
one of the program authors. Please transmit a description of the problem
by the most convenient means.

[^63] [^64] [^65]

Shell to DOS

A FILE menu option that loads a DOS shell so the user can run DOS
programs such as GSMUTIL or HPGLUTIL without exiting the program. The
screen drawing board will be erased, so a redraw command (type the
letter R) should be given after exiting from the DOS shell.

[^66] [^67] [^68]

Exit the program

A FILE menu option that closes the database and ends the program,
returning to windows.

[^69] [^70] [^71]

EDITING ENTITIES IN GSMAP DATABASES

The EDIT menu offers many choices for editing entities in the database.
Many of the options on the menu can also be efficiently activated from
the keyboard by using shortcut keys. The shortcut keys are indicated on
the right side of the pull down menu. The menu does not have to be
pulled down to activates the shortcuts. The fastest way to edit is to
type shortcut keys with one hand while pointing at the drawing with the
other. The cursor can be moved and points set using the mouse,
digitizing tablet keypad (if registered and activated), and arrow and
other keys from the keyboard. In addition to the shortcut keys listed on
the menu, other shortcut keys duplicate functions normally done with a
mouse. The \<Ins\> key sets a point; the period key \<.\> sets a point
on the nearest preexisting point; and the comma key \<,\> moves the
cursor to the nearest preexisting point without setting a point. Arrow
keys move the cursor on a grid spacing that can be varied (by using +
and - keys) from 1 inch to 0.001 inch.

Selecting entities for editingselect Continuing the search to select an
entitycontsel

Undo the last editundo Display information about an entityedquery

Change attributes of an entitychange Break a line into two partsedbreak

Delete an entityeditdel Undelete an entityedundel

Move an entityedmove Copy an entityedcopy

Move an entity by draggingeddrag1 Copy an entity by draggingeddrag2

Reverse the direction of a lineeditrev Move a single point in an
entityedmvpt

Add points to an entityaddp Delete points from an entityeddelpt

Move a nodeednode Set snap distancesetsdist

Registering a digitizing tabletedregdig Editing entities from a
digitizing tableteddig

[^72] [^73] [^74]

Selecting an entity for editing (shortcut \<S\>)

Allows user to select the entity to be edited by pointing with the mouse
or digitizer crosshairs. If the left mouse button or the zero key on the
digitizer key pad is used, then the entity must be within pointing
distance (1% of screen width) to be selected. If the right mouse button
or the 4 key on the digitizer key pad is used, then the entity
containing the closest point on the screen will be selected, even if it
is not within the pointing distance. If one of the editing commands is
invoked while no entity is selected, then those commands will
automatically invoke the select command first. Information about the
selected entity, or a notice that no entity is currently selected is
displayed near the upper right corner of the screen.

If more than one entity is within pointing distance, the first entry in
the database will be selected. If that is not the desired entity, then
the edit menu offers a choice to continue (shortcut \<C\>) the search to
the next database entry within pointing distance. If the screen window
is changed so that the selected entity is no longer visible, then it
will be unselected. Entities can also be unselected by using the select
command and pointing at an empty part of the drawing, or by using the
continue command until all the entities within pointing distance have
been passed over.

Another way an entity may be selected is to highlight it (click on row
number) in the database spreadsheet (List option under the DATABASE
menu). If it lies within the screen window, it will be selected after
returning to the drawing board.

[^75] [^76] [^77]

Continue the search to select an entity for editing (shortcut \<U\>)

An EDIT menu option that is active when an entity has been selected so
that the user can continue the search through the database for later
entries that may also be within pointing distance of the original
selection point. Allows differentiation of entities that coincide or are
too close to each other to be separated by pointing.

[^78] [^79] [^80]

Undo the last edit

For certain types of editing, the last edit can be undone, reverting
back to the preedit condition. This capability includes deleting an
entity, deleting a point, moving a point, adding points, and changing
the values (CODE, P1, P2) of an entity. A message box will appear
describing the edit to be undone and requesting confirmation. If the
entity is no longer in the screen window, then the capability to undo
the edit is lost, and the undo choice will not appear in the menu.

[^81] [^82] [^83]

Display information about an entity

The EDIT menu \<query\> option opens a box containing information about
the selected entity. The information varies depending on the type of
entity. Length is calculated for lines, and also area for polygons and
closed lines.

[^84] [^85] [^86]

Changing attributes (CODE, P1, P2) of an entity (shortcut \<H\>)

The edit menu \<change\> option opens a pulldown list (click on arrow to
see the list) tablating all the line codes defined in the plot file and
a brief description of their meaning. The user can choose one of those
codes or type in a new code for the selected entity. Depending on the
code selected, the user may also be prompted to enter new values for P1
and P2 attributes.

[^87] [^88] [^89]

Breaking a line into two pieces (shortcut \<B\>)

The EDIT menu \<break\> option to break a line into two parts, creating
a nodenodehelp at the break point. The break point is created at the
closest place on the line where a perpendicular can be projected through
a point set by the user with the mouse or digitizer. If the set point is
too far from the line or no perpendicular is possible, then the break
will fail.

Breaking a line will not change the position of the line unless the new
node created is within snap distance of a preexisting node, in which
case the line segments closest to the new node will be deflected as the
break point is moved to the preexisting node. For that reason it is
preferable to break the boundary lines of a map where they intersect
contacts before digitizing the contacts.

The first part of the broken line remains selected after the break, so
it can be broken again repeatedly without reselecting it. The second
part is created as a new entity at the end of the database.

[^90] [^91] [^92]

Deleting entity (shortcut \<Del\> key)

An EDIT menu option to delete the selected entity

[^93] [^94] [^95]

Undelete entity (no shortcut)

This EDIT menu item is used to recover entities that have been
inadvertently deleted. It must be used in conjunction with an option
under the DISPLAY menu to display deleted entitiesshowd. When an entity
is deleted, it is not removed from the database, but an attribute is
changed so that the entity normally does not plot. If the DISPLAY menu
option to display deleted entitiesshowd is checked, that attribute is
ignored and the deleted entities are plotted in light gray. When the
deleted entities are visible they can be selected graphically and
restored with the undelete option. No other editing operations can be
done on the entity until it has been undeleted.

A simpler way to recover an entity immediately after it has been deleted
is to use the Undoundo command.

[^96] [^97] [^98]

Move entity‑‑‑ (shortcut \<V\>)

The selected entity will be moved. Two points must be set. The fist
point is called a handle, and the second point indicates the new
location of the handle. All points in the entity will be moved a
distance and direction equal to the offset between the handle point and
its new location.

[^99] [^100] [^101]

Copy entity‑‑ (shortcut \<C\>)

Similar to the move entityedmove command except that selected entity
remains in its original position and a new identical entity is created
in the new location. Two points must be set. The fist point is called a
handle, and the second point indicates the new location of the handle.
All points in the copy entity will be offset from the corresponding
points in the selected entity a distance and direction equal to the
offset between the handle point and its new location.

[^102] [^103] [^104]

Drag‑move entity‑‑‑ (shortcut \<G\>)

An EDIT menu option that is similar to the move entityedmove command.
Two points must be set, and every point in the selected entity is moved
an amount equal to the displacement between the two points. In drag mode
a highlighted shadow of the selected entity visibly moves along with the
mouse pointer until the second point is set.

[^105] [^106] [^107]

Drag copy entity‑‑‑ (shortcut \<Y\>)

An EDIT menu option that is similar to the copy entityedcopy command.
Two points must be set, and a copy of the selected entity is created
displaced from the selected entity by an amount equal to the
displacement between the two points. In drag mode a highlighted shadow
of the selected entity visibly moves along with the mouse pointer until
the second point is set.

[^108] [^109] [^110]

Reverse the direction of line

An EDIT menu option used on decorated lines to control the side of the
line on which the decorations are plotted. Decorations are normally
plotted on the right side of the line in the direction that the line was
digitized. If the line was digitized in he wrong direction, it can be
corrected by using the reverse option.

[^111] [^112] [^113]

Move a single point in an entity (shortcut \<M\>)

One point in the selected entity can be moved. Two points must be set.
The first point indicates the point to be moved. A cross appears on the
selected point, the number of the selected point appears at the bottom
left of the screen, and the confirmation menu appears at the top left.
While the confirmation menu is visible, pressing the letter \<A\>
advances the cross forward to the next point, the letter \<B\> moves it
back to the last point. The letter \<C\> confirms that the correct point
has been selected, or the letter \<E\> aborts the whole process, and the
confirmation menu disappears. If an entity point has been confirmed, a
second point must be set and the entity point is moved to the location
of the second set point.

[^114] [^115] [^116]

Add points to an entity (shortcut \<A\>)

A line that has an angular appearance because it was digitized with too
few points can be improved by adding intermediate points. The user sets
successive points near the selected line. If the point can be projected
onto the line, the set point will be inserted into the line, adding an
additional line segment and more curvature. The line is redrawn through
the new point and the user can continue to set points. The confirmation
menu is visible, and the user ends the edit by either confirming the
changes \<C\> or escaping \<E\> and abandoning the changes. Even after
the change has been confirmed, the user can return to the original line
by using the Undoundo option.

[^117] [^118] [^119]

Delete points from an entity (shortcut \<T\>)

An EDIT menu option allows erroneous points to be removed from selected
entities. The point is identified by pointing with the mouse and using
the confirmation menu as described for moving a pointedmove.

[^120] [^121] [^122]

Move Node (shortcut \<N\>)

A nodenodehelp is an endpoint of at least one line, and is commonly an
endpoint shared by several lines. When a node is moved, the endpoints of
all the attached lines also move and the appearance of the lines is
changed. The move node option is separated from the rest of the edit
menu because it does not operate on a selected entity. The node is
identified by setting a point with the mouse within the edit distance
(one percent of screen width) of the desired node. The selected node is
highlighted with a green circle if more than one line is attached and
with a green square if only one line is attached (hanging node). The
user must then set a point with the mouse or digitizer to indicate the
new position for the node.

[^123] [^124] [^125]

Set snap distance

A nodenodehelp created or moved to within snap distance of an older node
will be automatically moved to the position of the older node. This
process facilitates digitizing lines that will be used to construct
closed polygons by eliminating invisibly small gaps between lines that
need to be connected. The default value is 0.02 inches, but can be
changed using this EDIT menu option. If the value is set too high,
undesired connections will be made and narrow units may be choked off. A
preferable method for assuring connections is the use the gravity option
(see digitizing menu) when digitizing to assure that beginning and
ending points of lines are set exactly on the ends of the adjacent line.

[^126] [^127] [^128]

Registering a drawing on a digitizer tablet

When a digitizing tablet is to be used as the pointing device for
editing or drawing new entries, the map on the tablet must first be
registered to the database by selecting this EDIT menu choice. The user
may elect to use the four database corners as registration tics
(default) or may type in coordinates for four alternate points, in
counterclockwise order from the upper left. A zero must be pressed on
the digitizer puck keypad to synchronize tablet output with the program
and establish the tablet is properly connected and configured. If
everything is in order a beep is produced and the user is prompted to
place the puck crosshairs on each of the registration points and press
the zero key. After the last point, the program calculates the rotation
of the map on the tablet, the offset from the lower left corner of the
tablet, the x scale, the y scale, and some other parameters to determine
the probable accuracy of the registration. These are reported in a
window, and a warning is given if the x scale and y scale differ by more
than 2 percent. The user must then accept or reject the registration.
The registration remains in effect until another database is opened, the
digitizer registration menu item is selected again, or the program ends.
If the map is moved for some reason, it is vital that it be
reregistered.

[^129] [^130] [^131]

Setting up a digitizing tablet

Setting up a digitizing tablet to communicate properly with GSMCAD is
simple in theory, but can be difficult because of many variable factors
that are unfamiliar to most program users. First the digitizer itself
must be configured using banks of dip switches, soft switches on the
face of the tablet, or software commands that control the serial
communications parameters, the frequency of data transmission, and the
data format. To understand these it is essential to refer to the
documentation supplied with the digitizer. Second a file called
CONFIG9.DIG must be edited to inform GSMCAD of the switch settings and
characteristics of the digitizer.

The CONFIG9.DIG file supplied with the installation disk corresponds to
some of the most common default digitizer tablet settings, so in some
rare cases a tablet will work immediately without any modifications. If
modifications are necessary, the critical information needed about the
digitizer settings includes the following: The number of the serial port
to which the digitizer is connected (usually COM1 or COM2); the baud
rate (9600 recommended), parity (N recommended), databits (8 or 7), and
stop bits (usually 1); the mode (run recommended for binary and line
incremental for ASCII); resolution ( .001 in recommended); and format
(GTCO high resolution binary recommended, summagraphics and various
ASCII formats acceptable); the number of keys onthe keypad and the ASCII
characters transmitted when digitizer keypad buttons are pressed (only
needed for ASCII formats).

If a digitizing tablet is set up properly to work with GSMAP, it will
also work with GSMCAD. GSMCAD also offers additional capabilities that
require modifications which are incompatible with GSMAP. GSMAP only
supports ASCII data transmission in point or line incremental mode.
GSMCAD supports stream-mode (continuous) transmission of coordinates
when coupled with binary rather than ASCII data format. The advantages
are that a cursor on the screen can follow the movement of the puck
across the digitizer tablet so the relation between the map on the
screen and the map on the tablet is always obvious, and also that the
experienced digitizer can choose to digitize some lines by tracing
without having to repeatedly press the \<0\> key for each
pointdigkeypad.

The only two binary modes that are supported are GTCO high resolution
binary (6 bytes) (use KEYPADB for 16 button or MENUB for 4 or 1 button
as the second line of the CONFIG9.DIG file) and summagraphics MM (5
byte) (use SUMMA4 as the second line of the CONFIG9.DIG file). SUMMA4
assumes 4 buttons and thus a menu templet. You either must be able to
set those format modes on your digitizer or work in ascii mode.

GSMCAD works most conveniently with digitizers that have a
sixteen-button cursor keypad that transmits a code indicating which key
was depressed in addition to the X,Y coordinate location of the cursor
on the digitizer. Certain keys are used at critical times to communicate
the user\'s desires. For example during entry of a numeric value the A
key indicates end of field. If the digitizer puck has only four keys,
than those keys must be mapped in the CONFIG9.DIG file to the most
important of the sixteen keys by placing the most important numbers or
letters right of the comma in the first four rows of the key mapping
part of the CONFIG9.DIG file. The other digitizing functions must be
invoked from the keyboard, by using mouse and screen menus, or by using
the digitizer puck to point to a 16-cell virtual keypad (4x4 paper grid)
taped to the digitizer tablet.

Various brands of digitizers with sixteen-button cursors vary in the
code transmitted by each key when in ASCII mode. This is a common cause
of problems and confusion. GTCO and some other digitizers do not
transmit the same character that is printed on the key, so key mapping
in the CONFIG9.DIG file is necessary. The numbers and characters left of
the comma should correspond to to the ascii code sent by the digitizer,
which can be determined from the digitizer documentation or by
experimentation. Those right of the comma correspond to the numbers and
letters that actually appear on the keys of a 16 button keypad and the
ascii codes expected by the program. For digitizers set to binary mode
the characters left of the comma are place holders without significance
since the key number is transmitted rather than a character.

If the digitizer does not seem to be responding properly, a useful
troubleshooting tool is the digitizer stream display option under the
HELP menu. When toggled on this option prints the raw data from the
digitizer on the bottom of the screen. If no data is being received it
prints NO DATA. If the CONFIG9.DIG specifies binary data then the ASCII
number corresponding to each byte received is displayed, and the byte
thought to represent the key press is preceeded by a {. If a key is
pressed, the keypress and coordinate pair as interpreted by GSMCAD are
printed at the bottom of the screen after a pause. This is most useful
at the first stages of attempting to register a map on the digitizer
tablet at the time of the prompt \"PRESS ZERO TO SYNCHRONIZE
DIGITIZER\". By pressing all the characters on the keypad except zero
and noting what is displayed, the user can discover what each key
actually transmits and how that is being transmitted.

If ascii mode is used, the user must discover the format of the
information contained within the ASCII string that is transmitted when a
key is de­pressed on the digitizer. The character(s) transmitted to
iden­tify each key uniquely and the starting position and width of the X
and Y coordinates within the string must be known. After information
about the coordinate format is gathered, it must be typed in and saved
in a file called CONFIG9.DIG so that GSMAP can communicate with the
digitizer and translate the information properly.

STRUCTURE OF THE CONFIG9.DIG FILE

First line

This line contains the communications parameters definition. This
information is enclosed by a set of double quotes (\"). The program uses
this string to establish communication between the serial port of the
computer and the digitizer. The following example assumes that the
digitizer has been attached to the computer by a cable plugged into
serial port #1 on the computer and that the digitizer has been
initialized (via switches or software) to transmit at a rate of 9600
baud (bits per second), no parity, eight bits per character, and 1 stop
bit per character.

\"COM1: 9600,N, 8, 1\"

\"KEYPAD\"

1,1

2, 5, .001

8, 5, .001

16

0,0

1,1

2,2

3,3

4,4

5,5

6,6

7,7

8,8

9,9

:,A

;,B

\<,C

=,D

\>,E

?,F

The second line conveys information about the digitizer keypad and mode
of data transmission. Options presently supported are listed below:

KEYPAD Keypad present, ascii format, point or continuous incremental
mode (standard GSMAP setup)

KEYPADB Keypad present, GTCO high resolution binary format, continuous
(stream) mode

MENU No keypad (or less than 16-button), ascii format, point or
continuous-incremental mode

MENUB No keypad (or less than 16-button), GTCO binary format, continuous
(stream) mode

SUMMA4 Four-button keypad, Summagraphic MM binary format, stream mode

Only GTCO and Summagraphics binary formats are presently supported, but
many newer digitizers will emulate the GTCO format. The Calcomp 9500
recognizes it as format 23 (also known as 9500 Format \# 5), which can
be set by soft switches in the format area in the lower left of the
digitizing tablet (on off on on on). On the Calcomp 9500 stream mode is
called \<RUN\> mode and is selected by setting the soft switches in the
mode area to off on off off off.

Lines 3 to 5 must be included, but are used primarily for ascii format
setup. In ascii format the digitizer transmits a text string that must
be subdivided to extract the coordinates and the key pressed. The third
line indicate the number of letter spaces from the left where the
keypress information starts, and how many letters long that piece of
information is. Lines 4 and 5 indicate the same information about the X
coordinate and Y coordinate respectively. The third entry on lines 4 and
5 indicate the resolution of the digitizer in inches (1000 lines per
inch = 0.001, 500 lpi = 0.002).

The sixth line indicates that all sixteen keys on the keypad are to be
translated using the sixteen lines that follow. The following sixteen
lines contain the ASCII code that is transmitted when a key is depressed
(determined by the digitizing tablet) followed by the ASCII code to
which it should be translated by GSMCAD. Example - a GTCO has a keypad
labeled with keys numbered 0 to 9 and A to F. However, when the F key is
depressed, ASCII code 063 (which prints as \<?\>) is transmitted. The
translation table indicated to GSMAP that when a ? is re­ceived in the
first character of the transmitted string it should be translated to F.

The remaining lines of the CONFIG9.DIG file are used by GSMAP but not by
GSMCAD.

[^132] [^133] [^134]

Editing entities from a digitizer tablet

This option is enabled only after the digitizer is registered. After
this option is selected, the digitizer tablet can be used as a pointing
device for editing. Menu choices corresponding to keys on the digitizer
puck keyboard appear across the bottom of the screen. These relate
digitizer key to many of the edit menu choices described above, so that
editing can be done from the digitizer without having to return to the
computer keyboard. The keyboard and mouse continue to function, however.

There are two menus as follows:

First digitizer menu:

0 = Select an entity to edit. Corresponds to the Select option on the
edit menu.

1 = Edit the entity. Accept the selected entity and change to the second
menu that lists edit options.

2 = Continue search. Reject the selection and look for another entity
within edit distance of the original point. Corresponds to the Continue
option on the edit menu.

B = Window. Define a new screen window by setting points on two opposite
corners on the digitizer tablet.

D = Add entities. Activates the DIGITIZE choice on the menu bar and
enters the mode for digitizing new entries

E = Move nodenodehelp. Corresponds to the Move node option on the edit
menu.

F = Exit editing from the digitizer. Deactivates the digitizer, although
registration is maintained.

Second digitizer menu:

5 = Redraw the screen

9 = Delete a point from the selected entity

A = Add points to the selected entity

B = Break. Break a line into two parts.

C = Change CODE, P1, or P2 of the selected entity

D = Delete

E = Move a point in the selected entity

F = Exit the second menu and return to the first digitizer menu.

[^135] [^136] [^137]

Editing a block of entities

Block operations are used for certain types of editing on groups of
entities that are selected graphically. The various methods of selection
act as a toggle. An entity that is not part of the block will be added
to the block when selected under the block method. If the entity is
already part of the block, however, it will be removed from the block.

Select a group of entities for the block listedselblock

Add or remove single entities from the block listblkadd

Remove all entities from the block listblkempty

Move all the entities in the blocklistblkmove

Copy all the entities in the blocklistblkcopy

Change the attributes of all the entities in the blocklistblkchange

Delete all the entities in the blocklisteddelblk

[^138] [^139] [^140]

Selecting a group of entities for the block list

By holding down the mouse button while moving the mouse the user draws a
temporary rectangle on the screen. All entities that fall entirely
within the rectangle are added to the block list and will be highlighted
in green

[^141] [^142] [^143]

Add or remove single entities from the block list (shortcut Ctrl +)

Allows individual entities to be added to or subtracted from the block
list by pointing at them with the mouse

[^144] [^145] [^146]

Remove all entities from the block list (shortcut Ctrl ‑)

Removes all the entities from the block list. The entities are not
affected, but the length of the list is set to zero so that previously
listed entities will not be affected by future block edits.

[^147] [^148] [^149]

Moving all entities in the block list

Similar to the move entityedmove command under the edit menu except that
all the entities in the block are moved in exactly the same way,
maintaining the same relation to each other. Requires two points to be
set. First is the base point and the second the destination.

[^150] [^151] [^152]

Copying all entities in the block list

Similar to the copy entityedcopy command under the edit menu except that
all the entities in the block are moved in exactly the same way,
maintaining the same relation to each other. Requires two points to be
set. First is the base point and the second the destination of the copy.

[^153] [^154] [^155]

Changing attributes of all entities in the block list

Similar to the change entitychange command under the edit menu except
that all the entities in the block are changed in exactly the same way.
The user must choose whether to change CODE, P1, or P2 for all the
entities in the block. Only one attribute can be changed at a time.

[^156] [^157] [^158]

Delete all the entities in the block list

Deletes all the entities in the block list

[^159] [^160] [^161]

Drawing new entities in the database

Selecting the digitize option deactivates the regular menu bar and
substitutes a menu of digitizing sub options. Points can be entered by
pointing on the screen with a mouse, by moving the cursor with keyboard
arrow keys, by typing coordinates from the keyboard, and by pointing at
a map mounted on a digitizing tablet.

Assign attributes (CODE, P1, P2) for entities to be createddigmnu0

Complete point entry for new entitydigmnu1

Complete point entry for new entity and close polygondigmnu2

Close part of a polygon but leave entry open for more pointsdigmnu3

Draw special shapesdigmnu4

Enter point coordinates from the keyboarddigmnu5

Abandon entry of points for a new entitydigmnu6

Switch from digitizing to editingdigmnu7

Digitizing tablet keypad menudigkeypad

[^162] [^163] [^164]

Assign attributes (CODE, P1, P2) for entities to be created

The attributes (CODE, P1, P2) of new entities must be defined before
they can be added to a database. Initially these will be set to 1, 0, 0
respectively, but can be changed from the digitizer puck or by selecting
the New Code menu.

A pull down list box appears near the upper left corner of the screen.
It either shows the last code selected, or says \"SELECT NEW CODE\". To
the right of the text are a down arrow and an OK button. If the user
clicks on the down arrow, a list of all the codes defined in the plot
files appears with a comment about what the code represents (contact,
fault, dip symbol, etc.). The user can change the choice in the box by
clicking on something from the list or by typing a choice into the box.
Clicking on the OK button accepts the choice and leads to input boxes
prompting for the appropriate P1 and P2 codes, depending on what type of
code was chosen. The choices will remain in effect until changed even
after leaving digitizing and returning. Changing attributes with the
digitizer keypad is different and is described below.

Codes for text (500-599, 700-799) offer special options for entering the
P1 value. The P1 value for text codes is normally a number corresponding
to a text entry in an ASCII text file that is named in the plot file.
For text codes the P1 input box will also accept direct entry of the
text, and add the text to the ASCII file. This requires that the text
begins with a letter rather than a number. Otherwise enter a zero for
the P1 value, and a box will open to accept any type of text.

[^165] [^166] [^167]

Complete point entry for new entity

(short cut - hold down the shift key while setting the last point) (=
digitizer key 1)

The DONE option closes the entry after all points have been digitized.

[^168] [^169] [^170]

Complete point entry and close polygon (= digitizer key 2)

The CLOSE-END option closes the entry and connects the last point of a
line to the first point to close a polygon.

[^171] [^172] [^173]

Close part of a polygon but leave entry open for more points (=
digitizer key 3)

The close poly option connects the last point of a line to the first
point of the current polygon segment to close one part of a polygon
without closing the entry. This is used when digitizing a polygon that
includes internal areas of exclusion.

[^174] [^175] [^176]

Draw special shapes

The shapes option opens a pop up menu that offers choices to draw
various special shapes. Shapes include a rectangle, circle, standard
size box and standard size bracket for correlation of map units diagram,
and text centered between two points.

[^177] [^178] [^179]

Enter point coordinates from the keyboard

Opens a input box so that a point can be digitized by typing in exact
coordinates rather than pointing with the mouse or digitizer puck.

[^180] [^181] [^182]

Abandon entry of points for a new entity (= digitizer key E)

Clears the buffer of points for an uncompleted entry. Provides a way to
abandon mistakes.

[^183] [^184] [^185]

Quit digitizing and return to editing (= digitizer key F)

Closes the digitize menu bar and returns to the normal menu.

[^186] [^187] [^188]

KEYPAD MENU FOR DIGITIZING

0 = Set a point. Corresponds to the left mouse button or the \<Ins\> key

1 = Set a point and end an entry. Corresponds to shift key plus left
mouse button

2 = Set a point, append a copy of the first point of the present polygon
segment, and end the entry

3 = Set a point, append a copy of the first point of the present polygon
segment, but do not end the entry (for polygons with internal
exclusions)

4 = Set a point on top of the nearest preexisting point (can also be
done with the period \<.\> key on the keyboard, or the right mouse
button

5 = Set a point on top of the nearest preexisting point and end the
entry (can also be done with the shift key plus the right mouse button

8 = Begin continuous point collection. This is equivalent to holding
down the zero key. Should only be used when digitizing long lines. If
the puck is moved more than a certain critical distance, a point is
added to the line being digitized. Remains in effect until any other key
is pressed. Only functional with digitizer set to GTCO continuous binary
mode, which is not compatible with standard GSMAP.

A = Enter. Functions like the enter key to signify the end of a number
input from the keypad. Only used when changing Code, P1, or P2 after
pressing \<D\> as described below. Pressing \<A\> without preceeding
numbers will transmit a zero value.

B = Window. Redefine the area shown in the screen window by setting two
points on opposite corners of a rectangle.

C = Pan center. Move the screen window by setting one point at the new
screen center.

D = Change the CODE, P1, or P2 to be used for adding new entries. The
program will prompt to type in new values from the key pad. If the new
values do not fill the data field, then the entry must be ended with the
\<A\> key. If the user wants to retain the previous value of one of the
attributes, press the \<D\> key again instead of typing in an entry. If
a mistaken number has been entered, press the \<E\> key to reenter.

E = Error. Aborts the entry in progress and clears the buffer of points.
Provides a way to abandon mistakes.

F = Exit digitizing mode and return to editing mode.

[^189] [^190] [^191]

SCREEN DISPLAY OPTIONS

Several options affecting the way data, information, and editing tools
are displayed. Check marks appear next to an option when it is toggled
on.

Redrawing the screenredraw

Toggle cursor position box between database coordinates and page
coordinatesdispaper

Measure bearing and distance from a pointshowbd

Toggle the cursor display between a cross and crosshairsshowhair

Showing nodesshown

Showing entry pointsshowv

Displaying deleted entitiesshowd

Displaying a reference gridshowg Setting the spacing for the reference
gridshowgsp

Displaying a background databaseshowb

Displaying data from a GSPOST ascii tableshowpost

Displaying map unit areas in colorshowcolor

[^192] [^193] [^194]

Redrawing the screen (shortcut \<R\>)

Erases the screen and replots the drawing. Used when part of the plot
has been erased or obscured.

[^195] [^196] [^197]

Display cursor position in page coordinates

The coordinates of the mouse cursor position are normally displayed in
text boxes in the upper left corner of the screen. The default display
is in database units (latitude and longitude for a
[geodetic]{.underline}geodeticdef database), but can be toggled to show
distance in inches up and right from the lower left corner of the
drawing as defined in the plot file.

[^198] [^199] [^200]

Measure bearing and distance from a point

This option facilitates making measurements on the screen plot. After
this option is toggled on, one base point must be set at a point of
interest. A moving rubber band line then appears connecting the mouse
cursor to the basepoint. The length and bearing of this line is
displayed in the lower left corner of the screen. Distance is displayed
in kilometers, miles, and plot inches if the database is
[geodetic]{.underline}geodeticdef; and database units and plot inches if
the database is [cartesian]{.underline}geodeticdef.

[^201] [^202] [^203]

Changing the cursor display to a crosshair

When the \<crosshair\> option is toggled one the mouse cursor is
suppemented with horizontal and vertical moving lines that extend across
the height and width of the screen.

[^204] [^205] [^206]

Showing nodes

A nodenodehelp is an endpoint of at least one line, and is commonly an
endpoint shared by several lines. When node display is toggled on, nodes
shared by two or more lines are shown as small black circles with
crosses. Hanging nodes associated with only one line are shown as small
red boxes. This display is an aid in correcting topology so that
polygons may be constructed. Lines that can be properly connected to
form a polygon (for producing colored maps) do not have any hanging
nodes.

[^207] [^208] [^209]

Displaying entity points

A display menu option causes the location of each digitized point in
every entity to be shown as a small circle. The screen is not
immediately changed, but the change takes effect the next time the
screen is redrawn

[^210] [^211] [^212]

Displaying deleted entities

This display, used in connection with the undeleteedundel command
described under the EDIT menu, aids in the recovering important entities
that have been inadvertently deleted. Deleted entities that remain in
the database are shown in light gray, and can be selected using the
select option from the edit menu when the deleted entities display is
toggled on. Once selected, they can be undeleted.

[^213] [^214] [^215]

Display entities that are not described in the plot file

Entity types that exist in the database but that are not mentioned in
the plot file will be shown in yellow when this toggle is on. This
facilitates editing and correction of the plot file, and is on by
default. For final hardcopy plots, it should be toggled off.

[^216] [^217] [^218]

Displaying a reference grid

Displays a reference grid over the drawing in light gray. The spacing of
the grid for a [geodetic]{.underline}geodeticdef database is 7.5 minutes
and 10 database units for a [cartesian]{.underline}geodeticdef database
if not changed by using the grid spacing optionshowgsp in the DISPLAY
menu. This grid is not part of the database, but will be plotted if it
is turned on during outputoutputm operations.

[^219] [^220] [^221]

Showing a background database

This option toggles display of a second database as a backdrop for the
database being edited, as described under the option to open a
background databasefopenback in the FILE menu.

[^222] [^223] [^224]

Displaying data from a GSPOST ascii table

Symbols and labels representing observation points can be plotted in the
drawing from a tabular text file if the table is prepared in GSPOST
format and the GSPOST data option is selected. The parameters for
plotting must be added to the plot file using the format for a 100
series code, and the user is queried for the unique 100 series code to
associate with the GSPOST table. The program handles the code like any
other 100 series code, except that the coordinates are read from the
GSPOST table rather than from the GSMAP database. This allows tables of
laboratory data or positions downloaded from global positioning
satellite systems to be easily and temporarily added to the map plot.

[^225] [^226] [^227]

Displaying map unit areas in color

If the color map option under the DISPLAY menu is toggled on, the
program has the potential to fill the tagged areas between contacts with
colors distinctive to each unit. This affects only the screen display
and not printer or plotter output. Pressing \<ALT\> and the Prt Scr key,
however, will capture the colored screen image to the clipboard, from
where it may be pasted into a paint program for hardcopy output.

For the screen coloring function to work correctly the plot file (.PLT)
must identify which lines are contacts and which 500 code (text) points
serve as polygon label points. This information is read off the comment
entry for each code in the plot file. If the comment for a line code (1
to 99) includes the word \"contact\", all lines of that code will serve
to divide the colored areas. If the comment for a text code (500 to 599)
includes the word \"tag\", some points from entities of that code will
serve as source points from which a color distinctive to the P1
attribute will spread. If the tag entity has only one point, color will
spread from that point. If it has several points (a label with leaders)
color will spread from the far end of each leader. The use of the
comment is identical to the format used when exporting to ARC/INFO, so a
plot files properly formated for export to ARC/INFO will automatically
color on screen.

The primary function of this option is to check for unlabeled polygons
and leaks (polygons that are not properly closed), but false errors
occur. If the tag point for an area is outside the screen window, that
part of the area in the screen window will not color, although the area
is properly tagged. Also constrictions may stop the flow of color if the
area is less than one pixil wide at screen scale. The program assigns
colors to units arbitrarily according to the P1 value, and there is no
option to control the colors.

[^228] [^229] [^230]

Setting the spacing for a reference grid

Selecting this option allows the user to customize the spacing of the
temporary grid that can be displayed using the display grid optionshowg
in the DISPLAY menu.

[^231] [^232] [^233]

ZOOMING THE SCREEN WINDOW

This menu offers options to control which area of the drawing is shown
on the screen.

Defining a screen window using a mousezoomw

Changing the size of the screen window by a factorout

Returning to the previous screen windowzprev

Setting the screen window to the plot file or database cornerszoomdb

Setting the screen window to show all entities in the databaseall

Changing the zoom factorzooms

[^234] [^235] [^236]

Defining a screen window using a mouse (shortcut W)

The user defines a rectangular area on the screen that is then enlarged
to fill the entire screen so that critical details may be easily seen.
The area is defined by depressing the mouse button when the cursor is on
one corner of the area and releasing it when the cursor is on the
opposite corner. A moving box representing the area to be enlarged is
shown on the screen while the mouse is moving with the button is
depressed. All of the area within the box will be on the screen after
enlargement, and additional area may be shown to fill the screen. This
function will work with the shortcut key even when the main menu is
hidden during digitizing, but will not work while an entry is partially
digitized.

[^237] [^238] [^239]

Changing the size of the screen window by a factor (shortcut \<Ctrl O\>)

A zoom menu choice changes the dimensions of the screen window by the
zoom factor (set by the change zoom factor optionzooms). The coordinates
of the screen center remain unchanged. A zoom factor greater than one
results in a zoom out, less than one zooms in.

[^240] [^241] [^242]

Returning to the previous screen window (shortcut \<Ctrl P\>)

Regenerates the previous screen window.

[^243] [^244] [^245]

Setting the screen window to the plot file or database corners

Generates a window large enough to show everything within the area
defined by the plot file, which commonly corresponds to the database
corners.

[^246] [^247] [^248]

Setting the screen window to show all entities in the database

Generates a window large enough to show every entity in the database,
even those that lie outside the plot corners and the database corners.

[^249] [^250] [^251]

Changing the zoom factor

Changes the factor for enlarging or reducing the size of the screen
window, and zooms the screen using the new factor. A zoom factor greater
than one results in a zoom out, less than one zooms in.

[^252] [^253] [^254]

PANNING THE SCREEN WINDOW

A selection of options that affect the location of the screen window but
not its size. This menu is seldom used because the choices are more
conveniently implemented using the shortcut keys, which are the
combination of the \<Ctrl\> key with keys on the numeric keypad or the
arrow keys. In most cases the screen window is moved vertically,
horizontally, or both so as to overlap the previous window by about 15
percent. In this way the entire database can be systematically reviewed
at appropriate magnification. Pan center (\<Ctrl\>\<5\> on the numeric
pad) is an exception in that the new window is generated centered on a
point set by the user to allow focus on particular problems.

[^255] [^256] [^257]

EDITING THE DATA BASE

The database menu provides information and options that concern the
entire database more than individual entities. The information is
provided in tabular rather than graphic format.

Displaying general information about the open data basedbinform

Listing the contents of the databasedblist

Global change of entity attributesglobal

Changing database cornersdbnewcorner

[^258] [^259] [^260]

Displaying general information about the open database

The DATABASE \<info\> item opens a message box that lists the name,
title, and corners of the database, when the file was last edited, the
scale, number of entities, whether it is
[geodetic]{.underline}geodeticdef or [cartesian]{.underline}geodeticdef,
and the current projection if the database is geodetic.

[^261] [^262] [^263]

Listing the contents of a database

The DATABASE menu \<list\> item opens a spreadsheet form that has
columns listing the entity number, CODE, P1, P2, number of points, and
coordinates of the first and last points for each entity. Deleted
entities also appear, and can be distinguished by an asterisk next to
their entity number. The user can choose to list all entities, or only
those with a certain code. As many as one hundred entities at a time are
loaded into the spreadsheet, although fewer appear on the screen. The
others can be examined by using the scroll bar on the right hand side.
To see another page of one hundred, the user must click on the \<more\>
button.

CODE, P1, or P2 of an entity or range of entities can be edited by
highlighting the appropriate cells then typing a new value into a text
box at the top of the form. A single entity can also be changed by
highlighting the entity number and clicking on the \<change entity\>
button. This method provides the user with guidance on the meaning of
the different parameters. Entities can be deleted or undeleted by
highlighting an entity number or a range of entity numbers, then
clicking on the \<toggle delete\> button. The first of the entities that
are highlighted when the spread sheet is closed will also be highlighted
and selected on the graphical screen if it lies within the current
screen window. This enables the user to easily locate on the map an
entity that has been identified in the spreadsheet.

[^264] [^265] [^266]

Global change of entity attributes

Parameters of all entities of a particular code in the data base can be
changed at once. The entities can also be deleted or undeleted in mass.
A sub menu displays the possible types of changes (CODE, P1, P2, delete,
undelete). After one is selected, the user indicates the code which is
to be changed, and, if appropriate, the new value for the selected
attribute. Note that a global delete is not strictly reversable because
global undelete will apply to entities that have been deleted throughout
the life of the database, and will commonly produce undesirable results.

[^267] [^268] [^269]

Change database corners

Any one of the four database corners, which serve as registration
points, can be changed by either typing in a new coordinate or
digitizing a point on the drawing.

[^270] [^271] [^272]

Using the confirmation menu

For some operations the user must confirm a selection or result before
the change is written into the database. It may also be necessary to
step from one entity point to another in order to select the exact point
to be modified. On such occassions a special menu appears across the top
of the screen offering options to \<confirm\> or \<escape\> and, when
appropriate, to \<advance\> to the next entity point or go \<back\> to
the previous point. These options can be activated by shortcut keys
without pressing \<ALT\>. While the confirmation menu is visible,
pressing the letter \<A\> advances the selection cross forward to the
next point, the letter \<B\> moves it back to the last point. The point
number appears at the bottom of the screen. The letter \<C\> confirms
that the correct point has been selected, or the letter \<E\> aborts the
whole process, and the confirmation menu disappears.

[^273] [^274] [^275]

List of shortcut keys

Shortcut keys invoke certain commands with a single keystroke, even when
the menu listing of the command is not visible. Use of shortcut keys for
commands while using the mouse only for pointing can greatly speed
editing. Editing function shortcut keys only work when the EDIT menu is
visible, and the confirmation command shortcut keys (Confirm, Escape,
Advance, Back) only work when the confirmation menu is displayed.

A = Add points to an entity

B = Break a line into two parts

C = Copy an entity

G = Drag move an entity

H = Change attributes of an entity

M = Move a single point in an entity

N = Move a nodenodehelp

P = Set a point

R = Redraw the screen

S = Select an entity

T = Delete points from an entity

U = Continue search to select an entity

V = Move an entity

W = Define a screen window by drawing a rectangle with the mouse

Y = Drag copy an entity

, = move the cursor to the nearest point

. = Set a point on the nearest point

Ins = Set a point

Del = Delete an entity

\+ = increase the cursor grid spacing by an order of magnitude

\- = decrease the cursor grid spacing by an order of magnitude

Arrow keys = move the cursor one grid space on a grid

Shift arrow keys = move the cursor one grid space, but not on a grid

Ctrl arrow = Pan the screen window in the direction of the arrow

Ctrl 5 = Pan the screen window to center on a digitized point

Ctrl + = Add or remove single entities from the block list

Ctrl - = Empty the block list

Ctrl O = Zoom out by a factor

Ctrl P = Zoom back to the previous window

F1 = Help

F12 = Open a new databse

The confirmation command shortcut keys below only work when the
confirmation menu is displayed.

A = Advance to the next point in an entity

B = Move back to the previous point in an entity

C = Confirm a choice

E = Escape without making a choice (abort)

[^276] [^277] [^278]

Map projections and projection files

GSMAP can use either Cartesian data (X, Y coordinates) or geodetic data
(latitude, longitude coordinates). The choice of coordinate system is
made by the user. Cartesian coordinates are most useful for
illustrations, cross sections, and maps where latitude, longitude
coordinates are unavailable, where the use of a geodetic system adds
unneeded complexity, or where it lacks sufficient precision (e.g. a map
at a scale of 1 inch equals 1 foot). Geodetic coordinates are used for
larger areas where the curvature of the earth\'s surface prevents
accurate represention using planar geometry.

Plotting of geodetic coordinates on a planar surface such as a sheet of
paper or a computer screen require that the coordinates be
systematically transformed according to a set of mathmatical equations.
The systematic representation of all (or a portion) of an ellipsoid on a
plane is called a map projection. Many types of projections have been
developed, and the GSMAP system supports several of the most commonly
used standard projections.

The Earth is an ellisoid rotated about its shorter axis. The radius of
the Earth at the Equator is referred to as the equatorial radius; that
at the poles, as the polar radius. The origin of the latitude-longitude
coordinate system is the Equator and the Prime meridian (Greenwich).
GSMAP utilizes north latitudes and east longitudes as positive; west
longitudes and south latitudes are negative.

The user supplies GSMCAD information regarding the projec­tion to utilize
and the value of the required projection parame­ters in short ASCII text
files that have the extension \<.PRJ\>, and are called projection files.

Map projections supported by the GSMAP system

Mercator

Universal Transverse Mercator (UTM)

Transverse Mercator

Oblique Mercator

Lambert Confor­mal Conic

Albers Equal Area

Equidistant Conic

Polyconic map projections.

[Projection Files]{.underline}

Projection files are prepared by the user and supply infor­mation
regarding the projection to be used and the parameters that define the
projection. Example files are illustrated below for each of the
supported projections. Any valid DOS filename can be used for this file
but normally these files are given a DOS filename of the data base name
followed by the .PRJ exten­sion.

Map projections and USGS practice are described in a 1987 U.S.
Geological Survey Professional Paper by Snyder. Information on the map
projection is given in marginal notes on USGS maps, but the data on the
parallels and meridian used to prepare the map is not provided. The
summary below should help, but please read the original by Snyder
(1987). Unless otherwise stated on the map margin or in Snyder\'s
report, use the Clarke 1866 Ellipsoid.

Small-Scale Maps

Maps labeled Albers Equal-Area projection

When used for maps of the 48 conterminous states, the stan­dard parallels
are 29,30,0,N and 45,30,0,N. The central meridian is 96,0,0,W.

For maps of Alaska, the standard parallels are 55,0,0,N and 65,0,0,N.
The central meridian is 154,0,0,W.

For maps of Hawaii, the standard parallels are 8,0,0,N and 18,0,0,N. The
central meridian is 157,0,0,W.

Maps labeled Lambert Conformal Conic

The Lambert conformal conic is used by the USGS for a map of the US
showing all 50 states in true relative position. This map has been
issued at scales of 1:6,000,000 and 1:10,000,000. For this map the
standard parallels are 37,0,0,N and 65,0,0 N. The central meridian is
the line of longitude at the center of the sheet.

Maps labeled Transverse Mercator

In 1979 a spherical form of the Transverse Mercator was chosen for a
base map of North America at a scale of 1:5,000,000 for tectonic and
other geologic maps. The scale factor along the central meridian of
100,0,0,W longitude is reduced to 0.926, see projection parameter file
Example 7 below.

State-Scale Maps (1:500,000)

For the 500,000-scale base maps of the 48 contiguous states, the Lambert
projection was used. The standard meridian is the line of longitude
central to the map.

1 x 2 Degree Maps (1:250,000)

Maps labeled Transverse Mercator

Army Map Service (AMS) 1 degree by 2 degree sheets use the Transverse
Mercator projection. The principal meridian is the line of longitude
central to the map.

Maps labeled Universal Transverse Mercator (UTM)

The UTM projection will be used by the USGS for 1 x 2 degree sheets as
it updates the AMS series. The proper central meridian can be determined
either by using tables listing the central meridian for the UTM Zone or
by locating the nearest line of longitude of whole number of degrees
that is divisible by 3 but not by 2.

30\' x 60\' Maps (1:100,000)

For all new 30 minute by 60 minute quadrangles, the UTM projection is
used. The proper central meridian can be deter­mined either by using
tables listing the central meridian for the UTM Zone or by locating the
nearest line of longitude of whole number of degrees that is divisible
by 3 but not by 2.

15\' Quadrangles (1:62,500)

Maps labeled Polyconic

Many 15 minute quadrangle maps have been drawn using the Polyconic
projection. The central meridian is the line of longi­tude central to the
map.

7 1/2\' Quadrangles (1:24,000)

Maps labeled Polyconic

Many old 7 1/2 minute quadrangle maps were drawn using the Polyconic
projection. The central meridian is generally the line of longitude
central to the map.

Maps labeled Lambert or Transverse Mercator

Beginning in the late 1950\'s the USGS began using projec­tions that were
based on the parameters that serve as the basis of the State Plane
Coordinate system. Depending on the state, the projection will be
Lambert Conformal Conic, Transverse Merca­tor, or Oblique Mercator
(panhandle of Alaska only). USGS Bulletin 1532 (Snyder, 1982) presents
an excellent description of the basis of the SPCS and the projection
that is used for each State. This Bulletin also describes in Table 8 the
projection parameters that are used for each zone of each State. Table 8
lists a scale reduction for Transverse Mercator such as 1:2500. The
projection file requires a scale factor. The formula to compute scale
factor from scale reduction is scale factor = 1.0 - (1/scale reduction),
i.e. a 1:2500 scale reduction results in a scale factor of 0.9996 or
scale factor=1.0 -(1.0/2500)=0.9996. A useful approximation for
digitizing and plotting is to use the Polyconic Projection. The maximum
difference in the 700-800 mm diagonals of 7 1/2 or 15 minute quadrangles
between Transverse Mercator, Lambert, and Polyconic projections is about
0.05 mm. This is a much smaller figure than that expected due to size
changes related to changes in humidity for a paper copy. It is only
twice the accuracy attributed to a good digitizer.

Projections supported are:

Cylindrical:

Mercator, Transverse Mercator, Universal Transverse Merca­tor, Oblique
Mercator

Conic:

Polyconic, Lambert Conformal Conic, Albers Equal Area, Equidistant Conic

Examples of Projection Files

Latitude,Longitude values are entered in Degrees, Minutes, Seconds and
followed by the appropriate letter designating com­pass direction: for
example, W longitude, N latitude in the conterminous U.S. Equatorial and
polar radii are specified in kilometers.

Universal Transverse Mercator

File \| Description of Contents

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\|\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

1 \|\"1\" designates Universal Transverse Mercator

6378.2064 \| Equatorial radius, in km, Clarke 1866

6356.5838 \| Polar radius in km, Clarke 1866

105,0,0,W \| Longitude, Principal Meridian of UTM Zone

0.9996 \| Scale factor

Albers Equal Area

File \| Description of contents

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\|\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

2 \|\"2\" designates Albers Equal Area

6378.2064 \| Equatorial radius, in km, Clarke 1866

6356.5838 \| Polar radius in km, Clarke 1866

45,30,0,N \| Latitude, first standard parallel

29,30,0,N \| Latitude, second standard parallel

100,0,0,W \| Longitude, meridian central to map

Lambert Conformal Conic

File \| Description of contents

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\|\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

3 \|\"3\" designates Lambert Conformal Conic

6378.2064 \| Equatorial radius, in km, Clarke 1866

6356.5838 \| Polar radius in km, Clarke 1866

33,0,0,N \| Latitude, first standard parallel

45,0,0,N \| Latitude, second standard parallel

105,0,0,W \| Longitude, meridian central to map

Mercator

File \| Description of contents

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\|\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

4 \|\"4\" designates Mercator

6378.2064 \| Equatorial radius, in km, Clarke 1866

6356.5838 \| Polar radius in km, Clarke 1866

105,0,0,W \| Longitude, Meridian Central to map

Polyconic

File \| Description of contents

\_\_\_\_\_\_\_\_\_\_\_\_
\|\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

5 \|\"5\" designates Polyconic

6378.2064 \| Equatorial radius, in km, Clarke 1866

6356.5838 \| Polar radius in km, Clarke 1866

105,0,0,W \| Longitude, meridian central to map

Transverse Mercator

File \| Description of contents

\_\_\_\_\_\_\_\_\_\_\_\_
\|\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

6 \|\"6\" designates Transverse Mercator

6378.2064 \| Equatorial radius, in km, Clarke 1866

6356.5838 \| Polar radius in km, Clarke 1866

105,0,0,W \| Longitude, meridian central to map

0.9996 \| Scale factor

Parameters of special DNAG map for spherical Earth

File \| Description of contents

\_\_\_\_\_\_\_\_\_\_\_\_
\|\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

6 \|\"6\" designates Transverse Mercator

6371.204 \| Radius of Earth in km

6371.204 \| Radius of Earth in Km

100,0,0,W \| Longitude, meridian central to map

0.926 \| Scale factor unique to this map

Oblique Mercator Projection

File \| Contents

\_\_\_\_\_\_\_\_\_\_\_\_
\|\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

7 \|\"7\" designates Oblique Mercator

6378.2064 \| Equatorial radius, in km, Clarke 1866

6356.5838 \| Polar radius in km, Clarke 1866

1.0 \| Scale factor along central axis

42,0,0,N \| Latitude, center point of projection

73,0,0,W \| Longitude, center point of projection

51,30,0,N \| Latitude, S end of line defining axis

56,0,0,W \| Longitude, S end of line defining axis

33,30,0,N \| Latitude, N end of line defining axis

84,30,0,W \| Longitude, N end of line defining axis

The sample oblique mercator projection file provides parameters used in
generating the Appalachian Map

Equidistant Conic

File \| Description of contents

\_\_\_\_\_\_\_\_\_\_\_\_
\|\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

8 \|\"8\" designates Equidistant Conic

6378.38584 \| Radius of Earth in km

6356.910 \| Radius of Earth in Km

9,0,0,N \| Latitude, first standard parallel

4,0,0,N \| Latitude, second standard parallel

66,0,0,W \| Longitude, meridian central to map

Values in this example are for Venezuela maps labeled \"Proyeccion
Conico Secante Compensada.\" This projection is also used for certain
maps in Alaska labeled \"Modified Mercator\", see Snyder, (1982).

[^279] [^280] [^281]

Plotting lines, decorated lines, and splined lines (CODE GROUP 1-99)

Plot control instructions for a specific CODE require one (or two) sets
of parameters entered in the plot file.

The first set consists of five parameters separated by commas:
CODE,PEN,LINE PATTERN,DECORATING SYMBOL,COMMENT. e.g.
**12,5,0,0,\"CONTACT SOLID\"**.

Parameter 1: the CODE specified (1-99) as defined by the user and
specified for each entry during digitizing, then a comma (,)

Parameter 2: the pen number, a number from 1 to 255, or less, depending
on the capabilities of the plotting device followed by a comma (,). This
number may correspond to a pen in a plotter carousel, a screen color, or
a color from the palette of an inkjet plotter.

Parameter 3: the line type, a number 0-17, 98(see SPECIAL CASE 1), or 99
(see SPECIAL CASE 2), then a comma (,).

Parameter 4: **0** for all lines without decorations; for thrust faults
and other \"decorated\" lines the appropriate symbol number (from the
symbol sheet that can be printed from the help menu) should be entered.
The number must also be followed by a comma (,)

Parameter 5: A comment enclosed between quotation marks is an essential
part of the file to record the use of the code. A carriage return is
required at the end of this parameter.

Plots of decorated lines require a second row in the plot file to
specify two parame­ters, the spacing desired for the decorating symbols
and the pen to be used for the decorations (alternate pen). The size of
the decorating symbol will be the value of P2 for each entry unless the
value is 0 in which case a default value of 100 will be used. The first
symbol will be plotted at a distance of 1/2 the spacing distance,
subsequent symbols at spacings along the line equal to the spacing
interval. The symbol on a decorat­ed line will be rotated during plotting
to preserve a constant angular relationship between the symbol and the
line. If line pattern 99 was specified, no line will be plotted , but
this phantom trace can be decorated. To decorate a line with symbols at
digitized points, specify a [negative]{.underline} spacing value.

[^282] [^283] [^284]

Nodes

A node is an endpoint of at least one line, and is commonly an endpoint
shared by several lines. Nodes are important for making colored geologic
maps. A list of all the nodes in a drawing is used to connect individual
lines to form closed polygonal areas that can be filled with color or
patterns. A hanging or dangling node is one associated with only one
line. Contact lines intended to enclose a geologic unit to be colored
should not have any hanging nodes. Display of nodes can be toggled by
the \<show nodesshown\> option under the DISPLAY menu. Red boxes
indicate hanging nodes and signify misplaced, extra, or missing lines if
they appear on a contact line. Sometime hanging nodes result when one
contact is connected to another in the middle rather than at the end.
This error can be corrected by using the \<breakedbreak\> option under
the EDIT menu to divide the unbroken line at the hanging node.

[^285] [^286] [^287]

Database file structure and standard DOS file extensions

Each data base consists of three DOS binary files: an index file, a line
segment file and a nodenodehelp file. A data base has a unique data base
name up to eight characters long. The DOS filenames for the index, line
segment and node files respectively are designated by adding the
extension of .NDX, .LSF and .NOD respectively to the data base name. The
user only refers to the data base name and never has to individually
reference the indi­vidual files. The user creates the files using a GSMAP
program. Since the files are binary, they cannot be edited or modified
except through a GSMAP program. A single entry can contain a maximum of
5000 points.

[Index File]{.underline}

The index file allows for rapid selection of entries by the attribute
CODE. The first record of the index file records the number of entries
in the data base and the number of records within the line segment file.
Each graphical entry in a data base has a record in the index file. This
record stores three attributes (CODE, P1 and P2) of the entry, pointers
to the start­ing and ending records within the line segment file that
contain positional data and the starting and ending nodenodehelp numbers
for lines. The index file will always contain N+1 records where N is the
number of entries in the data base.

[Line Segment File]{.underline}

This file stores a short title(sixteen characters), the coordinates of
the corners of the data base area, and the coordi­nates of the points
that make up each of the graphical entries. The first five records are
created when the data base is started; other records are stored as
entries are added.

[Node File]{.underline}

Each record contains the coordinates of a nodenodehelp point. Node
points define the beginning or end of one or more line entries (code
group 1-99 only). The records contain the coordinates of the node point
and the number of lines attached to the node point.

Example:

Normally you will choose a data base name which is sugges­tive. For
example, you declare the data base name to be TESTMAP. GSMAP will create
three DOS files: TESTMAP.NDX, TESTMAP.LSF and TESTMAP.NOD.

Each data base will also have an associated set of ASCII files to
provide specific information for plotting, projectionprojectionhelp
parameters and may also have associated text files. These files can be
written using any text edit program that produces an ASCII file without
embedded characters (used as control charac­ters for printing by many
programs). Almost all of the standard word processing programs can
produce or export such a file.

Plot Control Filespltfile

These files select corners, provide plotting parame­ters, select entries
for plotting, and control all aspects of plotting. They also control how
entities are exported to ARC/INFO under the export function on the FILE
menu.

Word and character file for text codes (500 and 700 code groupsrufile

[^288] [^289] [^290]

[Plot Control File]{.underline}

GSMAP Plot Control Files are used for plotting to the screen, to a disk,
or to the plotter, and for digitizing so that text and symbology can be
shown on the screen. The same plot control files are used by the GSMEDIT
program. Any valid DOS filename can be used for this file but normally
these files are given a DOS filename of the data base name followed by
the .PLT extension. These files select corners, provide plotting
parame­ters, select entries for plotting, and control all aspects of
plotting. Notes can be added to the Plot Control file after the
End-Of-File line (0,0,0,0,\"EOF\"). Some of the terms used are discussed
below.

Plot corners

Plot corners other than the data base corners can be set by entering a
**N** as the first line of the Plot Control File, and specifying the
geodetic (or Cartesian) coordinates of the plot window in the next four
lines of the Plot Control File.

Offsets

Offsets XOFF and YOFF are used to move the entire plot to a new place on
the plot media. The desired X offset and Y offset are entered in decimal
inches.

Draft mode

If Draft Mode is set to Y, the entry number will be plotted to the left
of the first digitized point for each entry and a small circle is drawn
around the first and last points of each line. If Draft Mode is set to
N, entry numbers and circles will not be plotted.

Rotation

Rotation is a plotter feature calling for a 90 degree rota­tion of a plot
on the plotter media. Check the plotter manual for rotation
instructions. In most cases if the X dimension of the plot exceeds the
Y, rotation should not be specified.

Speed and force

Speed and force are plotter characteristics. Pen speed is specified in
cm/sec. Force by integers 1 to 8 that increase the downward force.
Optimum speed and force depend on pen type and plot media. The quality
of final plots generally is improved by slowing the pen speed. You
should consult your plotter manual for specific information regarding
recommended speed and force settings for specific pen/media
combinations.

Pen and Alternate Pen

When plotting to the plotter, these numbers refer to the carousel pen
position. When used used for plotting to the screen, these numbers refer
to the screen color desired. When used on the Hewlett-Packard DesignJet
plotter they refer to the color,width definition in a table (DJ.TAB).
When lines are deco­rated, the primary pen will be used to draw the line;
the alter­nate pen, the decorating symbol. When polygons are drawn, the
primary pen is used for the outline (if drawn); the alternate pen, for
the interior fill (if filled). The following table indicates the colors
displayed on the screen when a specific pen is specified.

Pen #1=Blue Pen #9=Light Blue

Pen #2=Green Pen #10=Light Green

Pen #3=Cyan Pen #11=Light Cyan

Pen #4=Red Pen #12=Light Red

Pen #5=Magenta Pen #13=Light Magenta

Pen #6=Brown Pen #14=Yellow

Pen #7=White Pen #15=High Intensity White

Pen #8=Gray

Line Type

This number refers to the line type definitions.

[Example Plot Control File for a Cartesian data base]{.underline}

Comments to the right not enclosed in quotation marks are annotations,
not a part of the file.

Entry in Plot Control File \| Comments

\|

Y \| Use data base corners as plot corners

1,1 \| X,Y scales

1,2 \| X,Y offsets

N \|Draft mode=N

Y \|Rotate=Y

12,2 \|Speed=12, Force=2

1,1,0,0, \"SOLID LINE CONTACTS\" \|CODE=1,Pen=1,Line type=0,0=No
decoration

2,1,1,0, \"dotted line contacts\" \|CODE=2,Pen=1,Line Type=1,0=no
decoration

4,5,0,0, \"SOLID LINE FAULTS\" \|CODE=4,Pen=5,Line type=0,0=No
decoration

101,3,0,80, \"SYMBOLS with POSTING\" \|CODE=101,Pen=3,Line
type=0,Symbolsize=80

DRAW.DAT,2 \|File containing data for 101 Code,Font#=2

0.04,0.06 \|Width=0.04\", Height =0.06\" of posted characters

201,2,0,0,\"DIP & STRIKE SYMBOLS\" \|CODE=201,Pen=2,Line type=0,0,

300,2,0,0, \"SYMBOLS\" \|CODE=300,Pen=2,Line type=0, Rotate=0

N \|Randomize=N

400,1,0,1, \"Igneous rocks, solid fill\" \|CODE=400,Pen=1,Line
type=0,0,Fill type=1

0.01,0,1,0 \|spacing=.01\",Angle=0,Alt pen=1,Alt Line type =0

401,2,0,1, \"Alteration\" \|CODE=401,Pen=2,Line type=0,Fill type=1

06,45,2,0 \|spacing=0.06\",angle=45, Alt pen=2, alt line type=1

555,1,0,0, \"ROCK UNIT LABELS\" \|CODE=555,Pen=1,Rotate letters=0,
Rotate words=0

FILENAME.TXT,0 \|File with rock unit labels, Font#=0rufile

701,1,0,0, \"Map title\" \|CODE=701,Pen=1,Line type=1,0,

DRAW.TXTrufile,3 \|File containing text for 701 Coderufile,Font#=3

0,0,0,0,\"EOF\" \| End of the plot file

Word and character file for text codes (500 and 700 code groupsrufile

[^291] [^292] [^293]

[Word and character files]{.underline}

Words and symbols are entered into files in the format specified below
for retrieval by GSMAP using codes 500-599code500 and 700-799code700.
Any valid DOS filename can be used for this file but normally these
files are given a DOS filename of the data base name followed by the .RU
extension. In this file, the number is the index for the succeeding
words, characters, or numbers which constitute the label entry that will
be plotted on the diagram. The index number at the start of each label
entry corresponds to attribute P1 entered from the keypad during
digitizing. The \"EOT\" is the tag marking the end of the entry and must
be placed on the line below the text for the entry (EOT stands for \'end
of text\'). Commas are used to separate the three parts of the table
entry.

Number, \"Label\",

\"EOT\"

For multi-line text entries do not put a comma (,) at the end of the
lines of text except at the end of the last line. A comma at the end of
any previous line of text will be equivalent to a blank line of text.
The comma at the end of the line of text before the \"EOT\" end of text
line is optional.

A blank line of text needed for spacing can be entered as a record
reading \" \" (double quote space double quote); although a comma after
the previous line has the same effect it\'s too hard to recognize it as
a blank line when reading the file.

Quotation marks (\") cannot be used in a label because they are a
delimiter in BASIC. A substitutealiaslist is provided by redefining the
} character in Font #0 as shown below and in the extended character sets
as ASCII 180 in Font #1 and as ASCII 214 in Font #2. Several other
substitutes are also available for special geologic characters.aliaslist

A maximum of 150 characters (including blanks) can be en­closed between
the quotation marks on a single line. There is essentially no limit to
the number of lines that can be put into a multi-line entry.

[Example text file]{.underline}:

1,\"@m\",

\"EOT\"

2,\"&sc\",

\"EOT\"

3,\"\\s\",

\"EOT\"

4,\"Xgn\",

\"EOT\"

5,\"Ti\",

\"EOT\"

6,\"LAST CHANCE\"

\" LODE\",

\"EOT\" 11,\"MY FAULT\",

\"EOT\"

12,\"YOUR FAULT\",

\"EOT\"

10,\"GEOLOGIC MAP OF THE EXERCISE AREA\",

\"EOT\"

An entry such as:

27,\"UNKNOWN\"

\"RESOURCE\"

\"POTENTIAL\",

\"EOT\"

will plot as :

UNKNOWN

RESOURCE

POTENTIAL

[^294] [^295] [^296]

GEOLOGIC AND OTHER SPECIAL SYMBOLS

Placing the text listed below in the left column in the rock unit text
file will produce the symbol named in the right column on the face of
the map. Letter case must match the example.

GEOLOGIC SYMBOLS

%Oligocene Oligocene symbol

%Og Oligocene symbol

%Eocene Eocene symbol

%Eo Eocene symbol

%Paleocene Paleocene symbol

%Pa Paleocene symbol

@ Triassic symbol

%Triassic Triassic symbol

%Tr Triassic symbol

& Pennsylvanian symbol

%Pennsylvanian Pennsylvanian symbol

%Pn Pennsylvanian symbol

\\ Cambrian symbol

%Cambrian Cambrian symbol

%C Cambrian symbol

%Mesozoic Mesozoic symbol

%Mz Mesozoic symbol

%Paleozoic Paleozoic symbol

%Pz Paleozoic symbol

%Proterozoic Proterozoic symbol

%Pr Proterozoic symbol

SUPERSCRIPTS AND SUBSCRIPTS (not supported in translation to ARC/INFO)

%P1 Proterozoic symbol subscript 1

%P2 Proterozoic symbol subscript 2

%P3 Proterozoic symbol subscript 3

%S1 Subscript 1

%S2 Subscript 2

%S3 Subscript 3

%S4 Subscript 4

%S5 Subscript 5

%S6 Subscript 6

%S7 Subscript 7

%S8 Subscript 8

%S9 Subscript 9

%S0 Subscript 0

MISCELLANEOUS

%DATE Current date and time stamp

%NDXFILE Name of the database file

%TITLE Title of the database

%PLTFILE Name of the plot file in use

%PROJECTION Name of the map projection

{ Degree symbol

%DEGREE Degree symbol

} Second symbol (double quote)

%SECOND Second symbol (double quote)

[^297] [^298] [^299]

OUTPUT

Controls hardcopy production using either a printer, a plotter attached
to a serial port, or Hewelett-Packard graphics language plotter commands
written to a file.

Output to a plotterplotterout

Output to a printerprintout

Printing the screen windowprintrot

Saving an image of the screenscreendump

[^300] [^301] [^302]

Output to a plotter

Plotter options are offered on a special form with its own menu system.

Plotter typedevice

Plot orientation and centeringorienthead

Plotter connectionconnection

Registering the plot to a basemapreghead

Controlling pen color and thicknessdevice

Starting the plotgoplot

Aborting a plotgoplot

[^303] [^304] [^305]

Plotter type

The default plotter device is a pen plotter. The line color and
thickness associated with a pen number are controlled by selection of
pens placed in the numbered positions in the plotter carousel. An
alternative option is a raster plotter such as a HP Designjet inkjet
plotter. Line thickness and color produced by a raster plotter are
controlled by software commands. The default colors and thicknesses for
256 logical pens are stored in the ascii file dj.tab and used when the
raster plotter option is selected. Those colors and thicknesses can be
customized by editing that file.

[^306] [^307] [^308]

Orientation and centering of the plot

Default orientation of the plot is controlled by a line in the plot
file. Normal orientation (\<N\> in the plot file) is appropriate for
drawings that have greater width than height, since the X direction is
parallel to the direction of paper travel, which is usually the longer
dimension of the paper. Orientation can be changed by a menu choice at
the time of plotting. Landscape mode is the normal case and portrait
mode is the rotated case.

A second choice is whether to plot with the lower left corner of the
drawing in the lower left corner of the paper, or to center the drawing
on the paper.

[^309] [^310] [^311]

Connecting the computer to the plotter

Hewlett Packard graphics language (HPGL) commands generated by the
program can be sent through a cable to a plotter or stored in a file for
later plotting. The computer serial port number and settings (baud,
parity, data bits and stop bits) are read from the config9.plt file, but
can be changed using the connection menu on the plotter control form.
The paper size (A, B, C, D, or E) and plotter origin (lower left or
center) are provided by the plotter if it is connected, but must be
entered by the user when plotting to a file. When the OK option is
selected and output is directed to a file, a popup menu requests the
necessary information and a file list opens for entry of the output file
name before plotting of the drawing begins.

Small pen plotters that handle only A or B size paper sheets generally
have their origin in the lower left corner of the paper so that all
coordinates are positive. Larger pen plotters usually have their origin
in the middle of the paper sheet so that positive and negative
coordinates can be plotted. Raster plotter generally have their origin
in the lower left corner of the paper, but may also be able to emulate
the large pen plotters.

[^312] [^313] [^314]

Adding registration points to a HPGL output file

Plots to a pen plotter can be translated, rotated, and scaled to
register on a base map mounted in the plotter if a fiber optic sight in
the plotter is used to digitize points on the map that correspond to the
first points output by the program. The \<Registration points\> option
on the plotter form selects whether the first points output (with pen
up) are the database corners or the plot corners. The choice will depend
on which set is more easily identified on the basemap. Registration
points that are farthest apart generally provide the most accurate
registration. Plot registration from within the GSMCAD program is not
yet implemented, so plots to be registered must be output to a file, and
later registered on the plotter using the DOS program HPGLUTIL that is
installed in the GSMCAD directory. This can be done without leaving the
GSMCAD program by using the \<Shell to DOS\>shelldos option on the file
menu. The HPGLUTIL.DOC file documents the capabilities of the HPGLUTIL
program.

Registered plots are a useful and relatively easy way to combine
geologic data with the topographic and cultural information on a
basemap. Pen plots on paper topographic map sheets can be colored for
review copy and pen plots on greenline film can be submitted to make
open-file negatives.

[^315] [^316] [^317]

Beginning or aborting a plot

After all parameters on the plotter form are correctly set and the paper
mounted in the plotter, start the plot by selecting \<OK\>. If it is
necessary to abandon the plot, select \<Cancel\> instead. The new plot
will then be directed to the screen rather than the plotter.

[^318] [^319] [^320]

Printing a drawing

Printer options are offered on a special form with its own menu system.

Scaling the printscalehead

Print orientation and centeringposhead

Controlling line thicknessdefpen

Changing the printernewprinter

Starting the printer plotgoprint

Aborting a printer plotgoprint

[^321] [^322] [^323]

Scaling a printer plot

By default the printer draws at the scale defined in the plot file. If
the drawing is larger than a printer paper sheet, the top and/or right
side will be missing. The scaling can be changed at print time by
options under the scale menu on the printer form. The \<Fit to paper\>
option changes the scale to a value that will show all the drawing as
large as possible on a sheet of printer paper. The \<Set percent\>
option changes the scale by multiplying the scale from the plot file by
a value input by the user. The option can be activated by a menu choice
or by typing a new percent value into a text box on the printer form. It
will not be activated by attempting to type in a new scale value on the
form.

[^324] [^325] [^326]

Print orientation and centering

Options controlling the rotation and centering of the print are
available under the \<Position\> menu on the printer form. The default
orientation (Top up) is portrait, so the top of the drawing is along a
narrow edge of the paper. The alternative (Top left) places the top of
the drawing along a wide edge of the paper.

The lower left corner of the drawing will normally be placed in the
lower left corner of the paper, but two other options are available.
Either the center of the drawing can be placed in the center of the
paper or the center of the present screen window can be placed in the
center of the paper. The last option differs from the \<Print
screen\>printrot option of the OUTPUT menu in that it maintains the
scaling set in the plot file.and may show less or more than the screen
window.

[^327] [^328] [^329]

Controlling line thickness on the printer

The \<Define Pens\> option on the Printer Form allows line thickness to
be set for the pen numbers assigned in the plotter file. The value must
be input in pixils (printer dots). For a 300-dots-per-inch laser
printer, 3 pixils corresponds approximately to the thickness of fault
lines on published U.S.G.S. maps. Default line thickness is one pixil

[^330] [^331] [^332]

Changing the printer

The \<change printer\> menu button on the Printer Form activates the
windows print control dialog box and allows the user to select another
printer or change printer options

[^333] [^334] [^335]

Beginning or aborting printing the drawing

After all parameters on the printer form are correctly set, start the
print by selecting \<OK\>. If it is necessary to abandon printing the
drawing, select \<Cancel\> instead. The new plot will then be directed
to the screen rather than the printer. Plotting on the printer requires
that vector data be rasterized in memory, and the process can consume
several minutes before any data is directed to the printer.

[^336] [^337] [^338]

Print the screen

When the output option to print the screen is selected, the area of the
screen window is drawn by the printer scaled to fit on a sheet of
printer paper in landscape orientation. The output is a vector plot, not
a raster screen dump. The printer form does not appear because scale,
orientation, and area are predetermined. This option differs from the
\<Center on screen\>poshead option in that scaling is independant of the
scale values in the plot file.

If a raster screen dump is desired, pressing \<Alt\>\<Prt Scr\> will
store the screen image in the clipboard in a bitmap (BMP) format that
can be edited and printed from the windows paint program.

[^339] [^340] [^341]

Saving an image of the screen

If a raster screen dump is desired, pressing \<Alt\>\<Prt Scr\> will
store the screen image in the clipboard in a bitmap (BMP) format that
can be edited and printed from the windows paint program.

[^342] [^343] [^344]

DRAWING ENTITY TYPES (CODE GROUPS)

There are several drawing catagories used to represent information on
geologic maps and other illustrations that require distinct techniques
for digitizing and plotting. These are separated in GSMAP databases by
assigning them to different code groups, or ranges of line code. Line
codes 1 to 99 are reserved for lines and decorated lines, so 99
different types of line can be shown on a single map. Most code groups
are assigned a range of 100 line codes, except that the polygon group is
assigned a range of 200 to allow plotting of colored maps having more
than 100 geologic units.

Lines and decorated lines (CODE GROUP 1-99)code1

Data points (CODE GROUP 100-199)code100

Individually rotatable symbols (CODE GROUP 200-299)code200

User defined symbols (CODE GROUP 300-399)code300

Polygonal areas (CODE GROUP 400-499 and 800-899)code400

Text and leaders (CODE GROUP 500-599)code500

Splined lines (CODE GROUP 600-699)code600

Curved text (CODE GROUP 700-799)code700

Profile lines (CODE GROUP 900-998)code900

[^345] [^346] [^347]

Codes for lines and decorated lines (CODE GROUP 1 - 99)

Code group 1-99 is used for various kinds of lines. All lines are
digitized as if continuous, even though they may eventually be plotted
using a line type that appears discontinuous, such line type 1, which is
dotted. Line types, colors, line weights, and sometimes decorations to
be used in plotting entries of each code are specified in the plot file.
For directions on plotting lines see the topic Plotting lines and
decorated linesplotline

Use of some regular convention for codes for common kinds of lines will
aid digitizing and plotting. One convention easily remembered is to use
codes 1, 2, and 3 for fine solid, dashed, and dotted lines (contacts),
4, 5, and 6 for heavy solid, dashed, and dotted lines (faults). We
suggest reserving codes 1-15 for geologic lines. Code special lines such
as border lines using higher numbers.

Lines can be plotted with \"decorations\" drawn perpendicular to the
line at evenly spaced intervals. The most common example is the line
symbol for thrust faults in which triangles point away from the line
toward the overthrust plate. Decorations are always drawn on the
right-hand side of the line when looking in the direction of digitizing,
so it is important to digitize in the direction necessary to convey the
correct information. If this is not done the decorations will plot on
the wrong side, but correction is easy using the \<Reverse\> option
under the EDIT menu.

Instructions for plotting lines, decorated lines, and splined
linesplotline

[^348] [^349] [^350]

Codes for symbols and posting of tabular data (CODE GROUP 100 - 199)

Code group 100-199 is used to plot symbols and post near the symbol
asso­ciated tabular data drawn from ASCII row-column files. The first
column of the ASCII data file is used for the locality identifier;
succeeding columns are used for data pertaining to this locality.
Locality number, value 1, value 2, value 3, etc. The first column is
restricted to numbers. Alpha and numeric characters can be used in the
other columns. Commas (,) **must** be used to separate the columns.
Every column must contain a value for each row. If data is missing for a
column, put in a comma, or \" \" (double quote blank double quote). Be
careful to observe the format for the data table, especially checking to
see that the commas separating the columns are in place. Don\'t use
characters such as commas and semicolons within the columns, because
these are delimiters and will be interpreted as additional columns. An
example file follows:

410, 50, 10, 100, 105

411, 15, 2, 20, 106

412, 30, 50, 150, 107

413, 70, 10, 300, 500

Three entries are required from the digitizer keypad or screen menu:

1\. CODE, (100-199): Use a different code for each different symbol or
data file. Symbol types and sizes, and data files for each code are
defined in the associated plot file.

2\. P1: Locality number (containing up to 6 digits).

3\. P2: Angle of rotation of plotted posting, in degrees measured
counterclockwise from the horizontal. A value of zero selects horizontal
posting to the right of the digi­tized point. **Angles between 91 and 269
degrees cause posting of numbers to the LEFT of the locality point,
angles 270-360, 0-90 degrees plot to the RIGHT of the point**.

The **1** key is used to digitize the point and complete the entry. Move
the cursor to the exact point required, press the 1 key. The system will
record the point and complete the entry.

Plotting data points and posting tabular dataplot100

[^351] [^352] [^353]

Plotting symbols and posting tabular data (CODE GROUP 100-199)

Plot files require four sets of parameters. Each set is specified on a
separate line of a plot control file.

The first set answers provides:

CODE,PEN NUMBER, SYMBOL, SYMBOL SIZE,COMMENT e.g. **101,1,9,50,\"SAMPLE
IDS\"**.

Parameter 1: CODE (100-199), then a comma (,)

Parameter 2: the pen number, then a comma (,)

Parameter 3: the number of the symbol desired defined in the CONFIG9.SYM
file, then a comma (,)

Parameter 4: the size of the symbol desired in 1/1000 inch, followed by
a comma (,).

When plotting data bases with Cartesian coordinates, symbols are sized
based on the Parameter 4 value but sizes are modified according to the
scale of the plot in **X** (not Y). For example, a symbol of size=100
would be plotted at a size of 50 on a plot with XSCALE=0.5 (half-sized
plot). For a geodetic data base symbols are plotted at the sizes
specified regardless of plot scale.

Parameter 5: A comment enclosed between quotation marks is an essential
part of the file to record the use of the code. A carriage return is
required at the end of this parameter.

The second set of parameters provides for:

FILENAME FOR DATA FILE, FONT \# e.g. **DRAW.DAT,1**

Parameter 1: enter the complete name of the file, including extension
followed by a comma,

Parameter 2: the number of the font to be used, e.g. **DATA.DAT,2**

The third set of parameters provides for:

\# COLUMNS IN DATA TABLE, \# OF COLUMN TO BE PLOTTED e.g **3,1**

Parameter 1: the number of columns of data in the table (not including
the locality number column)

Parameter 2: the number of the data column containing the data that is
to be plotted; if 0 is specified, the locality number will be plotted, 1
will cause data from the first (left) column of data to be plotted, 2,
the next column to the right, and so on.

The fourth set of parameters provides for:

WIDTH OF POSTED CHARACTERS, HEIGHT OF POSTED CHARACTERS (in inches e.g.
**0.04,0.06**).

Parameter 1: Width of posted characters in inches

Parameter 2: Height of posted characters in inches

Posting will be done with a space between the center of the symbol and
the adjacent number equal to one-half the symbol size specified plus the
width specified for the label characters. The size of the numbers used
for posting will be the size specified in the fourth set.

If no symbol is wanted, specify symbol 30 (symbol 30 has no pen down
moves) and no symbol will be plotted. If a symbol is wanted without
posting, substitute a blank space then a comma, then 0 (zero) in the
plot control file at the place appropriate for the data file name and
font number. Specify that the file has one data column and request
plotting from column 1.

If locality numbers are wanted without the bother of creating a data
file, use a dummy file name, then a comma and zero (e.g. A,0) followed
by a carriage return as the second entry in the third set (FILENAME FOR
TABLE, column to the plotted). Specify that the table has 1 data column,
and that you wish column 0 plotted. The program will read the locality
number entered as P1 in the database, and plot this number in the
appropriate place.

GSMCAD (but not GSMAP) also has the capability to read a data file that
consists of a text narrative of observations at the data point, perhaps
from field notes. The format for the data file is the site number (P1)
on a line alone, followed by the text, followed by a blank line.

The column to be plotted entry in the plot file must be \<-1\>. Only the
locality number is plotted on the map, but the narrative can be read by
selecting the symbol and using the \<query\>edquery option under the
EDIT menu.

[^354] [^355] [^356]

Rotatable Symbols (CODE GROUP 200-299)

Code group 200-299 is used for individually rotatable sym­bols. Unlike
other code groups, each code in this group has a specific use. Each code
specifies a single specific symbol. For example code 201 specifies the
symbol for strike and dip of bedding. A page showing all the symbols and
their numbers can be printed by selecting the \<Print symbol page\>
option under the HELP menu. The location of the symbol is digitized with
one point if the rotation angle (strike) is known, and two points if the
rotation must be calculated from the graphical representation on the map
being digitized. The size of symbols codes 200-299 is set by the program
(100 rasters, 0.1 inch) and does not change as a function of the scale
of the plot.

Three entries from the digitizer keypad are required:

1\. CODE: the code of the desired symbol.

2\. P1: the angle of rotation of the symbol in degrees, measured in a
clockwise direction from north (or vertical) if known, followed by an
**A**, otherwise an **A** alone.

3\. P2: the angle of dip or plunge (degrees) to be posted, followed by
an **A**. If no angle is required for the symbol chosen, enter **A**.

One-point digitizing (used when the angle of rotation of the symbol is
known):

The position of the symbol is digitized and the entry completed by
pressing the **1** key at the location desired. The symbol will be
rotated around this point during plotting. Most symbols, including
strike and dip, foliation, anticline symbol, and syncline symbol rotate
from the center of the symbol. The bar and ball rotate from the end
opposite the ball; lineation symbols rotate from the end of the symbol
away from the point of posting. The position of this point has been
chosen to assist its use and match standard practice.

Two-point digitizing (used to digitize accurately plotted sym­bols; the
angle of rotation (P1) is calculated by the program):

After entry of CODE (200-299), P1=**0** (use **A** key), enter P2=angle
to be posted, then digitize location of the symbol with the **0** key,
then following the right hand rule (to properly rotate the symbol),
digitize a second point with the **1** key. This point sets P1 to the
angle of azimuth measured by the two digitized points. It\'s a quick way
to digitize a carefully plotted symbol. To help establish the second
point to be digitized, visualize the symbol with 0 degree rotation as
plotted on fig. 2; digitize the second point \"up\" on the symbol. In
tests of two-point digitiz­ing, the azimuth of small symbols was
calculated within 1.5 degrees of the plotted value.

The location where the dip value is to be posted is normally determined
automatically by the program, but can be modified by the user to avoid
overposting. A rotatable symbol entity is recorded initially by two
identical points. As long as those points remain identical, posting is
automatic. If the second point is moved using the \<move pointedmvpt\>
option under the EDIT menu, the second point then becomes the posting
point for the dip value.

Plotting individually rotatable symbolsplot200

[^357] [^358] [^359]

Plotting Rotatable Symbols - CODES 200-299

The only option in plotting rotatable symbols is the pen number, which
controls line color and thickness. Fine tip pens must be used or the
numbers that are posted, e.g. the angle of dip will not be legible.
Plots of each symbol type require one set of four entries. Each code is
specified on one line of a plot control file.

The set provides:

CODE, PEN NUMBER, 0, 0, \"COMMENT\"

Parameter 1: the CODE specifying the particular symbol to be plotted,
followed by a comma (,).

Parameter 2: the pen number, followed by a comma (,).

Parameter 3: 0, followed by a comma (,).

Parameter 4: 0, followed by a comma (,).

Parameter 5: A comment enclosed between quotation marks is an essential
part of the file to record the use of the code. A carriage return is
required at the end of this parameter.

[^360] [^361] [^362]

[CODES 300-399 User Defined Symbols]{.underline}

Code group 300-399 is used for symbols. The user defines the use of each
code. The kind and size of each symbol can be specified during
digitizing. A page showing all the symbols and their numbers can be
printed by selecting the \<Print symbol page\> option under the HELP
menu. During plotting all symbols of a particular code can be rotated by
a specified angle (as a group). The orientation of symbols can be
\"randomized\"; that is, each symbol differently rotated using a random
number generator. The instructions to the plotter that define symbols
are contained in the file named CONFIG9.SYM.

When using Cartesian coordinates the size of the SYMBOLS that will be
plotted varies with the scale of the plot in X (horizontal); e.g. a
half-sized plot, XSCALE=0.5, will have letters half the size of the
values recorded as P2. The size of the symbols is independent of the
scale in Y. When using geode­tic coordinates the size of the symbol will
not be changed as a function of plot scale. The size will be as
specified by P2.

Three parameters from the digitizer keypad are required:

1\. CODE: user defined, on the basis of pen to be used, and rotation
desired in plotting.

2\. P1: symbol number (use HELP option to print page showing standard
symbols).

3\. P2: symbol size in units of 1/1,000 inch.

Move the cursor to the point desired. If a single symbol is desired, the
**1** key should be used. If a number of the same kind of symbol with
the same size and rotation are desired, digitize the points using the
**0** key up to the final point, where the **1** key should be used to
end the entry. Most symbols are centered at the central point. For
example, symbol 13 is centered at the crossing point of the pick and
hammer. However, the digitized point for symbol 11 is at the top of the
symbol. This is the point placed at the digitized point.

Instructions for plotting user defined symbolsplot300

[^363] [^364] [^365]

[CODES 400-499 (and 800-899) Polygons]{.underline}

Code groups 400-499 and 800-899 are used for closed polygons so that
their interior can be patterned/filled during plotting. The area is
outlined as a closed area during digitizing. Fill types (types of
patterns) and the kind of line to be used are specified when plotting.

Three entries from the digitizer keypad are required:

1\. CODE: user defined, on the basis of fill pattern desired. Polygons
to be filled with different patterns should be assigned different codes.

2\. P1: 0. Use the **A** key.

3\. P2: 0. Use the **A** key.

The outline of the polygon is digitized using a series of **0** key
entries until the last point before closing. This next-to-last point may
be digitized using the **2** key, which records the point and closes the
polygon, or with the **0** key, then the last point with the **3** key
which closes the first (external) polygon but leaves the entry open so
that internal closed polygons can be added. Internal polygons are
digitized with a series of **0**\'s, and closed with the **3** key,
except for the last internal polygon which must be closed with the **2**
key. When plotted, these internal polygons will be left as unfilled
\"windows\" inside the filled polygon. No more than 5,000 points can be
digitized to define both exterior and interior polygons for a single
entry.

Instructions for plotting polygonsplot400

[^366] [^367] [^368]

Plotting Polygons - CODES 400-499 and 800-899

Polygon entities are digitized or assembled from line segments so that
they can be filled with a pattern or color. GSMCAD supports 8 types of
fill having fill parameters that can be varied to produce a virtually
infinite variety of fills. Plot file instructions for polygon fills
require two lines except in the case of symbol fills, which require
three lines

Fill types:

0 \-- A line outlines the polygon without fill (patterning).

1 \-- A set of parallel lines fill the polygon (no outline).

2 \-- Two sets of mutually perpendicular parallel lines (a grid) fill
the polygon (no outline).

3 - Symbols of type and size specified by the user will be drawn on
horizontal lines spaced at user defined intervals (Y DELTA), at a
spacing specified by the user (X DELTA) (no outline).

4 \-- A set of parallel lines fill the polygon, and the border of the
polygon will be drawn.

5 \-- Two sets of mutually perpendicular parallel lines (a grid) fill
the polygon and the border of the polygon will be drawn.

6 - Symbols of type and size specified by the user will be drawn on
horizontal lines spaced at user defined intervals (Y DELTA), at a
spacing specified by the user (X DELTA), and the border of the polygon
will be drawn.

7 - A special fill type that can only be used on the Hewlett-Packard
DesignJet plotter. It is a solid fill.

The first set of parameters for all fill types is:

CODE, PEN NUMBER, LINE TYPE, 0, \"COMMENT\"

Parameter 1: the CODE, a number (between 400 and 499) followed by a
comma (,).

Parameter 2: the pen number, followed by a comma (,); this pen will be
used for the outline of the polygon if required.

Parameter 3: line type, followed by a comma (,); this line type will be
used for the outline of the polygon if required.

Parameter 4: Always zero.

Parameter 5: A comment enclosed between quotation marks is an essential
part of the file to record the use of the code. A carriage return is
required at the end of this parameter.

The second line of parameters varies according to the fill type

Fill Type 0 Outline without fill

The second and last set of parameters is:

Parameter 1: fill type (0) followed by a comma

Parameter 2: zero followed by a comma

Parameter 3: zero followed by a comma

Parameter 4: zero followed by a comma.

Parameter 5: zero

Fill Types 1 (parallel lines-no outline) and 4 (parallel lines and
outline)

The second and last set of parameters is:

Parameter 1: fill type (1 or 4) followed by a comma

Parameter 2: the spacing between fill lines in inches. For **solid**
fills on a pen plotter a spacing of 0.01 inches works with all but the
finest pens.

Parameter 3: an angle in degrees. This entry specifies the angle
measured from the horizontal (+ counterclockwise, - clock­wise) for the
direction of the lines

Parameter 4: The number of the pen to be used for the fill.

Parameter 5: The line type to be used for the fill.

Fill Types 2 (cross hatch-no outline) and 5 (cross hatch and outline)

The second and last set of parameters is:

Parameter 1: fill type (2 or 5) followed by a comma

Parameter 2: the spacing between grid lines in inches.

Parameter 3: an angle in degrees. This entry specifies the angle
measured from the horizontal (+ counterclockwise, - clock­wise) for the
direction of the horizontal lines. Vertical lines will be drawn
perpendicular.

Parameter 4: The number of the pen to be used for the fill.

Parameter 5: The line type to be used for the fill.

Fill types 3 (symbols - no outline) and 6 (symbols and outline)

The second set of four parameters is:

Parameter 1: fill type (3 or 6) followed by a comma

Parameter 2: X DELTA (the spacing in X (horizontal) entered as the
spacing between symbols in inches, followed by a comma (,).

Parameter 3: Y DELTA (the spacing in Y (vertical) entered as the spacing
between lines of symbols in inches, followed by a comma (,).

Parameter 4: The number of the pen to be used for the fill.

Parameter 5: The line type to used for the fill (always 0).

The third and final set of parameters for fill types 3 and 6 consists
of:

Parameter 1: the number of the symbol as defined in the CONFIG9.SYM file
followed by a comma (,).

Parameter 2: the symbol size measured in 1/1000 inch followed bya comma
(,). Parameter 3: a **Y** or **N**. **Y** specifies that the orientation
of the symbols is to be randomized. **N** specifies a rotation of 0
degrees for all symbols.

Fill type 7 (solid color on the Hewlett-Packard DesignJet inkjet
plotter)

The second and last set of parameters is:

Parameter 1: fill type (7) followed by a comma

Parameter 2: always zero (0) followed by a comma

Parameter 3: the level of shading (0 to 100%). A value of 0 is
interpreted to be 100%.

Parameter 4: The number of the pen (color) to be used for the fill.

Parameter 5: always zero (0).

[^369] [^370] [^371]

Plotting User Defined Symbols - CODES 300-399

Plots of symbols and symbol groups, codes 300-399, require two sets of
parameters; each set is specified on one line of a plot control file.

The first set provides:

CODE, PEN NUMBER, 0, 0, \"COMMENT\"

Parameter 1: the CODE specified by the user followed by a comma(,).

Parameter 2: pen number, followed by a comma (,).

Parameter 3: 0, followed by a comma (,).

Parameter 4: the angle in degrees (+ clockwise) that all symbols of this
code are to be rotated, assuming that rotations are not randomized,
followed by a comma (,).

Parameter 5: A comment enclosed between quotation marks is an essential
part of the file to record the use of the code. A carriage return is
required at the end of this parameter.

The second set consists of a single parameter providing for randomly
rotating the symbol. In GSMCAD this line may be omitted if random
rotation is not desired. Otherwise **N** will cause all symbols of this
code to be rotated by the angle specified in Parameter 4 of the first
set. **Y** will cause symbols digitized as a single entry to be rotated
at random angles based on a random number calculat­ed by the computer.
Although the random number generator is \"random\" in one sense, it
always uses the same series of \"random\" numbers - like a printed
random number table if you always start at the same place. Sequential
plots will have the same symbols rotated by the same amount.

Parameter 1: N or Y (or omit)

[^372] [^373] [^374]

Codes for single or multiple lines of text with or without leaders (CODE
GROUP 500 - 599)

Code group 500-599 is used for alphanumeric entries that make up single
or multiple lines of ordinary text (normally spaced along a straight
line), and unit labels where leader lines are required. The letters and
numbers to be plotted are entered into an ASCII data file that will be
called by its file name during plotting, and plotted according to the
positions digitized. The selection of codes is based on, 1) pen needed
for plotting, 2) slant angle for letters (block letters or italics), and
3) the angle that the character, word, or block of text is to be rotated
on the page. Separate groups of text entries accordingly using different
codes. Code group 500-599 should be used for text if multi-line entries
are needed or if leaders are needed, as for rock unit labels on geologic
maps.

A single entry can contain leaders and position of text. The first
digitized point of the entry determines the position of the lower left
corner of the text. Additional points are digitized only If leader lines
are needed. The second point and all other even numbered points locate
the start of leader lines. All odd numbered points after the first point
locate the end of leader lines. A proper entry for 500-599 codes always
has an odd number of points.

This code group can function to identify (tag) polygonal areas for
coloring and exportingexporthead to other geographic information systems
(GIS programs). If there are no leaders, the first (and only) point of
the text entity is the tag point. If leaders are present, then the end
of each leader serves as a tag point, but the first point does not. Thus
it is very important that leaders be digitized in the direction from the
text label to the polygonal area.

Three entries from the digitizer keypad are required:

1\. CODE: user defined on the basis of pen, slant of letters and words
desired in plotting. Any code numbered between 500 and 599 can be used.

2\. P1: the number of the text item to be placed on the plot
corre­sponding to the number next to the text item in the ASCII data
file. This number is used by the program to \"look up\" the text item.

3\. P2: the size of the lettering, expressed in units of 1/1000 inch.

The first point digitized, using either the **0** or the **1** key,
positions the text block or character. The digitized point lo­cates the
lower left corner of the first character in the block of text.

\- If the **1** key is used, the entry is complete.

\- If the **0** key is used, the block of text is placed, and succeed­ing
points positioned by using the **0** and the **1** key define
straight-line leader between the two points, and complete the entry.

\- Multiple leaders can be drawn. Use the **0** key for all but the
final point. Points 2 and 3, 4 and 5 (etc.) will be connected to draw
leaders.

When using Cartesian coordinates the size of the lettering that will be
plotted varies with the scale of the plot in X (horizontal); e.g. a
half-sized plot, XSCALE=0.5, will generate letters half the size of the
values recorded as P2. The size of the characters is independent of the
scale in Y. When using geodetic coordinates the size of the lettering
will not be changed as a function of plot scale. The size will be as
speci­fied by P2.

If the plot control file does [not]{.underline} include the code
specified or the text file doesn\'t exist, or include the index number
specified as P1, the screen will show the position of the point
digitized and the leader(s) but not the words or characters that will be
plotted. If the code is included and the specified text file includes
the number required, the text will be drawn on the screen in the font
specified. If a number is entered for P1 that does not correspond to an
entry in the text file called, no entry will be plotted. The omission
will be noted at the bottom of the screen during plotting.

Plotting text and leaders (CODE GROUPS 500-599)plot500

[^375] [^376] [^377]

Plotting text and leaders (CODE GROUPS 500-599)

The text rotates around the initial digitized point during plotting.
When using Cartesian coordinates the size of the lettering that will be
plotted varies with the scale of the plot in X (horizontal), e.g. a
half-sized plot, XSCALE=0.5, will have letters half the size of the
values recorded as P2. The size of the characters is independent of the
scale in Y. When using geodetic coordinates the size of the lettering
will not change as a function of plot scale. The size will be as
specified by P2. If a number is entered for P1 that does not correspond
to an entry in the text file called, no entry will be plotted. The
omission will be noted on the screen during plotting.

Plots of codes 500-599 require two sets of parameters. Each set is
specified on one line of a plot control file.

The first set provides:

CODE, PEN NUMBER, SLANT ANGLE, ROTATION ANGLE,\"COMMENT\":

The first set is:

Parameter 1: the CODE desired, a number between 500 and 599, followed by
a comma (,).

Parameter 2: the pen number, followed by a comma (,).

Parameter 3: the slant angle for letters (an angle measured clockwise
from the vertical see Fig. 8); 0 degrees for block lettering, about 30
degrees for simulated italic letters, followed by a comma (,).

Parameter 4: the angle of rotation for blocks of text on plot (an angle
measured from the horizontal, + counterclockwise, - clockwise, see Fig.
8), followed by a comma.

Parameter 5: A comment enclosed between quotation marks is an essential
part of the file to record the use of the code. A carriage return is
required at the end of this parameter.

The second set consists of two parameters that supply the name of the
file containing the text and the number of the font to be used:

FILENAM.TEXT, FONT \#

Parameter 1: the name of the text filesrufile containing the text to be
plotted, followed by a comma (,). This entry must contain the complete
filename with its extension.

Parameter 2. the number of the font desired.

Example:

501, 2, 0, 0, \"Unit label text\"

mapunit.ru, 0

[^378] [^379] [^380]

Splined lines (CODE GROUP 600-699)

Code group 600-699 is used for lines and functions much like code group
1-99, but when the lines are plotted they are smoothed by splining. Up
to five times as many segments as digitized are plotted for each entry.
The computer generates the required points by \"curve-fitting\" the line
according to a cubic equation. The splined line starts at the first
point digitized, ends at the last point digitized, and goes through all
digitized points.

Codes for splined lines are especially appropriate if line type 98
(parallel lines) is to be used when plotting. All lines are drawn by the
plotter as a series of straight line segments. The effect of splining is
to smooth the \"curve\" digitized by a series of short straight lines
(on the plotter and on the screen); the data base is not modified.
Splining is done for entries made up of 6 to 2500 digitized points. If
there are 5 or fewer data points, or 2501 or more, no splining will be
done. The maximum effect will be seen on lines with less than 1000
points. The splining algorithm creates a series of equally spaced points
along the line, to fit a series of cubic curves calculated to fit each
set of four digitized points in sequence down the line. The plotted line
passes through these calculated points as well as through all of the
data points. If digitized points are not equally spaced, the maximum
effect will be seen where points are most widely spaced. In effect, if
the digitized points are close together, the line joining them is
relatively straight; if points are far apart, more curvature is allowed.
A line will be plotted connecting segments of equal length to a set of
points N times the number digitized, where N is the largest integer
determined by dividing 5,000 by the number of points in the line (a
number in the range 1 to 5).

Digitizing and plottingplotline is done exactly as described for code
group 1-99.

[^381] [^382] [^383]

CODES 700-799 Single-line text that can be drawn along a splined line
trace

Code group 700-799 is used for alphanumeric entries that have a single
line of text. The letters/numbers to be plotted are entered into an
ASCII data file that will be called by its file name during plotting,
and plotted according to the manner digitized. The selection of CODE is
based on the pen needed for plotting, the slant angle for letters (block
letters or italics), and the font to be used in plotting. The angle that
the charac­ter, word, or line of text is to be drawn on the page is
estab­lished at the time of digitizing. Separate groups of text en­tries
into different codes. Codes 700-799 codes are more effi­cient if the
angle for plotting the words is to be varied from entry to entry, or if
words are to be spaced along a digitized line.

When using Cartesian coordinates the size of the lettering that will be
plotted varies with the scale of the plot in X (horizontal); e.g. a
half-sized plot, XSCALE=0.5, will generate letters half the size of the
values recorded as P2. The size of the characters is independent of the
scale in Y. When using geodetic coordinates the size of the lettering
will not be changed as a function of plot scale. The size will be as
speci­fied by P2.

If the plot control file does not include the code speci­fied, the screen
will show the position of the point digitized but not the words or
characters that will be plotted. If the code is included and the
specified text file includes the number required, the text will be drawn
on the screen in the font specified. If a number is entered for P1 that
does not correspond to an entry in the text file called or if the text
file does not exist, no entry will be plotted. The omission will be
noted on the screen during plotting.

Three entries from the digitizer keypad are required:

1\. CODE: user defined on the basis of pen, slant of letters, words,
fonts, and text spacing desired.

2\. P1: the number of the entry to be placed on the plot corresponding
to the number for the entry in the ASCII data file.

3\. P2: the size of the lettering, expressed in units of 1/1000 inch.

The first point digitized, using either the **0** or the **1** key
positions the text line or character. The digitized point locates the
lower left corner of the first character of the line of text. Subsequent
points establish a line that positions and rotates the text.

If the **1** key is used for the first point, the entry is complete. The
text will print to the right of the point.

If the **0** key is used for the first point and the **1** key is used
to digitize a second point, these points define a rotation for the entry
(the **1** key completes the entry).

If the **0** key is used for the first point and for up to 3
intermediate points, and the **1** key for the last point, these points
define a series of line segments. The characters of the text will be
evenly spaced along these line segments.

If the **0** key is used for the first point, and for more than 3
intermediate points, and the **1** key for the last point, these points
define a line, The characters of the text will be evenly spaced along a
splined line through these points.

Instructions for plotting splined text (CODE GROUPS 700-799)plot700

[^384] [^385] [^386]

Plotting splined text (CODE GROUPS 700-799)

Plots of codes 700-799 require two sets of parameters. Each set is
specified on one line of a plot control file.

The first set provides:

CODE, PEN NUMBER, SLANT ANGLE, 0, \"COMMENT\"

Parameter 1: the CODE desired, a number between (700 and 799), followed
by a comma (,).

Parameter 2: the pen number, followed by a comma (,).

Parameter 3: the slant angle for letters (an angle measured clockwise
from the vertical): 0 degrees for block lettering, about 30 degrees for
simulated italic letters, followed by a comma (,).

Parameter 4: always zero (0) followed by a comma

Parameter 5: A comment enclosed between quotation marks is an essential
part of the file to record the use of the code. A carriage return is
required at the end of this parameter.

The second set of parameters provide for:

FILENAME FOR TEXT, FONT \#

Parameter 1: the name of the file containing the data to be plotted,
followed by a comma (,). This entry must contain the complete filename
with extension.

Parameter 2. the number of the font desired.

If proper plot control files and text filesrufile have been pre­pared the
screen will display the words and/or characters that will be plotted. If
these files have not been prepared, the screen will show the point
digitized for a one-point entry, or the line digitized for a multi-point
entry.

[^387] [^388] [^389]

Profile lines (CODE GROUP 900-998)

Code group 900-998 is used for lines and functions much like code group
1-99 except that an altitude value is stored with each point. The
primary use of the 900 code group is to digitize lines of section from
topographic base maps using a digitizing tablet. Points are usually
taken whereever the line of section crosses a contour, a contact, or a
known elevation. Digitizing a 900 code line allows the user the option
to automatically generate a new cartesian database of a cross sectional
view that includes the topographic profile, contact tics along the
profile that show the calculated apparent dip at the surface, and a
frame with labeled elevation tics. The geologist can then open and edit
the new database to extend and connect the contact tics so as to depict
an interpretation of the sub-surface geologic structure. The new cross
sectional database is generated when the user selects the appropriate
900 code line using the select function on the edit menu, then clicks on
the \<create profile database\> option under the FILE menu.

Digitizing 900 code group lines is slower and much more complicated than
digitizing other lines because an elevation has to be supplied for every
point. Prompts in the red box at the bottom of the screen need to be
followed carefully and the points to be digitized should be planned and
their elevations noted before beginning the line. To produce a smooth
and realistic profile elevations should be interpolated for the places
where the line crosses ridges, valley bottoms, and geologic contacts. As
these points are digitized the elevation value must be keyed in using
the keys on the digitizer puck. Pressing the \<D\> key results in a
prompt to enter an elevation value. Pressing the \<C\> key indicates a
contact and results in prompts to enter the elevation value, then to
enter the dip value, and then to digitize a point in the direction of
dip so the apparent dip can be calculated. Pressing the \<E\> key will
abort the line, but pressing the \<backspace\> key on the keyboard will
eliminate only the last point.

For points on even contours, the program will calculate the elevation
value based on the previous elevation and the contour interval. The
contour interval and elevation of the first point must be entered before
starting the line. A point digitized using the \<3\> key indicated an
elevation on the next contour above the previous point. The \<2\> key
indicates the same elevation as the last point and the \<0\> key
indicates an elevation equal to the next contour below the previous
point. Pressing the \<1\> key indicates the end of the line and will
result in a prompt to enter the final elevation on the keypad.

If mistakes are made entering elevations during digitizing they can be
corrected after the line is completed by returning to the edit screen,
selecting the line, and using the \<move point\> option under the EDIT
menu.

Plottingplotline of code group 900-998 lines is done exactly as
described for code group 1-99.

[^390] [^391] [^392]

GETTING STARTED

This section provides a simplified step by step guide to preparation of
a geologic map using GSMCAD.

Plan project

The first step is to think carefully about what information is to be
shown on the map and what symbols, different types of lines, and
labeling will be assigned to depict each type of information. The
symbols, line types, and text fonts available in GSMCAD can be reviewed
by using HELP menu options to print example sheets. Separate line codes
from appropriate code groups must be assigned to each distinct line
type, symbol, or text type. The selected codes and their meanings should
be recorded on a note sheet so they can be be used in preparation of the
plot file. Generally these will be similar from one map to another, so
focus on unusual characteristics of your map. Commonly a plot file from
a previous project or the DEFAULTG.PLT file can be copied and then
customized.

Prepare an ascii text file listing all the map unit letter symbols and
other text on the map, each entry on a separate line. Additions and
modifications to the list are inevitable, but are easily done later.
This list must then be numbered and reformatted so it can be read by
GSMCAD. This will be done by the program by using option FILE/Edit text
file/reformat. The name of the reformatted file (with suggested
extension .RU) will also be entered in the plot file as part of the
500code500 or 700code700 code group parameters. Print out a copy of the
reformatted list for reference when digitizing.

If the database will become part of a Geographic Information System, it
may be important to assign separate line codes to different types of
contacts and faults even though they may appear the same on the map. For
example, the distinction between strike-slip and normal faults should be
maintained in the data.

Create database

Select the \<New database\> option under the FILE menu to create an
empty data base consisting of a line segment file (.LSF), an index file
(.NDX), and a node file (.NOD). The option to create a boundary line for
the database should be usually accepted, because that line will be
needed to enclose polygonal areas if the map is to be colored. If you
create a geodetic database, the program will also create a projection
file (.PRJ). The projection file is not part of the database, but
controls input from and output to cartesian devices such as digitizer
and plotters. You may need to use two or more projection files for your
project if a change in projection is involved, for example digitizing
data from 7 1/2 \' quadrangles (commonly Transverse Mercator or Lambert
Conformal) and plotting the map on a standard 1:100,000 base (UTM). You
may be asked to enter a state code for the map area because the
projection used for 7 1/2\' maps varies by state.

The next step is creation of a plot file giving specific instructions
about how each entity on your map is to be drawn. Different types of
entities (Code Groups) require different parameters, so plot file
construction can be quite confusing. The program will automatically
generate a plot file for the database based on the suggested standard in
the DEFAULTG.PLT file, or it will lead you step by step to create a
custom file. Use of the standard makes future combination of data from
different workers much easier.

Digitize lines

After all files have been created and formatted, data entry can begin.
The usual first step is to place a map on a digitizing table, register
it, break the boundary line, and begin to trace lines with the digitizer
puck. The map is registered by selecting the \<Register digitizer\>
option from the EDIT menu, and then digitizing the NW, SW, SE, and NE
corners of the map.

If boundary lines have been created, and if the user wants to create
closed polygon topology, it may be preferable to add nodes to the
boundary lines before digitizing additional lines. This is done by using
the \<digitizer edit\> option under the EDIT menu after the the map has
been registered on the digitizer . Use the digitizer puck to select each
boundary line, then use the \<B\> key on the digitizer puck to break the
line at each point where a contact line will touch the boundary. If the
lines are broken from south to north and from east to west, nodes can be
quickly added without having to reselect the line after each break. The
purpose of breaking boundary lines first is to ensure that those lines
remain on an exact line of latitude or longtitude and are not pulled off
by snapping to nodes at the end of imprecisely digitized contact lines.
When done, exit digitizer edit by pressing the \<F\> key on the
digitizer keypad.

To start digitizing, select the draw menu, which brings up another bar
of menus of digitizing choices. The more important of those options can
be activated from the 16-button digitizer keypad without having to shift
back to the keyboard or mouse. Use the HELP menu to print out a page
that defines the function of each of the keys on the digitizer keypad.
Before digitizing points, use the keypad or the \<NEW CODE\> menu on the
left to set the proper CODE, P1, and P2 attributes for the entity you
are about to digitize (only CODE is needed for lines). The CODE links
the entity to the description and plotting instructions that you defined
in the plot file (.PLT). By default CODE = 1, P1 = 0, and P2 = 0 when
the program starts.

To best maintain polygon topology, lines should be digitized from node
to node. This is done by starting and ending lines at intersections. A
line can be started by positioning the cross hairs on the start point
and pressing the \<0\> or \<4\> key on the digitizer puck. The \<0\> key
will set the first point at the cross hair. The \<4\> key will search
the database and set a point exactly on the pre-existing point closest
to the cross hair, so that a perfect closure will result even if the
cross hair is beyond the snap distance. Points within the line are
digitized with the \<0\> key except if the \<8\> key is pressed to
toggle on automatic point collection until some other key is pressed.
Lines are ended with the \<1\> or the \<5\> key. The \<5\> key is used
when connecting to a pre-existing line, and places a point on top of the
closest point before ending the entry. If the user makes a mistake, the
line can be aborted by pressing the \<E\> key or activating the ABORT
menu on the screen.

Check nodes

Check the topology by turning on the node display using the node option
under the DISPLAY menu. Snapped nodes appear as small black circles
around a cross. Dangling nodes appear as red squares. Lines that form
color boundaries should not end in dangling nodes, so try to eliminate
the red squares. A simple miss can be fixed by using the move node
option under the EDIT menu. If lines cross or tee without a node, nodes
must be added by selecting and then breaking one or both lines

Digitize symbols

Print a copy of the symbol sheet from the HELP menu as a reference for
the numbers used to identify each type of symbol. The symbol number is
entered as P1 except in the case of individually rotatable symbols for
which the symbol number (between 200 and 299) is used as the CODE and
the strike is P1.

Individually rotatable symbols (Code group 200-299)code200 such as
strike and dip symbols can be digitized two ways. The strike can be
entered either by digitizing only the observation point and by keying in
the azimuth value from field notes or by digitizing the observation
point and a second point in the direction of strike (using right-hand
rule). The second method is appropriate for preexisting maps, but the
first method is more accurate.

When a symbol alone is sufficient, use Code group 300-399code300. The
symbol number is entered as P1 and the symbol size as P2. If a site
number that relates to a table of data, a text file of field notes, or a
scanned photograph is needed, use (Code group 100-199)code100 . The
unique site number is entered as P1 and a rotation angle for posting the
site number or data from a table is entered as P2. The specifications
about what data is associated with the site are given in the plot file.

Label the map

Labeling the geologic units on the map fulfills two functions. On an
uncolored map, every area must contain a letter symbol or be identified
by a leader line coming from a letter symbol. To build attributed
polygons and produce an automatically colored map, every area must
contain a tag point. In GSMCAD complete labeling results in complete
tagging, because the far end (odd numbered point) of each leader line
serves as a tag point. Entities in Code group 500-599code500 always have
an odd number of points. The first point is the lower left corner of the
text. If leaders are needed, they are defined by the 2nd and 3rd points,
4th and 5th points, etc. Bent leaders are not allowed, but can be
simulated by connecting a line to the near end of a leader. Generally at
least three different codes are needed for labeling. One represents
visible labels that tag polygon areas. Another represents visible labels
that do not tag polygons, for example a label that is leadered to a line
representing a marker bed too thin to be shown as a polygon. The third
code is used to tag polygons without a visible label. The letter size
can be made invisibly tiny, or the display of that code turned off.
Using such invisible tags reduces clutter on a colored map where the
color identifies the units, but the tags can be made visible if an
uncolored version of the map is also needed. Other codes may also be
needed for miscellaneous text. Generally each different text font and
text size should have a distinct code.

Each geologic unit is represented by a number. The rock units file
relates that number to a letter symbol. The letter symbol can be
changed, but generally the number remains the same once established. If
the project is a compilation of many maps, it is important that a
composite and comprehensive rock units file be established early, so
that identical units on different maps will be identified by identical
numbers.

Check labeling and topology

Some unlabeled polygons and gaps in contact lines can be detected by
using the color map option under the DISPLAY menu. This option works by
drawing all the lines described in the plot file comments as being a
"contact" or boundary, then filling the enclosed areas with a flood of
distinctive color starting at points defined by 500-599 group label
points that include the word tag in their plot file comment. The result
is a partially colored map on the screen. Uncolored areas occur where
there is no tag or the tag is off the screen. Wrong colors occur where
the tag is incorrect or the polygon leaks.

Output

A paper copy of the map is produced using the windows printer, a pen
plotter, an inkjet plotter, or by exporting to the ARC/INFO GIS program
and running the supplied AML programs to generate ARC coverages and a
printable graphics (GRA) image of the map. The various printer and
plotter options are found under the OUTPUT menu. The export option is
under the FILE menu.

Digitize lines

Digitize points

Compile data

Label

Edit

Plot

[^1]: ^\#^ contents

[^2]: ^\$^ CONTENTS

[^3]: ^\#^ files

[^4]: ^\$^ FILE MENU

[^5]: ^\#^ fopendb

[^6]: ^\$^ Open database

[^7]: ^\#^ geodeticdef

[^8]: ^\$^ Geodetic vs cartesian coordinates

[^9]: ^\#^ fmakenew

[^10]: ^\$^ New database

[^11]: ^K^ create; database; new; geodetic; cartesian; grid; lsf
    extension; ndx extension; nod extension; plot file; projection file;
    prj; plt;line segment;index;node

[^12]: ^\#^ fopenback

[^13]: ^\$^ Background database

[^14]: ^K^ background; back; display; open; database

[^15]: ^\#^ fdbbak

[^16]: ^\$^ Backup database

[^17]: ^K^ backup;save;database;LSF;NDX;NOD

[^18]: ^\#^ fopenprj

[^19]: ^\$^ Open projection file

[^20]: ^K^ projection;file;PRJ
    file;geodetic;latitude;longitude;UTM;conformal;polyconic

[^21]: ^\#^ fopenplt

[^22]: ^\$^ Open plot file

[^23]: ^K^ plot;file;PLT file

[^24]: ^\#^ firrplt

[^25]: ^\$^ Reread the plot file

[^26]: ^K^ plot ;file;read;notepad;redraw;edit

[^27]: ^\#^ fiimport

[^28]: ^\$^ Import from other databases

[^29]: ^K^ import;DXF;cartesian;geodetic;GSPOST;file

[^30]: ^\#^ fidxfin

[^31]: ^\$^ Convert a DXF file to GSMAP database

[^32]: ^K^ convert;DFX;import;cartesian;GSMAP

[^33]: ^\#^ fiappgsmap

[^34]: ^\$^ Append from a GSMAP database

[^35]: ^K^ append;merge;join;GSMAP;database

[^36]: ^\#^ cartin

[^37]: ^\$^ Paste GSMAP cartesian database

[^38]: ^K^ paste;insert;cartesian; database

[^39]: ^\#^ fiappost

[^40]: ^\$^ Append from GSPOST table

[^41]: ^K^ append;insert;add;GSPOST;table; database;data
    table;PLGR;MPS;GPS;import;points from table;satellite data

[^42]: ^\#^ exporthead

[^43]: ^\$^ Export GSMAP to other formats

[^44]: ^K^ export;convert;ascii;ARC/INFO;generate

[^45]: ^\#^ fitoarc

[^46]: ^\$^ Convert GSMAP to ARC/INFO generate format

[^47]: ^K^ convert;arc/info;generate;ascii;AML;export

[^48]: ^\#^ figsm2asc

[^49]: ^\$^ Convert GSMAP binary to GSMAP ascii

[^50]: ^K^ GSMAP;binary;ascii;convert;export;LSF;NDX;NOD

[^51]: ^\#^ fedit

[^52]: ^\$^ Edit a text file using NOTEPAD

[^53]: ^K^ NOTEPAD;projection;plot;text;edit;ascii;file

[^54]: ^\#^ flist2ru

[^55]: ^\$^ Convert text list to GSMAP formatted rock unit file.

[^56]: ^K^ text file;rock unit file;500 code; 700 code;special
    characters;Triassic symbol;Pennsylvanian symbol;Cambrian
    symbol;degree symbol;minute symbol;formatting a rock unit file;text
    entities

[^57]: ^\#^ lasttime

[^58]: ^\$^ Recall previous sessions

[^59]: ^K^ recall;open ;database; file;resume

[^60]: ^\#^ fibug

[^61]: ^\$^ Reporting bugs

[^62]: ^K^ bugs ; author; programmer; address; e-mail;telephone

[^63]: ^\#^ shelldos

[^64]: ^\$^ Shell to DOS

[^65]: ^K^ DOS;shell;GSMUTIL;run

[^66]: ^\#^ end

[^67]: ^\$^ Exit the program

[^68]: ^K^ exit ;end; quit

[^69]: ^\#^ editm

[^70]: ^\$^ Editing entities in GSMAP databases

[^71]: ^K^ edit;entity;shortcut;key;definitions;menu

[^72]: ^\#^ select

[^73]: ^\$^ Selecting entities for editing

[^74]: ^K^ select;entity;edit;highlight;pointing ;mouse

[^75]: ^\#^ contsel

[^76]: ^\$^ Continuing the search to select an entity

[^77]: ^K^ select;entity;edit;highlight;pointing
    ;mouse;continue;next;find

[^78]: ^\#^ undo

[^79]: ^\$^ Undo the last edit

[^80]: ^K^ undo;edit;oops;mistake;correct;error

[^81]: ^\#^ edquery

[^82]: ^\$^ Display information about an entity

[^83]: ^K^
    entity;edit;length;area;node;number;color;line;type;code;p1;p2;information
    about an entity;note;measure area;planimeter;query an entity

[^84]: ^\#^ change

[^85]: ^\$^ Change attributes of an entity (CODE, P1, P2)

[^86]: ^K^ change;attributes;code;p1;p2;correct;fix

[^87]: ^\#^ edbreak

[^88]: ^\$^ Break a line into two parts

[^89]: ^K^ edit;line;break;two;node;add;divide;cut

[^90]: ^\#^ editdel

[^91]: ^\$^ Delete an entity

[^92]: ^K^ undelete;delete;restore;oops;recover;lost

[^93]: ^\#^ edundel

[^94]: ^\$^ Undelete an entity

[^95]: ^K^ undelete;delete;restore;oops;recover;lost

[^96]: ^\#^ edmove

[^97]: ^\$^ Move an entity

[^98]: ^K^ move;entity;handle;base;pointing;mouse

[^99]: ^\#^ edcopy

[^100]: ^\$^ Copy an entity

[^101]: ^K^ move;entity;handle;base;pointing;mouse;copy;replicate

[^102]: ^\#^ eddrag1

[^103]: ^\$^ Move an entity by dragging

[^104]: ^K^ move;entity;handle;base;pointing;mouse;copy;replicate;drag

[^105]: ^\#^ eddrag2

[^106]: ^\$^ Copy an entity by dragging

[^107]: ^K^ move;entity;handle;base;pointing;mouse;copy;replicate;drag

[^108]: ^\#^ editrev

[^109]: ^\$^ Reverse the direction of a line

[^110]: ^K^ reverse;direction;decorate;line;symbols;side;digitize;change
    side;flip decorations

[^111]: ^\#^ edmvpt

[^112]: ^\$^ Move a single point in an entity

[^113]: ^K^ move point;advance;back;escape;confirm;mouse;points
    move;reshape

[^114]: ^\#^ addp

[^115]: ^\$^ Add points to an entity

[^116]: ^K^ smooth;escape;confirm;mouse;points;add;insert;reshape;curve

[^117]: ^\#^ eddelpt

[^118]: ^\$^ Delete points from an entity

[^119]: ^K^ delete points;points;entity;erase;straighten;simplify

[^120]: ^\#^ ednode

[^121]: ^\$^ Move a node

[^122]: ^K^ move node;node;edit;end; points;distance;snap;highlight

[^123]: ^\#^ setsdist

[^124]: ^\$^ Set snap distance

[^125]: ^K^ snap;distance;node;move point;move node;polygons;default

[^126]: ^\#^ edregdig

[^127]: ^\$^ Registering a drawing on a digitizer tablet

[^128]: ^K^
    digitize;register;orient;map;trace;corners;add;draw;points;scale;rotate

[^129]: ^\#^ setupdig

[^130]: ^\$^ Setting up a digitizing tablet

[^131]: ^K^ digitizing
    tablet;keypad;puck;key;menu;SUMMA4;KEYPAD;KEYPADB;
    MENU;MENUB;CONFIG9.DIG FILE; hardware;setup;connection; serial port

[^132]: ^\#^ eddig

[^133]: ^\$^ Edit entities from a digitizer tablet

[^134]: ^K^
    edit;digitize;tablet;point;keypad;puck;key;menu;select;window;

[^135]: ^\#^ blkhead

[^136]: ^\$^ Edit a block of entities

[^137]: ^K^ edit;block;group;select;many;add;remove

[^138]: ^\#^ edselblock

[^139]: ^\$^ Select a group of entities for the block list

[^140]: ^K^ block;select;mouse;rectangle;add;remove

[^141]: ^\#^ blkadd

[^142]: ^\$^ Add or remove single entities from the block list

[^143]: ^K^ block;select;add;remove;entity;edit;mouse

[^144]: ^\#^ blkempty

[^145]: ^\$^ Remove all entities from the block list

[^146]: ^K^ block;list;remove;empty;entity;edit

[^147]: ^\#^ blkmove

[^148]: ^\$^ Move all the entities in the block list

[^149]: ^K^ move;edit;entities;block;list;many;group

[^150]: ^\#^ blkcopy

[^151]: ^\$^ Copy all the entities in the block list

[^152]: ^K^ copy;edit;block;list;edit;group;many;mass;move

[^153]: ^\#^ blkchange

[^154]: ^\$^ Change the attributes (CODE, P1, P2) of the entities in the
    block list

[^155]: ^K^ change;edit;block;list;edit;group;many;mass

[^156]: ^\#^ eddelblk

[^157]: ^\$^ Delete all the entities in the block list

[^158]: ^K^ delete;entity;block;list;edit;group;many;mass

[^159]: ^\#^ digitize

[^160]: ^\$^ Drawing new entities in the database

[^161]: ^K^ draw;new;entity;database;digitize;mouse;puck;tablet

[^162]: ^\#^ digmnu0

[^163]: ^\$^ Assign attributes (CODE, P1, P2) for entities to be created

[^164]: ^K^
    digitize;attributes;create;entity;code;p1;p2;text;line;symbol;polygons;spline

[^165]: ^\#^ digmnu1

[^166]: ^\$^ Complete point entry for new entity

[^167]: ^K^ done;finish;last;final;points;entity;digitize;draw

[^168]: ^\#^ digmnu2

[^169]: ^\$^ Complete point entry and close polygon

[^170]: ^K^
    done;finish;last;final;points;entity;digitize;draw;polygons;close

[^171]: ^\#^ digmnu3

[^172]: ^\$^ Close part of a polygon but leave entry open for more
    points

[^173]: ^K^
    done;finish;last;final;points;entity;digitize;draw;polygons;close;internal;close;

[^174]: ^\#^ digmnu4

[^175]: ^\$^ Draw special shapes

[^176]: ^K^
    draw;special;shapes;digitize;rectangle;circle;text;box;centered;bracket

[^177]: ^\#^ digmnu5

[^178]: ^\$^ Enter point coordinates from the keyboard

[^179]: ^K^ points;keyboard;type;enter;draw;entity;add;digitize

[^180]: ^\#^ digmnu6

[^181]: ^\$^ Abandon entry of points for a new entity

[^182]: ^K^ abort;error;quit;points;draw;digitize;abandon

[^183]: ^\#^ digmnu7

[^184]: ^\$^ Switch from digitizing to editing

[^185]: ^K^ quit;end ;digitize;draw;return;edit

[^186]: ^\#^ digkeypad

[^187]: ^\$^ Keypad menu for digitizing

[^188]: ^K^ keypad;menu;digitize;points;continuous;error;draw

[^189]: ^\#^ display

[^190]: ^\$^ Screen display options

[^191]: ^K^
    screen;display;options;check;information;node;verticies;grid;bearing;distance;background

[^192]: ^\#^ redraw

[^193]: ^\$^ Redrawing the screen

[^194]: ^K^ redraw;clean;refresh;repaint;draw;new

[^195]: ^\#^ dispaper

[^196]: ^\$^ Display cursor position in page coordinates

[^197]: ^K^
    page;coordinates;inches;display;cursor;position;location;mouse;paper;plot

[^198]: ^\#^ showbd

[^199]: ^\$^ Measure bearing and distance from a point

[^200]: ^K^
    measure;bearing;distance;points;mouse;digitizer;kilometers;miles;inches;length

[^201]: ^\#^ showhair

[^202]: ^\$^ Changing the cursor display to a crosshair

[^203]: ^K^ cross;hair;display;cursor;toggle

[^204]: ^\#^ shown

[^205]: ^\$^ Showing nodes

[^206]: ^K^
    display;show;node;hanging;snaped;topology;polygons;square;circle

[^207]: ^\#^ showv

[^208]: ^\$^ Displaying entity points

[^209]: ^K^ points;display;show;verticies;entity

[^210]: ^\#^ showd

[^211]: ^\$^ Displaying deleted entities

[^212]: ^K^ deleted;entities;undelete;recover;restore;show;display;find

[^213]: ^\#^ showy

[^214]: ^\$^ Display entities that are not described in the plot file

[^215]: ^K^ plot;show;draw;entities;yellow;not;described;display

[^216]: ^\#^ showg

[^217]: ^\$^ Displaying a reference grid

[^218]: ^K^ grid;display;show;cartesian;geodetic;spacing;toggle

[^219]: ^\#^ showb

[^220]: ^\$^ Showing a background database

[^221]: ^K^ background;backcover;toggle;display;show;grey

[^222]: ^\#^ showpost

[^223]: ^\$^ Displaying data from a GSPOST ascii file

[^224]: ^K^ GSPOST;ascii;table;file;show;display;100 codes;data

[^225]: ^\#^ showcolor

[^226]: ^\$^ Displaying map unit areas in color

[^227]: ^K^ Coloring areas;comment;tag;contact;floodfill;plotfile;show
    area colors;display area colors;500 codes

[^228]: ^\#^ showgsp

[^229]: ^\$^ Setting the spacing for a reference grid

[^230]: ^K^ grid;spacing;set;change;reference;show;display

[^231]: ^\#^ zoom

[^232]: ^\$^ Zooming the display window

[^233]: ^K^ zoom;display;window

[^234]: ^\#^ zoomw

[^235]: ^\$^ Defining a screen window using a mouse

[^236]: ^K^ zoom;display;mouse;button;down;drag

[^237]: ^\#^ out

[^238]: ^\$^ Changing the size of the screen window by a factor

[^239]: ^K^ zoom;out;screen;window;reduce;enlarge

[^240]: ^\#^ zprev

[^241]: ^\$^ Returning to the previous screen window

[^242]: ^K^ previous;window;screen;return;back;view

[^243]: ^\#^ zoomdb

[^244]: ^\$^ Setting the screen window to the plot file or database
    corners

[^245]: ^K^ plot;corner;database;window;view;screen

[^246]: ^\#^ all

[^247]: ^\$^ Setting the screen window to show all entities in the
    database

[^248]: ^K^ screen;window;all;extent;entity;view

[^249]: ^\#^ zooms

[^250]: ^\$^ Changing the zoom factor

[^251]: ^K^ zoom;factor;screen;window;set;change;in;out

[^252]: ^\#^ pan

[^253]: ^\$^ Panning the screen window

[^254]: ^K^
    pan;screen;window;up;down;right;left;center;view;move;arrow;key

[^255]: ^\#^ dbase

[^256]: ^\$^ Editing the database

[^257]: ^K^ edit;database;global;spreadsheet;table

[^258]: ^\#^ dbinform

[^259]: ^\$^ Displaying general information about the open database

[^260]: ^K^ database;information;projection;date;entities;scale;title

[^261]: ^\#^ dblist

[^262]: ^\$^ Listing the contents of a database

[^263]: ^K^
    list;entity;contents;database;spreadsheet;table;attributes;code;p1;p2;first;last;point;delete

[^264]: ^\#^ global

[^265]: ^\$^ Global change of entity attributes

[^266]: ^K^ global;change;attributes;code;p1;p2;entity;delete;undelete

[^267]: ^\#^ dbnewcorner

[^268]: ^\$^ Change database corners

[^269]: ^K^ change;database;corners;digitize;move;keyboard

[^270]: ^\#^ accept

[^271]: ^\$^ Using the confirmation menu

[^272]: ^K^ confirm;escape;forward;back;points;select

[^273]: ^\#^ shortcuthelp

[^274]: ^\$^ List of shortcut keys

[^275]: ^K^ shortcut;key;list

[^276]: ^\#^ projectionhelp

[^277]: ^\$^ Map projections and projection files

[^278]: ^K^ projection;UTM;conformal;mercator;transverse;radius;
    Lambert;dnag;polyconic;azmuthal; geodetic;polar;equatorial

[^279]: ^\#^ plotline

[^280]: ^\$^ Plotting lines and decorated lines

[^281]: ^K^ 001 codes;pen;600 codes;type;dashed lines;dotted lines;solid
    lines;drawing lines;plotting lines;plot file; decorated lines;color
    of lines;symbols on a line;lines;thrust;double line;phantom
    line;railroad

[^282]: ^\#^ nodehelp

[^283]: ^\$^ Nodes

[^284]: ^K^ nodes;polygons;snap;hanging;line;end

[^285]: ^\#^ dosexthelp

[^286]: ^\$^ Database file structure and standard DOS file extensions

[^287]: ^K^ ndx;nod;lsf;plt;prj;txt;dig;scr;fnt;sym;files;database
    files;extensions;file names;naming files;plot file;index file;node
    file;line segment file;text file;projection file;character
    file;ru;word file;rock unit file;binary file;file format

[^288]: ^\#^ pltfile

[^289]: ^\$^ Plot control file

[^290]: ^K^ plt;files;database files;extensions;file names;naming
    files;plot file;index file;node file;line segment file;text
    file;projection file;character file;ru;word file;rock unit
    file;binary file;file format

[^291]: ^\#^ rufile

[^292]: ^\$^ Word and character files (rock unit text file)

[^293]: ^K^ text file;geologic symbols;rock unit file;RU file;map
    text;geologic unit symbols;500 codes;700 codes;multiline
    text;character file;file;code group 500;code group 700

[^294]: ^\#^ aliaslist

[^295]: ^\$^ Geologic and other special characters

[^296]: ^K^ special geologic symbols;Triassic symbol;Pennsylvanian
    symbol;Cambrian symbol; subscripts;Paleozoic symbol;Protorozoic
    symbol;date stamp;projection stamp;database name;projection
    name;Eocene symbol, Oligocene symbol;Paleocene symbol;geologic
    symbols;rock unit file;RU file;map text;geologic unit symbols

[^297]: ^\#^ outputm

[^298]: ^\$^ Output options

[^299]: ^K^ plotter;printer;screen

[^300]: ^\#^ plotterout

[^301]: ^\$^ Plotter output form

[^302]: ^K^
    plotter;device;connection;scale;orientation;abort;pen;color;com;lpt;file

[^303]: ^\#^ device

[^304]: ^\$^ Plotter type

[^305]: ^K^ plotter;device;pen;raster;designjet;color

[^306]: ^\#^ orienthead

[^307]: ^\$^ Orientation and centering of the plot

[^308]: ^K^ plot;orientation;rotation;center

[^309]: ^\#^ connection

[^310]: ^\$^ Connection between the computer and the plotter

[^311]: ^K^ plotter;device;connection;com;lpt;file

[^312]: ^\#^ reghead

[^313]: ^\$^ Adding registration points to a HPGL output file

[^314]: ^K^ plotter;device;register;corners;points;database;plot file

[^315]: ^\#^ goplot

[^316]: ^\$^ Beginning or aborting a plot

[^317]: ^K^ plotter;begin;abort;abandon;cancel

[^318]: ^\#^ printout

[^319]: ^\$^ Printing a drawing

[^320]: ^K^ printer;pen;thick;scale;center;rotate;orientation;change
    printer

[^321]: ^\#^ scalehead

[^322]: ^\$^ Scaling a printer drawing

[^323]: ^K^ printer;scale;percent;set scale

[^324]: ^\#^ poshead

[^325]: ^\$^ Print orientation and centering

[^326]: ^K^ printer;orientation;landscape;portrait;centering;screen
    center

[^327]: ^\#^ defpen

[^328]: ^\$^ Controlling line thickness on the printer

[^329]: ^K^ printer;line thickness;set;pixil

[^330]: ^\#^ newprinter

[^331]: ^\$^ Changing the printer

[^332]: ^K^ change;windows;printer dialog box

[^333]: ^\#^ goprint

[^334]: ^\$^ Beginning or aborting printing a drawing

[^335]: ^K^ printer;start;begin;abort;abandon;cancel

[^336]: ^\#^ printrot

[^337]: ^\$^ Print the screen

[^338]: ^K^ printer;screen;paper;plot;scale;bitmap;vector;BMP

[^339]: ^\#^ screendump

[^340]: ^\$^ Saving an image of the screen

[^341]: ^K^ printer;screen image;bitmap;BMP;paint;screen dump

[^342]: ^\#^ code0

[^343]: ^\$^ Drawing entity types (CODE GROUPS)

[^344]: ^K^ line code;code groups;entity types;drawing
    entities;lines;points;text;table;pattern;hatch;polygons;digitizing
    entities

[^345]: ^\#^ code1

[^346]: ^\$^ Lines and decorated lines (CODE GROUP 1-99)

[^347]: ^K^ line code;code groups;decorated lines;line
    types;lines;digitizing lines;001 codes;thrust fault line
    symbol;faults;contacts;border

[^348]: ^\#^ code100

[^349]: ^\$^ Symbols and posting of tabular data (CODE GROUP 100-199)

[^350]: ^K^ line code;code groups;symbols;posting;tabular
    data;digitizing data points;100 codes;data table

[^351]: ^\#^ plot100

[^352]: ^\$^ Plotting symbols and posting tabular data (CODE GROUP
    100-199)

[^353]: ^K^ plot file;plotting symbols;symbols;posting data;plotting
    point values;tabular data;plotting data points;100 codes;data
    table;field notes;narrative text file

[^354]: ^\#^ code200

[^355]: ^\$^ Rotatable Symbols (CODE GROUP 200-299)

[^356]: ^K^ line code;code groups;dip symbols;strike;bedding
    attitude;plunge;anticline;syncline ;overturned bed;digitizing
    symbols;200 codes;digitizing dips

[^357]: ^\#^ plot200

[^358]: ^\$^ Plotting Rotatable Symbols (CODE GROUP 200-299)

[^359]: ^K^ code groups;dip symbols;strike;bedding
    attitude;plunge;anticline;syncline ;overturned bed;plotting
    symbols;200 codes;plotting dips;symbols;plot file

[^360]: ^\#^ code300

[^361]: ^\$^ User defined symbols (CODE GROUP 300-399)

[^362]: ^K^ line code;code groups;symbols;custom symbols;point
    marks;digitizing symbols;300 codes

[^363]: ^\#^ code400

[^364]: ^\$^ Polygons (CODE GROUP 400-499 and 800-899)

[^365]: ^K^ line code;code groups;polygons;patterns;hatch;area fill;area
    computation;400 codes;800 codes;coloring map areas;digitizing
    areas;planimeter

[^366]: ^\#^ plot400

[^367]: ^\$^ Plotting Polygons (CODE GROUP 400-499 and 800-899)

[^368]: ^K^ line code;code groups;polygons;patterns;hatch;area fill;400
    codes;800 codes;coloring map areas;plot file

[^369]: ^\#^ plot300

[^370]: ^\$^ Plotting User Defined Symbols (CODE GROUP 300-399)

[^371]: ^K^ plotting symbols;300 codes;rotated symbols;drawing
    symbols;plot file;symbols

[^372]: ^\#^ code500

[^373]: ^\$^ Text and unit labels (CODE GROUP 500-599)

[^374]: ^K^ line code;code groups;text; unit labels;leader lines;polygon
    tags;coloring map areas;tags;digitizing text;labels;500 codes

[^375]: ^\#^ plot500

[^376]: ^\$^ Plotting text and leaders (CODE GROUPS 500-599)

[^377]: ^K^ code groups;text;plotting text; unit labels;leader
    lines;labels;500 code

[^378]: ^\#^ code600

[^379]: ^\$^ Splined lines (CODE GROUP 600-699)

[^380]: ^K^ line code;code groups;curved lines;line;smooth;contour;600
    codes;digitizing lines

[^381]: ^\#^ code700

[^382]: ^\$^ Splined text (CODE GROUP 700-799)

[^383]: ^K^ line code;code groups;curved text; text, splined;700
    codes;digitizing text

[^384]: ^\#^ plot700

[^385]: ^\$^ Plotting splined text (CODE GROUPS 700-799)

[^386]: ^K^ code groups;text;plotting text; splined text;plot file;700
    codes

[^387]: ^\#^ code900

[^388]: ^\$^ Profile lines (CODE GROUP 900-998)

[^389]: ^K^ line code;code groups;profile lines;line;contour;900
    codes;digitizing lines;cross section;profile;topography;section; 3-D
    lines;generating profile database;contour interval

[^390]: ^\#^ getstart

[^391]: ^\$^ GETTING STARTED

[^392]: ^K^ code groups;text;plotting;digitizing; plot file;How to start
    a project;starting; jumpstart;cookbook;beginning;new
    project;create;getting started