Hamish wrote:
what we should do is explicitly look for profile=- for
reading from stdin, to make it more clear that it exists. another
more GUI friendly way is to add a new option for an input file, which
would be mutually exclusive with the profile=[east,north[,east,north,...]
method of
note WinGRASS binaries are still 32 bit,
actually there is OSGeo4W-64bit ready for testing
(http://trac.osgeo.org/osgeo4w/):
(1) Download the 32bit or 64bit OSGeo4W network installer (previous 32bit
only installer)
winGRASS6.4.3.-64bit is included.
-
best regards
Helmut
--
View this
2014-02-14 10:10 GMT+01:00 Hamish hamis...@yahoo.com:
Hamish wrote:
Once done in r.profile, this functionality will be instantly
available for MS Windows users (using only GUI).
fwiw both stdin and command line are just as available and work in
the same way on MS Windows as in Mac and UNIX.
On Fri, Feb 14, 2014 at 8:08 AM, Enrico Gallo enrico.ga...@gmail.comwrote:
I think stdin is not an option
Actually, it is for Python (m.proj example):
from grass.script import core as gcore
...
proc = gcore.start_command('m.proj', input='-', separator=' , ',
Hamish:
note WinGRASS binaries are still 32 bit,
Helmut wrote:
actually there is OSGeo4W-64bit ready for testing
(http://trac.osgeo.org/osgeo4w/):
(1) Download the 32bit or 64bit OSGeo4W network installer (previous 32bit
only installer)
winGRASS6.4.3.-64bit is included.
great
Enrico wrote:
due to strange misbehaviours, we are doing some stress tests on
r.profile under Grass 6.4 and Windows 7
Case A (less interesting, IMHO):
r.profile fails with ERROR: G_malloc when the number of pixel queried
is more than 1E6
our test: profile lenght: 300km, res=3 OK,
On Thu, Feb 13, 2014 at 9:19 PM, Hamish hamis...@yahoo.com wrote:
will get you past the command line length limit (and is easier to work
with too). what we should do is explicitly look for profile=- for
reading from stdin, to make it more clear that it exists. another
more GUI friendly way is
Dear list,
due to strange misbehaviours, we are doing some stress tests on
r.profile under Grass 6.4 and Windows 7
Case A (less interesting, IMHO):
r.profile fails with ERROR: G_malloc when the number of pixel queried
is more than 1E6
our test: profile lenght: 300km, res=3 OK, res=2 failure (
Hello Enrico,
please open a trac wish ticket for case A, as it should be possible to
sample large datasets as to obtain the result of module it does not
require to keep whole data set in RAM.
JFYI - one solution would be to share code with v.profile add-on that
allows to use a line from existing
