[GRASS5] [bug #1066] (grass) strange r.reclass warning

[Markus Neteler]

On Tue, May 28, 2002 at 11:07:28PM +0100, Glynn Clements wrote:
> 
> Request Tracker wrote:
> 
> > Subject: strange r.reclass  warning
> > 
> > grass obtained from: CVS
> > grass binary for platform: Compiled from Sources
> > 
> > Dear developers,
> > 
> > the r.reclass command prints a strange message:
> > 
> > r.reclass in=riserve2001 out=tberiserve < reclassfile
> > WARNING: Unable to create dependency file in [riserve2001 in
> >          habitatCap2001]
> > 
> > The reclassfile looks like this:
> > 164 45 49 28 78 34 171 = 1 caprioli campionati negativi
> > 213 206 152 182 = 2 solo caprioli campionati positivi
> > 6 65 57 15 = 3 solo casi umani
> > 185 83 192 = 4 casi umani e caprioli campionati positivi
> > 
> > The original map is not in the current mapset and belongs to a different owner.
> > r.info riserve2001
> >  | Layer:    riserve2001                    Date: Thu May 31 15:42:47 2001      | Mapset:   habitatCap2001                 Login of Creator: lpotrich          | Location: pat                                                                | DataBase: /mpa_gdata/ssi/BIO/GRASS_DATA/data                               
> > 
> > g.gisenv
> > GISDBASE=/mpa_gdata/ssi/BIO/GRASS_DATA/data
> > LOCATION_NAME=pat
> > MAPSET=adonini
> > 
> > Perhaps the reclass_to file cannot be written?
> 
> Correct.
> 
> BTW, this was the very first change I made to GRASS (bug #229, March
> 2001). Before that, r.reclass would just fail if you didn't have write
> permission on the source mapset.
> 
> > The current warning is not really helpful...
> 
> src/libes/gis/reclass.c, line 261:
> 
>         G_warning (_("Unable to create dependency file in [%s in %s]"),
>     	    buf2, reclass->mapset);
> 
> Feel free to change it; although I'm not sure that any message will be
> helpful to a user that doesn't understand the details of the reclass
> mechanism. Maybe the situation should be silently ignored?

I suggest yes - it will be more confusing than helpful (and the user
can even do nothing about it except generating an own local copy
of the "foreign" mapset which is mostly not possible or desired).

We could keep the warning commented in the code in case we change our
opinion in future.

 Markus