Hi,
I just tried to build GRASS7 on Ubuntu with the r.stream.* and r.fuzzy
add-ons in the scripts-folder (the subdirs have been added to the makefile
in the scripts folder).
When running make I face a compilation error in the /man subfolder:
radinger@grassgis:/usr/local/src/grass7_trunk/man$
Hi,
is there a simple way to set the value of a specific raster cell (e.g.
defined by the coordinate of its cell center). One way could be to define a
point by the coordinates (e.g. v.in.ascii) and then to convert the point to
raster (v.to.rast) and use the mapcalculator to modify the original
You can use r.mapcalc. If mymap is your raster layer and you want to
change the raster cell at coordinates 52deg and 10deg, use
r.mapcalc mymap = if(x()==52.0 y()==10.00, 1, mymap) --replace
Cheers,
Paulo
On 05/13/2013 11:56 AM, Johannes Radinger wrote:
Hi,
is there a simple way to set
fyi we have just added OpenCL GPU (graphics card) support to the build system
for GRASS 7.
This is really exciting. Thanks to all who made this happen.
Looking forward to seeing how and where it will be implemented.
Excellent work.
Mark
___
Johannes Radinger wrote:
I just tried to build GRASS7 on Ubuntu with the r.stream.* and r.fuzzy
add-ons in the scripts-folder (the subdirs have been added to the makefile
in the scripts folder).
When running make I face a compilation error in the /man subfolder:
VERSION_NUMBER=7.0.svn
Hi everyone,
I downloaded the Windows binary for Grass 6.4.3RC3 (dated April 20, 2013,
available on http://grass.osgeo.org/grass64/binary/mswindows/native/) and
installed it on my Windows PC (6-4 bit, running Windows 7).
I got the following error message on start-up.
Starting GRASS ...
Paulo van Breugel wrote:
You can use r.mapcalc. If mymap is your raster layer and you want to
change the raster cell at coordinates 52deg and 10deg, use
r.mapcalc mymap = if(x()==52.0 y()==10.00, 1, mymap) --replace
Comparing floating-point values with == is seldom a good idea.
Instead:
Thank you for that answer. I am not sure if I am
able to understand the problem in all details resp. to solve the problem.
So does these changes in the keywords-list (in the main.c?) involve lots of
work or are just minor changes necessary?
I am just asking as I want to use the r.fuzzy tool in
I had the same problem and found out that a system-wide Python
installation (2.7.2, independent of GRASS) caused the trouble.
Uninstalling the system-wide python helped, but this may not be an
option for many users, because other software might rely on a
particular python version installed.
Johannes Radinger wrote:
Thank you for that answer. I am not sure if I am
able to understand the problem in all details resp. to solve the problem.
So does these changes in the keywords-list (in the main.c?) involve lots of
work or are just minor changes necessary?
I am just asking as I
I just want to confirm that replacing my system-wide Python installation with
version 2.7.4, instead of 2.7.2, solved the problem.
Thank you very much
Hanan
-Original Message-
From: Markus Metz [mailto:markus.metz.gisw...@gmail.com]
Sent: 13 May 2013 16:11
To: Hanan Karam
Cc:
Hanan wrote:
I just want to confirm that replacing
my system-wide Python installation with version 2.7.4,
instead of 2.7.2, solved the problem.
thanks for the confirmation.
(@devs: where to put wingrass release notes these days?)
MarkusM:
I had the same problem and found out that a
Johannes:
So maybe it is possible to update the r.fuzzy tools to
be successfully compiled with GRASS7.
Glynn:
AFAICT, it's just a case of replacing:
module-keywords = _(raster, fuzzy logic);
with:
G_add_keyword(_(raster));
G_add_keyword(_(fuzzy logic));
try r56245.
Hamish
13 matches
Mail list logo
