---SPECIAL NOTES---

NOTE #1.

It is possible to make an input file from a previously stored chain or profile. A detailed explanation can be found in "Civil Geometry", Part I, Chapter 5, Page 5-32 in the Geopak 2001 Manuals.

EXAMPLE:

If you wanted to make an ASCII file of a stored chain or profile, edit it, and reload it into your GPK file, (for example) do this:

Given: A stored profile named "VERT"
Desired: An input file named "VERTICAL".

In the COGO Key-in field, type... MAKE INPUT FILE VERTICAL123.ISP PROF VERT

Note:

The "123" is the JOB NUMBER.
The "SP" is the OPERATOR CODE.

To then edit this input file...access Window's Explorer, select the input file, associate it with an editor, such as NOTEPAD or UltraEdit-32 and edit your input file, (in this case VERTICAL123.ISP). Save the file. Using the "Coordinate Geometry" dialog box, click on FILE and click LOAD. This brings up the "Load" window. A file named VERTICAL (in my example here) should appear.

Click on your file and click OK.

You will see the loaded file in the "Coordinate Geometry" dialog box, but it hasn't actually been READ yet. To READ the file, (which in turn will restore the profile) click on EDIT, click on READ, and click on ALL. Now the new profile has been restored by reading the edited input file that you created.

NOTE #2.

NAMING CONVENTIONS...

job###.gpk
This is created when the user starts a Coordinate Geometry (COGO) session for the first time, or uses Store Graphics for the first time. This file may also be appended during the design process. All coordinate geometry data is stored in this data base file. The ### is the only variable in this name. It represents a job number unique to a project and is defined by the user upon creation. Example: job123.gpk.

name###.ioc
This is an input file used for loading data into the GPK file during a COGO session. The ### represents the job number (gpk file to receive the data for storage) and the "oc" represents the "operator code", usually the user's initials. The only variable is the "name" that the user assigns. Example: HA1123.isp

j###ooc.inp

This is a special COGO input file that is created the first time that either Store Graphics or Create Existing Ground Profile is used. This file is appended automatically as each of these tools are used during the design process. Example: j123osp.inp.

name###.ooc

This is an output file created by GEOPAK during a COGO session. The file can be created by using the COGO pulldowns File > Output or simply typing Out [name], in the COGO command window. The only variable is the "name" that the user assigns. Example: HA1123.osp would result from typing OUT HA1

name.inp

This is the simple naming convention for any input file used in conjunction with the Geopak Process Cross Sections tool. These would include input files for creating "auto shapes", proposed cross sections, earthwork, etc... The only variable is the "name". It is user defined and can support 1-8 characters.
Example: PRXS_09.inp.

name.dat

This is an input file for generating topographical surfaces, (DTM input file) The only variable is the "name". It is user defined and can support 1-8 characters. Example: site_1.dat

name.tin

Binary DTM file created from processing the .dat file used for all surface computations and creating things such as contours. The only variable is the "name". It is user defined and can support 1-8 characters. Example: site_1.tin

Back to The Complete Knuckleheads Guide