FeatureWriter and geometry type handling with GeoPackages

Hi ​@chau!

This is an expected behavior when writing to GeoPackages. You're correct; it's mapping to the broadest geometry type rather than the narrowest. This is because the Writer’s Automatic Schema Definition (<from first feature>) inherits the geometry from the first incoming feature, which in your case comes from the Creator’s generic <all> geometry source. This causes the writer to map to the broadest matching type (3D Measured Multi Curve). 

A workaround is to specify the geometry type by switching the Schema Definition to Manual and selecting "geopackage_linestring" under the Geometry Definition (shown below).

[Internal Reference: FMEENGINE-88364]

Hi ​@chau!

This is an expected behavior when writing to GeoPackages. You're correct; it's mapping to the broadest geometry type rather than the narrowest. This is because the Writer’s Automatic Schema Definition (<from first feature>) inherits the geometry from the first incoming feature, which in your case comes from the Creator’s generic <all> geometry source. This causes the writer to map to the broadest matching type (3D Measured Multi Curve). 

A workaround is to specify the geometry type by switching the Schema Definition to Manual and selecting "geopackage_linestring" under the Geometry Definition (shown below).

 

[Internal Reference: FMEENGINE-88364]

Hi ​@abbyatsafe 

So does this mean that the geometry of the Creator object has multipart, 3D and measures by default (even though the GeometryExtractor only reports 2D linestring) or does the FeatureWriter only determine the basic geometry type (point, line, area, ...) and applies the most broad definition?