Oracle Spatial is based on the Oracle Spatial Java API. Oracle Spatial exposes Oracle Spatial functionality in the com.oracle.cep.cartridge.spatial.Geometry class. Oracle Spatial functionality that is not in the Oracle Spatial Java API is not accessible from Oracle Spatial.

Using Oracle Spatial, your Oracle CQL queries can access the Oracle Spatial functionality that Table 4-1 describes.

For more information on how to access these Oracle Spatial features using Oracle Spatial, see Using Oracle Spatial.

You can define an application context for an instance of Oracle Spatial and propagate this application context at runtime. This allows you to associate specific Oracle Spatial application defaults (such as an SDO_SRID) with a particular Oracle Spatial instance.

Before you can define an Oracle Spatial application context, edit your Oracle Stream Analytics application EPN assembly file to add the required namespace and schema location entries:

<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xmlns:osgi="http://www.springframework.org/schema/osgi"
       xmlns:wlevs="http://www.bea.com/ns/wlevs/spring"
       xmlns:spatial="http://www.oracle.com/ns/ocep/spatial"
       xsi:schemaLocation="
  http://www.springframework.org/schema/beans
  http://www.springframework.org/schema/beans/spring-beans.xsd
  http://www.springframework.org/schema/osgi
  http://www.springframework.org/schema/osgi/spring-osgi.xsd
  http://www.bea.com/ns/wlevs/spring
  http://www.bea.com/ns/wlevs/spring/spring-wlevs-v11_1_1_6.xsd"
  http://www.oracle.com/ns/ocep/spatial
  http://www.oracle.com/ns/ocep/spatial/ocep-spatial.xsd">

The following example shows how to create a spatial context named SpatialGRS80 in an EPN assembly file using the Geodetic Reference System 1980 (GRS80) coordinate system.

<spatial:context id="SpatialGRS80" srid="4269" sma="6378137" rof="298.25722101" />

The following example shows how to reference a spatial:context in an Oracle CQL query. In this case, the query uses link name SpatialGRS80 (defined in the above example) to propagate this application context to Oracle Spatial. The spatial:context attribute settings of SpatialGRS80 are applied to the createPoint method call.

<view  id="createPoint">
    select com.oracle.cep.cartridge.spatial.Geometry.createPoint@SpatialGRS80(
        lng, lat)
    from CustomerPos[NOW]
</view>

This procedure describes how to access Oracle Spatial geometry types SDO_GTYPE, SDO_ELEMENT_INFO, and ORDINATES using Oracle Spatial in an Oracle CQL query.

To access the geometry types that the Oracle Spatial Java API supports:

You can use Oracle Spatial to create a geometry in an Oracle CQL query by invoking:

• static methods in com.oracle.cartridge.spatial.Geometry

• methods in oracle.spatial.geometry.JGeometry that conform to the scope and geometry types that Oracle Spatial supports.

• constructor methods in oracle.spatial.geometry.J3D_Geometry

• static methods from oracle.spatial.geometry.J3D_Geometry

For more information, see Geometry API.

Using a Static Method in the Oracle Spatial Geometry Class

The following example shows how to create a point geometry using a static method in com.oracle.cartridge.spatial.Geometry. In this case, you must use a link (@spatial) to identify the data cartridge that provides this class. The advantage of using this approach is that the Oracle Spatial application context is applied to set the SRID and other Oracle Spatial options, either by default or based on an application context you configure (see Oracle Spatial Application Context).

<view  id="CustomerPosGeom">
    select com.oracle.cep.cartridge.spatial.Geometry.createPoint@spatial(
        lng, lat) as geom
    from CustomerPos[NOW]
</view>

Using an Oracle Spatial J3D_Geometry Constructor

The following example shows how to create a geometry using a constructor method in oracle.spatial.geometry.J3D_Geometry. In this case, you do not use a link (@spatial) because J3D_Geometry is just a Java class. The disadvantage of this approach compared with using com.oracle.cartridge.spatial.Geometry is that you must set the SRID because no application context is available.

<view  id="CustomerPosGeom">
    select oracle.spatial.geometry.J3D_Geometry(
        oracle.spatial.geometry.GTYPE_POINT, srid, x, y, z) as geom
    from CustomerPos[NOW]
</view>

Using a Static Method in the Oracle Spatial J3D_Geometry

The following example shows how to create a geometry using a static method in oracle.spatial.geometry.J3D_Geometry.

<view  id="CustomerPosGeom">
    select  oracle.spatial.geometry.J3D_Geometry.createArc@spatial(
        x1, y1, x2, y2, x3, y3) as geom
    from CustomerPos[NOW]
