[GRASS-dev] [GRASS GIS] #3914: v.import/r.import error: "No layer selected. Operation cancelled"

[GRASS GIS]

#3914: v.import/r.import error: "No layer selected. Operation cancelled"
+-
 Reporter:  veroandreo  |  Owner:  grass-dev@…
 Type:  defect  | Status:  new
 Priority:  normal  |  Milestone:  7.8.1
Component:  wxGUI   |Version:  git-releasebranch78
 Keywords:  r.import, v.import  |CPU:  Unspecified
 Platform:  Linux   |
+-
 When trying to import vector and raster maps using G7:v.import and
 G7:r.import GUIs respectively, I get a small dialog box saying "No layers
 selected. Operation cancelled" even if I specifically click over the maps
 and the line turns blue.

 It happens the same in 78 relbranch and 79dev

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] v.in.ogr Killed by Linux for saturating RAM+SWAP

[Yann Chemin]

Answering to my own question.

I can increase the SWAP size on a running Linux by:

sudo swapoff -a
sudo dd if=/dev/zero of=/swapfile bs=1G count=8
>> 8+0 records in
>> 8+0 records out
>> 8589934592 bytes (8.6 GB, 8.0 GiB) copied, 12.7623 s, 673 MB/s
sudo mkswap /swapfile
>> Setting up swapspace version 1, size = 8 GiB (8589930496 bytes)
>> no label, UUID=x
sudo swapon /swapfile
grep SwapTotal /proc/meminfo
>> SwapTotal:   8388604 kB

--
Dr. Yann Chemin
+33 7 83 85 5234
JRC, Ispra, IT



On Mon, 30 Sep 2019 at 14:16, Yann Chemin  wrote:

> Hi devs,
> I am trying to import a vector and it gets killed. Is there a direct way
> to let it not use the whole RAM+SWAP or should I get a bigger RAM system to
> do the manipulation ?
> Thanks,
> Yann
>
> Importing 6146401 features (OGR layer )...
>  100%
> -
> Registering primitives...
> -
> Cleaning polygons
> -
> Breaking polygons...
> Breaking polygons (pass 1: select break points)...
>  100%
> Breaking polygons (pass 2: break at selected points)...
> Killed
>
>
> --
> Dr. Yann Chemin
> +33 7 83 85 5234
> JRC, Ispra, IT
>
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] v.in.ogr Killed by Linux for saturating RAM+SWAP

[Stefan Blumentrath]

Hi Yann,

Did you try:
GRASS_VECTOR_LOWMEM
Environment variable?
See:
https://grass.osgeo.org/grass76/manuals/variables.html

Cheers
Stefan

From: grass-dev  On Behalf Of Yann Chemin
Sent: mandag 30. september 2019 14:17
To: GRASS-dev 
Subject: [GRASS-dev] v.in.ogr Killed by Linux for saturating RAM+SWAP

Hi devs,
I am trying to import a vector and it gets killed. Is there a direct way to let 
it not use the whole RAM+SWAP or should I get a bigger RAM system to do the 
manipulation ?
Thanks,
Yann

Importing 6146401 features (OGR layer )...
 100%
-
Registering primitives...
-
Cleaning polygons
-
Breaking polygons...
Breaking polygons (pass 1: select break points)...
 100%
Breaking polygons (pass 2: break at selected points)...
Killed


--
Dr. Yann Chemin
+33 7 83 85 5234
JRC, Ispra, IT

___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] v.in.ogr Killed by Linux for saturating RAM+SWAP

[Yann Chemin]

Hi devs,
I am trying to import a vector and it gets killed. Is there a direct way to
let it not use the whole RAM+SWAP or should I get a bigger RAM system to do
the manipulation ?
Thanks,
Yann

Importing 6146401 features (OGR layer )...
 100%
-
Registering primitives...
-
Cleaning polygons
-
Breaking polygons...
Breaking polygons (pass 1: select break points)...
 100%
Breaking polygons (pass 2: break at selected points)...
Killed


--
Dr. Yann Chemin
+33 7 83 85 5234
JRC, Ispra, IT
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev