Skip to main content
Hi,

 

 

Hi, I have a scenario where I have a Geodatabase Feature class which has a subtype.

 

 

Depending on the subtype I split the data into a feature class and a related table. The relationship class is defined as 

 

 

Source OID

 

Destination RelatedOID

 

 

In a standard scenario one would have a pre-existing Destination table and can use counters, and renamers, etc  or the data model would not have used the OID for the relationship.

 

 

Does anyone know how one might go about getting the OID of the newly created feature and populating that into the related table?  I might have to do this as a subprocess or seperate model to post process the data but would like to avoid that if at all possible.

 

 

Thanks
Hi,

 

 

I may not understand your question correctly...

 

If you need to write features into different tables depending on subtype, the "fanout" option of the writer could be a solution.

 

Open "Feature Type Properties" dialog box of the writer, check on "Fanout By Attribute" and select the attribute containing subtype identifier.

 

Then, the writer will output features to different tables depending on subtype.

 

And if you need to create new ID as sequential number for each subtype, you can use the Counter; specify the subtype attribute to "Counter Name".

 

Takashi
About the relationship classes, here is a related documentation: 

 

Creating Relationship Classes

 

http://docs.safe.com/fme/html/FME_ReadersWriters/Default.htm#geodatabase/Creating_Relationship_Cl.htm

 

"Currently, FME cannot be used to create relationship classes."
Hi

 

 

for new created features you can create our own OID with the counter. The attribute name has to be "geodb_oid".

 

 

Thomas
Turns out all one needs to do is create a counter as mentioned and assign it to the related table - into the Destination field. Works, odd, but works

Reply