Hi,
r.pack is failing on reclassed maps and just packaging the reclass stuff.
how to deal with that?
- either fatal error with a reasonable suggestion to the user
- or generate internally a map copy with r.mapcalc (slower), then package
?
Markus
Markus Neteler wrote:
r.pack is failing on reclassed maps and just packaging the reclass stuff.
how to deal with that?- either fatal error with a reasonable suggestion to the user
- or generate internally a map copy with r.mapcalc (slower), then package
?
First, is this actually a failure?
In any case, there doesn't appear to be a supported programmatic
method for determining that a map is a reclass. r.info includes
relcass information in the default "formatted" output, and in the
output for -h, but neither of these are designed to be
machine-readable.
--
Glynn Clements <glynn@gclements.plus.com>
Glynn wrote:
In any case, there doesn't appear to be a
supported programmatic method for determining
that a map is a reclass.
at the filesystem level, checking the first line of
cellhd/$map_name gives you the info.
Hamish
On Thu, Oct 13, 2011 at 11:12 AM, Glynn Clements
<glynn@gclements.plus.com> wrote:
Markus Neteler wrote:
r.pack is failing on reclassed maps and just packaging the reclass stuff.
how to deal with that?- either fatal error with a reasonable suggestion to the user
- or generate internally a map copy with r.mapcalc (slower), then package
?First, is this actually a failure?
Yesm in a sense that r.unpack fails on such a package.
In any case, there doesn't appear to be a supported programmatic
method for determining that a map is a reclass. r.info includes
relcass information in the default "formatted" output, and in the
output for -h, but neither of these are designed to be
machine-readable.
Probably yet another flag is needed since I don't like to much
to mess around in the mapset at filesystem level.
For example
-i Is map a reclassified map?
reclass=yes|no
Markus
Markus Neteler wrote:
>> r.pack is failing on reclassed maps and just packaging the reclass stuff.
>> how to deal with that?
>>
>> - either fatal error with a reasonable suggestion to the user
>> - or generate internally a map copy with r.mapcalc (slower), then package
>> ?
>
> First, is this actually a failure?Yesm in a sense that r.unpack fails on such a package.
In what way? It assumes that certain elements exist?
> In any case, there doesn't appear to be a supported programmatic
> method for determining that a map is a reclass. r.info includes
> relcass information in the default "formatted" output, and in the
> output for -h, but neither of these are designed to be
> machine-readable.Probably yet another flag is needed since I don't like to much
to mess around in the mapset at filesystem level.For example
-i Is map a reclassified map?
reclass=yes|no
For a reclass map, it should output at least the base map and
optionally the reclass table (although the latter may be a job for a
separate module, e.g. r.reclasss.out).
--
Glynn Clements <glynn@gclements.plus.com>