[GRASS5] v.what and r.what

GRASS GIS GRASS GIS developer
1

As mentioned by Michael, I trimmed code from d.what.vect to
create v.what as part of the new gis.m. Right now its output
format is just like the shell script option for d.what.vect.
However when I wrote it it didn't look at r.what before hand
and added input of east and north as separate parameters,
but r.what takes them as a pair. Also the r.what output is
column like separated by vertical bars, where v.what has
each attribute on its on line with the field name and its
value.

I intend to add an option to r.what to provide the same kind
of output as v.what, but since it is desirable to have the
commands similar should I modify v.what to take a coordinate
pair or modify r.what to take coordinate input as two
parameters. Michael prefers the separate parameters and I
prefer it to, but I don't want to break anything, so I'm
asking for advice before I do anything.

Thanks

T
--
Trevor Wiens
twiens@interbaun.com

2

On ¶ro, 2006-01-18 at 07:55 -0700, twiens wrote:

<> snip

Also the r.what output is
column like separated by vertical bars, where v.what has
each attribute on its on line with the field name and its
value.

Could you post an example?

I intend to add an option to r.what to provide the same kind
of output as v.what, but since it is desirable to have the
commands similar should I modify v.what to take a coordinate
pair or modify r.what to take coordinate input as two
parameters. Michael prefers the separate parameters and I
prefer it to,

Why would separate parameters be better?

Best,
Maciek

--------------------
Szukasz do¶wiadczonej firmy poligraficznej? Zale¿y Ci na terminowo¶ci i atrakcyjnych cenach?
Zapraszamy do nas!
http://www.foldruk.pl/

3

twiens wrote:

I intend to add an option to r.what to provide the same kind
of output as v.what, but since it is desirable to have the
commands similar should I modify v.what to take a coordinate
pair or modify r.what to take coordinate input as two
parameters.

Modify v.what to match r.what. r.what has been around for a while, so
you need to maintain compatibility, whereas v.what is new.

--
Glynn Clements <glynn@gclements.plus.com>