GEOPAK Help and Tips

Check Angle Macro

This is an example of using a MicroStation macro to perform the tedious yet arguably critical checking of alignment data. This macro will read a GEOPAK Coordinate Geometry output file that contains the description of a chain. It will then compare the direction (Bearing or Azimuth) of each tangent and curve to ensure that no non-tangent curves are defined in the alignment. Two text files are created as a result of running the macro: the checkangle.err file will contain only direction mismatches while the checkangle.log file will list the direction of each component of the chain relative to the next element.

1. Download the macro checkang and copy to the following folder: \Bentley\Workspace\ standards\macros.
2. Create an output file containing the describe chain command of any chain.
3. Start the macro by clicking Utilities > Macro from the MicroStation pulldown menu. Checkang will appear in the list box. Highlight it, then click Run.
4. The macro will first prompt for the COGO output file from step 2.
5. The next dialog prompts for the desired tolerance value for comparing the bearings. Select an acceptable tolerance and click OK.
6. Upon completion, a Notepad window will open the checkangle.err file showing the results. As noted, a checkangle.log file is also created listing directions of each successive component.

This macro was originally created by Don Knoedel of FHWA’s CFL division, and modified by James Hogenson of Illinois DOT’s District 2 office. The new Check Angle Macro is available for download here.

Customizing MicroStation Toolboxes

Problem: Inability to customize your MicroStation Toolboxes while GEOPAK 2001 is active.
Resolution: In GEOPAK 2001 there is a file in the bin directory called gpk2001.toolbox, a toolbox resource file that contains the icon definition and the associated command dispatcher. You will need to follow the instructions below to get the toolbox to work:

1. Move gpk2001.toolbox under your workspace, for example (Bentley\MicroStation\Interfaces\Workspace\Default).
2. Rename this file as ustn.m01.
3. Start GEOPAK 2001.
4. Now, deactivate GEOPAK. This step is very important.
5. In, MicroStation, go to Tools > Toolboxes...
6. Press New... and enter your toolbox name, for example "My Special Tools".
7. On the Customize tab you will see choices of Tool Frames or Tool Boxes. Select the Tool Boxes tab.
8. On the Available Tools from combo box, select default. Note: If in Step 1 you placed this file into another workspace, you must select that workspace name.
9. You should now be able to scroll down and see the GEOPAK toolbox names. You will see four occurrences of Plans Preparations because there is one for Road, one for Site, one for Survey and one for CivilPAK. Pick any one of these and select the desired icon, for example Plan View Labeler. Now you can press the Copy button to build your own toolbox as you copy over more and more icons.

   Note: What will happen at this step if you did not deactivate GEOPAK in step 4? You will see eight occurrences of these toolboxes — four from the resource file gpk2001.toolbox and four from the running version of GEOPAK. This will be confusing and if you mistakenly select an icon from the running version, the icons will result in irresolvable ID or errors.

10. After you are done composing the icons, you can move up and down, or rearrange these icons in the toolbox.
11. Save your work and exit MicroStation.
12. In the directory now you should see ustn.m02. This is the file you should use and distribute to other users. We advise that you delete the ustn.m01 file and use this instead. You can then rename this file to ustn.m01 or ustn.p01 or ustn.s01. Each one has different priorities during startup. If you do not maintain multiple workspace files, then keep it as ustn.m01. Also, you can keep the original ustn.m01 file stored elsewhere in case you want to modify it later.

This file can also be copied to a non-GEOPAK machine and it will not cause any error on MicroStation startup. If you press the icon it will say "Unable to load PLANVIEWLABELER".

GEOPAK Civil Engineering Suite 2000

Q: The control points of my survey have been altered. How can I update my TIN file?
A: From the Load DTM Features dialog, draw the triangles into a 3D MicroStation design file. Utilizing the MicroStation Move command, relocate the triangles to the desired location. Lastly, Extract these relocated 3D triangles and Build new triangles.

When using the COGO Best Fit tool, make sure the Max Shot Distance preference is set correctly. This preference should be set so that no two points are farther apart than the distance specified in this preference. The program uses this Max Shot Distance when determining the order of the candidate points.

In response to many user requests, in GEOPAK 2000, cells are brought intact into cross-section sheet layouts rather than being dropped in as MicroStation base elements. Be aware, though, that since a cell by definition is on level 0, you are no longer able to control the cells through level symbology.

The cells are now controlled only by the “type=cell” syntax. For example, if you want the cells brought over you would simply specify “type=cell,line,line_string, etc.” Unfortunately, this is an all-or-nothing function. You can either specify to bring all cells over (Important note: the GEOPAK cross section cell is automatically left out) or none at all.

Some users have reported that their Criteria runs fine in GEOPAK 98, but when they attempt to run it for the first time in GEOPAK 2000, they are receiving the following syntax error:

%XS-E-INVIEI. Invalid sequence of ‘IF/ELSE IF’ statements.

‘IF’ statement must precede an ‘ELSE IF’ statement for a sequence of ‘IF/ELSE IF’ statements.

The reason for this is that GEOPAK 98 would sometimes let you get by if you had a bracket out of place or perhaps an incorrect if/else statement. In GEOPAK 2000, GEOPAK tightened up the syntax checking so that errors that used to slip through are now caught. If you encounter these and are using agency-supplied Criteria, you should contact the agency to get updated Criteria. If it’s your own Criteria, please call the GEOPAK Help Line at 1-888-GEOPAK1 and we’ll be glad to help you resolve syntax errors.

You can label the VPC and VPT points on a profile with a VPC and VPT prefix?

In the Design & Computation Manager > Profile setup, access the VPC/VPT Label option. In the prefix field, key-in the following: ~c~ + any other desired prefix.

Did you know?

1. You can display the side slopes of objects in a site model.

   Object displays can be achieved separately from the model or the original ground. Select Object > Edit. On the Slopes tab, you will find the toggle to turn the slope display On or Off. Then select the Display tab and set your display to the symbology of your choosing.

2. You can automatically find the top or bottom of a site object, such as a pond.

   Once you have a starting elevation, known point, boundary areas, etc., select the Element > New/Edit tool. Here you will find the Side Slope tab. This tool will create new graphic elements at automatically computed locations based on your supplied constraints.

3. You can determine what is and what is not visible from any given vantage point within a GEOPAK Site model.

   Simply utilize the new Analysis > Visibility tool. By selecting your vantage point within the model, set the height above any surface and press Process. The resulting diagram will display all visible and non-visible locations within the model.

Q: How can I copy a preset text from one field to another within the Bar Labeling dialog?
A: Highlight the preset text in the reference field and select the text with the Ctrl + C keys. Next place your cursor focus in the destination field and press the Shift + Insert keys.

Tip

Having problems selecting the Start/End of Longitudinal Bar Group with the Indicated Ends setting? This is a problem with MicroStation version 7.01.01.36. Upgrading to version 7.01.01.57 and higher corrects the problem.

General

Windows NT 4.0 Nagling Problem

If you are having problems with small file operations that once took seconds but now take minutes or longer to process, this may be a Windows NT Service Pack 6.0 issue. As reported by Microsoft, programs that perform numerous small file operations, such as lock and unlocking files or writing small records, can experience slow performance. This problem can be resolved by obtaining the latest service pack for Windows NT 4.0.

More information on Nagling can be found here.