Opened 10 years ago

Last modified 3 years ago

#1673 new enhancement

Automatic column name import via v.in.ascii

Reported by: jradinger Owned by: grass-dev@…
Priority: normal Milestone: 7.6.2
Component: Vector Version: unspecified
Keywords: v.in.ascii Cc:
CPU: All Platform: All

Description

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.

Change History (10)

comment:1 by martinl, 10 years ago

Component: DefaultVector
Keywords: v.in.ascii added

in reply to:  description comment:2 by neteler, 9 years ago

Milestone: 6.4.37.0.0

Replying to 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.

comment:3 by martinl, 6 years ago

Milestone: 7.0.07.0.5

comment:4 by martinl, 6 years ago

Milestone: 7.0.57.3.0

comment:5 by martinl, 6 years ago

Milestone: 7.3.07.4.0

Milestone renamed

comment:6 by neteler, 5 years ago

Milestone: 7.4.07.4.1

Ticket retargeted after milestone closed

comment:7 by neteler, 4 years ago

Milestone: 7.4.17.4.2

comment:8 by martinl, 4 years ago

Milestone: 7.4.27.6.0

All enhancement tickets should be assigned to 7.6 milestone.

comment:9 by martinl, 4 years ago

Milestone: 7.6.07.6.1

Ticket retargeted after milestone closed

comment:10 by martinl, 3 years ago

Milestone: 7.6.17.6.2

Ticket retargeted after milestone closed

Note: See TracTickets for help on using tickets.