I have read many posts and articles about FME and geodatabase domains, and nowhere can I find any mention of reading the domain name. I can resolve the domain code for any given feature, getting the <attribute>_resolved value. I am pretty clear on how I have to go about extracting all of the domains in a geodatabase. Given a full domain definition, I can create the coded_value(...)-formatted native_data_type value for a schema feature; however, I can find no reference to how to extract the associated domain name for a feature class in an existing geodatabase, at least with pure FME. This seems nuts, and I feel I must be missing something fundamental. Anyone have any pointers here? Any help is much appreciated.
Solved
How do I determine the domain name assigned to a feature class in a file geodatabase?
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.
+60- 2937 replies
- Best Answer
As far as I know this is not possible without the use of Python. See this topic for samples.
In earlier versions (2019?) the referenced domain was described in the FeatureReaders schema feature but not anymore as of today.
+1- Contributor
- 35 replies
As far as I know this is not possible without the use of Python. See this topic for samples.
In earlier versions (2019?) the referenced domain was described in the FeatureReaders schema feature but not anymore as of today.
Well, I was right, then: it's nuts. Any clue why Safe removed the reading of domains referenced? Thanks, @nielsgerrits