Jonathan Greenberg wrote:
I recall some time ago there was a way to hack grass (is this a more
formal boot-time option now?) and have it ignore .gislock to run concurrent
processes in the same mapset. I'm curious if this is still
possible,
The easiest way to get around the locking is to
Hi,
I'm running GRASS 6.4.0RC6 on Windows XP SP1.
Working my way through the book Open Source GIS a GRASS GIS Approach
3rd ed. by Markus Neteler and Helena Mitasova, I have noticed problems
with some d.* commands.
For example, when I type d.histogram into the GUI layer manager
command line, I
Jonathan Greenberg wrote:
I recall some time ago there was a way to hack grass (is this a more
formal boot-time option now?) and have it ignore .gislock to run
concurrent processes in the same mapset. I'm curious if this is still
possible, and, if so, if it would be safe to do this with
Hanlie Pretorius wrote:
However, d.correlate seems to output multiple files that overwrite one
another.
Is there a way around this?
Try making this change to the d.correlate script:
--- d.correlate (revision 41749)
+++ d.correlate (working copy)
@@ -97,6 +97,8 @@
fi
d.erase
Greetings
I need to import Landsat images (r.in.gdal) to my location but, my Landsat
images are in a specific Coordinate system (WGS84) that is different from
mine. Could anyone explain me (briefly ) the steps to import this images?
Thanks
Jenny
___
Tony Bazeley wrote:
I'm new to GRASS, even newer to WMS and am trying to import
some nearmap tiles. I have some partial success as shown below.
Could the solution be changing file extensions and running
gdalwarp with appropriate parameters?
If so I have no idea of the next step.
I've
On 10 May 2010, at 18:00, Jenny Turner wrote:
Greetings
I need to import Landsat images (r.in.gdal) to my location but, my Landsat
images are in a specific Coordinate system (WGS84) that is different from
mine. Could anyone explain me (briefly ) the steps to import this images?
Thanks
António
I have does this; I think it's helpful to first extract the fields you
need and group them together, otherwise you will probably end up with a
lot of unwanted fields being imported. I have written a Perl script to
do this if you want it. I'm sure you would need to edit it to meet your
from ESET NOD32 Antivirus, version of virus signature
database 5100 (20100510) __
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman
__ Information from ESET NOD32 Antivirus, version of virus signature
database 5100 (20100510) __
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman
Hello everyone,
before beginning to write script from scratch I'd like to know if I can use
the r.stream.* for my tasks.
What I need to this is:
- For each subbasin in a certain area extract each subbasin-outlet;
- Input a certain number of points and extract the subbasins using the
points as
of virus signature
database 5102 (20100510) __
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user
...
Thanks
__ Information from ESET NOD32 Antivirus, version of virus
signature database 5102 (20100510) __
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
___
grass-user mailing list
grass-user@lists.osgeo.org
Andrew MacIntyre wrote:
In the case where SWIG is using its own objects to contain returned
pointers, then I expect pyobj_to_ptr() needs to be changed to use
SWIG_ConvertPtr() rather than PyCObject_AsVoidPtr() to retrieve the
actual pointer, or the output typemaps for returned
Dear all,
I am trying to export some point data to a shapefile (admittedly a large number
of points, in the region of 195 but I'm sure I have exported larger files
before) and keep getting an error abut 1/3 of the way through the export
regarding running out of memory (error message
From: Glynn Clements
Andrew MacIntyre wrote:
In the case where SWIG is using its own objects to contain
returned
pointers, then I expect pyobj_to_ptr() needs to be changed to
use
SWIG_ConvertPtr() rather than PyCObject_AsVoidPtr() to retrieve
the
actual pointer, or the output
16 matches
Mail list logo