this bug's URL: http://intevation.de/rt/webrt?serial_num=4564
-------------------------------------------------------------------------
Subject: v.in.ogr w/ large datasets
Dear GRASSers,
we have problems importing a large dataset (~300.000 features) with v.in.ogr.
It eats up all mem and dies without importing.
We have tried using with -c (no clean) in order to reduce the mem consumption,
but without luck.
At least this thread seems to be realated to our problem.
http://grass.itc.it/pipermail/grass-dev/2006-May/023088.html
Some links to similar problems discussed on the mailinglist:
http://grass.itc.it/pipermail/grass-dev/2006-May/022917.html
Radim wrote something about it, but did not elaborate where to start solving
this problem.
Best regards
Stephan
-------------------------------------------- Managed by Request Tracker
H_B
2
this bug's URL: http://intevation.de/rt/webrt?serial_num=4564
---------------------------------------------------------------------
Subject: v.in.ogr w/ large datasets
Dear GRASSers,
we have problems importing a large dataset (~300.000 features) with
v.in.ogr. It eats up all mem and dies without importing.
We have tried using with -c (no clean) in order to reduce the mem
consumption, but without luck.
At least this thread seems to be realated to our problem.
http://grass.itc.it/pipermail/grass-dev/2006-May/023088.html
Some links to similar problems discussed on the mailinglist:
http://grass.itc.it/pipermail/grass-dev/2006-May/022917.html
Radim wrote something about it, but did not elaborate where to start
solving this problem.
populating the table will be the problem? Try running "top" in another
window and type "M" to sory by memory use.
Memory use of builing topology isn't a problem until ~ 1-3 million
features?
Try using v.external.
What sort of features? areas? lines? points? 3D?
Hamish