In a file geodatabase (GDB) to GDB translation, I am writing dynamically to a blank (unpopulated) template GBD that has relationship classes. From a source GDB I am reading features both from feature classes that participate in relationships and from the relationship feature classes themselves. I get the usual geodb_feature_has_relationships and geodb_oid format attributes on the participant features, and I get the usual geodb_type (= geodb_relationship in this case), geodb_rel_origin_oid, and geodb_rel_destination_oid format attributes on the relationship features; however, to keep the workspace generically dynamic and reusable, I need to determine--during translation--the names of the origin and destination feature classes for the relationship classes being read. Of course, I know what those feature classes are before runtime, but the dynamic, i.e., non-prescient, workspace does not. Is runtime determination of the origin and destination feature class names of an existing relationship class even possible in FME?
Best answer by natalieatsafe
View original