nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Unable to create view in an enterprise geodatabase - feature class with custom projection

Thomas_Puthusserry

I have a dataset with custom projection (: https://epsg.io/112041) in a postgreSQL enterprise geodatabase (11.3). The dataset works fine when accessed in Pro or published into enterprise.

When a view is created from the dataset in the database, the spatial reference is not saved (says unknow reference system). Is there a way to address this?

If a sample dataset is needed, this can be provided. Any helps?

Encuentra más publicaciones etiquetadas con

Accepted answers

VenkataKondepati

The problem is that your database view is just a "query in a mask".

It doesn't automatically inherit the spatial metadata that Esri buries in the sde_layers and sde_spatial_references system tables. Since you’re using a custom projection, PostgreSQL doesn't have a native EPSG entry for it in the spatial_ref_sys table, so it defaults to "Unknown."

You need to manually "register" the view's spatial identity so ArcGIS knows how to read it.

PostGIS Side: Use the ST_SetSRID(geom, 112041) function in your SQL view definition. This stamps the geometry column with your custom ID.

Esri Side: After creating the view, run the Register with Geodatabase geoprocessing tool in Pro. This manually inserts a row into the SDE metadata tables, linking your view name to the specific coordinate system definition.

Without that metadata registration, Pro is just looking at a pile of coordinates with no map to guide them.

All comments

VenkataKondepati

The problem is that your database view is just a "query in a mask".

You need to manually "register" the view's spatial identity so ArcGIS knows how to read it.

PostGIS Side: Use the ST_SetSRID(geom, 112041) function in your SQL view definition. This stamps the geometry column with your custom ID.

Without that metadata registration, Pro is just looking at a pile of coordinates with no map to guide them.

Thomas_Puthusserry

Hi @VenkataKondepati

Many thanks for your suggestion and I have some success and failures.

Success: where a code is listed in EPSG.io: Coordinate Systems Worldwide or https://spatialreference.org/ by importing the entry into public.spatial_ref_sys table and running the ST_SetSRID function in the view recognises the spatial reference while running the Register with Geodatabase in Pro. All looks good.

Failure: where the SRID code is not listed, but the entry into public_ref_sys table with an arbitrarily assigned Authority (CUSTOM) and SRID (900999), the create view with SRID stamped to the view's geometry column, but Register with Geodatabase is not identifying the spatial reference. Although the Register with Geodatabase runs without error, the view is without a spatial reference. Any idea whether this is addressable?

Kind regards,

Thomas

VenkataKondepati

This is a limitation of PostGIS / spatial_ref_sys behavior, not ArcGIS.
When you manually add a custom SRID (like 900999) to public.spatial_ref_sys, PostGIS will accept it, but ArcGIS Pro and the Geodatabase don’t automatically recognize it as a valid spatial reference. The geodatabase lookup for spatial references relies on known EPSG authority codes, and custom entries without a proper authority string are not matched, even if the SRID is set on the geometry column.
That’s why:

When you import a known EPSG definition, Register with Geodatabase sees and honors it.

When you inject a custom SRID with CUSTOM/900999, the tool runs without error, but ArcGIS cannot resolve it to a valid spatial reference, and the result is effectively unregistered (no recognized SR).

Why this happens
ArcGIS Pro expects:

A known authority (EPSG or ESRI)

Matching well-known text (WKT) that ArcGIS can interpret

PostGIS only cares that the SRID exists in its table; ArcGIS requires a recognizable authority + definition.
Workarounds / Options

Use a Real EPSG Code if Possible
Even if unofficial, pick an unused EPSG code and import its full definition. ArcGIS will accept it.

Define a Custom Coordinate System in ArcGIS
Export the WKT from spatial_ref_sys and create the coordinate system in Pro via Manage Coordinate Systems → Import → Save As. Then run Register with Geodatabase against that Pro definition.

Avoid Custom SRIDs
The safest pattern within Enterprise GDB + PostGIS is to use standard EPSG codes only, or define the SR in Pro first and register the view afterward.

ArcGIS doesn’t “see” your custom SRID because it doesn’t match a known authority lookup. Register with Geodatabase doesn’t fail, but doesn’t give it a valid spatial reference either. Using a known authority definition (or importing it into ArcGIS coordinate systems) is the reliable way to get the view properly registered.

TanuHoque

@Thomas_Puthusserry

Can you pls do me a favor?

pls upgrade to the latest release i.e. 3.6 and try the Spatial Reference picker button from the 2nd page on the New Query Layer dialog; that will bring up the Coordinate System picker; create a new custom projection or import one.

Thomas_Puthusserry

Hi @VenkataKondepati

Thanks for your suggestions and explanations, which make sense.

I tried with the following from your suggestion:

1. Created a new view (without enforcing a CRS as you initially suggested, because there is no ESRI/EPSG code)

2. Run the Register with Geodatabase (with custom reference selected after importing to Pro). However the tool checks but it is not selected / populated. I guess without an approved EPSG/ESRI code this is not possible in the scenario I am testing.

Thomas_Puthusserry

@TanuHoque Have I understood your point correctly?

This creates a view layer rather than a database view in the postgreSQL enterprise database, which is the requirement.

Thanks

Thomas

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.