On Thu, Jul 30, 2015 at 2:26 PM, patrick s. wrote:
> Thanks Stefan
>
> It seems first of all v.out.ascii is slow. Following your proposaI, the
> tmp-file has only 5300 observations after 9min15s. As I have 650.000 points
> this export will need approx. 18h! Can I speed this up somehow?
> (Database
On Thu, 30 Jul 2015, Glynn Clements wrote:
export GRASS_WXVERSION=2.8-gtk2-unicode
Glynn,
In ~/.bash_profile either:
export GRASS_WXVERSION=wxGTK-2.8.12
or
export GRASS_WXVERSION=wx-2.8-gtk2-unicode
and sourced.
Both result in same error in:
/home/rshepard/GIS/GR
Rich Shepard wrote:
> > The wxPython version is handled by the CheckForWx() function in
> > gui/wxpython/core/globalvar.py. The default is taken from the
> > GRASS_WXVERSION environment variable if that's defined, otherwise it
> > allows wxversion to select the version, subject to the constraint
BTW. On my Linux box v.out.ascii in GRASS 7 (SQLite backend) dumped 724,798
points in 8.2 seconds to stdout…
From: grass-user-boun...@lists.osgeo.org
[mailto:grass-user-boun...@lists.osgeo.org] On Behalf Of Blumentrath, Stefan
Sent: 30. juli 2015 14:47
To: patrick s.
Cc: GRASS user list
Subject:
OK, that sounds unreasonably slow. Maybe a bug… (or is this only due dbf
backend?)
You could try v.out.ogr (instead of v.out.ascii) and write to CSV?! You can
then use the CSV in r.in.xyz…
If you only need point counts (and not the sum of some values) you could use
v.to.db to generate a list w
Thanks Stefan
It seems first of all v.out.ascii is slow. Following your proposaI, the
tmp-file has only 5300 observations after 9min15s. As I have 650.000
points this export will need approx. 18h! Can I speed this up somehow?
(Database-driver is dbf)
Patrick
P.S. g.region -up & v.info are g
Hi Patrick,
From my experience r.in.xyz is very fast.
How many points are you processing (v.info pt) and what are your region
settings (g.region –up)?
In order to find out where time is spend yo could split upt the process into
two steps:
v.out.ascii input=pt output=./tmp column=VAL
r.in.xyz in
Hello!
Vector commands v.what.vect and v.distance do not fill the attribute
column of a point vector.
I created small test vectors, a vector map 'varea' of area type which has
an area polygon, and a vector map of points 'vpoints' - 191 GPS
way-points, 135 of which are inside the polygon.
Markus
I tested the approach you proposed, but seems to be very slow for large
datasets: I am processing ~1000.000 points of observation on a 25m-Grid
across Switzerland, where only few cells have multiple points inside.
While /v.to.rast/ takes a few minutes for conversion, the combination
"/
