Currently the attribute table of line resp. polygon features of a Query Feature Classes from a PostGIS/postgres client contain only the attributes of the data model and the "shape" attribute (see screenshot, attribute table at the top). The attribute table of the exact same data, but served as Enterprise Geodatabase Feature Class from an ArcSDE, contain additionally the attributes SHAPE.LEN for Line resp. Polygon features and SHAPE.AREA for Polygon features (see screenshot, attribute table at the bottom), which are calculated on the fly. Thus their value are always correct. SHAPE.AREA and SHAPE.LEN are updated when alterations of the geometry occurre, e.g. clip. This is a fundamental difference to calculating the length and area of the geometry using "calculate geometry", which calculates these values in a static way resulting in wrong values if later on the geometry would be modified.
![agp_swiss_parks_arcsde_bottom_and_postgis_top.png agp_swiss_parks_arcsde_bottom_and_postgis_top.png](https://community.esri.com/t5/image/serverpage/image-id/107745i653E375570F36040/image-size/large?v=v2&px=999)
We'd like to suggest to introduce the on the fly calculated fields SHAPE.LEN for Line resp. Polygon features and SHAPE.AREA for polygon features for Query Feature Classes from a PostGIS/postgres client, analogous to that functionality provided by a Enterprise Geodatabase Feature Class from an ArcSDE.