Hi JdB,
Thanks for tagging me! We’ve been doing some work on that one yes, as you know. It’s similar to the process you are describing but for us it connects to our inhouse developed library which is stored in .json format.
The workflow is as follows:
- Select stream, branch, commit
- Plug-in will read all the specific unique types
- Based on the “mapping json” (basically the key is the structural type from our library, the value is the Revit family name / type name from our library), it auto selects the right family for the right beam. If none is found you can fill it in yourself based on a dropdown.
- Second last step is to load the families automatically from our libarary, currently this is still local but something like a call to our sharepoint library would be better (not sure if that’s possible).
- Last step is to update the stream with new family names
This all sounds relatively easy, but we are struggling because we still have issues when both Speckle and our plug-in is installed… We’ll pick this development up again this month so I hope we will be able to solve that one.
Cheers,
Dirk