[Geoserver-devel] [jira] Created: (GEOS-285) GetMap with Oracle does not take point rotations into account

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/GEOS-285

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: GEOS-285
    Summary: GetMap with Oracle does not take point rotations into account
       Type: Bug

     Status: Open
   Priority: Major

Original Estimate: Unknown
Time Spent: Unknown
  Remaining: Unknown

    Project: GeoServer
Components:
             Oracle
   Fix Fors:
             1.2.5
   Versions:
             1.2.4

   Assignee: Sean Geoghegan
   Reporter: Chris Holmes

    Created: Mon, 14 Feb 2005 6:02 PM
    Updated: Mon, 14 Feb 2005 6:02 PM

Description:
Report from Matthew White:

I have set-up GeoServer and created an Oracle Spatial
datastore and several FeatureTypes. To test that
everything is working OK, I submitted several GetMap
requests with bbox set to the extent defined in the
FeatureType editor (used Generate to calculate). For
the polygon and line layers, everything worked OK and
I received the map as expected. However for point
layers, I was only receiving features that were
actually on the boundary defined by the bbox
parameter.

Looking at the SQL sent to Oracle, SDO_RELATE is being
used to select anything that is not DISJOINT to the
polygon defined by the bbox parameter (i.e., therefore
everything in the selected box). It appears that the
SDO_EMEL_INFO_ARRAY used to define the selection
polygon uses the value of 1003 (exterior polygon ring)
and the SDO_ORDINATE_ARRAY is passed the bbox
coordinate points in clockwise order. What I believe
may be my problem (speculation on my part) is that the
Oracle documentation indicates that for an element
type of 1003, the coordinate points should be passed
into SDO_ORDINATE_ARRAY in counterclockwise order
(clockwise ordering is indicated for element type 2003
interior polygon ring). If I switch the element type
to 2003 in the SQL, I get the results that I would
expect. So my question, is it possible that I have
set-up something incorrectly that would result in the
element type / point ordering combination that I am
seeing, or could the problem be caused from something
else that I may have configured incorrectly?

---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira