Whats the ideal structure for filtering

Obviously each object contains lists and children and can be endlessly nested. But I wonder what is ideal in terms of the filtering within the viewer. Is it relatively shallow and simple?

Ideally, yes - flat things help when dealing with objects in code. If you though want end-user filtering, structuring things a-la layers in Rhino seemed universally “legible”.

The filtering api is quite powerful, though you need to wrap your brain around it first (see: speckle-server/packages/viewer at main · specklesystems/speckle-server · GitHub).

I’ve just got fme writing and I have an opportunity to structure any which way. I’d noticed the qgis streams not exposing data attributes at quite a shallow level hence the question.

Will experiment - ootb fme will be as generic as possible.

1 Like