Miscellaneous Notes
NOTE #1. Make Input File
Creating an input file from a previously stored chain or profile may be useful for a number of reasons. Sometimes you may want to create an ASCII text file of a stored chain or profile, edit it, and reload it into your GPK file or load it into another GPK file. The process is explained below:
Given: A previously stored profile named "VERTMAIN"
Desired: An ASCII text input file named "VERTICAL".
In the COGO Key-in field, type... MAKE INPUT FILE VERTICAL261.ISP PROF VERTMAIN
Note:
The "261" is the JOB NUMBER.
The "SP" is the OPERATOR CODE.
Once the file is created, it can be modified with any text editor, such as UltraEdit.
Once the modifications have been made, use the COGO pulldowns, FILE > File Utility, as shown below:
The File Utility window appears as shown below. Highlight the file to Load select Load from the combo box and click on Apply.
The Coordinate Geometry dialog will show that the input file has been loaded. At this point the data is only in memory.
To store the data from the input file into COGO it must be Read. Using the COGO pulldowns, select Edit > Read All, as shown below:
The data (and subsequent profile) has now been stored (or updated) into COGO, as shown below:
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 Chain 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: job261.gpk.
name###.ioc
This is an ASCII text 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: HA1261.isp
j###ooc.inp
This is a special COGO input file that is created the first time that either
Store Chain or Create Existing Ground Profile is used.
This file is appended automatically as each of these tools are used during
the design process.
Example: j261osp.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 > File
Utility, then select Output from the File Utility dialog
or simply typing Out [name], in the COGO command window.
The only variable is the "name" that the user assigns.
Example: HA1261.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", earthwork, etc...
Example: V8_Earthwork.inp.
name.dat
This is an input file for generating topographical surfaces, (DTM input
file) The only variable is the "name".
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".
Example: site_1.tin
NOTE #3. Miscellaneous (Project Manager) file extensions:
.012 - Superelevation
.014 and .b14 - Plan / Profile Sheets
.003 - Proposed Cross Sections
.00d - Existing Ground (DTM)
.004 - Earthwork
.00c - Limits of Construction
.005 - Cross Section Sheets
.00e - Existing Ground Cross Sections
.008 - Define (Working Alignment)
.00f - Reports and XS Quantities
.009 - Existing Ground Profile
.010 - Model
.00a - Vertical Alignment
.011 - Draw Patterns