Hi,
On 06 Feb 2009, at 04:19, Patel, Ronak Avinash ((US SSA)) wrote:
> I was wondering if I can use the SpatialRestrictions Criteria
> functions
> for Spatial Queries with oracle SDO_PC data?
Hibernate Spatial doesn't support SDO_PC, so I'm afraid none of its
functions can deal properly with this type of data.
However, in special cases it might work. Specifically if you filter
on the sdo_pc column, but don't try to retrieve these point clouds.
(in that case Hibernate Spatial just generates SQL and doesn't
attempt to convert an sdo_pc object to a JTS geometry)
>
> Or, am I forced to convert the SDO_PC to an SDO_Geometry first and
> then
> use the functions documented at
>
http://www.hibernatespatial.org/tutorial.html?
>
That won't work: you always need to pass a JTS geometry to these
functions.
> Also, I was wondering why the SDOGeometryType.convertToJTS()
> methods all
> take a parameter. What parameter am I supposed to pass there?
The parameter is the STRUCT object returned by JDBC when accessing a
Geometry object in a row. But you're not supposed to use these
methods directly. I should make these methods should be protected or
private.
Regards,
Karel Maesen
_______________________________________________
hibernatespatial-users mailing list
[hidden email]
http://www.hibernatespatial.org/cgi-bin/mailman/listinfo/hibernatespatial-users
