Hello - I’m using Speckle to transfer a consultant’s Rhino site model into our Revit architectural model (primarily for viewing reference). We’d like to have independent visibility control of the context building geometry and the site/topography, each of which is comprised of many, many layers. The hope with this workflow is that, when new Rhino models arrive from the consultant, we can simply output a new version of the model without manually doing any relayering/model refinement, while outputting two “groups” of geometry for easy visibility control in Revit.
My question is this: Is there a way to group elements (short of the block to type method) that would allow me to categorize as two categories of element for easy visibility toggling? For example, all of the Rhino layers under “A” become DirectShapes categorized as Generic Models, and all Rhino layers under “B” become DirectShapes categorized as “Site” or “Topography” or similar? This seems like something that would be easy to set up, but I haven’t yet located the right workflow (if it’s available).
FYI I have both the latest v2 and v3 Rhino and Revit connectors installed. Happy to work with whichever one will help me get to my end goal.
Thanks for the detailed explanation, this sounds like a very valid use case!
Using v3 this is currently not possible, objects from Rhino are received in Revit as Generic models - good news is that @clrkng and @oguzhan are actively looking to improve the current workflows.
In v2 you can use the Mapper tool to assign specifc DirectShape categories before publishing to Speckle.
But it soulds like in your ideal workflow this mapping would instead happen online in the web app?
Hi Matteo - thanks for the reply. I had looked into the Mapper functionality, but it appeared to be limited in functionality. I’m hoping to select all geometry (in this case, 3,800+ blocks, breps, surfaces, curves, etc) on the “A” layer and subsequent sublayers, and assign it all to a single Revit category (ie Generic Models on a Context Buildings workset). Maybe if I had a single family/type in the model that was a container of all these elements I’m describing, I could map this geometry directly to that type?
For the moment, my workaround solution will be to isolate the geometry in Rhino as A or B groups, and upload two separate models to the Speckle project. From there, I’ll import each onto a specific workset to maintain separation of the elements for visibility purposes.
@teocomi I also forgot to follow up on your comment regarding sorting via the web app - I’m not entirely sure how that might be done? Is it possible to select geometry there and assign to a Revit category? Or were you suggesting something else?
@awoodhouse Mapper works exactly that way, while I haven’t personally tested it with so many elements, it should allow you to: select objects in Rhino > map them to a specific DS category.
Let us know if you found any limitations as that’d help us shapre its new iteration.
In regards to doing any mapping in the web app, that’s not possible, but I suggested that as a potential future feature (cc @benjavo )
Following up on this thread. My anticipated workaround is not actually working as I anticipated. In lieu of the Mapper approach, I opted to export two separate model uploads, and have intended to import each while on a separate, isolated workset.
My seemingly obvious quick fix isn’t working - when I upload the latter model (let’s say B after A has already been added), A disappears when B completes. If I re-add A, B disappears. There is no overlap in geometry, and the exports have two distinct names/uploads, and its happened even after closing Revit with one option loaded and added the second after re-opening. I’m running out of ideas for why this might be occurring.
Any thoughts or obvious solutions I’m missing? Here’s a screen capture, though there’s admittedly not much insight to glean from this image. The third/fourth models listed were a first attempt, and the fifth/sixth models were a refreshed attempt with brand new models, still to no avail.
Thanks @teocomi - what ended up working was extracting one half of the geometry (the A group) and putting in a separate model. I also did as you suggested, using the Create mode, which wasn’t previously being used. It ended up working as I intended.
