How do you import and export hydraulic prototypes under Drainage and Utilities from one hydraulic seed file (.dgnlib) to another? I was able to export the inlet catalogs, but not the prototypes. I am working in OpenRoads Designer CE - 2021 Release 1. I am exporting to same version software.
I'm afraid that we don't have a way to do this in OpenRoads at the moment James. There is an enhancement request for this functionality to be added.
Do you have an enhancement # for that functionality? I would like to be added to that for future updates
Microstation CONNECT - 10.17.2.61
ORD - 2021 R1 10.10.1.3
ORD 2022 R1.1 - 10.11.3.2
ORD 2022 R3 - 10.12.2.4
Microstation v8i SS 10 - 08.11.09.919
Power InRoads v8i - 08.11.09.615
ProjectWise - 10.0.3.453
If all team members are using the same SUDA SEED FILE dgn library, and that dgn library contains your prototypes, wouldn't that keep everyone in sync? Your maintenance would involve updating the prototypes in the one dgn library and then making sure that all team members receive (or are otherwise using through PW) the updated dgn library.
Karl Dauber, PEAdvance ConsultingLaurens County, SCkarldauber@advconsult.netwww.advconsult.netwww.linkedin.com/in/karldauber
Karl, this would work for all new projects, but the Prototypes, Catalogs and most of the settings are copied into a working DGN file when the Utility Project is created. After that there is no coordination between or connect back to the SUDA/SUE Seed files for these items.
Chris, not what you are looking for, but my effort in this regard is to update the Prototypes in the SUDA Seed and just track what I change and then replicate those changes individually where needed... cumbersome at best, prone to my capacity to make errors at worst.
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 / 2024
That's a good point Steve. Thanks for clarifying.
We have done an enhancement for the 2022 Release 1 version, so that if a prototype that's needed by a feature definition doesn't exist in the active file, then it's copied in from the dgnlib.
Jonathan, as always, thank you for the update.
I, however, am a little concerned that the functionality you describe does not address the question at hand. I am a little hard pressed to think of a situation where I would have a Feature Definition without the corresponding Prototype. My gut is, that the opposite is more likely. While completing a design task, I will discover I need a new node/structure and generate that for the effort at hand, and then, if it is something I am apt to discover again, would take that and want to move it into the DGNLIB for future use. I guess my concern is that this is a really specific resolution to only a small part of the original defined need.
My two cents.