Re: [udig-devel] uDig Plug-in: net.refractions.udig.catalog.oracle

["Jukka Sirviö" <Jukka.Sirvio@xxxxxxxxxxxx>]

Hello!
There was couple of problems in oracle plug-in (thanks to Vitali for 
resolving these):

1. "dummy_spatial-8.1.8.jar" -package in geotools -project's 
oracle-spatial plug-in contains OracleConnection etc. classes which are 
not compatible with latest releases of JRE, JDBC drivers etc. These 
classes have to be removed from this package! Otherwise Eclipse does not 
complain about errors during compilation, instead the errors exists during 
runtime!
2. In database connection's Parameter Map the port should be String 
instead of Integer. There was at least two places in 
net.refractions.udig.catalog.oracle where Integer was used! 

I'll continue testing the plug-in..


Yours:
Jukka






Jody Garnett <jgarnett@xxxxxxxxxxxxxxx>
Sent by: udig-devel-bounces@xxxxxxxxxxxxxxxxxxxxx
26/07/2005 18:19
Please respond to User-friendly Desktop Internet GIS
 
        To:     Jukka Sirviö <Jukka.Sirvio@xxxxxxxxxxxx>
        cc:     udig-devel@xxxxxxxxxxxxxxxxxxxxx, 
geotools-devel@xxxxxxxxxxxxxxxxxxxxx
        Subject:        Re: [udig-devel] uDig Plug-in: 
net.refractions.udig.catalog.oracle


Jukka Sirviö wrote:
> Hello!
> Ok, thanks for info. I checked (and tested) the geotools oracle module 
and 
> jdbc -connections which worked fine as stand-alone code in Eclipse. When 

> the code is used inside uDIG's Oracle plug-in it won't work 
(errormessage 
> described in original message). 
Okay - I do recall us testing oracle at one point. If there is a real 
user (you) that needs oracle and is willing to email on the topic we may 
be able to look at it again.

> I have couple of questions related to geotools library's oracle module.
> 
> 1. I'm interested in geotools library's import / export from SDO to JTS. 

> org.geotools.data.oracle.attributeio.AdapterJTS. Do you know if this 
> module is widely used?
So yes - I wrote that :-) It is widly used in geotools and geoserver 
(and a few JUMP projects). It has one known bug (with like encoding 
multigeometries), and a patch for the bug in jira (the bug tracker).

> 2. Do you know if there is any differences between JTS geometry 
validation 
> and SDO geometry validation in Oracle 
> (SDO_GEOM.VALIDATE_GEOMETRY_WITH_CONTEXT, pl/sql).

There is a few differences (clockwise order on polygons), single point 
lines and so on ...

> Oracle spatial reference manual which contains the documentation of 
above 
> function: http://download-uk.oracle.com/docs/html/A96630_01/toc.htm? Is 
> there any solutions how to 'automatically' avoid invalid Oracle SDO 
> geometries when converting them through JTS -> SDO geotools module? One 
> solution (definitely not optimal) is first convert JTS geometry to SDO 
> geometry and run PL/SQL validation procedure with that SDO geometry.. 

I would much rather manipulate the JTS geometry while encoding (that is 
what I do for clockwise / counter-clockwise linear ring order for 
polygons).

So if you can help me detect and fix the problem lets do that. Right now 
JTS does not have any concept of "curve", and I think I special case 
Rectangle as well. Oh and Point is always special cased because you can 
encode it two ways. In ELEM_INFO and SDO_ORDINATES or in a ELEM_POINT or 
something like that.

Perhaps you have discouvered a misassumption in the point encoding? I 
did follow the documentation and wrote testcases for everything...

Jody

_______________________________________________
User-friendly Desktop Internet GIS (uDig)
http://udig.refractions.net
http://lists.refractions.net/mailman/listinfo/udig-devel