For the moment, I created a workaround: I read the table, together with the spatial data, in a SpatiaLite reader. Then I read the same table in an SQLite reader, which can detect the PKUID field, but does not contain the spatial data. A FeatureMerger does the rest.
Best answer by brianatsafe
Hi @bakkermans,
I am writing to let you know that this issue should be fixed in the latest beta of FME 2017 (b#17159). If you have any issues with the fix please do let us know.
One note here is that the attribute won't come up as "PKUID" or alike. It will come up as a "spatialite_id" format attribute instead.
Regards,
Brian
+11Hi @bakkermans,
I am writing to let you know that this issue should be fixed in the latest beta of FME 2017 (b#17159). If you have any issues with the fix please do let us know.
One note here is that the attribute won't come up as "PKUID" or alike. It will come up as a "spatialite_id" format attribute instead.
Regards,
Brian
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
