FAQ: Why can't ArcSDE ignore the unsupported elements of an application-specific Oracle Spatial geometry, while processing the supported elements?
Why can't ArcSDE ignore the unsupported elements of an application-specific Oracle Spatial geometry, while processing the supported elements?
Only applications designed to create or process the application-specific geometry understand the inter-relationship of the elements. It is likely that attempts by another application, such as an ArcSDE client application, to display or edit the geometry would produce incorrect results. For example:
If a geometry contained a mixture of supported and unsupported elements, the order in which these elements appear in the geometry may hold some implied meaning. Unfortunately, this meaning would be unknown to applications that were not designed to understand these application-specific geometries. When such an application attempted to display those features, the resulting display might not bear any resemblance to the geometry's correct representation. Editing these geometries without knowledge of the interrelationships of the elements in the geometry would most likely result in incorrect results.
For more information about the Oracle Spatial schema, please refer to your "Oracle Spatial Users Guide and Reference."
Application-specific geometry contains ETYPE=0 geometry elements.
- How does ArcSDE handle SDO_GEOMETRY containing type 0 application-specific elements?
- How does ArcSDE handle Oracle Spatial application-specific geometry elements?