[OpenRoads] Feature Definitions library crashes

You should not use 'civil display browser' - that is not (and never was) meant for us users. It was meant only for the developers. Neither you or I have any idea of the functionality of this tool, and will probably do more harm than good trying to use it.

I would have the FD, FS, and Annotation Groups (with their Definitions) in the same file.

If you are in a configured DGNLIB, you can copy data from another DGNLIB into this one. There is not a risk, that I know of.

Hi Mark,

a follow-up question: what happens when I replace my .dgnlib with a file with the same name? I am wondering if models that use FD and FS from the library can get somehow broken. I know that you mentioned copying from 1 file to another, but I need to be fully convinced that I won't destroy any of our work.

It should make no difference - when a FD/FS is used from a library, it is copied into the local file - so the dgnlib is not needed for that particular FD again (unless you then synchronize with dgnlib).

And does ORD synchronize with feature definitions' names or some id numbers?

No idea. However, I will say 'by name' - as there is no ID (or GUID) in the XML file created when you export FD.

If you want to export and reimport into a new file, you need to make sure the Element Templates (ET) are available along with the FD and FS. We keep all FD, FS and ET in the same dgnlib. We do have a survey dgnlib with survey specific items, and a SUE dgnlib. But if an FD or FS points at an ET, then we keep that ET in the dgnlib as well, even if it is a duplicate of what is in another dgnlib.

I rely heavily on the migration utilities to review and organize all of these.

If you want to export and reimport into a new file, you need to make sure the Element Templates (ET) are available along with the FD and FS. We keep all FD, FS and ET in the same dgnlib. We do have a survey dgnlib with survey specific items, and a SUE dgnlib. But if an FD or FS points at an ET, then we keep that ET in the dgnlib as well, even if it is a duplicate of what is in another dgnlib.

I rely heavily on the migration utilities to review and organize all of these.