I have a dynamic workflow that writes spatial data from a MS SQL Server to a postgis database. Since my inital data is not always restrictive on geometry types, I want to ensure that Geometry types are well defined in my destination database.
I had an issue with mixed lines and multilines that I solved using an aggregator (destination geometry (multilinestring) ) but I had some geometry collections creating some issues when writing data so I added a GeometryFilter.
Visually no feature is filtered (only lines) and the writing is doing great. Removing this filter will make the writing fail.
My question is then : Is the GeometryFilter altering the data or the way the data is presented to the writer?
