Enterprise Geodatabase Connection Feature Geometry Invisible in ArcGIS Pro

Zartico-GIS

I have a database connection made to my PostgreSQL Enterprise Geodatabase through ArcGIS Pro.

I am connected to the database as a user other than sde, and trying to see features of a feature class under that corresponding user's schema.

When I add the layer to the map:

1. I can "zoom to" the feature and the map zooms to it
2. I can "flash" and it flashes its centroid on the screen
3. I can see all the attributes
4. I cannot see any feature geometry through the map. It appears invisible.

Interesting Notes:

• When I export the FC from the EGDB to a local FGDB the feature is visible
• When I have an active edit session on the direct EGDB connection layer through ArcPro the feature DOES become visible.

 

Anyone know what's going on here?

 

ArcGIS Pro 3.0 and Postgres 13.x, ST_Geometry spatial type, Shape polygon. It was originally inserted into the feature class via SQL of inserting a WKT representation into Esri's shape field.

visible_exported_local.png

visible_edit_session.png

invisible_sde.png

KyleCrawford_0-1725471489737.png

2021-04-21_11-07-54.png

DougBrowning_0-1725471234059.png

Zartico-GIS

Hi Marcelo,

1. I deleted and created a new spatial index on the layer
2. Recalculated spatial index on the layer
3. Closed and reopened/reconnected DB

None of these worked.

I then exported to local and then imported back into the Enterprise Geodatabase. Now the layer is visible in the map view direct from the db connection.

With this behavior in mind, what could be the reason it isn't showing up? Potentially a cast or st_<function> is required during the PostgreSQL insert? 

EDIT

I compared the layer source properties between the visible and invisible DB connection feature classes. (Image attached).

The only differences I see are the under Storage and the extent. 

The invisible lists a SRID 0 and the visible has the appropriate SRID 4326. Yet both have the spatial reference set to WGS84...

 

Answer: What I needed to do was specific an SRID at the insert. I thought it was defaulted to 4326, and that was the FC spatial reference was that I was inserting into. Geometry now visible upon new inserts.