1. © 2008 Bentley Systems, Incorporated GEOPAK Corridor Modeling Midwest DOT Roundtable October 21, 2008 Kansas City, MO

2. GEOPAK Corridor Modeling Review of Past Year Training Materials Corridor Modeling Overview New Enhancements in Athens On-line Content User’s Group Training Top User Questions

3. Review of Past Year Met in Sunrise (Oct. 1-3, 2007) KC Roundtable (Oct. 16, 2007) Roadway Designer Runs in GEOPAK (Dec., 2007) Deliver CM in XM 08.09.06.31 (July, 2008) Deliver CM Training Course (July, 2008)

4. Training Materials 1 st Class taught to Support (Aug., 2008) Already taught to NCDOT and several consultants

5. Applications > Road > 3D Tools > Corridor Modeling Corridor Modeling Overview

6. When you first open the Corridor Modeling (CM) application, a new sub-folder is created under your working directory. \rddbs This folder is where any files are created that are used exclusively by the CM application. Corridor Modeling Overview

7. GPK Job Selection Corridor Modeling Overview

8. Station Lock – Controls how the cross section interval is calculated in the Roadway Designer application. Slope Readout – Controls how the slopes are displayed to the user in the Create Templates and Roadway Designer applications. Horizontal Chord Height – When creating surfaces, controls the processing through horizontal curves. Vertical Chord Height – When creating surfaces, controls the processing through vertical curves. Template Library – Designates which template library CM applications will use. Preferences

9. GEOPAK delivers a ‘default.itl’ template library in the /bin directory which is used by default. The configuration variable GPK_RD_Template_Library can be used to specify another template library to use. Preferences – Template Library

10. Imports Drafting Standards from the DDB which are used to control symbologies within CM. You will also see these Drafting Standards called “Styles”. They are synonymous with one another. DDB

11. In XM, only the ‘Drafting Standards’ items in the DDB will be imported. These items are denoted with the ‘paintbrush’ icon. DDB

12. This area has been enhanced to now also allow the importation of Default standards as well. NEW in Athens

13. A ‘default_styles.ddb’ file is delivered in the /bin directory and used by default. The configuration variable GPK_ACBOOK_DDBFILE_STYLES can be used to specify another DDB to use. DDB

14. When the Drafting Standards are imported, a new file is created in the \rddbs subdirectory. This file uses the same name as the DDB but with an.XIN extension. Default_styles.ddb  default_styles.xin DDB

15. If you prefer that each user NOT have to import the DDB and create the.XIN file locally, you can point to a global.XIN file using the following configuration variable: GPK_ACBOOK_XINFILE_STYLES Note that the use of this variable will remove the ‘DDB’ option from the dialog. NEW in Athens

16. In order to use TIN files in CM, we have to import them. When you import a TIN, a new file will be created with the same name but using a.DTM extension. fm314.tin  fm314.dtm DTM

17. You can add both TIN and DTM files in the list box. Multiple files can be listed and imported simultaneously. DTM

18. Important! Only files that are listed in this list box will be available in Roadway Designer. DTM

19. Chains and profiles from the GPK must be imported into the CM application. Geometry

20. When the geometry items are imported, a new file is created in the \rddbs subdirectory. This file is named by taking the gpk name and adding a ‘cm’ prefix and.alg suffix. job314.gpk  cmjob314.alg Geometry

21. When geometry data is imported, a drafting standard is always assigned to it. Later, you can build templates to target the chains/profiles by their name or by the name of the drafting standard/style. Geometry

22. Since Roadway Designer does not read directly from plan graphic elements, we need a way to make the application aware of our graphics. We can do this by using the Plan Graphics import feature. Plan Graphics

23. We can read the plan graphics based on Symbology, a DDB Feature or a MicroStation Selection Set. Plan Graphics

24. When using Symbology or Feature, we can setup a ‘search corridor’ based on a chain name, a side and a beginning and ending offset. Plan Graphics

25. If our plan graphic doesn’t fit nicely into a search corridor, we always have the Selection Set option. The user can just place any elements into a MS Selection Set and add them to the list. Plan Graphics

