v.db.join1grass
Joins a database table to a vector map table.
Usage
v.db.join
v.db.join --help
v.db.join map=name
[layer=string]
column=name
other_table=name
other_column=name
[subset_columns=name
[,name, ...]]
[exclude_columns=name
[,name, ...]]
[--help]
[--verbose]
[--quiet]
[--ui]
Keywords
vector, attribute table, database
Overview
v.db.join joins the content of another table into the connected attribute table of a vector map.
Notes
v.db.join is a front-end to db.execute to allow easier usage. The vector attribute table must be stored in a SQL database (SQLite, PostgreSQL, MySQL, ODBC, ...). The DBF backend is not supported. Tables can be imported with db.in.ogr.
The vector map-database connection(s) can be verified with v.db.connect.
Examples
Exercise to join North Carolina geological classes from a CSV table to the "geology" map of the North Carolina sample dataset (requires download of legend CSV file nc_geology.csv from External data for NC sample dataset):
# check original map attributesv.db.select geology column=GEO_NAME,SHAPE_area# import of CSV tabledb.in.ogr input=nc_geology.csv output=nc_geology# work on copy of geology map in current mapsetg.copy vector=geology,mygeology# check column names of vector map attributesv.info -c mygeology# check column names of legend tabledb.describe -c nc_geology# join table using key columns (map: "GEO_NAME"; table: "geol_id")v.db.join map=mygeology column=GEO_NAME other_table=nc_geology other_column=geol_id# verify result (here abbreviated)v.db.select mygeology | head -3cat|onemap_pro|PERIMETER|GEOL250_|GEOL250_ID|GEO_NAME|SHAPE_area|SHAPE_len|geol_id|longname|comment1|963738.75|4083.97998|2|1|Zml|963738.608571|4083.979839|Zml|Metagraywacke|Interlayered with metaconglomerate, ...2|22189124|26628.261719|3|2|Zmf|22189123.2296|26628.261112|Zmf|Metafelsite|Light-colored porphyritic extrusive rock...
Soil map table join
Joining the soil type explanations from table soils_legend into the Spearfish soils map (download legend):
g.copy vect=soils,mysoils# import legend tabledb.in.ogr soils_legend.csv out=soils_legend# get join column namesv.info -c mysoilsdb.describe -c soils_legend# look at original tablev.db.select mysoilscat|label1|Aab2|Ba3|Bb4|BcB5|BcC...# look at legenddb.select table=soils_legenddb.select table=soils_legend | head -7id|shortname|longname0|no data|no data0|AaB|Alice fine sandy loam, 0 to 60|Ba|Barnum silt loam0|Bb|Barnum silt loam, channeled0|BcB|Boneek silt loam, 2 to 60|BcC|Boneek silt loam, 6 to 9...# join soils_legend into mysoils attribute tablev.db.join mysoils col=label other_table=soils_legend ocol=shortname# verification of joinv.db.select mysoilscat|label|id|shortname|longname1|Aab|||2|Ba|2|Ba|Barnum silt loam3|Bb|3|Bb|Barnum silt loam, channeled4|BcB|4|BcB|Boneek silt loam, 2 to 65|BcC|5|BcC|Boneek silt loam, 6 to 9...
Source code
Available at: v.db.join source code (history)
Accessed: Monday Feb 24 17:51:45 2025
Main index | Vector index | Topics index | Keywords index | Graphical index | Full index
© 2003-2025 GRASS Development Team, GRASS GIS 8.4.1 Reference Manual
Releases
8 releases since Debian 6.0 (Squeeze); the text changed 7 times.