Ticket #3578 (closed defect: fixed)

Opened 3 years ago

Last modified 2 years ago

Multipolygon geometry doesn´t work

Reported by: petrapie Owned by: aboudreault
Priority: high Milestone: 5.6.5 release
Component: WMS Server Version: unspecified
Severity: normal Keywords: multipolygon
Cc:

Description

We have a VIEW store in Oracle which contains polygon and multipolygon geometry. We used this view in older version of mapserver (5.4.1) for display polygon layer. It has worked fine. However this layer doesn´t work in newest version of mapserver (5.6.5).

The problem is detected when we use WMS for calling this layer. We tried to call it with WFS and it has worked fine.

We have this error: msDrawMap(): Image handling error. Failed to draw layer named 'VODSTVO_NADRZE_BUFF50'. msOGRFileOpen(): OGR error. Open failed for OGR connection in layer `VODSTVO_NADRZE_BUFF50'. File not found or unsupported format.

Attachments

test_mapfile.map Download (2.4 KB) - added by petrapie 3 years ago.

Change History

Changed 3 years ago by petrapie

Changed 3 years ago by aboudreault

  • owner changed from mapserverbugs to aboudreault

I'll take a look at this bug.

Changed 3 years ago by aboudreault

Could you provide some data? perhaps a dump of the table?

Changed 3 years ago by aboudreault

I've created a oracle table with 1 multipolygon in it.. Hope that's ok to reproduce the bug.

Changed 3 years ago by aboudreault

I'm not sure to understand why the test_mapfile.map is using CONNECTIONTYPE oraclespatial, which is the native oracle support of mapserver and your error message is from OGR. I've tested a few combinations, and my wms getmap requests work properly with the native support. However, the view doesn't seem to work using OGR driver. Here's the error:

msOGRFileOpen(): OGR error. GetLayer(park_view) failed for OGR connection `OCI:user/xxxxx@orthanc/testos'.
[Tue Oct 26 13:40:30 2010].391512 msDrawMap(): Image handling error. Failed to draw layer named 'VODSTVO_NADRZE_BUFF50'

Changed 2 years ago by petrapie

  • status changed from new to closed
  • resolution set to fixed

Thank you for your answer. The problem solution was to clean data in the problematic view. After that, polygon layer works fine..

Note: See TracTickets for help on using tickets.