[GRASS-user] r.sim.water depth and error ranges are the same

Hi, I ran r.sim.water on a DEM using the process in the manual for generating the rainfall, manning and infiltration maps. The height in the DEM vary from 1429.79 m to 1740.20 m. I opted to output the rainfall depth and the error maps. The ranges of both these output maps (as reported by

Re: [GRASS-user] r.watershed error

On Sun, May 23, 2010 at 8:10 PM, Kurt Springs ferret_b...@mac.com wrote: Problem was the resolution it starts working when I set it to 100m.  The dem is ~69 x 27 km. Apparently, the dem has a resolution of 1/3 arcsec (~10m), maybe reprojected and resampled. With these extends, there would be

[GRASS-user] Using an external hard drive as data source

Hi, I'm using GRASS 6.4 on two machines in different locations (one Win XP, the other Ubuntu 10.04), so I would like to keep my grassdata folder on an external drive. However, when I try to run grass in Ubuntu using the external hard drive (NTFS file system), I get the following error as soon as

[GRASS-user] conditional dissolve

Hi, I'm using the shapefile of the GADM database of Global Administrative Areas (http://www.gadm.org), but the subdivisions of some countries (such as Spain, Slovenia and others) are too small. In order to get divisions that are more evenly sized among all countries, I need to dissolve

Re: [GRASS-user] Importing Landsat images with different coordinates

Hi Following this topic I have tested this methodology by converting from UTM 29N to a specific local coordinate system (EPSG:3763) (available at PROJ4) gdalwarp -t_srs EPSG:3763 band_landsat.TIF destination.tif With that I got a segmentation error, one TIFFReadDirectory a lot of

[GRASS-user] Warnings while importing Kompsat-2 images

Hi there I imported Kompsat-2 images using r.in.gdal and I gfot this warnings: rning 1: TIFFFetchNormalTag:ASCII value for tag DocumentName does not end in null byte Warning 1: TIFFFetchNormalTag:ASCII value for tag ImageDescription does not end in null byte Warning 1: TIFFFetchNormalTag:ASCII

[GRASS-user] Georrectification using points

Greetings I have a few very-high resolution images that I need to georrectify in GRASS. Outside GRASS I created a text file with GCP position in the image and its real-coordinates. I have read this: http://grass.osgeo.org/wiki/Georeferencing I tried to use i.rectify but I didn't see no place to

Re: [GRASS-user] Georrectification using points

Luisa wrote: I have a few very-high resolution images that I need to georrectify in GRASS. Outside GRASS I created a text file with GCP position in the image and its real-coordinates. I have read this: http://grass.osgeo.org/wiki/Georeferencing I tried to use i.rectify but I didn't see no

Re: [GRASS-user] Using an external hard drive as data source

Hanlie Pretorius pisze: Hi, I'm using GRASS 6.4 on two machines in different locations (one Win XP, the other Ubuntu 10.04), so I would like to keep my grassdata folder on an external drive. However, when I try to run grass in Ubuntu using the external hard drive (NTFS file system), I get the

Re: [GRASS-user] Warnings while importing Kompsat-2 images

Luis wrote: Hi thereI imported Kompsat-2 images using r.in.gdal and I gfot this warnings:rning 1: TIFFFetchNormalTag:ASCII value for tagDocumentName does not end in null byteWarning 1: TIFFFetchNormalTag:ASCII value for tag ImageDescription does not end in null byteWarning 1:

Re: [GRASS-user] Using an external hard drive as data source

Hanlie wrote: I'm using GRASS 6.4 on two machines in different locations (one Win XP, the other Ubuntu 10.04), so I would like to keep my grassdata folder on an external drive. However, when I try to run grass in Ubuntu using the external hard drive (NTFS file system), I get the following

Re: [GRASS-user] Importing Landsat images with different coordinates

On 05/24/2010 06:26 PM, Jenny Turner wrote: Hi Following this topic I have tested this methodology by converting from UTM 29N to a specific local coordinate system (EPSG:3763) (available at PROJ4) gdalwarp -t_srs EPSG:3763 band_landsat.TIF destination.tif With that I got a segmentation

Re: [GRASS-user] r.watershed error

Thanks Markus, Let me make sure I understand. For best results I need to set the resolution to 10m for the 1/3 arcsec. With the region set as it is (most of Northern New England) when I do this I run out of memory. To over come this, I can set the region to just encompass just the NED13_01

Re: [GRASS-user] r.watershed multi flow direction

On Fri, May 21, 2010 at 1:27 PM, Kristian Foerster k.foers...@tu-bs.de wrote: Hi, I am using GRASS 6.4.0RC5+39438 (downloaded from svn server). I would like to obtain basins and stream segments from digital elevation data using the multi flow option in r.watershed as proposed in the

Re: [GRASS-user] Copying from a mapset in another data directory

Excellent -- symlinking is working properly -- now on to my next question -- is there a way to do some level of batch g.copy using a wildcard, e.g.: g.copy rast=ned_ca_masked_epsg331...@comet Or do I have to specific each raster individually, along with its target file name? --j On Wed, May

Re: [GRASS-user] v.split length=? in latlon

On Fri, May 21, 2010 at 6:59 PM, Achim Kisseler a...@jupiter.uni-freiburg.de wrote: Hi, in v.split: I wonder what units are be used as length in a lat-lon environment? Are these degrees? I am afraid yes since it uses Vect_line_length(). Certainly this is rather useless. The doxygen

Re: [GRASS-user] Copying from a mapset in another data directory

Jonathan Greenberg wrote: Excellent -- symlinking is working properly -- now on to my next question -- is there a way to do some level of batch g.copy using a wildcard, e.g.: g.copy rast=ned_ca_masked_epsg331...@comet Or do I have to specific each raster individually, along with its