26. Once all of our items are setup in our list box, we can import them. The resulting alignments are stored in the.alg file. Plan Graphics

27. We’ve added Filter Tolerances to the dialog. NEW in Athens

29. Data in the geometry database has a tendency to change throughout the life of a project. With that in mind, we need some way to keep our data in synch between the.gpk and the.alg. In order to facilitate this, there is a functionality built into the Corridor Modeling application called Smart Update. Every time you open Corridor Modeling, it checks the data in the gpk against data previously imported into the.alg. Smart Update

30. If a chain or profile has been modified in the gpk and is out of synch with the.alg, it will show up in blue. If a chain or profile has been deleted from the gpk and is out of synch with the.alg, it will show up in red. Smart Update

31. Any data in blue should be re-imported to update the.alg. Any data in red should be deleted from the list box. This will also delete the item from the.alg. Smart Update

32. Similar to the geometry, the plan graphic data also has a tendency to change throughout the life of a project. The Smart Update functionality also works with the Plan Graphics. Every time you open Corridor Modeling, it checks the plan graphic data in the design file against data previously imported into the.alg. Smart Update

33. If a plan graphic has been modified in the design file and is out of synch with the.alg, it will show up in blue. If a plan graphic has been deleted from the dgn and is out of synch with the.alg, it will show up in red. Smart Update

34. Any data in blue should be re-imported to update the.alg. Any data in red should be deleted from the list box. This will also delete the item from the.alg. Smart Update

36. Now that we have our data imported, we are ready to step into the CM workflow. The first step is to access our Create Template application. Corridor Modeling Overview

37. Create Template opens using the template library (.itl) specified in our preferences. The template library is composed of Components, End Conditions and Templates. Create Template

38. Components are individual “pieces” that can be assembled into a template. They consist of things like pavement, shoulders, curb, walls, etc.. Create Template

39. End Conditions are simply a special type of component that serves as the terminating point of the template. Create Template

40. Templates are a combination of components and end conditions that have been assembled to represent a particular roadway condition. Create Template

41. When components and end conditions are created, their individual elements are assigned styles (drafting standards). This controls how the elements are displayed. In the example here, this one component employs three different styles. Create Template

43. Once our templates are complete, we can move into the next application in our workflow, Roadway Designer. Roadway Designer

44. We create a corridor based on an alignment and profile. We can create one or multiple corridors for our project. Roadway Designer

45. Next, we drop templates along our corridor based upon a specified beginning station and a specified interval. You can drop a single template or multiple templates depending upon the configuration of your project. Roadway Designer

46. The application is divided into 3 views – Plan, Profile and Cross Section. This is very similar to GEOPAK’s 3-Port Viewer. Roadway Designer

47. In addition to the cross sections at stations generated by the given stations and increments of the template drops, you also have the capability under the Roadway Designer Options to include Critical Sections. Horizontal Cardinal Points  PI, PC, PT, etc. Vertical Control Points  VPI, VPC, VPT, etc. Roadway Designer

48. External Control Points – If a template targets an alignment (e.g. wall, ditch, etc.), then enabling this option will pick up all the critical points (PI’s, PC’s, PT’s, etc.) along this “external” alignment and include them as cross section locations. Roadway Designer

49. You also have the ability to generate stations at any location that you need. These are called Key Stations. These might occur at culvert crossings, driveway locations, etc.. Roadway Designer

50. For the GEOPAK version of Roadway Designer, we have added the ability to import your superelevation directly from the GEOPAK shape input file. Roadway Designer

51. When you are at the point in your design when you are ready to create a finished model, you can do so through the Create Surface dialog. This will result in the creation of the proposed surface (.DTM) and an associated XML file. Roadway Designer

52. The Display Features in Plan View option will result in the model being drawn into your design file. Roadway Designer

53. Your Roadway Designer session and all of it’s associated settings can be saved in an.IRD file. Roadway Designer

55. You can use the Drive Roadway application to review your completed model. Drive Roadway

56. This application allows us to ‘drive’ down our model using a specified camera location and speed. Drive Roadway

