Skip to main content
  • EN

Hello,

 

I have a simple workspace that is reading in a feature class from a source geodatabase and writing it out to my target geodatabase. I am using (and need to use) a drop and create table handling method to write the feature class.

 

The source feature class I am reading from is contained in a feature dataset. I don't want this feature dataset to be written out to the target geodatabase; I am only interested in writing the feature class it contains. However, the writer recreates the feature dataset from the source gdb, even though I left the Feature Dataset Table Creation Parameter in the writer null.

 

How do I configure my writer so that only the feature class from the source geodatabase is being dropped and created, while ignoring and not recreating the feature dataset?

 

Thank you.Capture

The answer to my own question:

  1. expose the geodb_feature_dataset format attribute
  2. Use an AttributeCreator or AttributeManager to change that value to null
  3. Issue fixed: feature dataset is no longer getting created.

Thank you Steve M of safe support for this resolution.

You'll need to null/empty the format parameter for the dataset...

You can view the source data in the Inspector to see if these attributes (fme_dataset or geodb_feature_dataset) are populated.

 

Try adding an AttributeCreator, and play with either fme_dataset and geodb_feature_dataset attributes by setting it to nothing. This will remove the source dataset value.

Alternatively, AttributeRemover and remove these attributes will probably do the same thing.

 

 

Reply


Community Stats

30,186
Posts
114,578
Replies
37,853
Members
Terms & ConditionsCookie settings
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.