Paving the Way for Roadway Designer in GEOPAK V8 i ( SELECTseries 1 )

1. Paving the Way for Roadway Designer in GEOPAK V8i (SELECTseries 1) Presented By: Chuck Lawson, PE

2. Corridor Modeling Dialog • Preferences • Parameters for setting up how Roadway Designer tools will operate • DDB • Imports drafting standards from a DDB file into a XIN file. • DTM • Imports the selected TIN or DTM file or files • Geometry • Imports various types of geometry data from the selected GPK file • Plan Graphics • Stores plan view graphical elements • All settings get saved to a RDP file

3. Standards - Introduction To Styles • A collection of standards used to assign symbologies to DGN graphics • Controls the symbologies of both plan and cross section DGN elements from Roadway Designer and the Draw Cross Sections from Surfaces application • Stored in a LandXML file format with a “*.XIN” file extension • The XIN file is generated through the importing of a Design and Computation Manager file (DDB file) within Corridor Modeler

4. Styles – Preparing the DDB • The XIN import creation process converts all items in the DDB file set to “Default” or “Drafting Standards”

5. Styles – Preparing the DDB • Only placement symbologies are utilized • Adhoc Attributes, Supplemental Search Criteria, Attributes, Class, and Cell Name are all ignored

6. Styles – Preparing the DDB • The “Item ID” converts to the Style Name in the XIN file. The “Description” field is ignored.

7. Styles to Include • Cross Sections • Pavt Layers • Slopes • Sidewalks • Etc. • Plan Graphics stored as ALG Alignments • Edge of Pavements / Shoulders • Sidewalks • Any plan graphic not parallel to the baseline that needs to control the template • Style Targets • Special ditches • Backs of entrances

8. Setting the DDB Location • The DDB file is not “Selectable” in the Corridor Modeler Dialog. There are two options: • By default, the example DDB file installed with GEOPAK will be used. • Alternatively (Recommended), a configuration variable may be set, pointing to the DDB file to use. GPK_ACBOOK_DDBFILE_STYLES = S:\Stds\Styles.DDB

9. Setting the XIN Location • Once the DDB file is complete and an XIN file generated, the DDB import process may be removed from the Corridor Modeler Dialog. • A configuration variable is used to point directly to the XIN file. No DDB option will be seen in the Corridor Modeler application when this variable is set. GPK_ACBOOK_XINFILE_STYLES = S:\Stds\Styles.XIN • Good way to enforce Company / Agency standards

10. Setting the XIN Location • Setting the variable to point to the XIN file removes the DDB category from the Corridor Modeler application.

11. Example – Creating the XIN File • When the DDB file is imported, an XIN file will be created and stored in the RDDBS subfolder under the Working Directory. • Let’s look at an example…

12. Example - Creating the XIN File

13. Styles for Plan Graphics • Styles assigned to Point Properties in Templates, control the symbology of 3D plan graphics

14. Styles for Plan GraphicsPoint Properties Example

15. Styles for Cross Sections • Styles assigned to Component Properties in Templates, control the symbology of all cross section elements

16. Styles for Cross SectionComponent Properties Example

17. Targeting Styles “Drafting Standards” • Styles or “Drafting Standards” can be targeted within the point properties of a template component • Especially useful for multiple special ditch profiles

18. Targeting Styles • The Style Constraint within the Point Properties provides the ability to target a Style • The Range sets a maximum search distance

19. Targeting Styles - Example

20. Editing the XIN Styles File • The Styles XIN file is an XML file. It can be modified by updating the DDB file and re-importing.

21. Example - Editing the XIN Styles File

22. Editing the XIN Styles File • Alternatively, the XIN file can be edited in any XML editor such as Altova XMLSpy.

23. Editing the XIN Styles File • Special feature. If editing the XIN file in an XML editor, access to the “Filled” field is available. Setting this to 1, makes the components appear filled or “shaded” in Roadway Designer.

24. Template Point Names • Point name standards are vital to Roadway Designer and trouble free transitions / surface creations. • Establish a standard and stick to it (enforce it). • Point names are used throughout the entire process: • Component Creation • Surface Creation • Transitioning • Point Controls • Superelevation • Cross Section Labeling

25. Template Point Names • The Point Name list should be developed before creating any components. • This allows the Styles to be “pre-assigned” to the point names.

26. Template Point Names • Point names are used to establish the feature names within the DTM model.

27. Template Point Names • Point naming conventions should be standardized and compliance enforced within your organization. • Example: • Component_Type_Location_Quantity_Display_Misc

28. Template Point Names • Point naming consistency between templates allows transitions to complete automatically.

29. Template Point Names • Point names are vital to setting point controls.

30. Template Point Names • Point name prefixes / suffixes should only used creating templates and not in the Point Name List.

31. Component Naming • Component naming is recommended to be consistent with the material type. • Used for displaying components • Component display rules • Displaying templates • Material quantities • Etc.

32. Component Naming • Component names are used when creating / using Component Display Rules.

33. Component Naming • Component names are used within the Display Templates application for creating typical sections.

34. ITL Folder Library • Use the template library folder structure to organize the workflow and minimize the “search”

35. ITL Folder Library • There are infinite possibilities and no right or wrong answer. Just keep it logical. Possible scenarios: • Organize by design speed • Organize by road classifications (rural, urban, highway, etc.) • Organize by design standards • etc

36. ITL Folder Library Location • Centralize a Master Copy of your standard Template Library file. • Store on Server with read and copy only access • Provides a starting point for users • Allows users to copy to their working directory

37. Template Library Organizer • The organizer allows a user to copy templates from one template library to another

38. Template Library Organizer • The organizer allows a user to copy templates from an IRD design file to an ITL file

39. Template Documentation Link • Use the Template Documentation link to point to help files for each template. Remembered in the ITL File. Uses right mouse click.

40. Superelevation (SE) • Use the Table Wizard to input general SE data Uses different SE look up tables than the GEOPAK Shape tools. The rate table has an .SUP extension Tables are setup one time • Import SE Rates as defined by the GEOPAK Automated Shape Tool Template EOP’s must match up No table editing available

41. Superelevation • Editing a SUP file Add any curve data and it’s associated super rate for any design as speed as required

42. Template Point Names Questions?