The ".arc" file is located in your user directory and runs whenever you start ARC/Info. You can insert these commands to create shortcuts and streamline your typing in ARC/Info:
&setvar .hja = &workspace /data/cascade/hja27
- set a variable that will jump to
a new workspace; at the ARC> prompt, typing "hja" will change workspaces to /data/cascade/hja27
&amlpath /data/gisinfo/aml
- define a path to a directory where
amls are stored
&atool /users/geo/atool /tools/esri/atool
- define one or more paths to the location of atool directories
&setvar .des = describe
- use abbreviated variables that shorten commands
that are awkward to type.
&abbreviations &on
- should also be included
if you use abbreviations.
- NOTE: watch for abbreviations that are the same as
system commands
display 9999 size canvas 700 690
- sets up graphics
&terminal 9999 &mouse
- sets up graphics environment for menus window
barscale - creates a simple bar scale in a map composition
Usage: barscale <num_units> <output_units> <AUTO | ticsize> <* | xy>
Example: barscale 10 KM AUTO 5.5 4.2
scalebar - creates a more complex professional looking barscale
Usage: scalebar BOX <* | xmin ymin xmax ymax> {units} {BLOCKS} {TENTHS}
CENTER <x y> <width height> {units} {BLOCKS} {TENTHS}
Example: scalebar center 5.5 4.2 0.35 KILOMETERS BLOCKS
inkjet - creates .rtl output for the HP 650 inkjet printer
Usage: inkjet {rootfilename} {page_width} {page_height} {rotate_plot}
Example: inkjet testplot 30 24 1
NOTE: inkjet works on map compositions, graphics files, and postscript files with extensions .cmp, .gra, .eps or .ps respectively. These extensions are not required in the command argument. However, enhanced postscript files from ArcView will not work. Users are prompted for input if arguments are not used.
listmaker - scans workspaces and creates a listing of coverages, grids, and.img files
gridspot - captures values in a grid underlying point locations
Usage: gridspot <grid_name> <point_cover> {spot_item}.
fsldoc - tool for assisting users in developing spatial data documentation
plstool - this tool converts Public Land Survey System data (Range, Township,Section, etc) to point locations in UTM or Lambert (or a projection of your own choosing). The input file must be formatted quite specifically - see /data/gisinfo/aml/plspnt.aml.doc for details. The output file is in arc generate format.
slopeposition - creates a grid of slope position from a grid of elevation. Values in the output range from 0 (valley floor) to 100 (ridgetop).
Usage: slopeposition <in_grid> <out_grid> {sink_fill_limit} {peak_fill_limit} {valley_accum_min} {ridge_accum_min}
autolist.aml - this short aml loops through a list of coverages to perform repetitive tasks. It's especially useful for killing a bunch of coverages. Make a copy of the aml and edit it to include the processes you need to perform.
NOTE: one easy way to create a coverlist file is to make use of the [filelist] function from aml: &setvar num = [filelist * coverlist -cover] creates the file coverlist and includes all coverages in the workspace.
Projection files - many useful projection files for Oregon are located in /data/gisinfo/projections.
Symbol sets are located in $ARCHOME/symbols. There are a number of new sets in ARC/Info 7.1.2.
Avoid using capital letters when naming coverages or subdirectories. We are finding more commands in ARC/Info that choke on caps.
Projections - on some occasions we have been stumped moving among projections, datums, and spheroids. Here is a process that will produce the appropriate projection for some data sets we use.
Arc/Info provides the DOCUMENT atool as the primary method of coverage documentation. Metadata is captured in info files that remain associated with the coverage through all sorts of processing including RENAME and EXPORT. Using DOCUMENT will assure FGDC compliant metadata. However, the menus of the tool lead the documenter to the spot we consider to be the most important and then essentially dump the user into the VI editor and say "Type away". This does not encourage very much data set documenation.
NOTE: FGDC is reviewing their standard and will likely develop a smaller core set. ESRI is apparently revising the DOCUMENT tool to match the standard modification - let's hope it turns up in version 8.
Meanwhile, we believe that metadata are the key to immortality. We have developed our own custom atool - fsldoc - that captures what we believe are the essential items associated with a GIS data set. The menus in fsldoc support documentation for coverages, grids, info files, arc macro language programs (aml), and arcview projects. The documenter is prompted for input, including the codes for the items in the feature attribute table. The output is written to ascii files, which can easily be edited in your favorite text editor; but which do not travel well with moving coverages or persist through exports or name changes. We anticipate that the documentation accomplished through fsldoc will eventually be folded in with the products of DOCUMENT.
To run fsldoc, you must be in the version 7+ workspace where the coverages or files reside. Any coverage or grid being documented must have a projection defined.