PostgreSQL Geometry field is ignored when trying to register dataset

[JVig]

I am attempting to migrate from SQL Server over to an Aurora PostgreSQL-Compatible RDS. During table registration, the geometry field appears to be omitted from the dataset. I cannot see it in data design tab, but it's present inside PGAdmin. I've also validated the geometry itself and viewed it in DBeaver.

My geometry field is created using ST_GeomFromText in this test dataset, but in our pipeline I write EWKB directly to the geometry field. Neither version shows up in arcgis - and the Register with Geodatabase tool's automated field detection is not finding any geometry field.

We have postgis installed along with postgis_topology and postgis_raster. The database is enabled and the data owner is able to invoke the postgis functions from within PG Admin.

Has anyone else run into this issue that might have some insight as to what is going on here? Interestingly enough, during proof of concept, I spun up a small RDS and tested this exact process and it works just fine. The larger database has more complexity with the roles, which may be the problem. 

[MarceloMarques]

Note, PostgreSQL Cloud Database Services only support PostGIS, the esri ST_GEOMETRY is not supported in Cloud Database Services because we cannot copy the ST_GEOMETRY library under the PostgreSQL Lib folder. If you use PostGIS functions, then everything should work fine. If your data is not stored in a PostgreSQL Esri Geodatabase then look into ArcGIS Pro Query Layers.

[JVig]

Hi Marcelo, thanks for the response. For clarification, we have a dataset in our db that has a geometry field in it. We run a spark sql pipeline that ingests EWKB into that geometry field to populate the values. I then tried to register the dataset (we have already used the Enable Enterprise Geodatabase and registered the connection with ArcGIS Portal) but the geometry field does not show up in the Registered with Geodatabase tool, nor does it show up when I look at the Data Design dialogue window. It's completely ommitted.

I decided that perhaps it's the way the binary is in the geometry field that caused the issue so instead I created a new table (as the data owner) with only a few data points in it and a geometry field. This time I populated the geometry field using ST_GeomFromText (a postgis function) to write the geometry. I went to register the data, and the geometry field once again is not showing up in the design tab and I cannot register the dataset.

[MarceloMarques]

Interesting, it should work. Please, open a ticket with Esri Technical Support to investigate this further and please keep us posted in this thread if you learn anything new about the issue. Thanks.  : )