I was importing some ascii files with gravity data, using r.in.xyz.
Since the resolution I was using was the same as the spacing between
the data points, I could use any of the stats in r.in.xyz, the result
would be the same. Then I was thinking that, maybe just to avoid
possible confusions, that the option "value" could be added.
Carlos
--
+-----------------------------------------------------------+
Carlos Henrique Grohmann - Guano
Geologist M.Sc - Doctorate Student at IGc-USP - Brazil
Linux User #89721 - carlos dot grohmann at gmail dot com
+-----------------------------------------------------------+
_________________
"Good morning, doctors. I have taken the liberty of removing Windows
95 from my hard drive."
--The winning entry in a "What were HAL's first words" contest judged
by 2001: A SPACE ODYSSEY creator Arthur C. Clarke
I was importing some ascii files with gravity data, using r.in.xyz.
Since the resolution I was using was the same as the spacing between
the data points, I could use any of the stats in r.in.xyz, the result
would be the same. Then I was thinking that, maybe just to avoid
possible confusions, that the option "value" could be added.
just use mean and make a "n" count map then run r.univar to check that
the count map is all "1"s.
If there was a value option, it should be "most recent value". If the
data file has more that one point in the same cell, the later point
overwrites the earlier one. It's possible to add that, but I'm not sure
if it is really needed. Can you think of a real-world example where
last-known value is wanted over mean? (or other stat)
A higher priority for me it letting r.in.xyz read a data stream from
stdin. Need for "most recent value" makes a little more sense to me
then.