What happend to OGR OVF layers since gdal 1.3.1

[Frank Warmerdam]

Huub Fleuren wrote:
> GDAL 1.3.2
> 
> <?xml version='1.0' encoding="ISO-8859-1" standalone="no" ?>
> <!DOCTYPE ServiceExceptionReport SYSTEM 
> "http://schemas.opengis.net/wms/1.1.0/exception_1_1_0.dtd">
> <ServiceExceptionReport version="1.1.0">
> <ServiceException>
> msDrawMap(): Image handling error. Failed to draw layer named 
> &#39;kpxy&#39;.
> msOGRFileNextShape(): OGR error. SetAttributeFilter() not supported on 
> ExecuteSQL() results.

Huub,

This was a known issue between GDAL 1.3.2 and MapServer 4.8.

> GDAL 1.4.2
> 
> <?xml version='1.0' encoding="ISO-8859-1" standalone="no" ?>
> <!DOCTYPE ServiceExceptionReport SYSTEM 
> "http://schemas.opengis.net/wms/1.1.0/exception_1_1_0.dtd">
> <ServiceExceptionReport version="1.1.0">
> <ServiceException>
> msDrawMap(): Image handling error. Failed to draw layer named 
> &#39;kpxy&#39;.
> msOGRFileNextShape(): OGR error. No column definitions found for table 
> &#39;q_getBBoxAbonnement_1&#39;, layer not usable

This indicates that OGR tried to initialize access to a table called
q_getBBoxAbonnement_l but it could not find any understandable
field definitions.  This might be because it has none or more likely
because the fields it does have are of a special type that OGR's
ODBC driver doesn't recognise.

The workaround for this is to avoid having the OGR driver translate
all the tables in the ODBC datasource into layers.  The most likely
way of doing this is to list a single simple table in the datasource
connection string.

eg.
<SrcDataSource>ODBC:admin/admin at anwb,wwall</SrcDataSource>

I appologise for the relative fragility of the ODBC/OVF/MapServer
mechanism.

Best regards,
-- 
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up   | Frank Warmerdam, warmerdam at pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush    | President OSGeo, http://osgeo.org