"v.in.ogr converts '.', '-' and '#' to '_' (underscore) during import. The
-w flag changes capital column names to lowercase characters as a
convenience for SQL usage (lowercase column names avoid the need to quote
them if the attribute table is stored in a SQL DBMS such as PostgreSQL). The
cnames parameter is used to define new column names during import.
The DBF database specification limits column names to 10 characters. If the
default DB is set to DBF and the input data contains longer column/field
names, they will be truncated. If this results in multiple columns with the
same name then v.in.ogr will produce an error. In this case you will either
have to modify the input data or use v.in.ogr's cnames parameter to rename
columns to something unique. (hint: copy and modify the list given with the
error message). Alternatively, change the local DB with db.connect. "
"v.in.ogr converts ‘.’, ‘-’ and ‘#’ to ‘_’ (underscore) during import. The
-w flag changes capital column names to lowercase characters as a
convenience for SQL usage (lowercase column names avoid the need to quote
them if the attribute table is stored in a SQL DBMS such as PostgreSQL). The
cnames parameter is used to define new column names during import.
The DBF database specification limits column names to 10 characters. If the
default DB is set to DBF and the input data contains longer column/field
names, they will be truncated. If this results in multiple columns with the
same name then v.in.ogr will produce an error. In this case you will either
have to modify the input data or use v.in.ogr’s cnames parameter to rename
columns to something unique. (hint: copy and modify the list given with the
error message). Alternatively, change the local DB with db.connect. "
"v.in.ogr converts '.', '-' and '#' to '_' (underscore) during import.
The
-w flag changes capital column names to lowercase characters as a
convenience for SQL usage (lowercase column names avoid the need to quote
them if the attribute table is stored in a SQL DBMS such as PostgreSQL).
The
cnames parameter is used to define new column names during import.
The DBF database specification limits column names to 10 characters. If
the
default DB is set to DBF and the input data contains longer column/field
names, they will be truncated. If this results in multiple columns with
the
same name then v.in.ogr will produce an error. In this case you will
either
have to modify the input data or use v.in.ogr's cnames parameter to rename
columns to something unique. (hint: copy and modify the list given with
the
error message). Alternatively, change the local DB with db.connect. "
am I right that the manual should be changed?
-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.
nabble.com/v-in-ogr-cnames-vs-columns-tp5332012.html
Sent from the Grass - Dev mailing list archive at Nabble.com.
_______________________________________________
grass-dev mailing list