Skip to main content
Solved

How can I see attributes with SchemaScanner when the dataset is empty?

  • September 21, 2022
  • 2 replies
  • 21 views
carmijo
Supporter
Forum|alt.badge.img+11

I'm working with the SchemaScanner transformer and trying to compare two similar schemas for differences.

 

However, one of my datasets is a shell and has no features in it (the top feature reader and stream in the workspace screenshot) This seems to be causing SchemaScanner to output different results than my dataset that has features.

 

I'm basing my workspace off this article here - https://community.safe.com/s/article/How-to-SchemaScanner-Transformer

 

How can I compare the schemas in this case?

 

workspace 

Here's the list exploder output from the feature class that has features

list exploder output feature class with featuresWhile here's the list exploder output from the featureclass with no features

list exploder output feature class without features

Best answer by debbiatsafe

Hi @carmijo​ 

I believe you should get the same results for both feature classes if you change the input for the ListExploder to accept the feature from SchemaScanner's Output port instead of the Schema port for the feature class without features (ie. so it matches the bottom workflow).

Note that it is not necessary to use a SchemaScanner transformer in your case since you already have a schema feature from the FeatureReader and you have not modified the schema in any way before passing the schema feature to the ListExploder.

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

2 replies

debbiatsafe
Safer
Forum|alt.badge.img+20
  • debbiatsafeSafer
  • Safer
  • Best Answer
  • September 24, 2022

Hi @carmijo​ 

I believe you should get the same results for both feature classes if you change the input for the ListExploder to accept the feature from SchemaScanner's Output port instead of the Schema port for the feature class without features (ie. so it matches the bottom workflow).

Note that it is not necessary to use a SchemaScanner transformer in your case since you already have a schema feature from the FeatureReader and you have not modified the schema in any way before passing the schema feature to the ListExploder.

carmijo
Supporter
Forum|alt.badge.img+11
  • carmijoSupporter
  • Author
  • Supporter
  • September 24, 2022
debbiatsafe wrote:

Hi @carmijo​ 

I believe you should get the same results for both feature classes if you change the input for the ListExploder to accept the feature from SchemaScanner's Output port instead of the Schema port for the feature class without features (ie. so it matches the bottom workflow).

Note that it is not necessary to use a SchemaScanner transformer in your case since you already have a schema feature from the FeatureReader and you have not modified the schema in any way before passing the schema feature to the ListExploder.

Hi @debbiatsafe​, thanks for the response. I confirmed that fixes it. Take care!

Reply


Helpful Members This Week

Community Stats

31,191
Posts
118,235
Replies
38,799
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.