General Geometry from Range/Reference collection node

Hi all,

I am trying to grab a mixed bag of otherwise valid elements from a reference file, using the range node, to pass them through to the "Solids" and "PlanSymbols" inputs of the Compound Cell node.

Please tell me there a neat "General" geometry node trick to do this, rather than having to create a node for each type of element...

Regards

Robert

  • Hi Rob

    Not that I am aware of but having a way of providing a list of all elements inside a range, where you might be able to pick and choose the ones you want might be very useful. 

    Could you raise a ticket for that and link it to this thread? 

    I wonder if a function could provide that, looking for a set list of object types. In a Compound Cell you are likely to have Solids for the 3D Component, then lines, arcs, circles, polygons, etc for the 2D components. The list shouldn't be too exhaustive I would have thought. 

    Stuart


    This is a test

  • Hi,

    I was thinking of a similar workflow that would create all the necessary nodes(eg. solid, line, polyline...) required. In this workflow, we would not require to check with every node to find out which one is working.

    I would try creating this function. 

    Thanks,

    Anik

  • Well - I was thinking along the lines of the element enumerator in VBA, where you need to filter for valid components yourself, either with scan criteria beforehand, or a element by element check as a post scan loop.

    I guess toy could set a bunch of checkboxes as a node inputs, for things to filter for, along with the range+reference inputs, and you would get nice neat lists of each kind of filtered element as output.

    Ticket number:  7001172424

    Look Like i might need to try code something in the meantime.

    Thanks

  • Hi Robert,
    I'm not quite sure what you're trying to achieve; if you only need those 2 specific feature types from the reference then it should be easy enough to use the standard nodes, GC will automatically filter for the element types e.g. when using Solid.ElementsInRange and specifying the ReferenceAttachment in the input, only the solids are returned from that specified reference file.

    Alternatively if you do want to retrieve all the valid feature types possibly found in a reference (instead of just 2 types) then you could script this in a function node as Stuart suggested.
    Cheers,

    Ed

  • I am trying to automate the building (and rebuilding) of large arrays of compounds cells.
    I have gotten round my immediate problem scripting in VBA to drive the OBD dialogs (slow), and using named groups to split out 3D, 3D, perforator elements.

    Yes, I realise I could set up several nodes, one for each type of element, to filter out the reference info and pass those to the compound cell node. (sort of a bottom up approach)
    This way you approach the problem from the direction of types of node GC already knows about.

    I was looking for a way to grab and pass through elements that there may not be explicit GC nodes for. eg. forms or complex compound/stitched elements. GC might not know how to deal with these (directly) but they can/should be passed through to the Compound cell node. So I was looking for a node/method that approaches the problem from the top down.

    Thanks for the reply.