Using 3D data with Oracle Locator
(Doc ID 1630196.1)
Last updated on FEBRUARY 27, 2014
Applies to:Oracle Spatial and Graph - Version 220.127.116.11 and later
Information in this document applies to any platform.
Oracle Locator does not support the use of 3D indexes however you can still use your 3D data if you use one of the following methods:
1) If the geometry is not true 3D data, the Y axis is NULL or 0, then you can convert the geometry to 2D using the following method
- drop the spatial index
- update the geometries:
update my_table set my_geom = sdo_cs.make_2d(my_geom);
- update the metadata by removing the Z dimension
- re-create the spatial index.
2) If the geometry is true 3D, then you can still perform Locator functions as long as you perform them on the 2D representation
select sdo_geom.sdo_area (sdo_cs.make_2d(my_geom), 0.05) from my_table where …
3) You can create a 2D index on the 3D data
create index my_sdo_index on my_table(my_geom) indextype is mdsys.spatial_index parameters ('... sdo_indx_dims = 2 ...');
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|