</view>

For more information, see Geometry Types.

Using Oracle Spatial, you can access the public member functions and public member fields of Oracle Spatial classes directly in Oracle CQL.

Oracle Spatial functionality inaccessible from the Geometry class (or not conforming to the scope and geometry types that Oracle Spatial supports) is inaccessible from Oracle Spatial.

In the following example, the view ShopGeom creates an Oracle Spatial geometry called geom. The view shopMBR calls JGeometry static method getMBR which returns a double[] as stream element mbr. The query qshopMBR accesses this double[] using regular Java API.

<view id="ShopGeom">
    select  com.oracle.cep.cartridge.spatial.Geometry.createGeometry@spatial(
        com.oracle.cep.cartridge.spatial.Geometry.GTYPE_POLYGON,
        com.oracle.cep.cartridge.spatial.Geometry.createElemInfo(1, 1003, 1),
        ordsgenerator@spatial(
            lng1, lat1, lng2, lat2, lng3, lat3,
            lng4, lat4, lng5, lat5, lng6, lat6
        ) 
    ) as geom
    from ShopDesc
</view>
<view  id="shopMBR">
    select geom.getMBR() as mbr
    from ShopGeom
</view>
<query  id="qshopMBR">
    select mbr[0], mbr[1], mbr[2], mbr[3]
    from shopMBR
</query>

For more information, see:

• Geometry Types

• Oracle Java Data Cartridge.

Using Oracle Spatial, you can access the following Oracle Spatial geometry relation operators in either the WHERE or SELECT clause of an Oracle CQL query:

• ANYINTERACT

• CONTAIN

• INSIDE

• INSIDE3D

• WITHINDISTANCE

In the following example, the view op_in_where uses the CONTAIN geometry relation operator in the WHERE clause: in this case, Oracle Spatial uses R-Tree indexing. The view op_in_proj uses CONTAIN in the SELECT clause.

<view id="op_in_where">
    RStream(
        select 
            loc.customerId, 
            shop.shopId
        from 
            LocGeomStream[NOW] as loc, 
            ShopGeomRelation as shop
        where 
            CONTAIN@spatial(shop.geom, loc.curLoc, 5.0d) = true
    )
</view>
<view id="op_in_proj">
    RStream(
        select 
            loc.customerId, 
            shop.shopId, 
            CONTAIN@spatial(shop.geom, loc.curLoc, 5.0d)
        from 
            LocGeomStream[NOW] as loc, 
            ShopGeomRelation as shop
    )
</view>

For more information, see Geometric Relation Operators.

Using Oracle Spatial, you can access the following Oracle Spatial geometry filter operators in the WHERE clause of an Oracle CQL query:

• FILTER

• NN

In the following example, the view filter uses the FILTER geometry filter operator in the WHERE clause.

<view id="filter">
    RStream(
        select loc.customerId, shop.shopId
        from LocGeomStream[NOW] as loc, ShopGeomRelation as shop
        where FILTER@spatial(shop.geom, loc.curLoc, 5.0d) = true
    )
</view>

For more information, see Geometric Filter Operators.

Using the Oracle Spatial data cartridge, you can access the following Oracle Spatial aggregate operators in the SELECT clause of an Oracle CQL query:

• MBR

In the following example, the view vaggrmbr uses the MBR geometry aggregate operator in the SELECT clause. The query qaggrmbr access the double[] returned by the MBR geometry aggregate operator directly using standard Java API.

<view id="vaggrmbr">
    select MBR@spatial1(shop.geom) as mbr
    from ShopGeomRelation as shop
</view>
<query id="qaggrmbr">
    select mbr[0], mbr[1], mbr[2], mbr[3], mbr[4], mbr[5], mbr[6]
    from vaggrmbr
</query>

For more information, see Geometric Filter Operators.

When you create an Oracle CQL query using the default Oracle Spatial application context, the default SRID will be set to CARTESIAN.

The following example shows, the createPoint method call uses the default link (@spatial). This guarantees that the default Oracle Spatial application context is applied.

<view  id="createPoint">
    select com.oracle.cep.cartridge.spatial.Geometry.createPoint@spatial(
        lng, lat)
    from CustomerPos[NOW]
</view>

For more information, see:

• Oracle Spatial Application Context

• Ordinates and Coordinate Systems and the SDO_SRID.

This procedure describes how to use the Oracle Spatial application context to specify a geodetic coordinate system other than the default Cartesian geodetic coordinate system in an Oracle CQL query:

For more information, see:

• Oracle Spatial Application Context

• Ordinates and Coordinate Systems and the SDO_SRID.

To use other geodetic coordinates: