Skip to main content
Question

Data loading to an existing feature class

  • January 23, 2014
  • 2 replies
  • 55 views
G
Forum|alt.badge.img
Good morning to all

 

 

 I am running a process using schema mapper  to load data into an existing feature class. The problem that I am seeing in the translation is that FME is generating extra attributes that are not part of the schema of the featureclass that I am 

 

 

 

 When reviewing the log this is what I see:

 

 

"Value of feature type parameter 'GEODB_OBJECT_ID_NAME' for table/feature class 'Bridge' has been changed from 'OBJECTID' to 'OBJECTID_1' as it conflicted with user field name. Value of feature type parameter 'GEODB_SHAPE_NAME' for table/feature class 'Bridge' has been changed from 'SHAPE' to 'SHAPE_1' as it conflicted with user field name."

 

 

I added an attribute remover for the input files so that they didnt transfer over but I still get  the OBJECT and OBJECT_1, SHAPE_Area1, SHAPE_Lenght1.

 

 

Any thoughts?

 

 

 

2 replies

C
Hi Gerardo,

 

 

when you write into an ESRI format FME generates OBJECTID and SHAPE_Area, because it es necessary in every ESRI output.

 

When you copy your Reader schema to the Writer schema OBJECTID and SHAPE_Area are also includet (-> as User Attributes).

 

 

When FME starts the writing process it detects OBJECTID and SHAPE_Area but also wants to create these attributes. So FME gives a new name  -> 'OBJECTID_1'

 

 

You can avoid this by deleting OBJECTID and SHAPE_Area in your writer user attributes. Then the warning messages should dissapear.

 

 

Best regards,

 

Stefan
G
Forum|alt.badge.img
  • gerardo
  • Author
  • January 23, 2014
Stephan:

 

 Thanks for your response. I can try that but dont want to mess with the feature class schema..

 

 

The one thing I did was: I added an attribute remover to not include the "schemamapper_row_ids" attribute and now the output is working like it should-- I still see the warning in the log, but no extra attributes are created in the GDB.

 

 

I hope I could understandwhy it is doing this a little better. I need to add the "schemamapper_row_ids"  and run the model again to see if this is the  cause of the problem I am seen when loading the data into the existing feature class.

 

 Thanks

 

 

Reply


Most helpful members this week

Community Stats

30,846
Posts
116,935
Replies
38,669
Members
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.