Skip to main content
Solved

Attributes - exposing them when they show in inspector but don't show in any attribute list

  • January 31, 2018
  • 9 replies
  • 280 views
G
Forum|alt.badge.img

I have created a polygon layer from a numeric raster. RastertoPolygonCoercer shows a _label attribute to be created and this appears in inspector as the values from the raster. Perfect - but - I want to ensure this is carried through and written out to shapefile - except I can't "see" the attribute in subsequent transformers. So I thought attribute creator and map the attribute to a new field, or attribute exposer and ensure it appears, or even attribute mapper sounds a possibility. Except when it comes to picking the attribute you want to make available (_label) it doesn't appear in any list of available attributes. It doesn't appear in a shapefile written out and

I don't know how else to access it - Help.....

Best answer by david_r

You have to type in the attribute names manually:

 

 

Alternatively you can use the Import-button on the bottom right to import attribute names from e.g. a sample data file.

 

This happens when you have dynamic elements in your workspace where FME doesn't know at design-time (i.e. when you're authoring your workspace) what attributes will be available once the translation starts (run-time).
View original
Did this help you find an answer to your question?

9 replies

nielsgerrits
VIP
Forum|alt.badge.img+54

These attributes are unexposed attributes. Use the Exposer transformer to expose it.

G
Forum|alt.badge.img
  • garethgis
  • Author
  • January 31, 2018

Forgive a newbie but if I add and connect an AttributeExposer and click on the drop down list of attributes to expose the _label attribute doesn't show. So how do I get it to expose?

david_r
Celebrity
  • david_rCelebrity
  • Best Answer
  • January 31, 2018
You have to type in the attribute names manually:

 

 

Alternatively you can use the Import-button on the bottom right to import attribute names from e.g. a sample data file.

 

This happens when you have dynamic elements in your workspace where FME doesn't know at design-time (i.e. when you're authoring your workspace) what attributes will be available once the translation starts (run-time).
david_r
Celebrity
  • david_rCelebrity
  • January 31, 2018
garethgis wrote:

Forgive a newbie but if I add and connect an AttributeExposer and click on the drop down list of attributes to expose the _label attribute doesn't show. So how do I get it to expose?

You have to type in the attribute names manually:

 

 

Alternatively you can use the Import-button on the bottom right to import attribute names from e.g. a sample data file.

 

This happens when you have dynamic elements in your workspace where FME doesn't know at design-time (i.e. when you're authoring your workspace) what attributes will be available once the translation starts (run-time).
G
Forum|alt.badge.img
  • garethgis
  • Author
  • February 1, 2018

@david_rExcellent answer. I thought you could only pick from the drop down list that comes up as soon as you click in the box. Extra thumbs up for the explanation of the significance and importance of dynamic elements and run-time and the use of the import button. Made my day as my whole process was hanging on that one attribute.

R
Forum|alt.badge.img
  • ramcgreg
  • November 26, 2019
nielsgerrits wrote:

These attributes are unexposed attributes. Use the Exposer transformer to expose it.

I tried the import option and chose a table with a list of the names of attributes I wanted to expose. All I ended up with was the name of the field that contains the 48 separate field names. Is this some obvious mistake I'm making that is easily explained?

 

Thank you,

 

Randy McGregor

ebygomm
Influencer
Forum|alt.badge.img+38
  • ebygommInfluencer
  • Influencer
  • November 26, 2019
ramcgreg wrote:

I tried the import option and chose a table with a list of the names of attributes I wanted to expose. All I ended up with was the name of the field that contains the 48 separate field names. Is this some obvious mistake I'm making that is easily explained?

 

Thank you,

 

Randy McGregor

You need to choose attribute values rather than attribute names when you import the list

R
Forum|alt.badge.img
  • ramcgreg
  • November 26, 2019
nielsgerrits wrote:

These attributes are unexposed attributes. Use the Exposer transformer to expose it.

You need to select "Attribute values" not "Attribute names" in the "Import from:" option. Unintuitive to me because these are the names of the attributes, not the values that populate them. Anyway, "Import" works beautifully for this. I had to create a table containing these values first, then I used that table with the "Import" option.

R
Forum|alt.badge.img
  • ramcgreg
  • November 26, 2019
ebygomm wrote:

You need to choose attribute values rather than attribute names when you import the list

Thank you! That was it.

Reply


Helpful Members This Week

Community Stats

31,333
Posts
118,864
Replies
38,957
Members

Latest FME

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie 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.