[GRASS-user] r.param.scale Incorrect Output

   I'm stymied trying to get output from r.param.scale that is equivalent to
the example on the bottom of the man page.

   1) GRASS 6.4.0svn (Oregon):/usr4/grassbase > g.region rast=aberDEM res=10
-ap
projection: 99 (Lambert Conformal Conic)
zone: 0
datum: nad83
ellipsoid: grs80
north: 1334420
south: 1279150
west: 769190
east: 819260
nsres: 10
ewres: 10
rows: 5527
cols: 5007
cells: 27673689

   This sets the region to the input DEM map at 10m resolution.

   2) GRASS 6.4.0svn (Oregon):/usr4/grassbase > r.param.scale in=aberDEM
out=morphology param=feature size=9 --o
  100%

   No complaints. However, when I view the results using

   3) d.mon x0
      d.rast.leg morphology

the results are shown in the attached screenshot (shrunk to keep the file
size small).

   What might cause such output?

TIA,

Rich

(attachments)

screenshot.jpg

On Thu, 28 Jan 2010, Rich Shepard wrote:

I'm stymied trying to get output from r.param.scale that is equivalent to
the example on the bottom of the man page.

   Resetting g.region to the input elevation map without any additional
options and adding a zmult factor of 5 appears to help. When the specified
param is 'features' I see what should be ridges and channels, but no peaks
or pits.

   Changing the calculated param to either elev or profc yields blank maps
when I try to display them with d.rast.

   Suggestions on how to properly apply this module will be very helpful.

Rich

On Thursday 28 January 2010, Rich Shepard wrote:

On Thu, 28 Jan 2010, Rich Shepard wrote:
> I'm stymied trying to get output from r.param.scale that is equivalent
> to the example on the bottom of the man page.

   Resetting g.region to the input elevation map without any additional
options and adding a zmult factor of 5 appears to help. When the specified
param is 'features' I see what should be ridges and channels, but no peaks
or pits.

   Changing the calculated param to either elev or profc yields blank maps
when I try to display them with d.rast.

   Suggestions on how to properly apply this module will be very helpful.

Rich
_______________________________________________

Hi,

Are you working with data in a projected coordinate system? Are you x,y and z
coordinates all in the same units. What is the general nature of the terrain
you are looking at? Try adjusting the window size to get generalized
features-- remember that the quantification of terrain is a fractal problem.

Cheers,
Dylan

--
Dylan Beaudette
Soil Resource Laboratory
http://casoilresource.lawr.ucdavis.edu/
University of California at Davis
530.754.7341

On Thu, 28 Jan 2010, Dylan Beaudette wrote:

Are you working with data in a projected coordinate system? Are you x,y
and z coordinates all in the same units. What is the general nature of the
terrain you are looking at? Try adjusting the window size to get
generalized features-- remember that the quantification of terrain is a
fractal problem.

Dylan,

   All data are Oregon Lambert Conformal Conic. x,y distances are in metres,
z in international feet. I specify the zmult of 0.3048 or the module does
this automatically.

   The drainage basin has an area about 12,000 acres. There are portions of
surrounding basins in the window, but I'm interested only in the one basin.

   The attached screenshot has the DEM, basin boundaries, streams, and other
features too small to see at the reduced scale.

Rich

(attachments)

screenshot.jpg

Rich wrote:

> I'm stymied trying to get output from
> r.param.scale that is equivalent to
> the example on the bottom of the man page.

even using the Speafish dataset?

  Resetting g.region to the input elevation map
without any additional options and adding a zmult
factor of 5 appears to help.

It may be (just guessing here) that the module assumes that the x,y
and z values are all using the same units (eg all meters or all feet).

in that case a zmult of 3.28 would get you pretty close. how reliefy
your area is probably makes a bit of a difference as well.

When the specified param is 'features' I see what should be ridges
and channels, but no peaks or pits.

should it have them? (ok, Oregon is for the most part a fairly hilly pace,
it probably should). but if you were looking at a floodplain it might not.

see feature.c and param.c in the source for the formulas used.

maybe it is artificially flat: if it isn't already try using the zscale=
option or r.mapcalc to make z match x & y scale units.

  Changing the calculated param to either elev or
profc yields blank maps
when I try to display them with d.rast.

sometimes the colors can be misleading. check with r.univar and if
needed rerun 'r.colors -e' to be sure.

Hamish

On Thu, 28 Jan 2010, Rich Shepard wrote:

I'm stymied trying to get output from r.param.scale that is equivalent to
the example on the bottom of the man page.

   Turns out it's all a matter of scale. When I zoom in to the specific area
of interest within the drainage basin the output map ('morphology') is much
better represented. Still doesn't show any peaks, saddles, or other
features, but that may be because the local topographic changes don't fall
within the algorithm's definitions.

Rich