Skip to main content
Solved

Schema Mapper - Unexposed Attributes

  • September 27, 2019
  • 2 replies
  • 63 views
tomw202
Contributor
Forum|alt.badge.img+4

Hi All,

I've got a situation where I am dynamically feature reading in any number of feature types, and exporting via the generic port. I then have a list of all possible feature types and the schema mapping required. Am I right in assuming the SchemaMapper requires attributes to be exposed to be "mapped"? I'm looking for a solution where the SchemaMapper can see the dynamic unexposed attributes and map them.

Best answer by takashi

Hi @tomw202, I don't think it's essential that attributes to be mapped are exposed. The SchemaMapper should work based on an external table defining schema mapping even if the source attributes are unexposed.

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.

2 replies

takashi
Celebrity
  • takashiCelebrity
  • 7843 replies
  • Best Answer
  • September 27, 2019

Hi @tomw202, I don't think it's essential that attributes to be mapped are exposed. The SchemaMapper should work based on an external table defining schema mapping even if the source attributes are unexposed.

Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
tomw202
Contributor
Forum|alt.badge.img+4
  • tomw202Contributor
  • Author
  • Contributor
  • 18 replies
  • September 27, 2019

Hi @tomw202, I don't think it's essential that attributes to be mapped are exposed. The SchemaMapper should work based on an external table defining schema mapping even if the source attributes are unexposed.

You're correct! I had a simple error in my mapping file that meant they were not working. But unexposed attributes work fine :)

Community Stats

32,079
Posts
121,817
Replies
39,714
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
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.