Split Geometries
This tool makes it possible to apply the Location Tools functionality to models from a script or template. This tool can not be run from the Simplebim user interface.
Configuration Options
Key | Type | Value | Description |
---|---|---|---|
SPLIT_TYPE | Text | Default=ALL | Defines which objects are split |
ALL | All objects. | ||
MARKED | Resolves and splits objects according to the Split attribute values. | ||
LOCATIONS_ONLY | Resolves location only for all the objects. No splitting will occur. | ||
SPLIT_ASSEMBLIES | On/Off | Default=OFF | Defines how assemblies are split. |
ON | Splits assemblies based on the locations of the assemblies’ children. | ||
OFF | Does not split assemblies. | ||
ASSEMBLY_CHILD_LOCATION | Choice | Default=SINGLE | Defines how locations are assigned when assemblies are split. |
SINGLE | Assigns assembly’s location identifier to all the children. | ||
MULTI | Assigns location identifiers to the children based on their actual location. | ||
GUID_MAP_READ | Path | The full file path. | Reads guid mappings from a specific file path. Mapping file is a text file of type .mpf. The default is the path from which the current model was opened or imported. |
GUID_MAP_WRITE | Path | The full file path. | Writes guid mapping to a specific file path. By default the guid mappings are stored to the same folder as the model. |
SMART_SPLIT | On/Off | Default=ON | Smart split avoids leaving small pieces of split objects to the result, splitting walls, columns and beams along their axis or slabs horizontally. |
ON | Smart split on. | ||
OFF | Smart split off. Splitting uses basic geometric boolean operations between the location prisms and building elements. | ||
SMART_SPLIT_ANGLE | Number | The angle. | The angle is used for defining, if the splitting is about to happen along the wall, column or beam axis or horizontally for slabs. The angle is given in radians. It is the smallest allowed angle between the object’s axis and the split direction. Meaning that only the split directions which have bigger angle to the object’s axis than defined are used. This is only applies, when the Smart Split is on. Default is 0,965. |
MINIMUM_SPLIT_DIMENSION | Number | The value in millimeters. | Minimum dimension for split objects. If the resulting split object is smaller than the minimum, then no splitting will be applied. This only applies, when the Smart Split is on. Default is 300mm. |
DEFAULT_NO_SPLIT | On/Off | Default=OFF | Building elements from a set of default object classes are not split. The default set of object classes include windows, doors, furniture, railings and stairs. |
ON | Splitting is done with default split settings. | ||
OFF | Objects are split according to the split type setting and the Split attribute values. No default split settings are used. | ||
DECIMATE | On/Off | Default=ON | Decimation is the process of reducing the complexity of the geometry without adversely affecting the shape of the geometry. |
ON | Geometry decimation is on. Normally this should be on. It makes the rendering of the resulting splitting much more effective. | ||
OFF | Geometry decimation is off. This should be used only in debugging and testing. | ||
CALC_QTO | On/Off | Default=ON | Calculates the quantities after splitting based on the resulting geometry. Note that this runs the Calculate Basic Quantities tool with the default settings for that tool. |
ON | Calculates quantities after splitting. | ||
OFF | Does not calculate quantities after splitting. | ||
REMOVE_ORIG_QTY | On/Off | Default=ON | Removes all quantities from the split objects because after the object is split the original quantities are no longer correct. |
ON | Remove original quantities after splitting. | ||
OFF | Do not remove original quantities after splitting. | ||
REMOVE_ORIG_OBJ | On/Off | Default=OFF | Removes original building elements after the splitting. Original building elements are the building elements, that were split. |
ON | Remove the original building elements. | ||
OFF | Do not remove the original building elements. | ||
REMOVE_LOC_PRISMS | On/Off | Default=OFF | Removes location prisms after resolving the locations. |
ON | Remove the location prisms. | ||
OFF | Do not remove the location prisms. | ||
SPLITSPECIALROWS | On/Off | Default=OFF | Controls the splitting of the following spatial containers: site, building, building storey. |
ON | Splits spatial containers. | ||
OFF | Does not split spatial containers. | ||
RESET | Choice | Default=OFF | Controls the resetting of the model after the locations have been resolved. Resetting is needed when multiple location types are applied to the model in sequence, for example if you first set the building storey locations you need to reset before you set the construction section locations to the same model. |
OFF | No resetting. | ||
SEQUENT_RUN | Reset the model after resolving it. When only resolving the locations, the reset means that everything is classified as Not Decided Yet and the existing location prisms are removed. When resolving the locations and splitting, the reset means that the resulting objects are classified as Not Decided Yet and the original objects and the existing location prisms are removed. | ||
SEQUENT_RUN_EXCLUDE_ERRORS | Reset the model after resolving it. With this configuration value the reset means that everything is classified as Not Decided Yet and both the original objects, objects with errors and the existing location prisms are removed. |
GUID Mapping Instructions
GUID mapping is controlled by the GUID_MAP_READ and GUID_MAP_WRITE configurations. When GUID_MAP_READ is defined, the tool will try to read the GUID map from this file and once the splitting is done, it will write the result to the GUID_MAP_WRITE file. When you have only one set of location prisms this is very straight forward, because you can use the same file for GUID_MAP_READ and GUID_MAP_WRITE. In this scenario the file is simply updated after each splitting.
- GUID_MAP_READ = C:\temp\MyGuidMap.mpf
- GUID_MAP_WRITE = C:\temp\MyGuidMap.mpf
The situation becomes more complex when you use multiple sets of location prisms, for example one set for construction sections and another for takt areas. Here you don’t want the situation where the GUID map for the takt areas overwrites the previously created GUID map for construction sections. Here you would use a different GUID map file for both operations.
Splitting by construction sections:
- GUID_MAP_READ = C:\temp\MyGuidMap-ForSections.mpf
- GUID_MAP_WRITE = C:\temp\MyGuidMap-ForSections.mpf
And splitting by takt areas:
- GUID_MAP_READ = C:\temp\MyGuidMap-ForTaktAreas.mpf
- GUID_MAP_WRITE = C:\temp\MyGuidMap-ForTaktAreas.mpf
In addition, please take care that you run the splitting in the same project always in the same order, e.g. first construction section and then takt areas. Running the splitting in different order in the same project would mess up the GUID mapping.