Levels

Question: Below is an image showing the level manager in a cell file. Notice the Level SHET_Border does not show as having a defined library even though it does indeed live in the same library as the SHET_Boundary_NoPlot level. However, when I open the MaineDOT_Road_ROW.dgnlib the level does indeed live inside the library. Am I missing something?

Parents
  • No that really doesn't help. My goal here is to verify that the levels in the cell library actually reside in the level library dgnlib file. 

  • We are starting to use Element Templates to set levels and cell names, and have the cells all created on level Default. This way, no levels exist in the cell library and the cells get their levels from the DGNLIB with the Element Templates. But it is possible to have levels in an element template that is not in the level tables.


    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
  • Chuck,

    I have done that as well for cells that only need to be placed on a single level. However, my example happens to be a cell that includes more than one level. I have not dove deep enough into element templates to see if it's capable of placing elements within a cell on different levels.  

    The issue behind my original post stems from the level manager. My level manager is telling me there are levels in my file that don't reside in the level library. However, that is false. The levels do indeed reside in the level library. If I try to delete the SHET_Border level in the level manager it doesn't allow me to re-path that level to the same level as I would suspect. Now, if I change the level name to SHET_Borders and I close the file / re-open and delete the level SHET_Borders it does indeed find the SHET_Border level within the level library. 

    But that process of jumping back and forth from file to file to see if the level resides in the level library is time-consuming and truthfully I don't understand why the level manager in my cell file doesn't show that level as being in the dgnlib. 

  •  may Update Standards From dgnlib in your cell library file and see if it will re-read the dgnlib containing the levels

  • Good thought. But didn't do that trick either. 

  • If you export the level to a csv file, it only exports levels actually in the file. You can use that list to see if the level is in the cell library but not used and if so, remove it, And the same list from the level library can be used as your single point of truth for level names and settings.

    Bring the file into Excel and hide the rows except for the level names and column headers .And rotate the headers 90 degrees for columns with long header names but narrow data. and if you enable filters, you can even temporarily hide rows according to some column criteria.

    To get really clever, export your element templates to XML and use the migration tools to turn those into o spreadsheet and use some of the excel formulas to verify that no levels from the element templates are not in the library. Watch out for the levels in the terrain element columns - do not forget them.


    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
  • If you export the level to a csv file, it only exports levels actually in the file. You can use that list to see if the level is in the cell library but not used and if so, remove it, And the same list from the level library can be used as your single point of truth for level names and settings.

    Bring the file into Excel and hide the rows except for the level names and column headers .And rotate the headers 90 degrees for columns with long header names but narrow data. and if you enable filters, you can even temporarily hide rows according to some column criteria.

    To get really clever, export your element templates to XML and use the migration tools to turn those into o spreadsheet and use some of the excel formulas to verify that no levels from the element templates are not in the library. Watch out for the levels in the terrain element columns - do not forget them.


    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