topic Re: When registering a new st_geometry enabled table with a SDE geodatabase, why can't enable M and Z values? in Data Management Questions

When registering a new st_geometry enabled table with a SDE geodatabase, why can't enable M and Z values?

AllenGuan2 — Thu, 12 Oct 2017 18:40:50 GMT

I created a table in Oracle with sde.st_geometry as the shape, then tried to register it in Catalog (ArcGIS 10.3.1). But the options for enabling "Coordinates include M/Z values, Used to ..." are disabled. On the other hand, if I create a feature class using the ArcGIS create feature class tool, I can specify enabling both of them. Anything I missed for the 1st method?

Re: When registering a new st_geometry enabled table with a SDE geodatabase, why can't enable M and Z values?

VinceAngelo — Thu, 12 Oct 2017 19:12:44 GMT

The spatial reference properties of a layer are established at creation. You can't add Z or M (or both) to an existing layer. What was the exact SQL you used to create the table?

- V

Re: When registering a new st_geometry enabled table with a SDE geodatabase, why can't enable M and Z values?

AllenGuan2 — Fri, 13 Oct 2017 12:00:34 GMT

My sql is as simple as this "create table (x number,y,number,z number,shape sde.st_geometry)". Then I would use Catalog to register it as a feature class with geodatabase, such as adding objectid and setting coordinate system. First time trying to enable Z and M. Maybe for M and Z setting, the feature class needs to be created from Catalog?

Re: When registering a new st_geometry enabled table with a SDE geodatabase, why can't enable M and Z values?

VinceAngelo — Fri, 13 Oct 2017 13:31:31 GMT

You left off the registered rowid column. You should ALWAYS have a NUMBER(38) column.

Simple table creation likely defaults the SRID to zero, which doesn't have Z and M settings. I haven't used Oracle in a while so you 'll need to explore how to specify an appropriate spatial reference ID.

- V