[Geoserver-users] Bug in wms-SVG Renderer

GeoServer GeoServer User
1

We use the one that came with the geoserver 1.3.0 version. How can I
find out which one this is? Do I have to try a SLD and see the outcome?

Uli.

-----Original Message-----
From: Chris Holmes [mailto:cholmes@anonymised.com]
Sent: Dienstag, 30. Mai 2006 18:30
To: Hans-Ulrich Otto
Cc: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] Bug in wms-SVG Renderer

Is this with the fast SVG renderer that does no styling? Or the slower
one that does do styling?

Hans-Ulrich Otto wrote:

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=GetMap&width=50

0&height=500&format=image/svg&bbox=22.2253,60.4288,22.2608,60.44955&laye

rs=ta: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

=MN_BU,MN_LU,MN_WL,MN_WA,MN_08,MN_07,MN_06,MN_05,MN_04,MN_03,MN_02,MN_01

,MN_00,MN_PI,MN_SM&BGCOLOR=0xF0F0D0

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=anyinteract
querytype=WINDOW') = '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)
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.

-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and

Risk!

Fully trained technicians. The highest number of Red Hat

certifications in

the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid7521&bid$8729&dat1642
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

--
Chris Holmes
The Open Planning Project
http://topp.openplans.org

2

Looks like by default it uses the fast, no styling version. You can change it in Config -> WMS -> Rendering, switch to 'Batik'. That probably should not make the error. Go ahead and report this bug, but no one's really maintaining either SVG renderer, since we'd like to combine them and get a fast, styling renderer.

Chris

Hans-Ulrich Otto wrote:

We use the one that came with the geoserver 1.3.0 version. How can I
find out which one this is? Do I have to try a SLD and see the outcome?

Uli.

-----Original Message-----
From: Chris Holmes [mailto:cholmes@anonymised.com] Sent: Dienstag, 30. Mai 2006 18:30
To: Hans-Ulrich Otto
Cc: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] Bug in wms-SVG Renderer

Is this with the fast SVG renderer that does no styling? Or the slower one that does do styling?

Hans-Ulrich Otto wrote:

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=GetMap&width=50

0&height=500&format=image/svg&bbox=22.2253,60.4288,22.2608,60.44955&laye

rs=ta: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

=MN_BU,MN_LU,MN_WL,MN_WA,MN_08,MN_07,MN_06,MN_05,MN_04,MN_03,MN_02,MN_01

,MN_00,MN_PI,MN_SM&BGCOLOR=0xF0F0D0

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=anyinteract
querytype=WINDOW') = '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) 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.

-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and

Risk!

Fully trained technicians. The highest number of Red Hat

certifications in

the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid7521&bid$8729&dat1642
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

--
Chris Holmes
The Open Planning Project
http://topp.openplans.org