<aside> ❗ Please read the Release Notes for this version 2.0 which has breaking changes.
</aside>
The Grasshopper plugin has a workflow and dataflow that is centralized in Grasshopper but interacts actively with the RhinoDoc (Rhino 3D Model itself). UIM Data can be read/written back-and-forth between the two interfaces. There is no external Database connection since the UIM data is stored in the RhinoDoc Object on the unique GUID of the Rhino geometry. In this way, the Rhino .3DM file works as a spatial database.
UIM Data is structured in JSON format and can be exported for use in other software.
The above icons shows the collection of the different SIMO Grasshopper Components. They are clustered into feature families. We have tried to provide all the components to run a complete project workflow, including data querying, data visualization and import/export. For Microsoft Excel import/export, you can use TT Toolbox or your preferred plugin.
<aside> ➡️ The components accept either RhinoDoc Geometry or Grasshopper Geometry. You can bake Grasshopper geometry (including UIM Data) with the component Smart Bake Entities.
</aside>
<aside> ➡️ Note: The components have a lot of documentation and help notes.
</aside>
<aside> ❗ Each SIMO model must have at least 1 planning area.
</aside>
Please refer to the UIM Schema to understand the Areas components. Essentially, you have the flexibility to structure your urban model by different areas and reporting. They are organized in a hierarchy from outermost to innermost. The urban hierarchy is: