Skip to main content
Question

Preserving the ObjectID datatype in a file Geodatabase

  • March 5, 2020
  • 1 reply
  • 104 views
pimververgmail

A selection of features from an Oracle database by means of an Esri Geodatabase (ArcSDE Geodb) reader gets exported to a file geodatabase. The original database table has an ObjectID field which is unique. However, the reader considers this field as of type Integer. In de exported file geodatabase this field is still of type Integer. A python script compares the original table and the table in the file geodatabase on the basis of a common field of type ObjectID, which obviously fails.

Is there a way within FME to change the field type from type Integer into type ObjectID or should I take an alternative route?

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.

1 reply

M
Forum|alt.badge.img+2

@pimververgmail FME doesn't have a data type ObjectID - so represents it as 'integer'. In the underlying database, ObjectID is represented as an int (SQL Server say). But if you touch an attribute in something like AttributeManager then the data type might get switch to a string - check in the Data Inspector. If you're using Python to do the matching then you might have to cast the attribute to ensure they are the same data type. But matching works fine in ChangeDetector

Community Stats

32,207
Posts
122,305
Replies
39,891
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
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.