[Geoserver-users] Bug in wms-SVG Renderer

[Hans-Ulrich O. <Han...@te...>]

Hi,

We are using geoserver 1.3.0 with Oracle 10gR2 and tested the SVG
rendering of wms. E.g.
https://highway.teleatlas.com:8892/geoserver/wms?request=3DGetMap&width=3D=
50
0&height=3D500&format=3Dimage/svg&bbox=3D22.2253,60.4288,22.2608,60.44955=
&laye
rs=3Dta:MN_BU,ta:MN_LU,ta:MN_WL,ta:MN_WA,ta:MN_08,ta:MN_07,ta:MN_06,ta:MN=
_
05,ta:MN_04,ta:MN_03,ta:MN_02,ta:MN_01,ta:MN_00,ta:MN_PI,ta:MN_SM&styles
=3DMN_BU,MN_LU,MN_WL,MN_WA,MN_08,MN_07,MN_06,MN_05,MN_04,MN_03,MN_02,MN_0=
1
,MN_00,MN_PI,MN_SM&BGCOLOR=3D0xF0F0D0

We get the following error message in the logs:

Error Performing SQL query: SELECT "ID", "FEATTYP", "FEATAREA",
"FEATPERIM", "NAME", "NAMELC", "BUACODE", "GEOM" FROM "MN_BU" WHERE
SDO_RELATE(MDSYS.SDO_GEOMETRY(2003,8307,NULL,MDSYS.SDO_ELEM_INFO_ARRAY(1
,1003,1),MDSYS.SDO_ORDINATE_ARRAY(8.86,44.3857,8.943,44.3857,8.943,44.44
5,8.86,44.445,8.86,44.3857)),"GEOM",'mask=3Danyinteract
querytype=3DWINDOW') =3D 'TRUE'
...
ORA-13226: interface not supported without a spatial index ...

The reason is that that the parameters of the Oracle function SDO_RELATE
are in wrong order:
Correct order: SDO_RELATE(GEOM_COL_IN_DB,BBOX_GEOM,OPTIONS)=20
Order in query above: SDO_RELATE(BBOX_GEOM,GEOM_COL_IN_DB,OPTIONS)

We did not check if this is already fixed in the last recent version.

Cheers,

Hans-Ulrich Otto.