v.in.db: add v.in.ogr-like "-t" option

[grasslandtom]

An option to v.in.db that allows importing points without creating an attribute table from the original table would be useful to avoid copying of (especially large) tables when attributes are either not needed in GRASS or the original table will be connected to the resulting vector.

[hamish]

v.db.select | v.in.ascii -t

?

the whole point of v.to.db is to add stuff to a table.

Hamish

[grasslandtom]

Oops! I see, I should have asked on the mailinglist before filing this.

Nevertheless: what I meant was something like

#import vector from table without copying the table:
v.in.db -t sometable x=x_col y=y_col cat=id_col out=somevector
# connect to original table
v.db.connect somevector table=sometable key=id_col

But this could be mimicked by

db.select sometable sql='select x_col,y_col,id_col from sometable' | v.in.ascii -t cat=3 out=somevector
v.db.connect somevector table=sometable key=id_col

Thus I set this to resolved as invalid.

Thanks for the hint with the pipe! Sorry for being to quick asking here.

Tom

[neteler]

Tom, please consider to make this a FAQ entry at ​http://grass.osgeo.org/wiki/Category:FAQ

Markus

[grasslandtom]

For the sake of completeness: I missed the c-flag for db.select (or as an alternative skip=1 for v.in.ascii).

I will add the whole thing to the FAQ later.

[grasslandtom]

Thinking about a useful title for a FAQ-entry, I came to the conclusion that it might be better to add this as an example to the man-page of v.in.db. Though v.in.db is not used in the example, as a user I would search that man-page for a solution to the initialy described problem: "Import coordinates from table and use original table for attributes".

Any thoughts on this?