58. When our model is complete and we are ready to process proposed cross sections, we can do this through the Draw Cross Sections from Surfaces application. Draw Cross Sections

59. There has been no change to the XS Cells portion of the dialog. You can cut sections from a proposed surface (.DTM) exactly as you can from an existing surface (.TIN). Draw Cross Sections

60. On the Surfaces tab, you’ll notice the addition of a Dtm File option along with the standard Tin File option. Draw Cross Sections

61. You can cut existing sections from the.DTM file that was created when we imported our existing.TIN file. The existing sections will be generated using the symbology specified on the dialog. This works exactly the same as it would if you were using a.TIN file. Draw Cross Sections

62. The proposed surface (.DTM) can be added the same way. Draw Cross Sections

63. Even though the symbology is added to the list box along with the proposed surface, it will not be used. The proposed sections will be displayed using the styles specified in the templates. Draw Cross Sections

64. The Update Options do not work with.DTM files in the current version. This functionality will be added in a future release. Draw Cross Sections

65. When the sections are processed, the point names (from the template) are placed on the sections. Draw Cross Sections

66. The text is placed using the Active Text Attributes from the design file. Draw Cross Sections

68. The last step in the process is to label our sections. We can do this with the Cross Section Labeling application. Cross Section Labeling

69. The first tab is the General tab. It controls the range of stations that will be labeled. Cross Section Labeling

70. The Slope Label tab allows you to build slope labels. This is done by specifying point name text locations previously placed on the section. Cross Section Labeling

71. Likewise, elevation and offset labels can be generated via the Elev/Off Label tab. Cross Section Labeling

72. Delimiters have been added. NEW in Athens

73. Clicking the Draw Labels button on the General tab will process the labels. Cross Section Labeling

74. Settings can be saved to a preference file (.XLP). The idea is that the point name text will be consistent from project to project. So you should be able to load and use a standard.XLP file instead of re-generating these labels from project to project. Cross Section Labeling

75. The Cross Section Labeler application was deliberately created as a VBA application so that it could be edited by any user to add customized labels. The xslabeler.mvba can be found in the /bin directory. Cross Section Labeling

77. Corridor Modeling help can be found in the GEOPAK help files. Help

78. In addition, individual dialogs in Create Template and Roadway Designer all have Help buttons located in them. Help

79. Enhancements in Athens Corridor Modeling > Import DDB … Added the ability to specify a global XIN with the addition of the configuration variable GPK_ACBOOK_XINFILE_STYLES Corridor Modeling > Superelevation … Added support for Texas DOT parabolic transitions in Roadway Designer superelevation. Corridor Modeling > Import DDB … Added the ability to import Default features. Corridor Modeling > XS Labeling … Added support for delimiter lines. Corridor Modeling > Plan Graphics … Added support for filter tolerances. Corridor Modeling > XS Labeling... Previous limit of 20 labels increased to 50.

80. On-Line Content GEOPAK http://communities.bentley.com/Wiki/view.aspx/GEOPAK _TechNotes_And_FAQs InRoads http://communities.bentley.com/Wiki/view.aspx/InRoads _Product_TechNotes_FAQs_And_Support_Video_Clips

82. Top User Questions Turn Lanes Special Ditches Superelevation Driveways Overlay & Widening Adjacent Roadways Machine Control Earthwork Future of Criteria

83. Machine Control

85. Overlay & Widening

88. Turn Lanes Irregular Pavement

90. Special Ditches

92. Superelevation

93. Importing GEOPAK Shape Input Files

95. Using Superelevation Wizard

97. Shoulder Rollover Locks

99. Superelevation Control Lines

101. Driveways

103. Adjacent Roadways

104. Target Aliasing

106. Corridor Points

108. Point Controls

110. Earthwork

112. Future of Criteria Criteria will be fully supported and maintained for the foreseeable future. There will be no major enhancements to it, but then again there really is not much more we can do to it anyway.

113. © 2008 Bentley Systems, Incorporated GEOPAK Corridor Modeling Midwest DOT Roundtable October 21, 2008 Kansas City, MO