| On this page |
A partition is created for each bounds item, and includes all of the source items that overlap with that bounds item. This is done by comparing each source item with each bounds item, using the Compiled Block to do the test.
The default internal Compiled Block creates a Bounding Box for the bounds item to do the overlap test. This test can be overridden by specifying another external Compiled Block. The Compiled Block must return non-empty geometry if there is overlap. Therefore an empty geometry result means that there is no overlap.
Parameters
Bounding Geometry Parms
The geometry specifying the bounds for the intersection test.
Geometry Source
Where to load the geometry from:
SOP Node
Enter the path to a SOP node in the current HIP file. This node will cook that node and store its output geometry. Note that you can use the Evaluation time parameter to cook the SOP node at a different point in the timeline.
Upstream Output File
Get the file path from the incoming work item’s output attribute and read the file in as geometry. This is useful, for example, to use a 
File Pattern node to generate work items representing geometry files and then load them in this node.
Upstream Geometry Data
Get the geometry data from an attribute on the incoming work item. For example, if it has geometry data loaded by a previous Geometry Import node.
Custom File Path
Load the geometry data from a file at a given path.
SOP Path
When Geometry source is "SOP Node", the network path of the SOP node to cook. For example, /obj/geo1/output1.
Evaluate with Work Item Attributes
When Geometry source is "SOP Node", turn this on if the SOP network uses @attribute expressions to pull values from work items, for example for wedging. (If you use @attribute expressions, this node needs to cook the SOP separately for each work item. If you don’t, the node only has to cook the SOP once.)
File Tag
When Geometry source is "Upstream Output file", only load from file paths tagged with this file tag (for example, file/geo).
Load Geometry During Cook
When Geometry source is not "SOP Node", load the geometry when each work item cooks. Turn this on if you need to load files that are generated earlier in the network. When this is off, the node loads the geometry when the work items generate (including when you request generation of static work items ahead of time) rather than when the work items run.
Merge Input Geometry
When Geometry source is "Upstream Output file", what to do if an upstream work item has more than one path in the output attribute. If this is on, the multiple files are merged into one piece of geometry. If this is off, the first input file or geometry source is used.
File Path
When Geometry source is "Custom file path", the file path of the geometry file to import.
Source Geometry Parms
The source geometry that will be tested for intersection.
Geometry Source
Where to load the geometry from:
SOP Node
Enter the path to a SOP node in the current HIP file. This node will cook that node and store its output geometry. Note that you can use the Evaluation time parameter to cook the SOP node at a different point in the timeline.
Upstream Output File
Get the file path from the incoming work item’s output attribute and read the file in as geometry. This is useful, for example, to use a File Pattern node to generate work items representing geometry files and then load them in this node.
Upstream Geometry Data
Get the geometry data from an attribute on the incoming work item. For example, if it has geometry data loaded by a previous Geometry Import node.
Custom File Path
Load the geometry data from a file at a given path.
SOP Path
When Geometry source is "SOP Node", the network path of the SOP node to cook. For example, /obj/geo1/output1.
Evaluate with Work Item Attributes
When Geometry source is "SOP Node", turn this on if the SOP network uses @attribute expressions to pull values from work items, for example for wedging. (If you use @attribute expressions, this node needs to cook the SOP separately for each work item. If you don’t, the node only has to cook the SOP once.)
File Tag
When Geometry source is "Upstream Output file", only load from file paths tagged with this file tag (for example, file/geo).
Load Geometry During Cook
When Geometry source is not "SOP Node", load the geometry when each work item cooks. Turn this on if you need to load files that are generated earlier in the network. When this is off, the node loads the geometry when the work items generate (including when you request generation of static work items ahead of time) rather than when the work items run.
Merge Input Geometry
When Geometry source is "Upstream Output file", what to do if an upstream work item has more than one path in the output attribute. If this is on, the multiple files are merged into one piece of geometry. If this is off, the first input file or geometry source is used.
File Path
When Geometry source is "Custom file path", the file path of the geometry file to import.
Compiled Block Parms
This allows to override the default intersection test by specifying another Compiled Block.
Compiled Block
The Compiled Block used for the overlap test. The default Compiled Block uses a Bounding Box for the bounds item. The Compiled Block returns non-empty geometry if there is overlap. Therefore an empty geometry result means that there is no overlap.
Compiled Block Bounds
When using another Compiled Block, as an override, this should specify the Block Begin Compile’s Input Name, so it can be used to forward the bounds input items.
Compiled Block Source
When using another Compiled Block, as an override, this should specify the Block Begin Compile’s Input Name, so it can be used to forward the source input items.
Examples
example_top_partitionbybounds Example for Partition by Bounds TOP node
This example demonstrates how to use the partition by bounds node in PDG/TOPs.
| See also |
Partition by Tile
