After importing a vector map in GRASS GIS, when I try to open the table manager, I get the message that there is a “Inconsistent number of columns in the table <reptiles_east_Africa>”
I can open the same table without problems in sqlite managers such as navigat and sqlite manager.
I suspect the text in one or more of the entries contains a character that is interpreted as delimiter by the table manager. What characters are interpreted as delimiters by the table manager (so I know what to look for)? Or is there another likely reason for this problem?
On Fri, Apr 3, 2015 at 5:22 AM, Paulo van Breugel <p.vanbreugel@gmail.com>
wrote:
After importing a vector map in GRASS GIS, when I try to open the table
manager, I get the message that there is a "Inconsistent number of columns
in the table <reptiles_east_Africa>"
I can open the same table without problems in sqlite managers such as
navigat and sqlite manager.
I suspect the text in one or more of the entries contains a character that
is interpreted as delimiter by the table manager. What characters are
interpreted as delimiters by the table manager (so I know what to look
for)? Or is there another likely reason for this problem?
That's weird because the separator is composed of multiple characters (it
is string '{_sep_}'), so very unlikely to be in the data. Could you share
the data to test?
On Fri, Apr 3, 2015 at 8:34 AM, Anna Petrášová <kratochanna@gmail.com>
wrote:
On Fri, Apr 3, 2015 at 5:22 AM, Paulo van Breugel <p.vanbreugel@gmail.com>
wrote:
After importing a vector map in GRASS GIS, when I try to open the table
manager, I get the message that there is a "Inconsistent number of columns
in the table <reptiles_east_Africa>"
I can open the same table without problems in sqlite managers such as
navigat and sqlite manager.
I suspect the text in one or more of the entries contains a character
that is interpreted as delimiter by the table manager. What characters are
interpreted as delimiters by the table manager (so I know what to look
for)? Or is there another likely reason for this problem?
That's weird because the separator is composed of multiple characters (it
is string '{_sep_}'), so very unlikely to be in the data. Could you share
the data to test?
On Fri, Apr 3, 2015 at 4:42 PM, Anna Petrášová <kratochanna@gmail.com>
wrote:
On Fri, Apr 3, 2015 at 8:34 AM, Anna Petrášová <kratochanna@gmail.com>
wrote:
On Fri, Apr 3, 2015 at 5:22 AM, Paulo van Breugel <p.vanbreugel@gmail.com
> wrote:
After importing a vector map in GRASS GIS, when I try to open the table
manager, I get the message that there is a "Inconsistent number of columns
in the table <reptiles_east_Africa>"
I can open the same table without problems in sqlite managers such as
navigat and sqlite manager.
I suspect the text in one or more of the entries contains a character
that is interpreted as delimiter by the table manager. What characters are
interpreted as delimiters by the table manager (so I know what to look
for)? Or is there another likely reason for this problem?
That's weird because the separator is composed of multiple characters (it
is string '{_sep_}'), so very unlikely to be in the data. Could you share
the data to test?
On Fri, Apr 3, 2015 at 10:53 AM, Paulo van Breugel <p.vanbreugel@gmail.com>
wrote:
On Fri, Apr 3, 2015 at 4:42 PM, Anna Petrášová <kratochanna@gmail.com>
wrote:
On Fri, Apr 3, 2015 at 8:34 AM, Anna Petrášová <kratochanna@gmail.com>
wrote:
On Fri, Apr 3, 2015 at 5:22 AM, Paulo van Breugel <
p.vanbreugel@gmail.com> wrote:
After importing a vector map in GRASS GIS, when I try to open the table
manager, I get the message that there is a "Inconsistent number of columns
in the table <reptiles_east_Africa>"
I can open the same table without problems in sqlite managers such as
navigat and sqlite manager.
I suspect the text in one or more of the entries contains a character
that is interpreted as delimiter by the table manager. What characters are
interpreted as delimiters by the table manager (so I know what to look
for)? Or is there another likely reason for this problem?
That's weird because the separator is composed of multiple characters
(it is string '{_sep_}'), so very unlikely to be in the data. Could you
share the data to test?