AnsweredAssumed Answered

Calculating field on joined table populates attributes with ObjectID not the choosen field.

Question asked by gabrisch on Nov 20, 2015
Latest reply on Oct 10, 2018 by imc.manuel.mamani

I have a feature class of building footprints and a surface (LiDAR highest hit - LiDAR last return).  I am trying to use this surface to estimate the height of the buildings.

 

Transferring the values from the raster to the polygons should be a straight forward operation using add surface information but that tool is useless and returns a 99999 error code.

 

I tried the Zonal Statistics as a Table, then joined the table using the object ids.  I want to populate an existing field in the feature class with the mean value from the zonal statistics output but the field calculator (both within the attribute table and the Toolbox tool) populate the attribute with the objectID value.  This is odd behavior.

 

Both data are in the same projection, UOM, datum....

 

I do not understand why this is happening.  Is this a know bug or a problem specific to my installation?

Should I accept that I should export the join to a new FC and just clean up the e-trash later?

Outcomes