SUDA Tip: Importing Legacy Drainage Files from InRoads and GEOPAK

Published on May 3, 2016

Written by:  Robert Garrett

Importing legacy drainage projects into Subsurface Utilities Design and Analysis (SUDA) is easy and is accomplished from the menu:

SUDA Import Menu

When Importing from GEOPAK Drainage, InRoads S&S or MX Drainage, the imported features will be assigned a generic Feature Definition unless a feature definition is found which matches the name of the legacy library item name. A generic storm feature definition looks like this in 3D:
SUDA Generic Storm Node

Of course, the user can then change the feature definition in the properties panel. But, there is a more efficient way.

In InRoads Storm and Sanitary, the equivalent of feature definition for drainage is the structures library.
InRoads Drainage Structures File Inlets

And in GEOPAK it is called the drainage library.
GEOPAK Drainage Library Inlets

If you construct your feature definition library so that the drainage feature definitions name matches the names in the legacy library, then the proper feature definitions are assigned automatically while importing. Thus you get this instead of the generic model:
openroads SUDA 3D model catch basin

The same matching occurs for pipes, but it might not make sense to create your feature definition library to match imported library names. We’ll consider this question next time….

MORE HELPFUL TIPS

Standard Toggles                            fittings and appurtenances                                Recent Files Listing
OpenRoads Tip: Civil AccuDraw      Civil 3D Tip: PVC, HDPE,& Steel Pressure Pipe Parts             MS Connect Tip: Select
Working in Profile Views                              Catalogs Come-out-of-the-box                                           Model to Open

 


Tags: , , , ,
Like this article? Share it!

Leave a Comment

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

Privacy Policy