Using ANYINTERACT in sdo_relate

Question

Hey. OK I am having slight problems here with performing spatial queries using ANYINTERACT from the sdo_relate option. I presume that when you perform a window query using ANYINTERACT, the query returns all geoemtries that either 1) intersect the query window or 2) lie wholly inside the window without touching the window. In my application I am trying to return all geometries that either fall directly inside the window or intersect the window at any point. My only problem is that my application only returns those geometries that intersect the window and not those that lie inside the window. I consulted the Spatial Index Advisor and performed sdo_relate ANYINTERACT queries on the same data and those geometries that both intersect the window and fall inside the window are highlighted as a result of executing the query. I have compared my query to the sample one in the Index Advisor and cannot see any difference. Has anyone encountered this problem themselves or has anyone any suggestions on the matter. I am completely baffled. Thanks Joe

Answer 1

Hey. I just tried a few things there after I posted that message and they have not solved my dilemma but might be able to shed a little more light on the issue. When I perform sdo_nn, sdo_within_distance or sdo_filter queries on point, linestring and polygon geometries I dont encounter any problems. All the queries are constructed as they would appear in the Spatial Index Advisor except that I added sdo_cs.viewport_transform to each of the queries because I was getting errors of the form "Element of type Extent is not supported for Geodetic data". As I mentioned above, these three queries all work without any hassle. However my queries using ANYINTERACT, as I stated in my original post, are not working correctly. I have played around with the structure of the query and now it works some of the time but not all of the time. When the query is built as follows it kind of works and returns some but not all the point geometries falling inside the window:
select geom from table where sdo_relate(geom,
(mdsys.sdo_geometry(2003, 8307, null,
mdsys.sdo_elem_info_array(1, 1003, 1),
mdsys.sdo_ordinate_array(coords here))), 'MASK=(Anyinteract) querytype=window')='true';
This query is very inconsistent as it sometimes returns all the points inside the window and then when I run it again it only returns a subset of the total number of points falling inside the window. I am not sure as to why it works one minute and not the next. This query also returns only a subset of the total number of polygons or linestrings falling inside the query window!
When I restructure the query to appear as follows it returns all geometries (linestring or polygon) that intersect the window but not those lying directly inside the window!!!! However it does not return any point geometries interacting with the window at all. This is where my confusion stems from:
select geom from table where sdo_relate(geom,
sdo_cs.viewport_transform(mdsys.sdo_geometry
(2003, 0, null,
mdsys.sdo_elem_info_array(1, 1003, 3),
mdsys.sdo_ordinate_array(coords here)), 8307), 'MASK=(Anyinteract) querytype=window')='true';
The major differences between the two above queries are the addition of "sdo_cs.viewport_transform" into the second query and the modifcation of the elem_info_array from (1, 1003, 1) to (1, 1003, 3). Also the line
(2003, 8307, null,...) has become (2003, 0, null,...). Can you explain to me as to what affect these subtle changes
have on the query and also maybe show me one query that will return all geometries (polygon, linestring AND point)
that either intersect or fall directly inside the query window!!! Thank you for taking the time out to read my qyery. Joe