Skip to main content
Question

FME Dynamic writer to geopackage with no geometry creates geom column in table

  • July 24, 2026
  • 4 replies
  • 69 views
arnovananrooij
Contributor
Forum|alt.badge.img+5

Hi,

I have a dynamic feuture writer which writes tables from my PostGreSQL/PostGIS database to a geopackage. Some of the source tables are with no geometry and some are with. This is why I have two readers, one for Posgresql and one for PostGIS. I write all the tables dynamicly to the geopackage with a FeatureWriter and have set the geometry type to read from schema definition. In the resulting geopackage I see the table which should not have a geometry with a geom attribute with all null values. The table gpkg_contents has a data_type features instead of attributes. When I try the same with a manual definition it works fine.

QGIS does not seem to have any problems with the geopackage that has the wrong definition, but ArcGIS Pro has. How can i get the dynamic writer to write correct to the geopackage? Or is this a bug or a works as designed? 

I run FME 2023, but also tried it with FME 2025.

Thank you all

    4 replies

    j.botterill
    Evangelist
    Forum|alt.badge.img+62
    • j.botterillEvangelist
    • Evangelist
    • July 27, 2026

    So FME appears to be resolving the destination schema as a spatial table definition even when the incoming PostgreSQL table has no geometry.

    Just before the FeatureWriter, inspect the ‘Schema’ feature in feature/record information... expose:

    fme_geometry{}

    fme_schema_handling

    fme_schema_feature_type

    and any writer-related schema attributes such as geopackage_type = ?? 

     

    Does seem like a bug where dynamic schema generation is not propagating the equivalent of none geopackage. Perhaps raise this to safe support refereencing this article

    arnovananrooij
    Contributor
    Forum|alt.badge.img+5

    So FME appears to be resolving the destination schema as a spatial table definition even when the incoming PostgreSQL table has no geometry.

    Just before the FeatureWriter, inspect the ‘Schema’ feature in feature/record information... expose:

    fme_geometry{}

    fme_schema_handling

    fme_schema_feature_type

    and any writer-related schema attributes such as geopackage_type = ?? 

     

    Does seem like a bug where dynamic schema generation is not propagating the equivalent of none geopackage. Perhaps raise this to safe support refereencing this article

    Hi,

    To me it looks all good

     

    arnovananrooij
    Contributor
    Forum|alt.badge.img+5

    So FME appears to be resolving the destination schema as a spatial table definition even when the incoming PostgreSQL table has no geometry.

    Just before the FeatureWriter, inspect the ‘Schema’ feature in feature/record information... expose:

    fme_geometry{}

    fme_schema_handling

    fme_schema_feature_type

    and any writer-related schema attributes such as geopackage_type = ?? 

     

    Does seem like a bug where dynamic schema generation is not propagating the equivalent of none geopackage. Perhaps raise this to safe support refereencing this article

    Hi,

    To me it looks all good

     

     

    desiree_at_safe
    Safer
    Forum|alt.badge.img+22

    Thanks for opening a support case with us, ​@arnovananrooij! There’s an open case for our development team to dig into this issue.

    We’ll update the community once that’s been resolved! Thank you for raising this 🙂

     

    [Internal Note: FMEENGINE-99093]

    Happy FME-ing!

    Community Stats

    32,806
    Posts
    124,388
    Replies
    41,360
    Members
    Terms & ConditionsAccessibility statement
    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.