CTDOT CONNECT DDE GUIDE VOLUME 1 - OVERVIEW

   4.4 Converting from V8i to CONNECT

All preexisting *.dgn files will need to be recreated with CONNECT seed files for geospatial accuracy and proper working units. Certain traffic signal modification projects involving no other disciplines are exempt.

USING EXISTING V8i SURVEYS

ROADWAY PROJECT DGN FILES

ROADWAY TEMPLATE LIBRARY FILES

TRAFFIC SIGNAL MODIFICATION PROJECTS

USING EXISTING V8i SURVEYS

A converted survey will consist of two *.dgn files.

1. The original existing ground *.dgn file - to be used as is and properly referenced into the design.

When referencing the existing ground *.dgn, turn true scale off and set the scale to 1:1. Attachment properties for global line style scale may differ from project to project for various existing ground *.dgn files. Users should visually determine the required setting and set it either to Master or Reference. See image below.

The Scale Line Style By Reference Scale button should be toggled on.

2. An OpenRoads CONNECT Edition terrain file - converted from an InRoads *.dtm. The Design unit must request that the Survey unit convert the preexisting *.dtm to a *.dgn terrain.

ROADWAY PROJECT DGN FILES

• DO NOT copy *.dgn files created with the SELECTseries DDE (or any older file) to the new CTDOT CONNECT WorkSet (project) folders.
• DO create all new *.dgn files using seeds from the CTDOT CONNECT DDE. 
• Temporarily reference SELECTseries *.dgn files, align them geospatially, copy in needed line work, and modify line work to use the new element templates and levels.
• There are geometry import tools available in ORD to bring in old InRoads *.alg geometry. Be sure to set the horizontal and vertical feature definitions to centerline.

» Base Models

All civil design disciplines should create base models for their proposed design, as design elements drawn in a sheet model and drawing model will not be accepted. All design elements need to be in their proper geospatial location using the Geographic Coordinate System that matches the project’s survey files. For more information go to Volume 2, Module 1 - Working with Geographic Coordinate Systems. SELECTSeries *.dgn files with plan view graphics should be temporarily referenced into the new CONNECT CAD files, properly scaled and aligned geospatially. Users will need to copy in the needed graphics and modify them to use the new levels, element templates and/or feature definitions. The SELECTSeries *.dgn reference files will need to be detached after the graphics are properly copied.

» Contract Sheets

The CONNECT DDE no longer standardizes on the “one model per *.dgn file sheet” production workflow that was used in the SELECTSeries DDE. Each contract sheet *.dgn will contain several design, drawing and sheet models.

CONNECT Edition CAD applications all come with plans production tools to automate sheet production. For an overview of the OpenRoads tools go to Volume 13, Section 2 - OpenRoads Drawing Production. 

Basic steps in ORD for creating plan, profile and cross sections sheets:

1. Create a new file using the CTDOT CONNECT seed file …CT_CONNECT_DDE\CT_Configuration\Organization\Seed\Road\Seed2D - CT RoadDesign.dgn

2. Open the design model and attach a reference to the newly created base model (which contains the design elements). When referencing, enable nesting to bring in all the references that are attached to the base model.
3. Use the named boundaries tool Civil Plan to define plan clipping areas and create the drawing models and sheet models.
4. In the same dgn file, open a profile view of the alignment used to cut the plan sheets. Use the named boundaries tool Civil Profile to define the profile clipping areas, then create the drawing and sheet models.
5. Open each plan view drawing model and reference in the old cut sheet file from SELECTSeries. Properly scale, align and copy over the needed notes. Do not import the old border. When finished, detach the old cut sheet.

   Plans production automation - For drawing models:

   • Reference the design model’s named boundary
   • Place match marks

   Users will add call out notes.

    

Open each plan view sheet model and reference in the old sheet file from the SELECTSeries cut sheets. Properly scale, align and copy over the needed general notes and charts. Do not import the old border. When complete, detach the old cut sheet.

Plans Production Automation - For sheet models include:

• The new cell border with the integrated title block
• Nested references to drawing model

Users will add general notes and charts.

Note: SELECTSeries profile and cross section *.dgn files from InRoads cannot be attached as references and copied over; these will need to be recreated from the OpenRoads alignments, 3D roadway and drainage models.

Basic steps to convert typical sections and detail sheets:

1. Create a new file using the sheet seed …\CT_Configuration\Organization\Seed\Road\Seed2D - CT RoadSheet.dgn
2. Change the annotation scale to full size 1 = 1. Attach the contract border cell, snapping to the bottom left corner of the transient shape.
3. In the *.dgn file, copy this sheet model to create as many typical sections and detail sheets as needed.
4. Reference in, scale, move and copy the needed SELECTSeries typical sections and details into each model. Do not import the old border. Detach the old cut sheet when complete.

ROADWAY TEMPLATE LIBRARY FILES

Template libraries can either be batch or manually converted from old feature styles in the InRoads XIN to feature definitions in OpenRoads. 

» Batch Conversion

Migration utilities are available for download on the Bentley Communities website. If you encounter issues with these tools, please contact Bentley directly. After the download is complete, launch the Template Library ITL Converter executable itl_importexport_excel.exe. This standalone executable will convert a roadway template library (*.itl) file to an Excel spreadsheet for bulk editing. Additionally, it can also convert the Excel spreadsheet back to the *.itl format. 

