Re: [gdal-dev] Wrongly identified SQLITE_BLOB as geomtry

Hi Even and Jukka, Thanks for the quick fixes! Just tested the code from the master and it works for my use case. Cheers Christian On 24 October 2016 at 11:33:17 pm, Even Rouault (even.roua...@spatialys.com) wrote: Le lundi 24 octobre 2016 14:10:34, Christian Urich a écrit : >

Re: [gdal-dev] Wrongly identified SQLITE_BLOB as geomtry

Hi, will do. I run into another problem. The update statement for multiple geometry fails. ERROR 1: In SetFeature(): sqlite3_prepare(UPDATE 'timeseries' SET "data" = ?"GEOMETRY" = ?,"end" = ?,"start" = ?,"station_id" = ?,"timestep" = ?,"type" = ?,"s" = ? WHERE "ogc_fid" = 1): near ""GEOMETRY""

Re: [gdal-dev] Wrongly identified SQLITE_BLOB as geomtry

It is a spatialite database. The data field is the SQLITE_BLOB that should not be recognised as geometry. On 24 October 2016 at 10:42:21 pm, jratike80 ( jukka.rahko...@maanmittauslaitos.fi) wrote: How did you create the database? It is a spatial db for Spatialite as well because it contains a

Re: [gdal-dev] Wrongly identified SQLITE_BLOB as geomtry

Here is a link to a small test database https://www.dropbox.com/s/vwu4q7ud3e3sv2y/binary_blob.sqlite.zip?dl=0 The problem seems to come up when the BLOB is a bit bigger. I couldn’t reproduce it with a smaller dataset. Fo

[gdal-dev] Wrongly identified SQLITE_BLOB as geomtry

Hi all, I have created a binary blob in a spatialite db. If I try to open the db the column is wrongly identified as geometry which causes all kinds of problems. Is there a way to force gdal to only consider the geometry_columns table? Cheers Christian _

[gdal-dev] Binary fields in Python

Hi, I’m still running an older version of GDAL/OGR (1.11.3) and would like to access a binary field in python. It seems that GetFieldAsBinary is only available in version > 2.0 so I tried to access the data using GetFieldAsString. However the returned hex is cut off after 75 characters. Is th