Understanding the structure of streams from Revit

[dimitrie]

Hi @henkon, apologies for the late reply! No worries about the long post

Some of your remarks sound like potential bugs from our end. Specifically:

@henkon

there are two windows under grouping “windows” with no geometry and little other information.

Either those two windows are not hosted anywhere, or we’re fumbling something up.

@henkon

For doors, well, they just are not sent to Speckle when sending the model (“all”). They are not even a choice if I try to send Family and Types or categories. Only way to send a door that I have found, is by manual selection.

This one too. “All” should really mean all

@henkon

the wall “structure” does not seem to be part of the wall - by that I mean the materials/layers of the wall.

This is something that was requested in this thread - so it should make it in our todos.

@henkon

So, I am trying to find a “unified way” to query the model and process the response. I would think that I could query different categories - Revit categories, but unfortunately it is not that easy. I am not very used to graphql, and the way Speckle structures the data. I wanted to find “one query fits all”.

This is defintively something we should enable and/or write a tutorial about, as it’s not that straightforward, especially because we have two APIs right now through which you can do it (you probably noticed that ) - one is the GraphQL way, which you have tried out, and that supports queries, and the other one is the REST way, which we use for sending and receiving (and that doesn’t support queries).

In .NET, To resolve the “not fun” part of the dynamics and such, i would actually forego the graphql way, and go for receiving the objects the classic way the connectors do and writing a traversal function to isolate what object categories you need. Would you need some help with that? Someone from the team could give it a shot!

I’m recommending this way mostly because we have Support queries on the get object REST endpoints. · Issue #340 · specklesystems/speckle-server · GitHub in the backlog since a while, and we plan to tackle it sooner or later! (will add support for querying objects on the REST endpoint too).