Warning: This can make an *.itl file unusable (corrupt). Always start with a backup copy and work on the backup, then make sure the updated backup copy is functioning properly. Never work on the original file! Additionally, there are columns marked DO NOT EDIT in the Excel spreadsheet. Editing entries in these columns is NOT supported and will very likely cause corruption.

Usage:

1. Make a backup of the *.itl file you wish to edit.

2. Run the provided executable and follow the prompts to select the backup *.itl file.

3. This will create an Excel spreadsheet.

4. Make changes in Excel, then save the file and close the program. See below tables for the ORD feature definition paths.

InRoads – OpenRoads Linear Feature Name Relation Table

InRoads – OpenRoads Component Feature Name Relation Table

5. Run the executable a second time, this time selecting the Excel file to overwrite the original backup *.itl file.

6. Test the backup *.itl file in OpenRoads Designer CONNECT Edition.

Known Limitations: Some special characters are not supported. There is no list available for unsupported characters. In the event of an error, check for the use of special characters.

» Manual Conversion

Use the Template Library organizer to copy in old Roadway Templates and update the feature definitions.

–Points

1. Open the roadway template library that was copied from the CTDOT CONNECT DDE to your project. Use the template library organizer to bring over old roadway templates from InRoads SS2.

2. Select the roadway template you need to convert and redirect all points and components to the new feature definitions using the tools Apply Feature Definition to Points and Apply Feature Definition to Components.

3. Choose Tools > Apply Feature Definition to Points.

4. Select all points.

5. Select the feature definition pull-down and change all points to miscellaneous. Browse to Linear\Roadway Modeling\Template Library\Misc and click apply to accept. Switch to the appropriate definition on each individual item.

–Components

1. Select Tool > Apply Feature Definition to Components.

TRAFFIC SIGNAL MODIFICATION PROJECTS

There are three options for working in CONNECT on traffic signal modification projects. These types of projects reuse the *.dgn files stored in the traffic signal asset area in ProjectWise. These are projects where no other disciplines such as Survey, Highway, Bridge, Landscaping, Illumination etc. will be submitting contract sheets or *.dgn files.

Consultants working on these types of projects should discuss these options with the CTDOT consultant liaison. CTDOT employees should consult with their supervisors.

Option 1 – Limited Conversion

Re-use Stored Asset Plan Sheet 

1. Copy the signal asset *.dgn to the CONNECT project storage area …Traffic/Contract_Plans.
2. Using OpenRoads, open the copied asset *.dgn file. Verify that the model is a sheet model type. If it is not, modify the model type to sheet model and change the view background to black. 
3. Edit the sheet boundary. 
4. Work in the sheet model to edit design features, tables, movement diagram, call outs and construction notes. Do not attempt to use the new CONNECT Edition cells and line styles as they will come in at the wrong size. 

Option 1 is for files needing limited adjustments, major changes should use either Option 2 or 3 below.

Option 2 – Partial Conversion

Create a Geospatial Base Model – Reuse Asset Signal Plan Sheet

Base Model

1. Copy the signal asset *.dgn to the CONNECT project storage area …Traffic/Base_Models.
2. Using OpenRoads, open the copied asset *.dgn file. Delete tables, movement diagram, call outs and construction notes leaving only the design features.
3. Move match marked areas to line up with the main corridor.
4. Create a base model using a CONNECT seed file and reference in the copied asset *.dgn file. Follow Module 1 - Base Model Creation.
5. Move the reference file(s) to the correct geospatial location. This sample video should work for most *.dgns but some files may have been created incorrectly in the old versions, in which case the user will have to align and scale the reference file manually. 
6. In the reference dialog box use the merge to master tool. 
7. Edit the features as needed. 
8. After all the new design features are in place in the new base model *.dgn, delete the old signal asset *.dgn from the project folder.

Sheet Model

1. Copy the signal asset *.dgn to the CONNECT project storage area …Traffic/Contract_Plans.
2. Using OpenRoads, open the copied asset *.dgn file. Delete all design features.
3. Verify that the model is a sheet model type. If it is not, modify the model type to sheet model and change the view background to black. 
4. Edit the sheet boundary. 
5. Reference in the new base model, align and scale it within the sheet. Clip the reference as necessary.
6. Repeat for match marks.
7. Edit tables, movement diagram, call outs and construction notes as needed.

Option 3 – Full Conversion

Create Base and Sheet Models

Base Model

1. Copy signal asset *.dgn to the CONNECT project storage area …Traffic/Base_Models.
2. Create a base model using a CONNECT seed file and reference in the *.dgn file. Follow Module 1 - Base Model Creation.
3. Move the reference file(s) to be in the correct geospatial location. This sample video should work for most *.dgns but some files may have been created incorrectly in the old versions, in which case the user will have to align and scale the reference file manually. 
4. Use the asset *.dgn file as a tracing board and replace all new features using the cells and tools in CONNECT. DO NOT COPY ANYTHING IN FROM THE ASSET *.dgn. Follow Module 2 - Signal Base Modeling.
5. After all the new design features are in place in the new base model *.dgn delete the old signal asset *.dgn from the project folder.

Sheet Model

Follow the steps in M.3.4 Traffic Signal Sheets.