Skip to main content
Solved

Why FeatureReader produces different output if you automate reader parameters?

garbadek
Contributor
Forum|alt.badge.img

When I populate a FeatureReader with dynamically generated values containing the options I want, it works but not completely. It reads the parcel data I want, but returns no schema/attribute data:

 

image 

If I manually fill in the values in the exact same reader. It produces the output I do want (I.E. the parcels and their data).

image 

This is super inconvenient since our process is based on the assumption that we will not have to populate workspace objects manually each time we run them. I feel like I am missing something fundamental here that will great enhance my understanding of FME. Please help me to understand why this behavior is happening. Any help pointing me to how I might get the automated values to generate the output I want would be greatly appreciated. Thank you for your time.

 

Kim

Best answer by thijsknapen

I just had a look myself. It seems that if you make the Feature Type to Read dynamic (have the value come from an attribute), FME outputs the results through the <Generic> output port.

That does make some sense to me, as it's no longer certain that your attribute value is always that specific Feature Type 'Parcels' (with the schema of 'Parcels').

 

I guess you have two options;

  • Keep the Feature Types to Read set to the 'static value' of 'Parcels' (you can keep the dataset dynamic)
  • Expose the attributes of your 'Parcels' feature type at/after the Generic port

 

The latter can be done either directly in the FeatureReader (Output -> Attribute and Geometry Handling -> <Generic> Port -> Attributes to Expose), or using an AttributeExposer.

View original
Did this help you find an answer to your question?

2 replies

thijsknapen
Contributor
Forum|alt.badge.img+10
  • thijsknapenContributor
  • Contributor
  • Best Answer
  • August 5, 2023

I just had a look myself. It seems that if you make the Feature Type to Read dynamic (have the value come from an attribute), FME outputs the results through the <Generic> output port.

That does make some sense to me, as it's no longer certain that your attribute value is always that specific Feature Type 'Parcels' (with the schema of 'Parcels').

 

I guess you have two options;

  • Keep the Feature Types to Read set to the 'static value' of 'Parcels' (you can keep the dataset dynamic)
  • Expose the attributes of your 'Parcels' feature type at/after the Generic port

 

The latter can be done either directly in the FeatureReader (Output -> Attribute and Geometry Handling -> <Generic> Port -> Attributes to Expose), or using an AttributeExposer.

nielsgerrits
VIP
Forum|alt.badge.img+54
thijsknapen wrote:

I just had a look myself. It seems that if you make the Feature Type to Read dynamic (have the value come from an attribute), FME outputs the results through the <Generic> output port.

That does make some sense to me, as it's no longer certain that your attribute value is always that specific Feature Type 'Parcels' (with the schema of 'Parcels').

 

I guess you have two options;

  • Keep the Feature Types to Read set to the 'static value' of 'Parcels' (you can keep the dataset dynamic)
  • Expose the attributes of your 'Parcels' feature type at/after the Generic port

 

The latter can be done either directly in the FeatureReader (Output -> Attribute and Geometry Handling -> <Generic> Port -> Attributes to Expose), or using an AttributeExposer.

This is correct. If the source is dynamic, the features are output via the generic outputport. The features and attributes are there, but they are unexposed. Check the output, select a feature and look in the Feature Information to see the unexposed attributes.

 

You probably want a dynamic output. See Tutorial: Dynamic Workflows on how to do this.

Reply


Helpful Members This Week

Community Stats

31,313
Posts
118,739
Replies
38,900
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.