I use the -tbzr on v.in.ascii and v.build after for
topology. I have also utilised the sqlite db.
does the import data only have/need x,y,z or do you need
additional fields as well? if there is no need for other
data columns v.build/topology/databases will only slow
you down for little gain.
typically how many points in one 1000x1000 import block?
can you watch the memory use of the module? i.e. does it fill
up physical RAM after 25% then start using swap space on hard
disk for the rest (which is 100x slower).
I use the -tbzr on v.in.ascii and v.build after for
topology. I have also utilised the sqlite db.
does the import data only have/need x,y,z or do you need
additional fields as well?
I extracted xyz with lastools first, so only xyz in the imported ascii
can you watch the memory use of the module? i.e. does it fill
up physical RAM after 25% then start using swap space on hard
disk for the rest (which is 100x slower).
As it is writing the file (was at 6Mb after 3hrs), the mem usage is
on 114Mb with 1.4Gb free at the moment. It is not using the PageFile.
The book and manual mention the need for topology for the lidar tools to work, so have been trying v.build and thought a db could help.