On 2018-11-19 at 16:59 +0100, Markus Metz wrote:
> looking at your aim: get basins for all outlets, you could also use
> 1. r.stream.extract with stream_vector as output
> outlets have category value 2 in layer 2
> 2. extract the outlets with v.extract lyer=2 type=point cats=2
> 3. use the outle
On Mon, Nov 19, 2018 at 4:52 PM Ken Mankoff wrote:
>
> Hi Martin,
>
> On 2018-11-19 at 16:32 +0100, Markus Metz
wrote:
> >> On 2018-11-19 at 08:26 +0100, Ken Mankoff wrote:
> >>
> >> r.mapcalc "basin = if(basin, ${count}, null())" --o
> >> r.to.vect -v input=basin output=b type=area --o
> >> v.p
Hi Martin,
On 2018-11-19 at 16:32 +0100, Markus Metz wrote:
>> On 2018-11-19 at 08:26 +0100, Ken Mankoff wrote:
>>
>> r.mapcalc "basin = if(basin, ${count}, null())" --o
>> r.to.vect -v input=basin output=b type=area --o
>> v.patch -a input=b output=basin --o
>> v.clean in=basin out=basin_clean0
On Mon, Nov 19, 2018 at 12:20 PM Ken Mankoff wrote:
>
> Hi List,
>
> On 2018-11-19 at 08:26 +0100, Ken Mankoff wrote:
> > I'm having trouble getting v.patch to patch some vectors. I've tested
> > this on Linux grass 7.4.0 (default Ubuntu 18.04 version) and SVN trunk
> > from this evening.
>
> It
Hi List,
On 2018-11-19 at 08:26 +0100, Ken Mankoff wrote:
> I'm having trouble getting v.patch to patch some vectors. I've tested
> this on Linux grass 7.4.0 (default Ubuntu 18.04 version) and SVN trunk
> from this evening.
It appears I can get the patched vectors to work by using v.clean. In th
Hi GRASS List,
[Sorry if you see this 2x. Sent to grass-dev list by mistake].
I'm having trouble getting v.patch to patch some vectors. I've tested this on
Linux grass 7.4.0 (default Ubuntu 18.04 version) and SVN trunk from this
evening.
I'm trying to "accumulate" vectors, incrementally, via v
Thanks. That helps. I now use the output of that (SZA_lut) and the
following:
r.mapcalc --o < wrote:
>
>
> Le 17 octobre 2017 13:38:34 GMT+02:00, Ken Mankoff a
> écrit :
> >Dear GRASS List,
> >
> >I'm trying to do something in GRASS and can't figure out an efficient
> >way to do it. I'm guessing
Le 17 octobre 2017 13:38:34 GMT+02:00, Ken Mankoff a écrit :
>Dear GRASS List,
>
>I'm trying to do something in GRASS and can't figure out an efficient
>way to do it. I'm guessing it is possible with 1-3 lines, but don't
>know which ones. The algorithm I'm developing would be much more
>complex,
Dear GRASS List,
I'm trying to do something in GRASS and can't figure out an efficient way to do
it. I'm guessing it is possible with 1-3 lines, but don't know which ones. The
algorithm I'm developing would be much more complex, and I hope someone can
suggest a shortcut.
I have several satelli
--
>
> Message: 1
> Date: Mon, 19 May 2014 12:39:23 +0300
> From: Nick Ves
> To: Tim Southern
> Cc: Grass Users
> Subject: Re: [GRASS-user] patching maps together
> Message-ID:
>
> Content-Type: text/plain; charset=UTF-8
>
Tim wrote:
> I am trying to patch together a number of 1 km by 1 km tiles of a map
> whose values are either 0 or 1 (black on white background).
>
> If I use r.patch to put 2 tiles together is appears to work fine but
> if however I try and patch more, even if it is two tiles of already
> patched
Hey Tim,
If your maps don't overlap with each other you could use r.series in your case :
$ g.region rast=$(g.mlist rast sep=",")
$ r.series input=$(g.mlist rast sep=",") out=myMap method=sum
N
On Mon, May 19, 2014 at 11:31 AM, Tim Southern
wrote:
> Dear All,
>
> I am trying to patch together
Dear All,
I am trying to patch together a number of 1 km by 1 km tiles of a map whose
values are either 0 or 1 (black on white background).
If I use r.patch to put 2 tiles together is appears to work fine but if however
I try and patch more, even if it is two tiles of already patched tiles I ge
Dear List,
I have several ASTER GDEM (originally Latlong) images that I want to
reinterpolate from 30 to 10 m res. I also need to patch these images. I am
not sure whether:
- I should patch them in Latlong using r.series, reproject into UTM and
interpolate them using r.resamp.rst or
- reprojec
stephen wrote:
> r.info
> any ideas,
{
g.region rast=yourmap
+
r.univar yourmap
d.histogram yourmap
}
are other useful ways to see if there is really any data in the map,
even if the color map (r.colors) has somehow gone completely out of range
and 0-100% is all set to a single color.
Markus,
I made a Permanent Map set and put in everything from the projection
region, and followed your directions. They worked. I have created
the map, and I am now reprojecting it into another mapset so that I
can use v.strahler to calculate stream orders. Thank you so much for
your help. As i
stephen sefick wrote:
> yes still 0-296. I think the problem is this
>
> r.info -s series_map
> nsres=1:09:25.8
> ewres=1:01:15.8736
>
> however:
> g.region -p
> projection: 3 (Latitude-Longitude)
> zone: 0
> datum: nad83
> ellipsoid: grs80
> north: 34:23:38.97N
> south:
yes still 0-296. I think the problem is this
r.info -s series_map
nsres=1:09:25.8
ewres=1:01:15.8736
however:
g.region -p
projection: 3 (Latitude-Longitude)
zone: 0
datum: nad83
ellipsoid: grs80
north: 34:23:38.97N
south: 30:23:31.96N
west: 84:31:21.9W
eas
stephen sefick wrote:
> I followed the directions all set to srtm, computation region set to
> resolution of the coarsest (they are all the same and 00:00:01). The
> map is still coming out as 7 different solid color blocks.
>
You have set the region to include all tiles? You have zoomed to the
I followed the directions all set to srtm, computation region set to
resolution of the coarsest (they are all the same and 00:00:01). The
map is still coming out as 7 different solid color blocks.
On Thu, Jul 9, 2009 at 12:58 PM, Markus
Metz wrote:
> stephen sefick wrote:
>> values range from ~-9
stephen sefick wrote:
> values range from ~-9 to ~800 there is a tile which has no elevation.
> The patched dem only ranges from 0-296. This may be the problem.
>
It seems that the current computational region did not include all tiles.
Try setting the computational region to include all tiles
values range from ~-9 to ~800 there is a tile which has no elevation.
The patched dem only ranges from 0-296. This may be the problem.
On Thu, Jul 9, 2009 at 11:27 AM, Moritz
Lennert wrote:
> On 09/07/09 18:17, stephen sefick wrote:
>>
>> r.patch this gives me single color when the original dems
On 09/07/09 18:17, stephen sefick wrote:
r.patch this gives me single color when the original dems where
reliefs (there is topography). What am I doing wrong? I have set the
n-s e-w resolution to 00:00:03 because I downloaded 1/3 arc second dem
from the seamless server (.adf). I am confused as
On Thu, 2009-07-09 at 11:17 -0500, stephen sefick wrote:
> r.patch this gives me single color when the original dems where
> reliefs (there is topography). What am I doing wrong? I have set the
> n-s e-w resolution to 00:00:03 because I downloaded 1/3 arc second dem
> from the seamless server (.a
r.patch this gives me single color when the original dems where
reliefs (there is topography). What am I doing wrong? I have set the
n-s e-w resolution to 00:00:03 because I downloaded 1/3 arc second dem
from the seamless server (.adf). I am confused as to what to do next.
Is r.patch the wrong
Thanks-
I had originally been having trouble trying to extend the regions beyond the
end of the zone because when I used g.region with -p flag, the nesw borders
were given for each zone specifically, and I understood it that there were
overlapping borders between zones 16,17, and 18. When I v
You can try using the "-n" flag for r.proj to avoid region clipping or
you can extend your region beyond the edges of the zone.
On 1-Apr-09, at 4:10 PM, Renae Mackas wrote:
Hello GRASS users-
I am trying to create a mosaic of LANDSAT taken of Eastern Hudson
Bay area using GRASS 6.3.0. I
Hello GRASS users-
I am trying to create a mosaic of LANDSAT taken of Eastern Hudson Bay area
using GRASS 6.3.0. I have run into the problem though that some of these
images are from different UTM zones (16, 17, and 18). Currently, I have been
able to import images from the three UTM zones i
Markus Neteler wrote:
> Richard,
>
> without error messages it's hard to understand...
> Could you run it in command line? Then you may be able to
> copy the error.
>
> Alternative: tell us how to replicate it in the Spearfish or North
> Carolina sample data set...
>
Markus,
The error:
ERROR: B
Richard,
without error messages it's hard to understand...
Could you run it in command line? Then you may be able to
copy the error.
Alternative: tell us how to replicate it in the Spearfish or North
Carolina sample data set...
Markus
On Thu, Oct 23, 2008 at 11:49 PM, Richard Chirgwin
<[EMAIL P
Hi,
There seems to be a problem in handling of large numbers of vectors.
I had a large number of buffered points to put together. The buffer
areas (with centroids added) were constrained by non-overlapping areas
to avoid errors later, after which I wanted to patch them together into
a single file
Hi grass users,
I have 4 dem, 2 are 1x1 m resolution and 2 are 2x2 m a resolution; I
'd like to have just one global dem 2x2 m resolution.
If I import the data with their native resolution then I set the
region to the total area with a resolution of 2x2 (g.region -a res=2
rast=dem1, dem2,
Thanks a lot, Manfred,
It did solve the problem. I am quite new to grass so I've still a lot of
things to learn :-)
Jana
Dr. Manfred Redslob wrote:
>
> Am Freitag, 11. Juli 2008 13:56 schrieb Jana K.:
>> I have 2 raster maps in the same papset. I needed to complement the null
>> values in the
Am Freitag, 11. Juli 2008 13:56 schrieb Jana K.:
> I have 2 raster maps in the same papset. I needed to complement the null
> values in the first map with values from the second. I used r.patch
> input=map1,map2 output=map3. The resulting map3, however, is an empty map.
> Can the fact that map1 and
I have 2 raster maps in the same papset. I needed to complement the null
values in the first map with values from the second. I used r.patch
input=map1,map2 output=map3. The resulting map3, however, is an empty map.
Can the fact that map1 and map2 resulted from r.reclass procedures (the
original m
35 matches
Mail list logo
