Opened 13 years ago
Last modified 9 years ago
#1475 new defect
v.overlay error (column names) under Windows
Reported by: | lutra | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | 6.4.6 |
Component: | Vector | Version: | svn-trunk |
Keywords: | Cc: | ||
CPU: | Unspecified | Platform: | MSWindows 7 |
Description
Attached two vectors that when used with v.overlay are causing the following error under Windows (GRASS 6.4.2RC)
v.overlay ainput=pero@filipe atype=area alayer=1 binput=priori@filipe btype=area blayer=1 output=over1 operator=or Copying vector objects from vector map ... Collecting input attributes... Copying vector objects from vector map ... DBMI-DBF driver: column name 'b_Habitat_1' truncated to 'b_Habitat_' DBMI-DBF driver: column name 'b_Habitat_12' truncated to 'b_Habitat_' Collecting input attributes... DBMI-DBF driver error: Unable to create table: 'create table over1 (cat integer , a_cat integer, a_id integer, b_cat integer, b_Habitat double precision, b_Habitat_1 double precision, b_Habitat_12 double precision, b_Habitat_13 double precision, b_Habitat_14 double precision, b_Habitat_15 double precision, b_Habitat_16 double precision, b_Habitat_17 double precision, b_Habitat_18 double precision, b_Habitats varchar(254), b_Area_ha double precision )' Finished with error
The problem seems to be the column names in one of the two vectors, that after adding the "a_" prefix and the truncating due to DBF limitations.
The error causes the creation of an unclean vector
Cannot open vector over2 in mapset filipe on level 2 (topology not available, try to rebuild topology using v.build module).
then g.remove does not have any effect when trying delete it.
Under Linux the operation do not causes the above error, but the resulting vector misses the "offending" columns.
I guess the latter is the correct behavior in these cases so GRASS under Windows should behave the same as under Linux.
Attachments (2)
Change History (4)
by , 13 years ago
by , 13 years ago
Attachment: | priori.zip added |
---|
comment:1 by , 12 years ago
comment:2 by , 9 years ago
Milestone: | 6.4.3 → 6.4.6 |
---|
For a perhaps similar problem, see #1393 (v.db.join and "duplicate column name")