in GRASS6.4.3 I noticed that an error message shows up in red with ERROR in the 
GIS manager output window
while warning just shows the text in blue but the word WARNING is missing (it 
shows up when running this in shell)
This is causing confusion - students do not know what the message means - is 
that a problem or can they ignore it?
Would it be possible to add the word WARNING so that the message is consistent 
with the shell and with the 
ERROR message.
here is an example of what I am talking about:

r.average base=zipcodes cover=elevation out=elev_avgzip                         
ERROR: option <output>: <elev_avgzip> exists.
                                                     
r.average base=zipcodes cover=elevation out=elev_avgzip2                        
r.stats:
Cats for raster map <elevation@PERMANENT> are either missing or have no 
explicit labels. Using nsteps=255.
r.recode:
r.recode complete. Raster map <elev_avgzip2> created.

Thank you, Helena


Helena Mitasova
Associate Professor
Department of Marine, Earth, and Atmospheric Sciences
2800 Faucette Drive, Rm. 1125 Jordan Hall
North Carolina State University
Raleigh, NC 27695-8208
hmit...@ncsu.edu

"All electronic mail messages in connection with State business which are sent 
to or received by this account are subject to the NC Public Records Law and may 
be disclosed to third parties.” 

On Aug 28, 2012, at 11:28 AM, Markus Neteler wrote:

> On Fri, Aug 24, 2012 at 10:53 AM, Peter Löwe <plo...@gfz-potsdam.de> wrote:
> ...
>> Maybe this would be a good place to collect such kind of info:
>> http://grass.osgeo.org/wiki/GRASS_GIS_Performance
>> 
>> FWIW I included a section on the limitation concerning "vectors with LOTS of
>> attributes". I just ran into that concrete wall the other day.
> 
> For the record, I have updated
> http://grass.osgeo.org/wiki/GRASS_GIS_Performance#Maximum_Number_of_Attribute_Columns
> 
> Note that it is a DB backend limit which subsequently constraints GRASS GIS. 
> You
> can use a recompiled SQLite backend to manage *many* columns (see link in
> Wiki page above).
> 
> best,
> Markus
> _______________________________________________
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev

_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Reply via email to