[gdal-dev] WAsP map output for ogr

Vincent Mora vincent.mora at oslandia.com
Wed Mar 12 00:22:00 PDT 2014


On 11/03/2014 14:58, Even Rouault wrote:
> Selon Vincent Mora <vincent.mora at oslandia.com>:
>
>> On 11/03/2014 10:39, Even Rouault wrote:
>>> If you want to test the compliance of your driver (the read part) with the
>>> assumptions of the OGR API, you can go to the apps subdirectory of GDAL and
>>> "make test_ogrsf", and then "test_ogrsf a_wasp_file".
>> Thanks for the tip.
>>
>> It helped me fix some issues, and raises one question: test_ogrsf now
>> fails with 'ExecuteSQL() should have returned a non-NULL result', should
>> I implement all the sql queries that are specified in
>> http://www.gdal.org/ogr/ogr_sql.html for my driver to be OK ?
> You should completely remove your ExecuteSQL() implementation. The generic one
> in OGRDataSource should be sufficient.
I found my problem with the default ExecuteSQL() implementation: I was 
naming my layer "filename.map" and the extension was messing with the 
table_name.column_name parsing.

Fixed and pushed now, test_ogrsf passes.

  



More information about the gdal-dev mailing list