Skip to main content
Question

dynamic-workflows-destination-schema

  • October 11, 2018
  • 4 replies
  • 24 views
V

Mark2AtSafe

Hi Mark

Hope you can help me out with questions in regards.

1) I am using arcgis and FME 2018

2) In FME, I am trying to do an analysis and results output I would like to have the destination attribute fields based on Multiple source featureless. So I am flowing the same method used in the below article. “I have following this https://knowledge.safe.com/articles/33838/dynamic-workflows-destination-schema-derived-from.html”

I am not able to get this working.

3) I have got two parts to achieve :a) I want the results of output to be split in different folders – example from featureclass B on the attribute value field "E" -I managed to do this by fanout @ value C

b) I want the results of the multiple feature class to have the specific attribute in the output and I wanted to remove some of the unwanted fields –

Example : FClass A with attributes A,B,C & CLASS B (D,E,F,G)

The output results of special selection with criteria class A & to have the attributes value( A, C,D,E,F). With attribute remover I am not able to remove the unwanted fields with dynamic workflow – can you please help me out.

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.

4 replies

takashi
Celebrity
  • takashiCelebrity
  • 7842 replies
  • October 11, 2018

Hi @vdevi09,

  • You can apply Dataset Fanout to separate destination folder according to an attribute value. See here to learn more: Setting Dataset Fanout.
  • Create multiple schema features for each destination feature type, and merge appropriate schema to data feature using the destination feature type name as Join On.
Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
mark2atsafe
Safer
Forum|alt.badge.img+56
  • mark2atsafeSafer
  • Safer
  • 2554 replies
  • October 12, 2018

OK, first let's check if dynamic is really necessary.

Say you have multiple feature classes, Class1 (Attributes A,B,C) and Class2 (Attributes C,D,E) and you wish to get an output such as NewClass (Attributes A,B,C,D,E) - i.e. all of the attributes from the source classes are added.

Now, if you know what those source attributes are in advance (you know that they will always be A,B,C,D,E) then you don't need to have a dynamic workspace. You can just use Manual or Automatic. That would be fine.

It's only when you have Class1 (Attributes ?, ?, ?) and Class2 (Attributes ?,?,?) that you need to have dynamic, and it's only when these classes need merging that you would need this technique (if the output were Class1, Class2, etc the same as the input, then you could use dynamic but you don't need to use this list/merge technique)

Anyway, if you just want to get a certain attribute (say Attribute X) in the output, then even in a dynamic translation you can just add that to the Attribute Definition tab in the writer feature type. It will get added to all classes that you write. You don't necessarily need to add it to the schema through a list.

Also, if you want to remove certain attributes (say Attributes R,S,T) then just manually enter them into the Attributes to Remove parameter on the writer feature type. Then they will be removed from all classes that you write.

I hope that helps. If you can provide a copy of your workspace - a screenshot probably won't be enough in this case - then it would help to diagnose if something is not set up correctly. But you would need to be clear about what exactly is failing in the translation (if there is an error or warning in the log, or just incorrect output).

FME Evangelist to the Rich and Famous!!
V
  • vdevi09
  • Author
  • 2 replies
  • October 15, 2018

OK, first let's check if dynamic is really necessary.

Say you have multiple feature classes, Class1 (Attributes A,B,C) and Class2 (Attributes C,D,E) and you wish to get an output such as NewClass (Attributes A,B,C,D,E) - i.e. all of the attributes from the source classes are added.

Now, if you know what those source attributes are in advance (you know that they will always be A,B,C,D,E) then you don't need to have a dynamic workspace. You can just use Manual or Automatic. That would be fine.

It's only when you have Class1 (Attributes ?, ?, ?) and Class2 (Attributes ?,?,?) that you need to have dynamic, and it's only when these classes need merging that you would need this technique (if the output were Class1, Class2, etc the same as the input, then you could use dynamic but you don't need to use this list/merge technique)

Anyway, if you just want to get a certain attribute (say Attribute X) in the output, then even in a dynamic translation you can just add that to the Attribute Definition tab in the writer feature type. It will get added to all classes that you write. You don't necessarily need to add it to the schema through a list.

Also, if you want to remove certain attributes (say Attributes R,S,T) then just manually enter them into the Attributes to Remove parameter on the writer feature type. Then they will be removed from all classes that you write.

I hope that helps. If you can provide a copy of your workspace - a screenshot probably won't be enough in this case - then it would help to diagnose if something is not set up correctly. But you would need to be clear about what exactly is failing in the translation (if there is an error or warning in the log, or just incorrect output).

@Mark2AtSafe

 

Thanks, its not the first two parts, its third part that I am trying to achieve. Can i send you my workspace so you can guide me what i am missing. Can you please message me your contact on vdevi09@gmail.com please.

 

 

V
  • vdevi09
  • Author
  • 2 replies
  • October 15, 2018

Hi @vdevi09,

  • You can apply Dataset Fanout to separate destination folder according to an attribute value. See here to learn more: Setting Dataset Fanout.
  • Create multiple schema features for each destination feature type, and merge appropriate schema to data feature using the destination feature type name as Join On.
@takashi, I am doind the folder based fanout, I am able to get the fanout going @value(attributeA) with outputs of featureclassA &B;

 

and its outputting allthe fields and I wish to have selected field in the output.

 

 

Community Stats

32,061
Posts
121,725
Replies
39,688
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
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.