Bug report #17613

Spatial SQL queries are not working (wrong, empty result) in DB Manager for GeoPackage datasources

Added by Samuel Fernando Mesa Giraldo almost 3 years ago. Updated over 1 year ago.

Status:Feedback
Priority:Normal
Assignee:-
Category:DB Manager
Affected QGIS version:master Regression?:No
Operating System: Easy fix?:No
Pull Request or Patch supplied:No Resolution:
Crashes QGIS or corrupts data:No Copied to github as #:25510

Description

New description:

Affects both 2.18.14 and master.

The same spatial queries are ok for Spatialite datasources.

Also using virtual layers seems to work as expected.

A query like:

SELECT fid, ST_Buffer(geom,100) AS geom
FROM points

for a GPKG datasource will result in a layer (loaded using the "load as new layer" option) that has the same geometry as the source one (and is empty).

Old description:
I'm trying to apply some spatial SQL functions like ST_BUFFER in a point layer. The output is correct in the database manager but the representation is incorrect on the canvas.

The output is supposed to be a polygon layer.

test_points.gpkg - Test GeoPackage Points (224 KB) Samuel Fernando Mesa Giraldo, 2017-12-04 03:10 AM

History

#1 Updated by Giovanni Manghi almost 3 years ago

  • Subject changed from Error SQL spatial functions in DB Manager and GeoPakcage (QGIS v2.99) to Spatial SQL queries are not working DB Manager for GeoPackage datasources
  • Crashes QGIS or corrupts data changed from Yes to No
  • Operating System deleted (Arch Linux x64)
  • Description updated (diff)

#2 Updated by Giovanni Manghi almost 3 years ago

Description updated. Also: if QGIS uses Spatialite >= 4.3 then "CastAutomagic" is not necessary anymore. http://www.gdal.org/drv_geopackage.html

#3 Updated by Giovanni Manghi almost 3 years ago

  • Description updated (diff)
  • Subject changed from Spatial SQL queries are not working DB Manager for GeoPackage datasources to Spatial SQL queries are not working (wrong, empty result) in DB Manager for GeoPackage datasources

#4 Updated by Giovanni Manghi over 1 year ago

  • Status changed from Open to Feedback

Please check if this issue is still valid on QGIS 3.4.5 or 3.6.

Also available in: Atom PDF