[GRASS-user] Re: grass-user Digest, Vol 60, Issue 57

vinod kumar nani.kunithi at gmail.com
Wed Apr 27 08:48:56 EDT 2011


Hi all,

I have not found r.in.wms in the path where i have installed grass
C:\Archivos de programa\GRASS-64\bin

And so i am getting  an error as "no such command exists"

What should i do to run the command or should i get any r.in.wms.exe from
any source.

Thanks ,
nani

On Wed, Apr 27, 2011 at 12:38 PM, <grass-user-request at lists.osgeo.org>wrote:

> Send grass-user mailing list submissions to
>        grass-user at lists.osgeo.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        http://lists.osgeo.org/mailman/listinfo/grass-user
> or, via email, send a message with subject or body 'help' to
>        grass-user-request at lists.osgeo.org
>
> You can reach the person managing the list at
>        grass-user-owner at lists.osgeo.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of grass-user digest..."
>
>
> Today's Topics:
>
>   1. Re: remove grass 6.4.0 (Maris Nartiss)
>   2. Re: Re: how to only fill small sinks with r.fill.dir (Markus Metz)
>   3. color for stdout print output (Johannes Radinger)
>   4. Re: color for stdout print output (Martin Landa)
>   5. d.barb: call for testing (Hamish)
>   6. Re: color for stdout print output (Johannes Radinger)
>   7. info: overwrite option in r.mask (Johannes Radinger)
>   8. Re: info: overwrite option in r.mask (Martin Landa)
>   9. Re: GRASS GIS 6.4.1 released (Giovanni Manghi)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 27 Apr 2011 08:50:56 +0300
> From: Maris Nartiss <maris.gis at gmail.com>
> Subject: Re: [GRASS-user] remove grass 6.4.0
> To: mega saputra <mega.saputra7 at gmail.com>
> Cc: grass-user at lists.osgeo.org
> Message-ID: <BANLkTimymUbt=53aG7BN6kFNBSTTmUtaWw at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> Hello,
> You forgot to mention Your operating system.
>
> I look into my crystall ball and see You using MS-Windows and also
> using QuantumGIS.
> On Windows QuantumGIS comes with bundled GRASS 6.4.0. To get rid of
> those icons, simply uninstall QuantumGIS OR do not use those icons ;)
>
> Maris.
>
>
> 2011/4/27, mega saputra <mega.saputra7 at gmail.com>:
> > dear friends
> > i have remove grass 6.4.0. but not complete. there is still grass gis
> 6.4.0
> > (Text), grass gis 6.4.0 (TclTk), and grass gis 6.4.0 (wxPython). how to
> > remove them all?
> > now i have installed grass 6.4.1.
> > thanks for your help.
> >
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 27 Apr 2011 09:03:03 +0200
> From: Markus Metz <markus.metz.giswork at googlemail.com>
> Subject: Re: [GRASS-user] Re: how to only fill small sinks with
>        r.fill.dir
> To: Bryan Keith <bkeith at itascadenver.com>
> Cc: grass-user at lists.osgeo.org
> Message-ID: <BANLkTintsFZSKdQunBtHiJeCSCm9947fDQ at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On Tue, Apr 26, 2011 at 10:26 PM, Bryan Keith <bkeith at itascadenver.com>
> wrote:
> > On Tue, Apr 26, 2011 at 12:53, Markus Metz
> > <markus.metz.giswork at googlemail.com> wrote:
> >> On Tue, Apr 26, 2011 at 7:54 PM, Bryan Keith <bkeith at itascadenver.com>
> wrote:
> >>>
> >>> I think my problem is now with r.flow.  I would like to see flows
> >>> continue through the filled sink and out the other end (as if it were
> >>> a lake), but that doesn't happen.  I don't think it can happen with
> >>> r.flow because r.flow encounters a flat area.
> >>>
> >> r.watershed would do that. Also r.terrraflow, but r.terraflow fills
> >
> > You mean with the stream output?  The problem with that is you're
> > unable to specify where you'd like the streams to start.  You only get
> > the largest accumulation streams, but I want output similar to r.flow
> > which distributes particles throughout the area of interest.
> >
> You can use the flow option of r.watershed: create a raster map where
> all the starting points get a value of 100, all others get a value of
> 0, this map is then used as flow option. As threshold for stream
> initiation you would then use 100. The resulting flow accumulation
> (with MFD) shows you the percentage trickling down to a given cell
> from a start cell, the streams would start at the cells with value
> 100. Of course the value 100 is arbitrary, it can also be 1 or any
> other positive number, the important part is that overland flow for
> non-start cells must be zero.
>
> Markus M
>
> > r.drain allows you to specify where the particulars start, but it's
> > limited to 8-directional flow instead of the smooth flow that r.flow
> > generates (which I prefer).
> >
> >> all remaining sinks internally which is apparently not what you want.
> >> r.watershed also allows you to specify locations of real sinks which
> >> are not traversed.
> >>
> >> BTW, sometime in the next months I want to make available a new module
> >> that performs hydrological conditioning of a DEM using not sink
> >> filling but an impact reduction approach, and which has an option to
> >> remove only sinks smaller than a given size.
> >
> > Sounds like this may be what I'm after!
> >
> > Bryan
> >
> >>
> >> Markus M
> >>
> >>
> >>> Not sure what to try next.  This was a problem even before messing
> >>> around with the sink tolerance.
> >>>
> >>> Bryan
> >>>
> >>> On Tue, Apr 26, 2011 at 10:31, Saber <razmjooeis at faunalia.co.uk>
> wrote:
> >>>> Sorry...I thought the sinks are as null values.
> >>>> Ignore my previous email.
> >>>> I can't think of anything apart from improving your DEM to get rid of
> the
> >>>> artifacts.
> >>>> One way will be to get the initial result from the r.fill.dir.
> Identify
> >>>> the areas where the depth is more than say 10 metre (r.nulls
> >>>> map=initial_result setnull 0-9.99)
> >>>>
> >>>> You can then add the new depth raster to the DEM to create the "filled
> >>>> hole". (first r.mask to match initial_result and then r.mapcalc
> >>>> filled_holes=initial_result+DEM)
> >>>> Then remove the mast and r.patch
> >>>> r.patch input=filled_holes,DEM output=patched_DEM
> >>>>
> >>>> You can then use the patched_DEM for r.fill.dir
> >>>>
> >>>> Hope that helps.
> >>>>
> >>>>
> >>>>
> >>>>> Hmmm, I'm not following all your steps, but I don't want to manually
> >>>>> identify valid sinks vs. invalid sinks.  I have quite a lot of
> >>>>> surfaces to process, and I'm happy to fill all sinks except those
> >>>>> deeper than 10m.
> >>>>>
> >>>>> On Tue, Apr 26, 2011 at 10:04, Saber <razmjooeis at faunalia.co.uk>
> wrote:
> >>>>>> Here is a (not a very quick) solution I can think of:
> >>>>>>
> >>>>>> 1- Create an inverse mask
> >>>>>> 2- convert the mask to vector (r.to.vect)
> >>>>>> 3- clean the vector file to get rid of the areas not required
> (v.clean)
> >>>>>> 4- convert the vector back to raster (v.to.rast)
> >>>>>> 5- Use the new raster as a mask for filling holes (probably you need
> >>>>>> step
> >>>>>> 4.5 to slightly buffer the raster)
> >>>>>>
> >>>>>> Hope that helps
> >>>>>>
> >>>>>>
> >>>>>>> Any ideas on this?
> >>>>>>>
> >>>>>>> Bryan
> >>>>>>>
> >>>>>>> On Mon, Apr 18, 2011 at 14:49, Bryan Keith <
> bkeith at itascadenver.com>
> >>>>>>> wrote:
> >>>>>>>> Hello,
> >>>>>>>>
> >>>>>>>> Is there a way to only fill sinks in a DEM if they are smaller
> than a
> >>>>>>>> certain tolerance?  I have a couple areas of internal drainage
> that
> >>>>>>>> really are correct (and quite large), and I have a quite few small
> >>>>>>>> sinks that are incorrect and artifacts of the interpolation.  Any
> >>>>>>>> ideas how to this?  r.fill.dir attempt to fill all the sinks.
> >>>>>>>>
> >>>>>>>> I'm trying to improve the results from r.flow  Too many tracks end
> in
> >>>>>>>> small holes where I'd like them to continue downstream.  Thanks.
> >>>>>>>>
> >>>>>>>> Bryan
> >>>>>>>>
> >>>>>>> _______________________________________________
> >>>>>>> grass-user mailing list
> >>>>>>> grass-user at lists.osgeo.org
> >>>>>>> http://lists.osgeo.org/mailman/listinfo/grass-user
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>> _______________________________________________
> >>> grass-user mailing list
> >>> grass-user at lists.osgeo.org
> >>> http://lists.osgeo.org/mailman/listinfo/grass-user
> >>>
> >>
> >
>
>
> ------------------------------
>
> Message: 3
> Date: Wed, 27 Apr 2011 09:16:36 +0200
> From: "Johannes Radinger" <JRadinger at gmx.at>
> Subject: [GRASS-user] color for stdout print output
> To: grass-user at lists.osgeo.org
> Message-ID: <20110427071636.54600 at gmx.net>
> Content-Type: text/plain; charset="utf-8"
>
> Hello GRASS users,
>
> i think it should be possible to color the output of certain print-commands
> of a python script, but I don't know how.
>
> It'd be nice e.g if a command like 'print "Script processed succesfully"'
> is printed in green in the stdout of the GRASS command console.
>
> Does anyone know how this can be easily achieved in a python script?
>
> /johannes
> --
> NEU: FreePhone - kostenlos mobil telefonieren und surfen!
> Jetzt informieren: http://www.gmx.net/de/go/freephone
>
>
> ------------------------------
>
> Message: 4
> Date: Wed, 27 Apr 2011 11:01:56 +0200
> From: Martin Landa <landa.martin at gmail.com>
> Subject: Re: [GRASS-user] color for stdout print output
> To: Johannes Radinger <JRadinger at gmx.at>
> Cc: grass-user at lists.osgeo.org
> Message-ID: <BANLkTikq0gPMwJbUr5eYHEniSm3djRsa9w at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi,
>
> 2011/4/27 Johannes Radinger <JRadinger at gmx.at>:
> > It'd be nice e.g if a command like 'print "Script processed succesfully"'
> is printed in green in the stdout of the GRASS command console.
>
> do you mean terminal or wxGUI command output?
>
> Martin
>
> --
> Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa
>
>
> ------------------------------
>
> Message: 5
> Date: Wed, 27 Apr 2011 21:11:41 +1200
> From: Hamish <hamish_b at yahoo.com>
> Subject: [GRASS-user] d.barb: call for testing
> To: grass list <grass-user at lists.osgeo.org>
> Cc: grass-dev <grass-dev at lists.osgeo.org>
> Message-ID: <20110427211141.0fa7caae.hamish_b at yahoo.com>
> Content-Type: text/plain; charset=US-ASCII
>
> Hi,
>
> I have added a new C module in the addons svn which will draw wind barbs,
> straw plots, and arrow plots from a raster array or sparse vector point
> data. It can use either direction + magnitude, or u + v components as the
> input, and can produce a legend key.
>
> Some of this functionality is already covered by d.rast.arrow and d.vect,
> but I thought I'd bring it together into a dedicated tool and add some
> commonly needed options.
>
> It's still a work in progress, and there are still a few things on the
> todo list, but I think it's ready to get some testing now.
>
> Once the bugs are out and the design & feature set have been finalized
> I'd port it to grass7 and hope to add it to the main distribution + GUI.
> (One weird thing I notice is that in the tcl/tk GUI the legend_at=
> option appears as a tick box not a text entry field. ?)
>
>
>  http://grass.osgeo.org/wiki/GRASS_AddOns#d.barb
>  http://trac.osgeo.org/grass/browser/grass-addons/display/d.barb
>
> screenshot:  (style=arrow)
>
> http://bambi.otago.ac.nz/hamish/grass/screenshots/narr-a_221_20100629_1800_000_10m_winds.png
>
>
> maybe g.extension works to install it if you compiled grass yourself?
>  (I haven't tried installing it that way yet)
>
> comments, wishes, & criticisms welcome.  usage follows, see the help
> page for more explanation & examples.
>
>
> Hamish
>
>
>
> --------------------------------------
>
> GRASS65> d.barb --help
>
> Description:
>  Draws flow barbs.
>
> Keywords:
>
>
> Usage:
>  d.barb [-r] [direction=name] [magnitude=name] [u=name] [v=name]
>   [input=name] [layer=value] [style=string] [color=name] [skip=value]
>   [scale=value] [peak=value] [aspect_type=string]
>   [legend_at=x,y[,x,y,...]] [legend_velo=value[,value,...]]
>   [legend_fontsize=value] [--verbose] [--quiet]
>
> Flags:
>  -r   Rotate direction 180 degrees
>        Useful for switching between atmospheric and oceanographic
> conventions
>  --v   Verbose module output
>  --q   Quiet module output
>
> Parameters:
>        direction   Raster map (or attribute column) containing velocity
> direction
>        magnitude   Raster map (or attribute column) containing velocity
> magnitude
>                u   Raster map (or attribute column) containing u-component
> of velocity
>                v   Raster map (or attribute column) containing v-component
> of velocity
>            input   Name of input vector map
>            layer   Layer number
>                     A single vector map can be connected to multiple
> database tables. This number determines which table to use.
>                    default: 1
>            style   Style
>                    options: arrow,barb,straw
>                    default: arrow
>            color   Color
>                     Either a standard color name or R:G:B triplet
>                    default: black
>             skip   Draw arrow every Nth grid cell
>                    default: 10
>            scale   Scale factor for arrow rendering
>                    default: 1.0
>             peak   Maximum value for scaling (overrides map's maximum)
>      aspect_type   Direction map aspect type
>                    options: cartesian,compass
>                    default: cartesian
>        legend_at   Screen percentage for legend barb ([0,0] is bottom-left)
>                     Draws a single barb and exits
>                    options: 0-100
>                    default: 10.0,10.0
>      legend_velo   Velocity for legend key arrow
>  legend_fontsize   Font size used in legend
>                    default: 14
>
>
> ------------------------------
>
> Message: 6
> Date: Wed, 27 Apr 2011 11:22:28 +0200
> From: "Johannes Radinger" <JRadinger at gmx.at>
> Subject: Re: [GRASS-user] color for stdout print output
> To: Martin Landa <landa.martin at gmail.com>
> Cc: grass-user at lists.osgeo.org
> Message-ID: <20110427092228.171060 at gmx.net>
> Content-Type: text/plain; charset="utf-8"
>
>
> -------- Original-Nachricht --------
> > Datum: Wed, 27 Apr 2011 11:01:56 +0200
> > Von: Martin Landa <landa.martin at gmail.com>
> > An: Johannes Radinger <JRadinger at gmx.at>
> > CC: grass-user at lists.osgeo.org
> > Betreff: Re: [GRASS-user] color for stdout print output
>
> > Hi,
> >
> > 2011/4/27 Johannes Radinger <JRadinger at gmx.at>:
> > > It'd be nice e.g if a command like 'print "Script processed
> > succesfully"' is printed in green in the stdout of the GRASS command
> console.
> >
> > do you mean terminal or wxGUI command output?
>
> In my case I am starting my script in the GRASS in the command console,
> so the output is in the GUI command output.
>
> Johannes
>
> >
> > Martin
> >
> > --
> > Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa
>
> --
> GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit
> gratis Handy-Flat! http://portal.gmx.net/de/go/dsl
>
>
> ------------------------------
>
> Message: 7
> Date: Wed, 27 Apr 2011 11:52:06 +0200
> From: "Johannes Radinger" <JRadinger at gmx.at>
> Subject: [GRASS-user] info: overwrite option in r.mask
> To: grass-user at lists.osgeo.org
> Message-ID: <20110427095206.82160 at gmx.net>
> Content-Type: text/plain; charset="utf-8"
>
> I just wanted to inform you (developers), but the overwrite option
> in r.mask is somehow different from the other modules.
>
> Especially if it comes to python scripts usually the
> overwrite option is set with "overwrite=True" but for
> r.mask it has to be set with a flag like "flags="o"".
>
> I don't know if this is intended (probably because of the
> second option "r" (remove existing mask)).
>
> cheers
> /johannes
> --
> GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit
> gratis Handy-Flat! http://portal.gmx.net/de/go/dsl
>
>
> ------------------------------
>
> Message: 8
> Date: Wed, 27 Apr 2011 12:32:39 +0200
> From: Martin Landa <landa.martin at gmail.com>
> Subject: Re: [GRASS-user] info: overwrite option in r.mask
> To: Johannes Radinger <JRadinger at gmx.at>
> Cc: grass-user at lists.osgeo.org
> Message-ID: <BANLkTikJ6=T608K-s3WK9bn=kFckmLY6MQ at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi,
>
> 2011/4/27 Johannes Radinger <JRadinger at gmx.at>:
> > I just wanted to inform you (developers), but the overwrite option
> > in r.mask is somehow different from the other modules.
> >
> > Especially if it comes to python scripts usually the
> > overwrite option is set with "overwrite=True" but for
> > r.mask it has to be set with a flag like "flags="o"".
>
> this flag (o) has been already removed in GRASS 7 and replaced by
> `--overwrite`. There is just small bug - the parser doesn't note
> --overwrite flag.
>
> Martin
>
> --
> Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa
>
>
> ------------------------------
>
> Message: 9
> Date: Wed, 27 Apr 2011 11:38:08 +0100
> From: Giovanni Manghi <giovanni.manghi at gmail.com>
> Subject: Re: [GRASS-user] GRASS GIS 6.4.1 released
> To: Martin Landa <landa.martin at gmail.com>
> Cc: GRASS user list <grass-user at lists.osgeo.org>
> Message-ID: <1303900688.1833.118.camel at sibirica>
> Content-Type: text/plain; charset="UTF-8"
>
> Hi,
>
> > I am super busy this week, it's in my TODO. Anyway I will publish the
> > package till the end of this week, as I said before.
>
> sorry for bugging (again), any news about this?
>
> GRASS is actually unusable for osgeo4w users and I would really like to
> confirm if the issues were solved in 6.4.1
>
> Thanks in advance
>
> -- Giovanni --
>
>
>
> ------------------------------
>
> _______________________________________________
> grass-user mailing list
> grass-user at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-user
>
>
> End of grass-user Digest, Vol 60, Issue 57
> ******************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/grass-user/attachments/20110427/4a97ca1d/attachment-0001.html


More information about the grass-user mailing list