<aside> ➡️ Note: Please see the sample files which shows typical workflows of all the components.
</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 Database connection since the UIM data is stored in the RhinoDoc Object on the unique UUID 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> ➡️ Many components accept either RhinoDoc Geometry or Grasshopper Geometry. Right-click on the icon to choose the input geometry.
</aside>
<aside> ➡️ Note: The components have a lot of documentation and help notes.
</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: