Right, explanation makes sense.
Also, thanks for the quick fix. Much appreciated!
Allar
On 11/07/2013 12:30, Glynn Clements wrote:
When the output is an integer map, the result of the average, variance
and stddev methods is supposed to be rounded to the nearest integer
(rather than towards
Hi,
I noticed today that average method in r.neighbours gives an incorrect
value. Let me give you an example:
1) I have a raster soiltype1 consisting of 0's and 1's:
r.univar map=soiltype1@soil percentile=100
total null and non-null cells: 3500
total null cells: 10299386
Of the non-null
Hi,
I encountered an issue with some database modules in WinGRASS 7
(revision 56269). If I add a vector layer to the display, several v.db.*
modules give me an error, such as:
Traceback (most recent call last):
File C:\OSGeo4W\apps\grass\grass-7.0.svn\etc\gui\wxpython
\lmgr\frame.py, line
Hi,
I suspect the input raster file is imported as three rasters (one for
each RGB band). After r.in.gdal, check if there are some rasters in the
mapset (e.g. NP_source.red, NP_source.green, NP_source.blue) and then
combine them using r.composite.
Allar
On 11/05/2013 11:14, Dr Colin
I can confirm the problem with GRASS 7, but only with osgeo4w installer.
When using standalone from http://wingrass.fsv.cvut.cz/grass70/ I have
no issues. Mind you, however, there's the osgeo4w based standalone
available too which I did not test.
Regards,
Allar
On 21/04/2013 10:16, Markus
Ah, your sqlite3.dll renaming workaround suggested in the comments there
did the trick.
Thank you
Regards,
Allar
if you've updated your osgeo4w-python to 2.7.4, than it's another problem
with osgeo4w-wingrass7, see
http://lists.osgeo.org/pipermail/osgeo4w-dev/2013-April/002202.html
-
