[gdal-dev] Wrongly identified SQLITE_BLOB as geomtry

Christian Urich christian.urich at gmail.com
Mon Oct 24 05:10:34 PDT 2016


will do.

I run into another problem. The update statement for multiple geometry

ERROR 1: In SetFeature(): sqlite3_prepare(UPDATE 'timeseries' SET "data" =
?"GEOMETRY" = ?,"end" = ?,"start" = ?,"station_id" = ?,"timestep" =
?,"type" = ?,"s" = ? WHERE "ogc_fid" = 1):
  near ""GEOMETRY"": syntax error

Looks like a comma is missing. Looking at the code my guess is
gdal/gdal/ogr/ogrsf_frmts/sqlite/ogrsqlitetablelayer.cpp line 2640 misses a

if( bNeedComma )
            osCommand += ",";

On 24 October 2016 at 11:00:34 pm, jratike80 (
jukka.rahkonen at maanmittauslaitos.fi) wrote:


It does smell like a bug. Could you repeat my test and take care to have the
additional BLOB field created after the geometry field? For me this
workaround seems to work and there is only one geometry left and "data"
field is reported as "binary" type.

FID Column = ogc_fid
Geometry Column = geometry
end: String (0.0)
start: String (0.0)
station_id: Integer (0.0)
timestep: Integer (0.0)
type: String (0.0)
data: Binary (0.0)

View this message in context:
Sent from the GDAL - Dev mailing list archive at Nabble.com.
gdal-dev mailing list
gdal-dev at lists.osgeo.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20161024/7f4874b1/attachment.html>

More information about the gdal-dev mailing list