Anna wrote:
This doesn't seem related. I explained the problem in the
mail above but I can try to explain it more clearly if needed.
sorry, I reread you post and it was clear enough. the confusion
was all mine.
Here is the ticket:
http://trac.osgeo.org/grass/ticket/1633
it seems a bit
Hi,
does this have to do with parsing the vector/$MAP/dbln file?
There was an unfortunate thing in the 6.x format spec of that file where
space was used as the delimiter and it was impossible to fix for spaces
in the path, since the result would always be ambiguous. In GRASS 7 I
changed the
Hi,
On Sun, Sep 9, 2012 at 1:15 PM, Hamish hamis...@yahoo.com wrote:
Hi,
does this have to do with parsing the vector/$MAP/dbln file?
There was an unfortunate thing in the 6.x format spec of that file where
space was used as the delimiter and it was impossible to fix for spaces
in the
On Tue, Sep 4, 2012 at 2:01 PM, Anna Kratochvílová
kratocha...@gmail.com wrote:
...
Problem occurs when calling this (line 194, dbmgr/manager.py in grass64)
...
I recently added the fs parameter to be able to open data which
contain | character by changing the separator in preferences. On
Hi,
when loading roadsmajor of NC on various windows machines (with
and without white space in the grassdata path, we get
Error:
'columns' is not recognized as an internal or external command,
operable program or batch file
[OK]
Then the attrib. manager opens but it remains empty.
Maybe here?
On Tue, Sep 4, 2012 at 11:04 AM, Markus Neteler nete...@osgeo.org wrote:
Hi,
when loading roadsmajor of NC on various windows machines (with
and without white space in the grassdata path, we get
Error:
'columns' is not recognized as an internal or external command,
operable program or
