My format attributes are exposed from the source up to my destination feature class but these format attributes are not written on my FGDB. I can tell which of these formats have values from my inspector. Should I map these format attributes with an AttributeCreator or AttributManager so that they will be written?
Question
Format Attributes on FGDB writer
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.
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.
+62- Celebrity
Format attributes are specific to each format, in most cases you will not have to do anything special with them and they may indeed not (seem to) show up in your destination file. But "under water" FME usually does process them.
So short answer: you most likely don't have to map those attributes.
Inspect your destination data, both with the Data Inspector and with ArcGIS and if it looks ok then you don't need to worry about format attributes.
(I know, bit cryptic, sorry about that...)
Format attributes are not attributes in the regular sense, but carriers of metadata about your features. The format attributes are generated by the reader (whether you expose them in your workspace or not) and consumed by the writer, depending on the format.
You can e.g. use format attributes to instruct the writer to create your feature class inside a feature dataset, etc.
If you want to write your format attributes in your output feature class, I'd recommend renaming them to something else, e.g. rename "geodb_feature_dataset" to "DATASET" and then treat it like a regular attribute.