Hi I just updated from cvs, and some strange thing are happening with
v.to.rast (I think)
I am trying to convert to raster a xyz file I imported from a grd2xyz
conversion from GMT (as r.in.bin wasn't very happy with the GMT
grids..)
In the dialog, there are options for Raster3D and ImageGroup (as
input), which I don't understand why they are there...
So I tried in grass 6.2, but got errors about "v.to.rast can't open
old vector in level 2.." I just imported the vector, it is not old
format.. (v.in.ascii -zbt)
Carlos
--
+-----------------------------------------------------------+
Carlos Henrique Grohmann - Guano
Visiting Researcher at Kingston University London - UK
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
Hi I just updated from cvs, and some strange thing are happening with
v.to.rast (I think)
I am trying to convert to raster a xyz file I imported from a grd2xyz
conversion from GMT (as r.in.bin wasn't very happy with the GMT
grids..)
I suppose that r.in.xyz might be the tool you need.
In the dialog, there are options for Raster3D and ImageGroup (as
input), which I don't understand why they are there...
All looks OK for me in current CVS. Propably the famous 'make
distclean' before make can help you ;).
So I tried in grass 6.2, but got errors about "v.to.rast can't open
old vector in level 2.." I just imported the vector, it is not old
format.. (v.in.ascii -zbt)
This means that your vector has no topology, and this is correct,
because you've used "-b Do not build topology in points mode" flag.
The message in 6.2 is missleading though. This is fixed in 6.3. The
message would be "ERROR: Cannot open existing vector <name> on level
[2]" in 6.3.
On Mon, Sep 17, 2007 at 07:32:08PM +0200, Maciej Sieczka wrote:
> So I tried in grass 6.2, but got errors about "v.to.rast can't open
> old vector in level 2.." I just imported the vector, it is not old
> format.. (v.in.ascii -zbt)
The message in 6.2 is missleading though. This is fixed in 6.3. The
message would be "ERROR: Cannot open existing vector <name> on level
[2]" in 6.3.
Which are precisely the messages? Then we could fix it in 6.2.
Markus
------------------
ITC -> dall'1 marzo 2007 Fondazione Bruno Kessler
ITC -> since 1 March 2007 Fondazione Bruno Kessler
------------------
Markus Neteler wrote:
> On Mon, Sep 17, 2007 at 07:32:08PM +0200, Maciej Sieczka wrote:
>> The message in 6.2 is missleading though. This is fixed in 6.3. The
>> message would be "ERROR: Cannot open existing vector <name> on level
>> [2]" in 6.3.
> Which are precisely the messages? Then we could fix it in 6.2.
In 6.2 it's:
ERROR: Cannot open old vector map@mapset on level 2
In 6.3:
ERROR: Cannot open existing vector <map@mapset> on level [2]
It doesn't seem too misleading to me. Not enough to risk backporting
changes. Also, IMO the should be removed from the "on level ..." part
as the "2" is part of the sentence, it's not parenthetical.
The crux of the problem is that the various vector levels are not well
documented or known about. It's not obvious at all what "level 2" is or
means. We should work on the problem from that angle, starting with
something in the vector section of the wiki. (too technical for the
vectorintro.html page I think)
On Mon, Sep 17, 2007 at 07:32:08PM +0200, Maciej Sieczka wrote:
The message in 6.2 is missleading though. This is fixed in 6.3. The
message would be "ERROR: Cannot open existing vector <name> on level
[2]" in 6.3.
Which are precisely the messages? Then we could fix it in 6.2.
In 6.2 it's:
ERROR: Cannot open old vector map@mapset on level 2
In 6.3:
ERROR: Cannot open existing vector <map@mapset> on level [2]
It doesn't seem too misleading to me.
I'm not going to argue if to backport this, but many users will not
know how to understand "old vector", while "existing vector" is
obvious. What's "old vector"?
On Mon, Sep 17, 2007 at 07:32:08PM +0200, Maciej Sieczka wrote:
The message in 6.2 is missleading though. This is fixed in 6.3. The
message would be "ERROR: Cannot open existing vector <name> on level
[2]" in 6.3.
Which are precisely the messages? Then we could fix it in 6.2.
In 6.2 it's:
ERROR: Cannot open old vector map@mapset on level 2
In 6.3:
ERROR: Cannot open existing vector <map@mapset> on level [2]
It doesn't seem too misleading to me. Not enough to risk backporting
changes.
Hamish: where is a risk to change a message?
Also, IMO the should be removed from the "on level ..." part
as the "2" is part of the sentence, it's not parenthetical.
The crux of the problem is that the various vector levels are not well
documented or known about. It's not obvious at all what "level 2" is or
means. We should work on the problem from that angle, starting with
something in the vector section of the wiki. (too technical for the
vectorintro.html page I think)