Skip to main content
Question

Fanout by fme_feature_type but remove irrelevant columns in each excel sheet

  • April 26, 2018
  • 2 replies
  • 38 views
S

I have a problem with writing the multiple sheet output to excel but keeping only the attributes that are relevant to each sheet. For example (as you will see on the image) SAC_NAME should only be in the sheet named Special Areas of Conservation and should not be present in the sheet Wood Pasture and Parkland... and vice versa the PRIHABTXT attribute should not appear in the sheet Special Areas of Conservation... What I get now are columns of empty attributes.

I tried to use PythonCaller to remove the empty attributes but it did not work, since the writing actually happens in the writer and PythingCaller is before the fan-out happens (I imagine that before fanout all is in one sheet and none of the columns is entirely empty).

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.

2 replies

takashi
Celebrity
  • takashiCelebrity
  • April 26, 2018

Hi @sylwianikel, the fanout just separates features to different destination feature types (worksheets) depending on the feature type name, it doesn't configure destination schema (user attributes) automatically.

If you will configure the destination schema statically as you did, you have to add multiple writer feature types for each schema and route features to an appropriate writer feature type according to their feature type name.

Or, if you want to use just a single writer feature type and configure destination schema dynamically depending on feature type name, consider setting "Dynamic Schema Definition" and additional common user attribute (_distance).

Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
S

Hi @takashi, Thank you for your reply and I'm sorry I replied so late. I'll try your solutions and see what I can do.

Community Stats

32,207
Posts
122,305
Replies
39,891
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.