I’m running v.digit in Windows and, after I draw my boundaries in TclTk’s digitizer, when I close I get this warning in v.digit command output tab:
Unable to read vector map
But my vectorial is created without problems. Why is tbhis printed? And how can I avoid it?
This was a matter discussed in the past (http://trac.osgeo.org/grass/ticket/917).
I’m still obtaining the same message. I’m willing to eliminate this warning. From which function is it printed because, I have searched in V.digit and nothing was gfound
Thanks
luisa
I’m running v.digit in Windows and, after I draw my boundaries in TclTk’s digitizer, when I close I get this warning in v.digit command output tab:
Unable to read vector map
But my vectorial is created without problems. Why is tbhis printed? And how can I avoid it?
Hello,
eliminating this warning is not an easy task. As far I can see,
v.digit running under Linux does NOT call v.build for two times, still
it does for windows. Unless somebody running WinGRASS decides to spend
some time by recompiling and testing v.digit to see the cause of
double v.build processing, there's nothing we can do.
Only proper solution for You, is to use any normal operating system (GNU/Linux).
Guess: Issue could be related to tk . <Destory> binding. On Linux it
doesn't fire on Exit from application, still I have no idea if on
Windows it works in different way.
Maris.
2010/11/17, Luisa Peña <luisapena1979@gmail.com>:
This was a matter discussed in the past ( http://trac.osgeo.org/grass/ticket/917).
I'm still obtaining the same message. I'm willing to eliminate this warning.
>From which function is it printed because, I have searched in V.digit and
nothing was gfound
Thanks
luisa
2010/8/3 Luisa Peña <luisapena1979@gmail.com>
I'm running v.digit in Windows and, after I draw my boundaries in TclTk's
digitizer, when I close I get this warning in v.digit command output tab:
Unable to read vector map
But my vectorial is created without problems. Why is tbhis printed? And
how
can I avoid it?
Hello,
eliminating this warning is not an easy task. As far I can see,
v.digit running under Linux does NOT call v.build for two times, still
it does for windows. Unless somebody running WinGRASS decides to spend
some time by recompiling and testing v.digit to see the cause of
double v.build processing, there's nothing we can do.
Only proper solution for You, is to use any normal operating system (GNU/Linux).
The warning seems to be harmless because topology has been
successfully built in the first attempt and the vector map closed. The
second attempt to build topology fails because the vector map has been
closed. The warning is IMHO annoying but can be ignored (so far).
Markus M
Guess: Issue could be related to tk . <Destory> binding. On Linux it
doesn't fire on Exit from application, still I have no idea if on
Windows it works in different way.
Maris.
2010/11/17, Luisa Peña <luisapena1979@gmail.com>:
This was a matter discussed in the past ( http://trac.osgeo.org/grass/ticket/917).
I'm still obtaining the same message. I'm willing to eliminate this warning.
>From which function is it printed because, I have searched in V.digit and
nothing was gfound
Thanks
luisa
2010/8/3 Luisa Peña <luisapena1979@gmail.com>
I'm running v.digit in Windows and, after I draw my boundaries in TclTk's
digitizer, when I close I get this warning in v.digit command output tab:
Unable to read vector map
But my vectorial is created without problems. Why is tbhis printed? And
how
can I avoid it?