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.
However, in SUDA a single Feature Definition can be configured to contain all expected sizes for the designated material and utility type.
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.
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.