Problems with geometries of type 0

Question

Hi All,
We have a problem with Oracle Spatial (8.1.6 Object-relational) Functions and operators on data consisting both
standard Oracle geometry types and elements of "unknown" type, wich the functions seem not to ignore, as the
documentation says it is supposed to do.
Below you can se examples with extent_of analysis of layers and sdo_relate queries. It seems the "unknown" type
elements are read as geometries, and when an "unknown" is present following geometries are ignored. Have any of you
seen this before or even better have a solution?
Thanks
-- Test with extent_of
-- Create table for test geometries
Drop table geom_test;
create table geom_test
(id number,
GEOMETRY mdsys.sdo_geometry);
-- Populate sdo_geom_metadata
delete from user_sdo_geom_metadata
where table_name='GEOM_TEST'
and column_name='GEOMETRY';
insert into user_sdo_geom_metadata
values ('GEOM_TEST', 'GEOMETRY',
MDSYS.SDO_DIM_ARRAY(
MDSYS.SDO_DIM_ELEMENT('X', -380000000, 10, 1),
MDSYS.SDO_DIM_ELEMENT('Y', 0, 380000000, 1)),
null);
-- Test with no "unknown" elements
delete from geom_test;
insert into geom_test (id,geometry)
values(148855,
mdsys.sdo_geometry
(1, null, null,
mdsys.sdo_elem_info_array(1,1,1),
mdsys.sdo_ordinate_array(-253423935,216615534))
Select mdsys.sdo_tune.extent_of('GEOM_TEST', 'GEOMETRY') from dual;
-- Test with one "unknown" elements
delete from geom_test;
insert into geom_test (id,geometry)
values(148855,
mdsys.geometry
(2004, null, null,
mdsys.sdo_elem_info_array
(1,0,6000,
4,1,1),
mdsys.sdo_ordinate_array
(.956304,.292373,0,
-253423935,216615534))
Select mdsys.sdo_tune.extent_of('GEOM_TEST', 'GEOMETRY') from dual;
-- Test with two "unknown" elements
delete from geom_test;
insert into geom_test (id,geometry)
values(148855,
mdsys.geometry
(2004, null, null,
mdsys.sdo_elem_info_array
(1,0,6000,
4,1,1,
6,0,6000,
9,1,1),
mdsys.sdo_ordinate_array
(.956304,.292373,0,
-253423935,216615534,
.956304,.292373,0,
-254019015, 216442514))
select mdsys.sdo_tune.extent_of('GEOM_TEST', 'GEOMETRY') from dual;
-- sdo_relate test
-- Create table for test geometries
Drop table geom_test2;
create table geom_test2
(id number,
GEOMETRY mdsys.sdo_geometry);
-- Populate sdo_geom_metadata
delete from user_sdo_geom_metadata
where table_name='GEOM_TEST2'
and column_name='GEOMETRY';
insert into user_sdo_geom_metadata
values ('GEOM_TEST2', 'GEOMETRY',
MDSYS.SDO_DIM_ARRAY(
MDSYS.SDO_DIM_ELEMENT('X', -380000000, 10, 1),
MDSYS.SDO_DIM_ELEMENT('Y', 0, 380000000, 1)),
null);
-- Populate dataset
delete from geom_test2;
insert into geom_test2 (id,geometry)
values(1,
mdsys.sdo_geometry
(1, null, null,
mdsys.sdo_elem_info_array(1,1,1),
mdsys.sdo_ordinate_array(-253423935,216615534))
insert into geom_test2 (id,geometry)
values(2,
mdsys.sdo_geometry
(2004, null, null,
mdsys.sdo_elem_info_array
(1,0,6000,
4,1,1),
mdsys.sdo_ordinate_array
(.956304,.292373,0,
-253423935,216615534))
insert into geom_test2 (id,geometry)
values(3,
mdsys.sdo_geometry
(2004, null, null,
mdsys.sdo_elem_info_array
(1,0,6000,
4,1,1,
6,0,6000,
9,1,1),
mdsys.sdo_ordinate_array
(.956304,.292373,0,
-253423935,216615534,
.956304,.292373,0,
-254019015, 216442514))
select mdsys.sdo_tune.extent_of('GEOM_TEST2', 'GEOMETRY') from dual;
drop index g_test2_spatidx;
create index g_test2_spatidx on geom_test2(GEOMETRY)
indextype is mdsys.spatial_index parameters
('sdo_level=4, sdo_commit_interval=1000, tablespace=indx');
-- Query by expected coordinates
select id
from geom_test2
where mdsys.sdo_relate
(geometry,
mdsys.sdo_geometry
(3,null,null,
mdsys.sdo_elem_info_array(1,3,3),
mdsys.sdo_ordinate_array(-250000000,210000000,-260000000,220000000)),
'mask=ANYINTERACT')='TRUE';
--Query by "unknown" type values
select id
from geom_test2
where mdsys.sdo_relate
(geometry,
mdsys.sdo_geometry
(3,null,null,
mdsys.sdo_elem_info_array(1,3,3),
mdsys.sdo_ordinate_array(0,0,1,1)),
'mask=ANYINTERACT')='TRUE';
null

Answer 1

Hi,
This is a bug in the Oracle Spatial object model. A workaround for now is to
declare you etype 0's at the end of your ordinate array.
Correct expected behavior is for Oracle Spatial is for any non-zero SDO_GTYPE,
ignore all zero ETYPES.
We will try to get a fix into 8.1.7, and definitely into 8.2. Hope this helps. Thanks.
Dan
null