Skip to main content
  • EN

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?

 

image

If you're using Simple mode in the GeometryFilter, FME will try to homogenize heterogeneous collections, see the manual, under Parameters / General / Mode:

https://docs.safe.com/fme/html/FME-Form-Documentation/FME-Transformers/Transformers/geometryfilter.htm

If you're using Simple mode in the GeometryFilter, FME will try to homogenize heterogeneous collections, see the manual, under Parameters / General / Mode:

https://docs.safe.com/fme/html/FME-Form-Documentation/FME-Transformers/Transformers/geometryfilter.htm

So there's actually some little magic behind the scenes! Thank you for your feedback!

Reply


Community Stats

30,162
Posts
114,483
Replies
37,809
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.