Re: [UMN_MAPSERVER-USERS] What happend to OGR OVF layers since gdal 1.3.1

[Huub Fleuren]

Thanks Frank for your answer:

Huub wrote:
>> msOGRFileNextShape(): OGR error. No column definitions found for 
table > 'q_getBBoxAbonnement_1', layer not usable
Frank wrote:
>This indicates that OGR tried to initialize access to a table called 
q_getBBoxAbonnement_l but it could not find any understandable field 
definitions.

You suggested to specify the geo-table like:
<SrcDataSource>ODBC:admin/[EMAIL PROTECTED],wwall</SrcDataSource>
but that did did not work

The query q_getBBoxAbonnement_l  existed in the database, by the unlying 
table didn't exist anymore, much like you were guessing.
The query is not used in any way though. Obviously the process of 
accessing ODBC:admin/[EMAIL PROTECTED] now evaluates all the tables and views 
listed in the database.

Deleting the obsolete object was the solution in this case. It has 
helped to keep the database cleaner:-) I'm happy now with the upgrade to 
mapserver 4.10.2 and gdal 1.4.2


Regards, Huub


Hi List,


This is question about different gdal versions working on OVF layers

OGRINFO of any GDAL version gives me the data from such a layer using 
ogrinfo layer.ovf -al
Versions 4.5, 4.8, 4.10.0 4.10.2  of mapserver  compiled against gdal 
1.3.1 work OKE but later GDAL versions give errors

layerdefinition
--------------
 LAYER
   NAME kpxy
   TYPE POINT
   CONNECTIONTYPE OGR
   CONNECTION "<OGRVRTDataSource>
       <OGRVRTLayer name='kpxy'>
           <SrcDataSource>ODBC:admin/[EMAIL PROTECTED]</SrcDataSource>
           <SrcSQL>SELECT k.kp_nr as kp_nr,k.x as x, k.y as y, 
w.wegbeheerdercode as wegbeheerdercode, w.onderhoudsinstantiecode as 
onderhoudsinstantiecode FROM wwall w, kpxy k WHERE NOT (k.soort LIKE 
'D') and (w.x &gt; %xmin%) and (w.x &lt; %xmax%) and (w.y &gt; %ymin%) 
and (w.y &lt; %ymax%) and (w.kruispuntnummer = k.kp_nr)</SrcSQL>
           <GeometryType>wkbPoint</GeometryType>
           <LayerSRS>WGS84</LayerSRS>
           <GeometryField encoding='PointFromColumns' x='x' y='y'/>
       </OGRVRTLayer>
   </OGRVRTDataSource>"
   DATA "kpxy" # the name of the OGRVrtLayer

etc.


errors
-------

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.
</ServiceException>
</ServiceExceptionReport>

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
.
</ServiceException>
</ServiceExceptionReport>


I did not find documentation on changes concerning OVF layers. What 
happened?




Regards, Huub