Bug report #17613
Updated by Giovanni Manghi over 6 years ago
*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). one.
*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.
!{width:600px}https://i.imgur.com/p3YO9PF.png!
The output is supposed to be a polygon layer.
!{width:600px}https://i.imgur.com/1h26Ipo.png!
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). one.
*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.
!{width:600px}https://i.imgur.com/p3YO9PF.png!
The output is supposed to be a polygon layer.
!{width:600px}https://i.imgur.com/1h26Ipo.png!