Open Roads DGN Seed File

Does a dgn seed file based from a v7 converted to v8 affects openroads?

I am doing volume calculations for cut and fill from a corridor and an existing terrain and everytime I try to, the meshes are not created. This is all while using our usual seed file.

I tried doing the same thing but this time created all the terrain and corridors using the supplied seed files from openroads training datasets and all work fine without any problems.

Parents
  • so here is what i've discovered, it's not just actually the seed file that causes this problem but the global origin of the seed file.

    the openroads dgn seed comes with a go=0,0,0 while my company's is set at somewhere around go=-50xxx,-50xxx,-1xx. all other design file settings are the same, except for the global origin.

    adjusting the global origin of the openroads-delivered seed to my project's global origin made it not worked again.

    currently we have at least 30 years worth of dgn files, if we start using a new dgn seed with go=0,0,0.  Will we have any problem with regards to referencing those legacy files created with the old global origin?  I know setting the reference to attach Coincident World will fix this but is there anything else that I should know.

  • Because MicroStation supports Attachment by Coincident World and True Scale, you can usually work with files of different units and resolutions. Trust me, we feel your pain. We tried to migrate our V8i workspace to ORD and are now redoing the whole thing because of these issues. On the plus side, it is giving us a chance to revisit the organization of Features, Symbologies and Element Templates.

    We had found the Shifted Global Origin never played well with the V8 Sheet Models and using Reference Files as Sheet Definitions, so we thought we had resolved the Global Origin issues. But it turns out, a ton of our Cells also had shifted Global Origins. And those needed to be fixed before you start fixing resolution issues or you will be lost as to where in the cell that the xy=0,0 point is for many cells.


    Charles (Chuck) Rheault
    CADD Manager

    MDOT State Highway Administration

    • MicroStation user since IGDS, InRoads user since TDP.
    • AutoCAD, Land Desktop and Civil 3D, off and on since 1996
Reply
  • Because MicroStation supports Attachment by Coincident World and True Scale, you can usually work with files of different units and resolutions. Trust me, we feel your pain. We tried to migrate our V8i workspace to ORD and are now redoing the whole thing because of these issues. On the plus side, it is giving us a chance to revisit the organization of Features, Symbologies and Element Templates.

    We had found the Shifted Global Origin never played well with the V8 Sheet Models and using Reference Files as Sheet Definitions, so we thought we had resolved the Global Origin issues. But it turns out, a ton of our Cells also had shifted Global Origins. And those needed to be fixed before you start fixing resolution issues or you will be lost as to where in the cell that the xy=0,0 point is for many cells.


    Charles (Chuck) Rheault
    CADD Manager

    MDOT State Highway Administration

    • MicroStation user since IGDS, InRoads user since TDP.
    • AutoCAD, Land Desktop and Civil 3D, off and on since 1996
Children
No Data