Understanding Seed File

Hi Jaimin

Good question. There has been historical thoughts that some of the features in OpenBuildings, like structural objects, needed a certain resolution but I am not so sure how relevant this is now, but we should find out.

Is this seed file something that is expected to be used across many DGN based products on a single project?

Could you post the seed file?

Stuart

Hi Jaimin,

You can use your MicroStation seed file to create new GC design file for sure.

In OBD , a more reliable strategy would be to create a new file using the seed file of the active WorkSet and then acquiring the GCT file through the script Editor. That way, the file’s working units set up will be fully aligned with the current WorkSet’s standards.

Whenever the user opens a GCT file, GC reads those measurement units, and applies them to the active master DGN file.

Here are few scenarios :

1. The user opens a GCT file, which, in turn, opens the seed DGN file. The units that are stored in the seed DGN file are irrelevant. Those units are overwritten, immediately, by the units stored in the GCT file.
2. During the session, the user wishes to change the units, so they do so via the standard mechanism (File -> Settings -> File -> Design File Settings).
3. Later, when user is finished working, they save the GCT file, At that point, the newly-changed units are written into the GCT file

4. Later still, the user re-opens the same GCT file, which presumably has the updated units .

   Here are the few examples how the units are saved in GCT file , the 1st example is showing English units and resolution.

   environment
   {
       GCVersion                 = '10.07.00.90';
       MSVersion                 = '10.14.00.101';
       MSProject                 = '';
       MSDesignFile              = 'D:TEST-GC-UNITS.dgn';
       MSMasterUnit              = {Meter, '''', English, 3048.0, 10000.0};
       MSSubUnit                 = {Meter, '"', English, 254.0, 10000.0};
       MSStorageUnit             = {Meter, '', English, 3048.0, 10000.0};
       MSUorsPerStorageUnit      = 304800.0;
   }

   Here is the another example where it is showing changes in Unit system by user which getting saved as metric units.

   environment
   {
       GCVersion                 = '10.07.00.90';
       MSVersion                 = '10.14.00.101';
       MSProject                 = '';
       MSDesignFile              = 'D:TEST-GC-UNITS.dgn';
       MSMasterUnit              = {Meter, 'm', Metric, 1.0, 1.0};
       MSSubUnit                 = {Meter, 'mm', Metric, 1.0, 1000.0};
       MSStorageUnit             = {Meter, '', Metric, 1.0, 1.0};
       MSUorsPerStorageUnit      = 25400.0;
   }

HTH,

Rg,

Sandeep

Hi Stuart,

Please find attached 3D design seed file. We are working in Metric units with primary meters and secondary millimeters.

Regards,

Jaimin Patel

PW-Seed3d-model.dgn

Hi Jaimin

I don't see your seed being an issue. The only change here from the delivered seed in OpenBuildings and GC is the master unit. The resolution and SWA is still the same.

From this recommendation all looks to comply to this and the master unit change is not going to affect the resolution or SWA. 

communities.bentley.com/.../setting-up-in-the-real-world-or-quot-where-do-we-model-quot

Stuart

Hi Sundeep & Stuart,

Could a primary node (like baseCS) not be a useful place to explicitly set/define Units that the script uses? I appreciate the resolution of a file is stored in the DGN/Seed and should not be changed, but the choice of working units tends to be quite a personal thing. some like m, some like mm..
An option to automatically run through the nodes to reset the "apparent" unit in each one would be quite useful. In much the same way that you can retroactively store the position of nodes after they have been rearranged.

I suppose its hard to tell what is a unit value, vs just any old double, but maybe adding the unit abbreviation to the number is an option...

Regards

Robert