Could we please have a new transformer that enables basic vector operations [intersection, difference and union as a minimum] between two geometry columns (i.e., columns that have been created using GeometryExtractor within a processing sequence) and stores the result as a geometry column that can be accessed using the GeometryReplacer. This feature request acknowledges that the AreaonAreaOverlay does this job when configured correctly with other transformers. However this requires two datasets to be compared across all spatial combinations each time the process is run which can take a very long time for very large row counts. It is common in spatial database thinking, to have long term storage of multiple geometries that travel together in the same rows (with incremental update at times) and to do repeat assessments in different queries.
The proposed transformer would in effect enable the multi-geometry operations that are possible (and extremely useful) as in the Oracle as an example:
SDO_GEOM.SDO_INTERSECTION,
SDO_GEOM.SDO_DIFFERENCE and
SDO_GEOM.SDO_UNION operators (google these words for details)
Having multiple-geometry operations would speed up very large and repeated table vector operations that compare two shapes in the same row.
Thank you
