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 : > Hi, > > will

[gdal-dev] Need some information please

Hello all, I have tried to pass the parameter o: in the symbol toll parameter for constructing style string. The problem is that I always get a border/outline on my fill circle. Any ideas on how to mitigate this? ___ gdal-dev mailing list gdal-dev@lists.o

Re: [gdal-dev] gdal_translate to Rasterlite and (missing) srs

hi Even, Even Rouault-2 wrote > Helmut, > >> is this intentional that there is no srs by a simple gdal_translate of a >> geotiff to a Rasterlite db? > > From what I can see the driver doesn't handle adding a new entry in the > spatial_ref_sys table if there's no AUTHORITY node, such as in your

[gdal-dev] Fwd: [pdal] Riegl extrabytes stripped

On Mon, Oct 24, 2016 at 10:52 AM, Benjamin Kabelik wrote: > Dear mailing list members, > > > > I read the thread about the extra bytes and wrote a pdal translate command > for a ntv2 projection from UTM33n ETRS89 to Austria MGI M34: > > > > For %i in (*.las) do (docker run -v c:/temp/trafo_wien2/

Re: [gdal-dev] gdal_translate to Rasterlite and (missing) srs

Helmut, > is this intentional that there is no srs by a simple gdal_translate of a > geotiff to a Rasterlite db? From what I can see the driver doesn't handle adding a new entry in the spatial_ref_sys table if there's no AUTHORITY node, such as in your use case. From what I can see, it also pro

[gdal-dev] gdal_translate to Rasterlite and (missing) srs

hi, a question regarding gdal_translate to Rasterlite and srs (based upon [1]): a geotif with srs information: gdalinfo geotiff_out.tif Driver: GTiff/GeoTIFF Files: geotiff_out.tif Size is 7201, 7001 Coordinate System is: PROJCS["MGI / Austria GK Central", GEOGCS["bessel", DATUM["Mil

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

Le lundi 24 octobre 2016 14:10:34, Christian Urich a écrit : > 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"

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

Hi, 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 = g

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

Le lundi 24 octobre 2016 13:21:46, Christian Urich a écrit : > 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

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

How did you create the database? It is a spatial db for Spatialite as well because it contains also field GEOMETRY which is registered in geometry_columns. DLL of the "timeseries" table is CREATE TABLE 'timeseries' ( ogc_fid INTEGER PRIMARY KEY, 'data' BLOB, 'end' VARCHAR, 'start' VARCHAR, 'statio

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] GDAL 2.1.2 RC4 available

Hi, I've generated a new RC (hopefully the last one) with the following fixes since RC3: * gdalwarp: fix failure with cutline on a layer of touching polygons (#6694) * RMF: fix load/store inversion of cm and dm units in MTW files (https://github.com/OSGeo/gdal/pull/162) Updated links: http:/

Re: [gdal-dev] Error in gdalwarp

Il 24/10/2016 12:58, Paolo Cavallini ha scritto: > Il 24/10/2016 12:51, Even Rouault ha scritto: > >> Possibly. I've just fixed the issue per >> https://trac.osgeo.org/gdal/ticket/6694 >> and will issue a GDAL 2.1.2 RC4 with that extra fix. For the record, ticket open on Processing: https://hub

Re: [gdal-dev] Error in gdalwarp

Il 24/10/2016 12:51, Even Rouault ha scritto: > Possibly. I've just fixed the issue per > https://trac.osgeo.org/gdal/ticket/6694 > and will issue a GDAL 2.1.2 RC4 with that extra fix. thanks for that. > Hum, I'm not sure to understand. I don't see any difference when running > gdalwarp with

Re: [gdal-dev] Error in gdalwarp

> Rather tricky. The same analysis seems to run fine, however, on the same > data with different software. On individual polygons yes. But if you just aggregate all the polygons as a multipolygon (what gdalwarp does), it becomes invalid. > What would be your advice for gdalwarp usage in QGIS>Pro

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

Please put a test db somewhere or describe how to create such a database. I made a quick test by importing some XML file with spatialite-gui 1.8.0-dev. it creates a table as CREATE TABLE "xml" ( "pk_uid" INTEGER PRIMARY KEY AUTOINCREMENT, "xml_document" BLOB NOT NULL ,"file_name" TEXT NOT NULL ,"s

[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 _