That would be great. Let's say for example that I only want to classify
paved or dirt roads. So I setup two classes, one training area for dirt
road, and one for paved road. Then a third outlier class of everything else
that doesnt match the two inputted training classes.
It almost seems like
I have some lidar data, that has return strength or intensity values for an
infrared beam.
the lidar data points have a density to support at least a 3 foot cell size
(thanks to the results of r.in.xzy using meth=n and r.report - a great
tool!).
Because I'm working with about a 10 square mile
Hi
I am using SRTM data for my study area with elevation values ranging from 12
m to 960 m. I have set the color table to bgyr. When I tried composing a map
in ps.map using the above data with color table, it gave me the following
error message:
Your cats/ file is invalid. A cats/ file with
Mr. Rai,
First, which version of GRASS are you using? The GUI in the current GRASS
6.3.0 works with a TclTk canvas, not an x-mon (e.g., x0). If you are using
an old version of GRASS, I highly recommend that you upgrade to 6.3.
Second, if you want to interact with a display--show a map,
On Sat, May 31, 2008 at 6:23 AM, M S [EMAIL PROTECTED] wrote:
That would be great. Let's say for example that I only want to classify
paved or dirt roads. So I setup two classes, one training area for dirt
road, and one for paved road. Then a third outlier class of everything else
that
Hamish,
thank you. It's working
ramaraju
On Sat, May 31, 2008 at 8:58 PM, Hamish [EMAIL PROTECTED] wrote:
ramaraju:
I am using SRTM data for my study area with elevation
values ranging from 12 m to 960 m. I have set the color table to bgyr.
When I tried composing a map in ps.map using
On Sat, May 31, 2008 at 8:56 PM, Michael Barton [EMAIL PROTECTED] wrote:
First, which version of GRASS are you using?
GRASS6.2.2, which is default in Ubuntu Linux 8.04 (Hardy Heron).
The GUI in the current GRASS
6.3.0 works with a TclTk canvas, not an x-mon (e.g., x0). If you are using
an
This is Helena's answer:
Carlos,
first point found at a given location is preserved and any consequent
points within distance smaller than dmin are ignored (the z-values are
not taken into account). I have done some experiments with 3D distance as
well if you need to take into account the
Markus Neteler wrote:
(Hopefully) fixed in 6.4.develbranch and 7.trunk.
Do I understand correctly that the patch ignores the column if the name
already exists ? Wouldn't it be more user-friendly to rename it ?
I don't know about user-friendly, but it would be safer to just
abort
