I'm trying to create a series of attributes based on values of other attributes (I have some FieldName/FieldAttribute combos that I want to turn into attributes on the feature). When I create an attribute called @Value(FieldName), anything I output to the Data Inspector won't show. It just shows ? row(s) and doesn't load anything. Is this a bug or am I missing something?
Page 1 / 1
Which version FME are you using? If I remember correctly it is actually a bug in older builds
@jakethepainteryes you are right its an Inspector bug in 2016.1, where attributes are not displayed properly in the inspector but the issue has been fixed in FME 2017.
The workaround is
1) Add a Logger and inspect the attributes in the log.
2) Run with Full Inspection and either double click on the feature count after the transformer, or right-click on the feature count and select Inspect features, to view the attributes in Data Inspector.
Thanks. I am using 2016.1
Do you have any tips on how to expose the attributes that get created by this @Value(FieldName) in the workbench? For example, for one feature I might now have an attribute called Material where for another I have an attribute called Height. Say I want to use a FeatureMerger on the Material attribute later in the workbench... Or write out the data to a csv. I'm a little confused about how to make use of the value-driven attribute name.
Hi @jakethepainter you should be able to just use the @value attribute in the feature merger to merge the data that matches. But you can use the attribute exposer to then expose your new attribute values if you wish to write the data out to csv. I have attached a quick sample which will show you what I mean
If you have a lot of attributes to expose you might want to use the import function in the attribute exposer that way FME can scan the attribute values for you and import otherwise you can just type the possible values. Hope that helps!
Thanks, this is very helpful. The AttributeExposer is a great idea. That makes it explicit and a little easier to manage in my case.
Thanks, this is very helpful. The AttributeExposer is a great idea. That makes it explicit and a little easier to manage in my case.
@jakethepainteryes you are right its an Inspector bug in 2016.1, where attributes are not displayed properly in the inspector but the issue has been fixed in FME 2017.
The workaround is
1) Add a Logger and inspect the attributes in the log.
2) Run with Full Inspection and either double click on the feature count after the transformer, or right-click on the feature count and select Inspect features, to view the attributes in Data Inspector.