r.reclass by rules

[Agustin Lobo]

Is r.reclass leaving as null any original
value for which there is no reclassification rule?
I mean, if A had a range 1 to 10 and we reclassify
values 1, 4 and 6 to 100, are the rest
of values changed to null? No way of
leaving them unchanged?

Thanks

Agus

[alobolistas.vcf]

---

begin:vcard
fn:Agustin Lobo
n:Lobo;Agustin
org:Institut de Ciencies de la Terra "Jaume Almera" CSIC
adr:;;Lluis Sole Sabris s/n;Barcelona;;08028;Spain
email;internet:[hidden email]
url:http://www.ija.csic.es/gt/obster
version:2.1
end:vcard

---

_______________________________________________
grass-stats mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-stats

[Agustin Lobo]

Thanks, this is saving time, as I was having
to use r.mapcalc after r.reclass.
Is this important trick in the manual?
I could not find it. Perhaps I should have figured it out
after the example * = NULL, but I think
that should be specifically mentioned.

Agus

Aldo Clerici wrote:

> Agus,
>
> It should be:
> 1 4 6 = 100
> *=*
> end
>
> Greetings
> A.Clerici
>
>
> -----Messaggio originale-----
> Da: [hidden email]
> [mailto:[hidden email]] Per conto di Agustin Lobo
> Inviato: mercoledì 9 settembre 2009 14.53
> A: [hidden email]
> Oggetto: [GRASS-stats] r.reclass by rules
>
> Is r.reclass leaving as null any original
> value for which there is no reclassification rule?
> I mean, if A had a range 1 to 10 and we reclassify
> values 1, 4 and 6 to 100, are the rest
> of values changed to null? No way of
> leaving them unchanged?
>
> Thanks
>
> Agus
>
>

_______________________________________________
grass-stats mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-stats

[hamish-2]

Agustin wrote:
> Thanks, this is saving time, as I was having
> to use r.mapcalc after r.reclass.
> Is this important trick in the manual?
> I could not find it. Perhaps I should have figured it out
> after the example * = NULL, but I think
> that should be specifically mentioned.

thanks for mentioning it was missing. The r.reclass manual is now updated
in SVN to point out this trick.


Helena: some kind soul has added a fail-safe into g.remove, now if you try
to remove a raster which has a reclass based upon it you get an error
message:

GRASS65> g.remove landuse.copy
WARNING: [landuse.copy@user1] is a base map. Remove reclassed map first:
         landuse.copy.reclass@user1

I'm assuming the g.remove -f force flag is there to override that.
Not sure if it notices that there is a reclass based upon it existing
in another mapset (perhaps owned by another user), but I guess you
make reclass maps based on other people's maps at your own risk. ie you
would naturally get mad at them, not the GIS, when they remove it.


Hamish



     
_______________________________________________
grass-stats mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-stats