I have approximately 170 tables from a sqlite database that I need to convert to geojson and save as @Value(fme_feature_type). I have a workflow to process each table individually but I need a way to automate the process. Passing all tables through the same workflow merges the schemas of all input tables. It isn't practical to pass each table through its own set of transformers when dealing with this amount of tables. Some type of loop control seems logical to pass tables through the workflow one after another while ensuring that output schemas are refreshed after each iteration. I'm fairly new to FME so any help would be truly appreciated. 
Solved
Converting each table from a sqlite database to geojson and maintaining individual schemas
Best answer by takashi
GeoJSON file is treated as a dataset in FME, so you want to use Dataset Fanout when you need to separate destination GeoJSON file for each source feature type (table).
See here to learn more: Separating Output Data with Fanout
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
- Best Answer
GeoJSON file is treated as a dataset in FME, so you want to use Dataset Fanout when you need to separate destination GeoJSON file for each source feature type (table).
See here to learn more: Separating Output Data with Fanout