Hi all,
I see some strange behaviour when converting a simple 2D box from PostGIS to Geopackage in a dynamic mode (using schema).
I have attached a simple workspace which demonstrates the strange behaviour. A simple box is created in 2D and writen to PostGIS as a postgis_polygon. I ckecked the table in the database and is has the correct definition for the geometry (geometry(Polygon, 28992)). After the creation the table is read wit a FeatureReader of type PostGIS with the same connection parameters. It is set to read the schema and the features. The result is directly written to a geopackage with a FeatureWriter. Geometry is from schema definition. When i open the result in the Data Inspector i see the geometry type has become geopackage_multisurface where i would expect it to be of type geopackage_polygon.
At the moment we are upgrading our FME environment (Form and Flow) from FME 2021.2.6 to 2023.1.2 and ran into this problem. In FME 2021.2.6 i did not see this behaviour. This particular problem is part of a huge workspace which generates a lot of tables in PostgreSQL/PostGIS and at the end of the workspace all of these tables need to be exported to a desired format where Geopackage is one of the options.
Does anyone have a solution or an idea how to solve it?
