SUDA Tip: Importing Pipes from Legacy Drainage Files (InRoads and GEOPAK)

Written by:  Robert Garrett

In the previous SUDA tip we discussed how you can import from GEOPAK Drainage and InRoads S&S into SUDA and automatically match the legacy library name to an OpenRoads Feature Definition.  In that article we stated how the same Feature Definition matching demonstrated for nodes would also work for pipes, but may not be a good idea.  Here’s why you might not want to provide for this automatic matching:

Taking a look at a GEOPAK Drainage library, we see that pipe(link) library items are size specific.  InRoads S&S is the same in this regard.

GEOPAK Drainage Link Library

However, in SUDA a single Feature Definition can be configured to contain all expected sizes for the designated material and utility type.

SUDA Pipe Feature Defintion

In order to take advantage of the automatic matching when you import, you must structure the SUDA Feature Definitions to be size specific and exactly match the legacy library item name.  This makes a LOT more Feature Definitions which you must potentially maintain forever.

It is probably better to forego the Feature Definition matching capability for pipes and then change the pipe Feature Definitions after the import is finished. This is very easy to do.

After the import, you will have many very cool looking nodes connected by many very ordinary looking pipes of various sizes.

Generic Imported Storm Pipes

Simply select all the pipes using Selector or Select By Attributes or whatever.  Then change the Feature Definition of the entire selection set in Element Information.  The Feature Definition is changed and the sizes are matched to the closest matching size in the Feature Definition you choose.

Change Multiple Pipe Feature Defs

Robert Garrett

Robert has over 25 years experience as a practicing engineer and is licensed in the State of Tennessee. After graduating from Tennessee Technological University, Robert worked for the Mississippi State Highway Department, Bridge Design Division. Then he spent 12 years with the Tennessee Department of Transportation in the Roadway Design Office and later served as Regional Manager in the Design Survey Office.From 2000 to 2006, Robert worked for Robert G Campbell and Associates in Knoxville, TN where responsibilities included roadway, site, and utilities design projects.Joining Bentley Systems in March 2006, Robert wrote specifications & documentation for software development. Duties included testing, customer feedback and ensuring the products met the needs of the civil engineering user base. He also developed training material for education both internally to Bentley and for outside organizations. He served as Product Manager for Utilities Products, including the new OpenRoads Subsurface Utilities Design and Analysis software. Robert also provided guidance and implementation services for new technologies.He is a frequent presenter and trainer at user conferences.


2 comments on “SUDA Tip: Importing Pipes from Legacy Drainage Files (InRoads and GEOPAK)

  1. Jeff Abraham Reply


    Thank you for publishing this helpful information. Are you aware of any recent Bentley updates for OpenRoads and/or SUDA that has helped to simplify the export process from Geopak Drainage (legacy) to SUDA? Or will it still be the same process as what you have mentioned in this blog for pipes (as well as nodes)? In the past I’ve tried, I’ve come up with errors so found the export process to be difficult.

    • Steven Litzau Reply

      I am not aware of any changes to how this process is handled, so the process should continue very similarly to what is outlined.

Leave a Reply

Your email address will not be published. Required fields are marked *