Hi Everyone,
I’m kind of stuck with a problem with my Geopackage writer.
For a client, I’m working on building a script that generates multiple Geopackage tables, each with its own name. Each Geopackage table writer uses a fanout to automatically provide the writer with the needed file name. The writer also uses a Geopackage with styling embedded in the database, with 0 features, as a template file. This template is provided by an engineer from the team, which should automatically style the Geopackage based on the attributes it has.
The problem occurs when I have both fanout and template file enabled. This causes the Geopackage to only write certain features. I can’t find any logic behind why it writes some features and not others. The template file and the Geopackage writer are 1-to-1 copies of each other, and I get no errors/warnings regarding feature issues. For example, one table, which consists of 470 features, will write 233 features, and 237 features end up somewhere in space. :-)
When I disable the fanout and manually specify what my Geopackage should be named, there are no issues with the template file, and the output is automatically styled by the template.
This issue is easily resolved by not using a fanout, or by using a user parameter to describe the output name. However, I’ve had issues with FME FLOW not accepting my “output name” user parameter and thus creating random file names for my Geopackage writer, which is why I’ve wanted to use fanouts.
TL;DR: The Geopackage fanout writer causes issues with the template file. Only certain features get written, with no logic to be found by me.
Has anyone else encountered this issue?
Kind regards,
Roelof
