Il 16 novembre 2016 01:05:35 CET, Nyall Dawson ha
scritto:
>On 16 November 2016 at 01:00, Paolo Cavallini
>wrote:
>> Hi all,
>> on 2.18, the extraction of a shp from a large (18 Mpoints) PostGIS
>table
>> takes ages, even when the user chooses to
On 16 November 2016 at 01:00, Paolo Cavallini wrote:
> Hi all,
> on 2.18, the extraction of a shp from a large (18 Mpoints) PostGIS table
> takes ages, even when the user chooses to save only a small portion of
> it, selecting a small extent. This seems to be due to QGIS
Il 15/11/2016 16:00, Paolo Cavallini ha scritto:
> Hi all,
> on 2.18, the extraction of a shp from a large (18 Mpoints) PostGIS table
> takes ages, even when the user chooses to save only a small portion of
> it, selecting a small extent. This seems to be due to QGIS saving only
> the chosen
Il 15/11/2016 16:15, Randal Hale ha scritto:
> I'm using 2.18 on Ubuntu 16.04. I connect to a postgis database with 2.2
> million points covering the continental United States. I exported that
> to a shapefile and it took about 2.5 minutes.
Thanks for the check. My problem was that the dbf also
I'm using 2.18 on Ubuntu 16.04. I connect to a postgis database with 2.2
million points covering the continental United States. I exported that
to a shapefile and it took about 2.5 minutes.
Randy
On 11/15/2016 10:00 AM, Paolo Cavallini wrote:
Hi all,
on 2.18, the extraction of a shp from
Hi all,
on 2.18, the extraction of a shp from a large (18 Mpoints) PostGIS table
takes ages, even when the user chooses to save only a small portion of
it, selecting a small extent. This seems to be due to QGIS saving only
the chosen geoms, but the whole table. On 2.14 it seems to work fine.
Could