11-28-2019 01:49 AM
12-02-2019 12:53 AM
12-02-2019 05:22 AM
If the Union Features operator is hardcoded to assume/expect geometry fields named "Geometry" then that is a bug and should be submitted as a support ticket. But what I suspect is going on, is that it simply does not match the geometry fields because they have different names.
Study the information in the Union Features operator help topic that begins with "Fields are matched by name (case-insensitive comparison) and data type." Fields from two sets of features are never assumed to be the same (and therefore unionable) unless they share the same name. The solution is to ensure that the original geometry field name (whatever it may be) is carried through by all prior operators to the point of submission to the union.
This can be done in at least two ways:
12-02-2019 07:54 AM
Many thanks to Hal for explaning how Union function works. For ERDAS IMAGINE users it is useful to keep in mind that geometry is just another attribute of a particular type.
Meanwhile, there appeared to be an issue with how Rename Attributes operator renames the geometry field names, so for now Functional Attributes can be used to automatically match the geometry field names of 2 features. Example (model attached as well):