Known Issue: MultipleGeometryFilter, MultipleGeometryCoercer and all Transformers with GQuery Not Reading Multiple Geometries in FME 2025.2

Issue

In FME 2025.2.x, GML readers no longer read multiple geometries as a single geometry with a specialized multiple-geometry aggregate. Instead, multiple geometries are read as a single geometry with a generic aggregate that contains all component geometries. While this change does not appear to result in any loss of feature attributes or geometry information during read or write operations, it affects workflows that use the MultipleGeometryFilter, MultipleGeometryCoercer or any transformer that uses GQuery to work with the 'Multiple geometry' geometry type

This behavior applies to all GML-based formats, including (but not limited to) GML, CityGML, INSPIRE, and AIXM 5.

2025.2 Current Behaviour - Note simple Aggregate (missing multi-geometry descriptor)

2025.1 prior behaviour - note Aggregate (Multiple Geometry: 2 Geometries)

Resolution

This issue has been resolved in FME 2025.2.4

If workflows use either the MultipleGeometryFilter, MultipleGeometryCoercer or any transformer with GQuery, use FME 2025.1 or older.