search

landam / grass-gis-git-migration-test

0 stars 0 forks source link

Automatic column name import via v.in.ascii #69

Open landam opened 5 years ago

landam commented 5 years ago

Reported by jradinger on 9 Jun 2012 08:05 UTC According to M. Metz the module v.in.ascii can already automatically detect the column type during import. It would be nice to have also the option to read/import the column names from the import files from line X, e.g. names=1 to read column names from line 1.

Migrated-From: https://trac.osgeo.org/grass/ticket/1673

landam commented 5 years ago

Modified by @landam on 9 Jun 2012 10:00 UTC

landam commented 5 years ago

Comment by neteler on 12 Jan 2014 22:15 UTC Replying to [ticket:1673 jradinger]:

According to M. Metz the module v.in.ascii can already automatically detect the column type during import. It would be nice to have also the option to read/import the column names from the import files from line X, e.g. names=1 to read column names from line 1.

This requires to do name column names "laundery" in order to avoid incompatible names (e.g. white space, strange chars etc).

Perhaps the "cnames=" polishing code from v.in.ogr could be of use.

landam commented 5 years ago

Modified by @landam on 12 May 2016 06:42 UTC

landam commented 5 years ago

Modified by @landam on 25 Aug 2016 15:51 UTC

landam commented 5 years ago

Comment by @landam on 27 Aug 2016 13:42 UTC Milestone renamed

landam commented 5 years ago

Comment by neteler on 26 Jan 2018 11:40 UTC Ticket retargeted after milestone closed

landam commented 5 years ago

Modified by neteler on 12 Jun 2018 20:48 UTC

landam commented 5 years ago

Comment by @landam on 25 Sep 2018 16:51 UTC All enhancement tickets should be assigned to 7.6 milestone.

landam commented 5 years ago

Comment by @landam on 25 Jan 2019 21:07 UTC Ticket retargeted after milestone closed