topic Re: Point Feaure in SDO_GEOMETRY populating the SDO_POINT, instead of SDO_ORDINATES in Data Management Questions

Point Feaure in SDO_GEOMETRY populating the SDO_POINT, instead of SDO_ORDINATES

NicoleSchleifer — Wed, 14 Nov 2012 12:01:53 GMT

New to ESRI...

We have an existing Oracle 10g database with locator enabled and would like to be able to work in ESRI desktop and Server applications.
In ArcMap - Catalog 10.1
1 - right-clicked on table - Managed - Registered with GeoDatabase.
2 - Registered as Versioned

Set DBTUNE default to SDO_GEOMETRY

Added a new point in ArcMap, worked......... BUT...... it populated the SDO_POINT columns not the SDO_ORDINATES.

I feel that I've missed a step or a setting.

Looking for some suggestions and/or advice...

Re: Point Feaure in SDO_GEOMETRY populating the SDO_POINT, instead of SDO_ORDINATES

MelitaKennedy — Wed, 14 Nov 2012 16:50:34 GMT

I don't see the same statement in the current documentation, but I found this in an older version of the documentation:

ArcSDE feature classes defined exclusively as single point layers will store point features in the SDO_POINT type. Storing single point features in the SDO_POINT type improves performance when indexing and searching on single point features. All other single and multipart features along with multipart points are stored in the SDO_ORDINATES type.

And a knowledge base article about the same thing.

Melita

Re: Point Feaure in SDO_GEOMETRY populating the SDO_POINT, instead of SDO_ORDINATES

NicoleSchleifer — Wed, 14 Nov 2012 17:15:08 GMT

Thank-you for your response.

Our point geometry is already populated in the ORDINATES array because we use orientation.

1 - Do we need to convert the GEOMETRY to the SDO_POINT columns?
If so, does ESRI have a tool that will do this for us? Or should we use Oracle to move the coordinates?

2 - Is it possible to populate the SDE metadata to recognize my table as a point feature store as a oriented point feature (ORDINATES array)?

Re: Point Feaure in SDO_GEOMETRY populating the SDO_POINT, instead of SDO_ORDINATES

TravisVal — Fri, 16 Nov 2012 17:03:58 GMT

Unfortunately this is by design. ArcGIS and ArcSDE have no notion of orientated points, so when single points are stored they are always stored in the SDO_POINT type. Oracle Spatial orientated points can still be read (you don't have to reload your data), but the orientation of the point is not read by ArcSDE. This orientation information is lost if the row is updated. Currently there is no way to change this behavior.

If you would like this behavior to change, I would encourage you to submit an idea to the Geodatabase ideas page, or contact technical support and submit an enhancement request.

Sorry I couldn't help,
Travis

Re: Point Feaure in SDO_GEOMETRY populating the SDO_POINT, instead of SDO_ORDINATES

NicoleSchleifer — Thu, 29 Nov 2012 14:12:34 GMT

Thanks Travis,

That was very helpful.

Now... Would you know how to quickly convert my existing points in SDO_ORINATES into SDO_POINTS?
We have existing software that I can extract the orientation into a new column but does Esri have a tool that would move the coordinates from the SDO_ORINATES array into the SDO_POINTS?

Re: Point Feaure in SDO_GEOMETRY populating the SDO_POINT, instead of SDO_ORDINATES

VinceAngelo — Thu, 29 Nov 2012 16:28:01 GMT

In theory, you could just fashion a SQL statement to UPDATE all the geometries.

- V

Re: Point Feaure in SDO_GEOMETRY populating the SDO_POINT, instead of SDO_ORDINATES

NicoleSchleifer — Thu, 29 Nov 2012 16:32:21 GMT

Yes, of course!

Thanks for your help. I can move forward from here!

Re: Point Feaure in SDO_GEOMETRY populating the SDO_POINT, instead of SDO_ORDINATES

VinceAngelo — Thu, 29 Nov 2012 18:05:32 GMT

Make sure you drop the spatial index before doing the UPDATE, and be sure to use the
right index options that exploit SDO_POINT when you rebuild.

- V

Re: Point Feaure in SDO_GEOMETRY populating the SDO_POINT, instead of SDO_ORDINATES

NicoleSchleifer — Thu, 29 Nov 2012 18:14:13 GMT

Interesting....

I wasn't aware of an parameter to exploit SDO_POINT.
I was just planning on using:

CREATE INDEX CTADMIN.SUPPORT_SI3001 ON CTADMIN.SUPPORT
(POINTGEOMETRY)
INDEXTYPE IS MDSYS.SPATIAL_INDEX
PARAMETERS('LAYER_GTYPE=POINT TABLESPACE=TSPIND02 ')
NOPARALLEL

Re: Point Feaure in SDO_GEOMETRY populating the SDO_POINT, instead of SDO_ORDINATES

VinceAngelo — Thu, 29 Nov 2012 18:38:06 GMT

The LAYER_GTYPE=POINT is the switch that exploits SDO_POINT.

- V

Re: Point Feaure in SDO_GEOMETRY populating the SDO_POINT, instead of SDO_ORDINATES

NicoleSchleifer — Wed, 05 Dec 2012 17:03:34 GMT

UPDATE:

Trying to do this outside the Esri environment was clunky and a bit messy.

An easier method inside the Esri environment that was just pointed out to me.....

In ArcCatalog: Rename the original table (Feature Class), then copy and paste it with the original name.
*This is for Stand-alone Features*

Way cool......... worked like a charm and maintains all the spatial metadata that Esri requires.
Super Impressed!