Skip to main content
Solved

Relationship class with no source table

E
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

Best answer by tg

Hi

 

 

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

 

 

Thomas
View original
Did this help you find an answer to your question?
This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, 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.

4 replies

takashi
Contributor
Forum|alt.badge.img+19
  • takashiContributor
  • Contributor
  • October 23, 2013
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
takashi
Contributor
Forum|alt.badge.img+19
  • takashiContributor
  • Contributor
  • October 23, 2013
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."
T
  • tg
  • Best Answer
  • October 23, 2013
Hi

 

 

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

 

 

Thomas
E
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

Helpful Members This Week

Community Stats

30,938
Posts
117,250
Replies
38,740
Members

Latest FME

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
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.