I don't like dgnlibs because it is not obvious what is stored in which dgnlib.
Now we have level libraries in dgnlibs. Which is the active file looks in another file for the data.
So why can't we have the active file look in something more transparent and readable than a dgn? Like a csv, or a xls, which can be viewed parallel to the active dgn in ustn.
It would also be much easier to edit than through LM in ustn.
Hi Thomas,
As suggested below creating separate dgnlibs for the various resources is a good method for management.
A recommended workflow is to use the CSV as the source for the levels.dgnlib, the CSV content can then be manipulated using Excel tools (as you are obviously fully aware).
Changes can be imported into the levels.dgnlib individually, or all levels can be imported into an empty dgnlib to ensure an exact match to the source CSV.
Whilst adding a step, this does have the advantage that the CSV is not unintentionally modified during daily operations.
Regards
Marc