Models or DGNS which is better?

So we are still in the early days of adopting ORD in my organization. I was wondering if anyone has seen any performance difference between using multiple models in a single dgn VS using multiple DGNs?

our previous method was to create multiple DGNs and reference them as parts of the drawings. what I'm wondering is if theres a benefit to say placing all the parts of a design model in the same dgn and just using model spaces to separate them.

For Example a Detour.dgn would have the following as models:

-Detour Alignment

-Detour Corridor

-Detour Terrain

-Detour Earthwork

I was thinking the main benefit would just be reducing the number of separate files we generate but was also hoping that maybe it comes with fewer crashes and better functionality??

Parents
  • Multiple DGNs is the recomennded way to work, and it's my preference.

    I keeps the file from getting too large - by the time you have all of your design and your corridors and your terrains and everything else, I think that would make the file slower and less stable.

    Mike also mentioned a couple of good points, and the big one for me is that keeping the data federated means that more of the data is protected from corruption. If everything is in one file, and something happens to that file, everything is lost. If things are kept separate, we'd only lose that one chunk of data while everything else is untouched.

    That being said, There's wiggle room depending on the project. For something small like a single cul-de-sac, I would probably keep that all in one file. I keep my medians in a separate file from my roadway, but I don't have a separate file for every median; the same with driveways. My roadway drawing may have more than one corridor (backbone, sideslopes) For longer projects, I try to keep everything split into one mile regions so I might have RoadCorridorR1, MediansR1, DrivewaysR1, RoadCorridorR2, etc.

    I am convinced that having things split up is the best way to do it. I makes more drawings, but it also makes it easier to reference only the parts I need while protecting my data from getting all hosed at once.

    MaryB

    Power GeoPak 08.11.09.918
    Power InRoads 08.11.09.918
    OpenRoads Designer 2021 R2

        

Reply
  • Multiple DGNs is the recomennded way to work, and it's my preference.

    I keeps the file from getting too large - by the time you have all of your design and your corridors and your terrains and everything else, I think that would make the file slower and less stable.

    Mike also mentioned a couple of good points, and the big one for me is that keeping the data federated means that more of the data is protected from corruption. If everything is in one file, and something happens to that file, everything is lost. If things are kept separate, we'd only lose that one chunk of data while everything else is untouched.

    That being said, There's wiggle room depending on the project. For something small like a single cul-de-sac, I would probably keep that all in one file. I keep my medians in a separate file from my roadway, but I don't have a separate file for every median; the same with driveways. My roadway drawing may have more than one corridor (backbone, sideslopes) For longer projects, I try to keep everything split into one mile regions so I might have RoadCorridorR1, MediansR1, DrivewaysR1, RoadCorridorR2, etc.

    I am convinced that having things split up is the best way to do it. I makes more drawings, but it also makes it easier to reference only the parts I need while protecting my data from getting all hosed at once.

    MaryB

    Power GeoPak 08.11.09.918
    Power InRoads 08.11.09.918
    OpenRoads Designer 2021 R2

        

Children
No Data