Quick Navigator

Search Site

Unix VPS
A - Starter
B - Basic
C - Preferred
D - Commercial
MPS - Dedicated
Previous VPSs
* Sign Up! *

Contact Us
Online Help
Domain Status
Man Pages

Virtual Servers

Topology Map

Server Agreement
Year 2038

USA Flag



Man Pages
v.db.addtable(1) Grass User's Manual v.db.addtable(1)

v.db.addtable - Creates and connects a new attribute table to a given layer of an existing vector map.

vector, attribute table, database

v.db.addtable --help
v.db.addtable map=name [table=string] [layer= integer] [key=name] [columns=name type[, name type,...]] [--help] [--verbose] [--quiet] [--ui]

Print usage summary
Verbose module output
Quiet module output
Force launching GUI dialog

map=name [required]
Name of vector map
Or data source for direct OGR access
Name of new attribute table (default: vector map name)
Layer number where to add new attribute table
Default: 1
Name of key column
Must refer to an integer column
Default: cat
columns=name type[,name type,...]
Name and type of the new column(s) (’name type [,name type, ...]’)
Types depend on database backend, but all support VARCHAR(), INT, DOUBLE PRECISION and DATE. Example: ’label varchar(250), value integer’

v.db.addtable creates and adds a new attribute table to a given vector map. It links the table to the specified layer of the vector map. If the vector map is not yet linked to any table, new a database link is established based on the MAPSET database settings (see db.connect).

v.db.addtable is a front-end to db.execute to allow easier usage.
v.db.addtable will only insert category values into the table for those features which actually have a category value in the relevant layer. The user can add category values automatically by using v.category or manually with wxGUI vector digitizer before running v.db.addtable. Or one can run v.db.addtable first and then use either a combinatino of v.category + or wxGUI vector digitizer to add the relevant lines to the table.
The supported types of columns depend on the database backend. However, all backends should support VARCHAR, INT, DOUBLE PRECISION and DATE.
The existing database connection(s) can be verified with v.db.connect.

Adding a new attribute table with a single column to default layer 1:
g.copy vect=roadsmajor,myroads
v.db.addtable myroads columns="slope double precision"
v.db.connect -p myroads -c myroads
Adding a new attribute table with two columns to layer 2:
g.copy vect=roadsmajor,myroads
v.db.addtable myroads columns="slope double precision, roadname varchar(15)" layer=2
v.db.connect -p myroads -c myroads -c myroads layer=2

db.connect, db.droptable, db.execute, v.db.addtable, v.db.connect, v.db.dropcolumn, v.db.droptable,, v.db.update
GRASS SQL interface

Markus Neteler
Last changed: $Date: 2018-06-16 10:47:21 +0200 (Sat, 16 Jun 2018) $

Available at: v.db.addtable source code (history)
Main index | Vector index | Topics index | Keywords index | Graphical index | Full index
© 2003-2018 GRASS Development Team, GRASS GIS 7.4.3 Reference Manual
GRASS 7.4.3

Search for    or go to Top of page |  Section 1 |  Main Index

Powered by GSP Visit the GSP FreeBSD Man Page Interface.
Output converted with ManDoc.