Opened 14 years ago
Closed 13 years ago
#3578 closed defect (fixed)
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 (1)
Change History (6)
by , 14 years ago
Attachment: | test_mapfile.map added |
---|
comment:1 by , 14 years ago
Owner: | changed from | to
---|
comment:3 by , 14 years ago
I've created a oracle table with 1 multipolygon in it.. Hope that's ok to reproduce the bug.
comment:4 by , 14 years ago
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'
comment:5 by , 13 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Thank you for your answer. The problem solution was to clean data in the problematic view. After that, polygon layer works fine..
I'll take a look at this bug.