Is there a way to publish geometry from Linked models in Revit to Speckle?
I am currently testing it out, and it seems that it isn’t possible.
I know that BIM 360 has figured out a way to do it if it is a cloud model and linked in. Is there something similar like that for Speckle?
Hey Bowen,
Our Revit connector doesn’t yet support Linked models!
Last time I checked (a few years ago) it was not possible to easily access those elements, but maybe things have changed in the newest Revit APIs. I’ll open up an issue internally so we can look into this in the coming Sprints.
Will keep you posted and thanks for the suggestion!
Hey @bcall ,
I can confirm that from our next release linked files will be supported as well when sending from Revit
Let us know how it works for you once you get a chance to play with it.
Matteo
Is it only the whole linked model? I have a model from an MEP engineer and I would prefer not to ask them to change their setup. I would rather use the link to only send some Revit categories of things. For example just Ducts & Pipes.
How can this be achieved?
Yes, we just released 2.5 a couple of days ago!
Nevertheless @Jedd and I noticed that linked modes that have been moved around after having been placed are not coming throughout properly (see this issue).
We’ll work to improve this functionality over the next weeks, in the meantime any feedback is appreciated!
If you select only Duct and Pipe categories in the selection filters, then only items from these categories will be sent from the linked models. 
You can see in my image that there are ducts in the linked model, and ducts is one of the categories I have selected. When I try to send Speckle says there are zero objects.
Am I doing something wrong?
Support for linked files has been added to 2.5, please update to that version and try again 
I’m not getting an upgrade notification
Searching the net for “speckle manager download 2.5” also doesn’t give me any hits.
This download page isn’t giving me 2.5. I suggest also that it say in the text on the page or the name of the .exe what version it is.
Hi @DuncanNZ aren’t you able to download the 2.5.2 Revit installer directly from the releases page linked above?
If you do not see the update from Manager and are not getting a notification it might be that your network is blocking something. Here is a list of domains that should be let through your proxy/vpn/firewall: FAQs | Speckle Docs
Okay, we were talking about the Speckle Connector (I was looking for an updated Manager). Update now complete.
That’s getting better!
Revit:
I guess I shouldn’t pester you for the categories that are missing … all things in their time.
Awesome!
Sorry I didn’t clarify what needed an update hehe, it was late here
Feel free to suggest what categories to add, missing features, or other bugs.
We’d be happy to look at them!
Done for the three most noticeable unsupported categories for this particular project.
We’re planning to add a setting to configure whether linked models should be sent to Speckle or not.
Quick poll:
0 voters
how do you plan to tackle duplicate elementId’s coming from the linked models, when receiving the stream?
Good point @Dickels112 !
I think the most logical behavior would be to expand on what we currently do already when working on a single document:
It would probably also make sense to add a new Advanced Setting to always skip elements that belong to linked files… What do you think?
interesting question, apart from @teocomi’s answer.
I think you were also referring to the possibility of 2 completely different elements having the same element id in two different linked models. i.e.:
12345
12345
Is this right? If so, not sure if just checking in order as Matteo proposed will solve all edge-cases…
If you receive the beam in the architectural model… would we overwrite the wall? 
PS: Sorry for the edits, I pressed send to fast.
I think the safest thing would be to ignore linked files by default, so when sending and receiving. It can become quite problematic and risky when (new) users are not aware they modify linked files (for obvious reasons) or send data from linked files to another platform (Speckle server). Unintentionally sending linked models to the Speckle server could be an issue, for example, when you collaborate with external parties who might not want their model and data to be stored on a different platform.
This is anyway a great idea, then we can maintain origin of information