db.out.ogr(1grass)
π db.out.ogr β the GRASS manual but make it cute β¨
okay bestie, welcome to db.out.ogr(1grass), the GRASS User's Manual page that's about to walk you through yeeting your attribute tables out into literally any format you want π
πΈ NAME πΈ
db.out.ogr β Exports attribute tables into various formats. no cap.
π KEYWORDS π
database, export, output, attribute table β¨
π SYNOPSIS π
db.out.ogr
db.out.ogr --help
db.out.ogr input=name output=name [layer=string] format=string
[table=name] [--overwrite] [--help] [--verbose] [--quiet] [--ui]
π© Flags (the little toggles, she's giving options energy)
--overwriteβ Allow output files to overwrite existing files. she will literally just bulldoze whatever's already there, so be careful bestie π--helpβ Print usage summary. your girl explains herself π--verboseβ Verbose module output. so. much. talking.--quietβ Quiet module output. no thoughts head empty π€«--uiβ Force launching GUI dialog. buttons!! clicking!! π¦
π Parameters (the actual arguments, the main characters)
input=name[required] β GRASS table name. Or data source for direct OGR access. either or, she's flexible π«Άoutput=name[required] β Output table file name or DB connection string. like, tell her where it's going.layer=stringβ Layer number or name. Vector features can have category values in different layers. This number determines which layer to use. When used with direct OGR access this is the layer name. Default:1π§format=string[required] β Table format. Options:CSV,DBF,GML,MySQL,PostgreSQL,SQLite. Default:CSVβtable=nameβ Name for output table (default: input name). if you don't say anything she just copies the input's name, iconic
π« DESCRIPTION π«
db.out.ogr exports GRASS attribute tables into various formats as supported by the OGR driver on the local system (CSV, DBF, PostgreSQL, SQLite, MySQL, ODBC, etc.). okay so it's giving versatility, it's giving range π
The output parameter is used to define the output file name (if the path is not defined, the module will attempt to write to the current directory). In case of a database connection as output, the connection string has to be specified. yes queen, spell it out for her π
The layer parameter is needed if the attribute table to be exported is linked as non-default layer to a vector map. lowkey important, don't skip it π
β¨ EXAMPLES β¨
Export of GRASS attribute table to a CSV table file (default format)
db.out.ogr input=precip_30ynormals output=precip_30ynormals.csv
Export of a GRASS attribute table to a DBF table
db.out.ogr input=precip_30ynormals output=precip_30ynormals.dbf format=DBF
Export of GRASS attribute table into a PostgreSQL table
db.out.ogr input=precip_30ynormals \
output="PG:host=localhost dbname=meteo user=neteler" \
format=PostgreSQL
# verify
echo "SELECT * FROM precip_30ynormals" | psql meteo
look at her go, ate that fr fr π₯
π SEE ALSO π
db.tables- GRASS SQL interface
π AUTHORS π
- Markus Neteler
- Converted to Python by Glynn Clements
π οΈ SOURCE CODE π οΈ
Available at: db.out.ogr source code (history)
Latest change: Tuesday Oct 21 09:57:14 2025 in commit: fb0165c2d021b7700528aca09c224847be871729
Main index | Database index | Topics index | Keywords index | Graphical index | Full index
Β© 2003-2026 GRASS Development Team, GRASS 8.5.0 Reference Manual
and that's the whole page bestie π this was GRASS 8.5.0, db.out.ogr(1grass), and she served. go export something gorgeous πΈπ¦π
π¦ where this page comes from
- alpine 3.24: grass-gis-doc 8.5.0-r1 Β· GPL-2.0-or-later
- ubuntu stonking: grass-doc 8.5.0-1ubuntu1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms