Hi,
I want to use the Geopak TXDOT drainage library (e.g: storm nodes/conduits) in OpenRoads SS4 (SUE). I went through this post - Bentley Communities.and followed the steps.
The XML exported from there, I got to import in SUE, which came up in the engineering library.
But, when I'm placing the node or conduit, the feature definition seen is only "Generic"!
How to bring this imported XML library, which is seen under the engineering library ?
(Earlier I had not activated the SUE license, but later I activated successfully, and then did it again in the same dgn. I hope this is not the issue!)
Did you create Feature Definitions and link the imported data to them? The import process just brings forward the content into the catalogs, you will need to create the feature definitions to reference the catalogs.
Steve
www.envisioncad.com
ORD - 10.12.02.04 / 10.10.21.04 / 10.10.01.03 / 10.08.01.33Power GEOPAK / Power InRoads - 08.11.09.918Civil 3D - 2021 / 2022
So, I have the DDB as well to which I can try to map with Geopak Feature definitions. But, after bringing in the feature defs, you are saying, I need to map each node/conduit or by selection set, then those will come up in the list?
Thank you,
Abhiram
What Steven is saying is you need to create a dgnlib file and begin the process of creating feature definitions. You will import the the xml files into the Conduit Catalog and the Inlet Catalog. Then you will start creating Feature Definitions like these two videos step through
https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/17694/video-creating-a-feature-definition-for-a-sue-node
https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/17692/video-create-a-conduit-feature-definition
During the process of creating the Feature Definition you link to a Prototype which links to the Conduit or Inlet Catalog. You will need to create the Prototypes too if not already done.
The DDB file and Geopak DLB and GEOPAK Cell library are not needed at this point.
You reference a wiki article above. The point in the process that you are at is step 6.
Then for either GEOPAK or InRoads
For more information about the Road and Site design tools, visit the Road and Site design WIKI at: http://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki
Thank you Beebe. It is really helpful. You have detailed it out step by step with videos.
But, actually it is in itself a project to do this. I can do this, in downtime, but not when live on project.
Do you or anyone here on the group has any other U.S DOT's ready to use catalog, dgnlib to be used for SUDA SS4 software?
"But, actually it is in itself a project to do this"
This is my favorite line out of your comments here. It is a significant undertaking to develop these. I am working in one particular workspace (for ORD) and have created nearly 100 feature definitions, which equates almost twice that many feature symbologies, element templates and cells. And now I am moving onto look at the proposed utilities, where the effort is similar. One of the complications we run into here is each state, and often individual agencies in them, have different standards for drainage design. The structures I used doing road design in Minnesota don't resemble at all the structures in Colorado I grew up with. Do to the effort involved, I think a number of agencies that began the development originally for SS3, have since changed efforts to ORD, and I think TxDOT is in that group.
Enough on the soap box there. To your question, I did a quick check of a few of the DOTs that I am familiar with and I don't see anything in most of them. Looks like FDOT and CDOT may have some content. I didn't dig too deeply, but there are some DGNLIBs named there that give me a little hope.
CDOT - https://www.codot.gov/business/designsupport/cadd/v8i-ss4-consultants/ss4-v-06-01-02/view
FDOT - https://www.fdot.gov/cadd/downloads/software/FDOTSS4CaddSoftware.shtm
Again, these aren't going to match TxDOT but may give you a feel for what might be out there.