merge fields

merge fields

The merge fields module combines the input fields from up to 4 separate inputs into a unified single field with any number of nodal data components, which can be output to other modules for processing or directly to the viewer. This is useful when you want to slice through or otherwise subset multiple fields using the same criteria.

You must be aware that fields contain more than just grids and data. They contain meta-data set during the creation of those grids and data, including, but not limited to:

• Data Processing (log or linear)
• Coordinate units
• Data units (mg/kg or %)
• Data Min and Max values (ensures that datamaps from kriging match datamaps in post samples)

NOTE: There are potential dangers and serious consequences of merging fields because we allow for merging of data without requiring strict name or meta data matching.

• Meta data from the leftmost input field is always used for the merged result.
• You can only merge fields having the same number of nodal and/or cell data components.
• We do not require strict name matching, therefore it is possible to merge data with very negative consequences. Examples are:
  • Benzene data from one input field with Toluene from another field.
  • Log Processed TPH data with linear processed TPH data.
  • One field with coordinate units of meters with another in feet.
• Overlapping Volumes: When you merge fields you must be aware that this is not an alternative way to create the union of multiple plumes.
  • The merge fields module does not remove overlapping volumes.
  • Volume calculations with volumetrics can count overlapping regions multiple times giving nonsensical values.

The Merge Cell Sets When Possible option works only if you have matching types and names. A good and appropriate example is merging fault blocks so that all “Clay” cell sets are controlled as a single entity.

Ports

Properties