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