Select to view content in your preferred language

Shape_area and shape_length field disappear when exporting to a .sde

1354
2
Jump to solution
03-30-2022 12:21 PM
DanaYoung
Regular Contributor

Can anyone explain why these two fields disappear when I export/import the feature class from a file geodatabase (.gdb) to a server geodatabase (.sde). I have definition queries that use these fields, I tried to create new fields, but then the calculate geometry was unavailable.

0 Kudos
2 Solutions

Accepted Solutions
DanPatterson
MVP Esteemed Contributor

Fundamentals of field calculations—ArcGIS Pro | Documentation 

You would have to calculate area/length fields under a different name since the file geodatabase maintains those fields.


... sort of retired...

View solution in original post

VinceAngelo
Esri Esteemed Contributor

Long, long ago, Arc/Info had LENGTH field on LINE coverages, and AREA and PERIMETER on POINT and POLYGON (because they shared the ".PAT" suffix). Those properties were retained as methods on geometries in SDE, ArcSDE, and enterprise geodatabase, depending on the storage (and topology class).

In the meantime, file geodatabase was created, and it exposed these meta-properties as fields, but the units are Cartesian, so they're not completely useful in all use cases.

If you want to keep these phantom fields across datasets, it's often best to create your own fields to preserve them (but then you have to update them if the geometry changes).

- V

View solution in original post

2 Replies
DanPatterson
MVP Esteemed Contributor

Fundamentals of field calculations—ArcGIS Pro | Documentation 

You would have to calculate area/length fields under a different name since the file geodatabase maintains those fields.


... sort of retired...
VinceAngelo
Esri Esteemed Contributor

Long, long ago, Arc/Info had LENGTH field on LINE coverages, and AREA and PERIMETER on POINT and POLYGON (because they shared the ".PAT" suffix). Those properties were retained as methods on geometries in SDE, ArcSDE, and enterprise geodatabase, depending on the storage (and topology class).

In the meantime, file geodatabase was created, and it exposed these meta-properties as fields, but the units are Cartesian, so they're not completely useful in all use cases.

If you want to keep these phantom fields across datasets, it's often best to create your own fields to preserve them (but then you have to update them if the geometry changes).

- V