Skip to main content
Question

Strange Behavior in Conditional Value with "Attribute has a value" Operator

  • October 5, 2018
  • 3 replies
  • 29 views

takashi
Celebrity

When I was thinking of a solution for this question, encountered a strange behavior on conditional value setting.

Calculate percentage of how many features in a group have a certain value

My intention is to create a new attribute "_flag" and assign 1 if the attribute "Type" has a value, 0 otherwise. I believe that this conditional value setting in the AttributeCreator should work as expected.

Workspace: (FME 2018.1.0.2)

However, the result was:

I cannot find any specific reason, but I suspect that the "feature table" technology has a defect related to this symptom. Could you please investigate this?

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

Forum|alt.badge.img+2
  • 1891 replies
  • October 5, 2018

@takashi - it does look like this is related to feature tables. If you convert the source data to excel then your tests work fine. I have logged a change request to get this fixed.


Forum|alt.badge.img+2
  • 1891 replies
  • October 5, 2018

I also confirm this bad behaviour with MapInfo extended Tab - so it does indeed seem to be related to feature tables rather than CSV format only. Jira Issue: FMEENGINE-57152


takashi
Celebrity
  • Author
  • 7843 replies
  • October 5, 2018

I also confirm this bad behaviour with MapInfo extended Tab - so it does indeed seem to be related to feature tables rather than CSV format only. Jira Issue: FMEENGINE-57152

Thanks for your confirmation. Hope this issue will be fixed ASAP.