Skip to main content
Question

Fan out to feature classes, instead of separate Geodatabases

  • August 22, 2014
  • 3 replies
  • 51 views

Forum|alt.badge.img
Hi,

 

I have a rather large workbench that brings features from a SQL Spatial Server and has four Feature Types that use GeoDatabase Writers. I was hoping that there was a way to bring everything into one Geodatabase that will fan out into separate feature classes. Instead it is fanning out based on an attribute, but it is making multiple Geodatabases, instead of writing into one Geodatabase with separate feature classes within it. Is there a way to configure the writers in order to get this accomplished?

 

I attached the log from my last Translation to maybe better express what I am doing.

 

 

http://pastebin.com/taKBBib2
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.

3 replies

takashi
Celebrity
  • August 22, 2014
Hi,

 

 

I guess you are using Dataset Fanout. Try Feature Type Fanout instead.

 

Dataset Fanout (http://docs.safe.com/fme/html/FME_Workbench/Default.htm#Setting_Dataset_Fanout_Properties.htm)

 

Feature Type Fanout (http://docs.safe.com/fme/html/FME_Workbench/Default.htm#About_Fanout.htm)

 

 

Takashi

takashi
Celebrity
  • August 22, 2014

fmelizard
Safer
Forum|alt.badge.img+21
  • Safer
  • August 25, 2014
In addition for dataset fan out expose the geodb_feature_dataset on the writer and use it in the fanout option.