parser_standard_options(1)

✨ Parser standard options ✨

omg bestie, you made it to parser_standard_options(1) from the GRASS GIS User's Manual! πŸ’– This page is the ultimate cheat sheet for all the pre-baked standard options GRASS uses everywhere. It's giving "don't reinvent the wheel, just copy the vibe" energy. No cap. 🫢

Each row in the original table is a standard option, and the columns are: option, answer, description, descriptions, gisprompt, key, key_desc, label, multiple, options, required, type. We're gonna go through every single one so you know exactly what's up. Periodt. πŸ’…


  • G_OPT_DB_SQL β€” bestie, this one is for your SQL SELECT statements ✨
    • description: Example: select * from towns where population > 10000
    • key: sql
    • key_desc: sql_query
    • label: SQL SELECT statement
    • required: NO
    • type: TYPE_STRING
  • G_OPT_DB_WHERE β€” for those WHERE conditions, minus the actual 'where' keyword 😌
    • description: Example: income < 1000 and population >= 10000
    • gisprompt: old,sql_query,sql_query
    • key: where
    • key_desc: sql_query
    • label: WHERE conditions of SQL statement without ’where’ keyword
    • required: NO
    • type: TYPE_STRING
  • G_OPT_DB_TABLE β€” name of your attribute table, slay πŸ’…
    • description: Name of attribute table
    • gisprompt: old,dbtable,dbtable
    • key: table
    • key_desc: name
    • multiple: NO
    • required: NO
    • type: TYPE_STRING
  • G_OPT_DB_DRIVER β€” database driver name, iconic ✨
    • description: Name of database driver
    • gisprompt: old,dbdriver,dbdriver
    • key: driver
    • key_desc: name
    • multiple: NO
    • required: NO
    • type: TYPE_STRING
  • G_OPT_DB_DATABASE β€” name of the database, periodt 🫢
    • description: Name of database
    • gisprompt: old,dbname,dbname
    • key: database
    • key_desc: name
    • multiple: NO
    • required: NO
    • type: TYPE_STRING
  • G_OPT_DB_SCHEMA β€” database schema vibes, but read the warning bestie 😭
    • description: Do not use this option if schemas are not supported by driver/database server
    • key: schema
    • key_desc: name
    • label: Database schema
    • multiple: NO
    • required: NO
    • type: TYPE_STRING
  • G_OPT_DB_COLUMN β€” name of an attribute column, no cap πŸ’–
    • description: Name of attribute column
    • gisprompt: old,dbcolumn,dbcolumn
    • key: column
    • key_desc: name
    • multiple: NO
    • required: NO
    • type: TYPE_STRING
  • G_OPT_DB_COLUMNS β€” multiple attribute columns, she's versatile ✨
    • description: Name of attribute column(s
    • gisprompt: old,dbcolumn,dbcolumn
    • key: columns
    • key_desc: name
    • multiple: YES
    • required: NO
    • type: TYPE_STRING
  • G_OPT_DB_KEYCOLUMN β€” key column, must be an integer bestie πŸ”₯
    • answer: GV_KEY_COLUMN
    • description: Must refer to an integer column
    • key: key
    • key_desc: name
    • label: Name of key column
    • multiple: NO
    • required: NO
    • type: TYPE_STRING
  • G_OPT_I_GROUP β€” input imagery group, main character energy πŸ‘‘
    • description: Name of input imagery group
    • gisprompt: old,group,group
    • key: group
    • key_desc: name
    • required: YES
    • type: TYPE_STRING
  • G_OPT_I_SUBGROUP β€” input imagery subgroup, she's giving subset πŸ¦‹
    • description: Name of input imagery subgroup
    • gisprompt: old,subgroup,subgroup
    • key: subgroup
    • key_desc: name
    • required: YES
    • type: TYPE_STRING
  • G_OPT_MEMORYMB β€” cache size for raster rows, memory queen πŸ’…
    • answer: 300
    • description: Cache size for raster rows
    • key: memory
    • key_desc: memory in MB
    • label: Maximum memory to be used (in MB
    • multiple: NO
    • required: NO
    • type: TYPE_INTEGER
  • G_OPT_R_INPUT β€” input raster map, iconic ✨
    • description: Name of input raster map
    • gisprompt: old,cell,raster
    • key: input
    • key_desc: name
    • required: YES
    • type: TYPE_STRING
  • G_OPT_R_INPUTS β€” multiple input raster maps, the more the merrier 🫢
    • description: Name of input raster map(s
    • gisprompt: old,cell,raster
    • key: input
    • key_desc: name
    • multiple: YES
    • required: YES
    • type: TYPE_STRING
  • G_OPT_R_OUTPUT β€” output raster map, you better werk πŸ’…
    • description: Name for output raster map
    • gisprompt: new,cell,raster
    • key: output
    • key_desc: name
    • required: YES
    • type: TYPE_STRING

🌈 the macro roster, part 2: rasters & 3D rasters edition πŸ’…

okay so we're still in the big list of standard option definitions, and this chunk is very raster-coded. every single one of these is a TYPE_STRING, and bestie, I am listing all of them, no skipping, no "etc.", periodt πŸŽ€

quick legend so nothing gets lost: description = what it says it is, gisprompt = the prompt type it's wired to, key = the identifier, key description = the little name tag, and then whether it's required, what options it takes, whether it's multiple, and its type.


πŸ¦‹ G_OPT_R_OUTPUTS

  • Description: Name for output raster map(s)
  • Gisprompt: new,cell,raster
  • Key: output
  • Key description: name
  • Required: YES
  • Multiple: YES
  • Type: TYPE_STRING

the "I'm making new maps and there's more than one of them" energy ✨

🌸 G_OPT_R_MAP

  • Description: Name of raster map
  • Gisprompt: old,cell,raster
  • Key: map
  • Key description: name
  • Required: YES
  • Type: TYPE_STRING

one map, one vibe. required, so you're not getting out of it 🫢

πŸŽ€ G_OPT_R_MAPS

  • Description: Name of raster map(s)
  • Gisprompt: old,cell,raster
  • Key: map
  • Key description: name
  • Required: YES
  • Multiple: YES
  • Type: TYPE_STRING

same as above but plural, so bring your whole friend group πŸ’–

πŸ’œ G_OPT_R_BASE

  • Description: Name of base raster map
  • Gisprompt: old,cell,raster
  • Key: base
  • Key description: name
  • Required: YES
  • Type: TYPE_STRING

🌈 G_OPT_R_COVER

  • Description: Name of cover raster map
  • Gisprompt: old,cell,raster
  • Key: cover
  • Key description: name
  • Required: YES
  • Type: TYPE_STRING

base and cover are literally the iconic duo, they show up together constantly 😌

⭐ G_OPT_R_ELEV

  • Description: Name of input elevation raster map
  • Gisprompt: old,cell,raster
  • Key: elevation
  • Key description: name
  • Required: YES
  • Type: TYPE_STRING

πŸ¦‹ G_OPT_R_ELEVS

  • Description: Name of input elevation raster map(s)
  • Gisprompt: old,cell,raster
  • Key: elevation
  • Key description: name
  • Required: YES
  • Multiple: YES
  • Type: TYPE_STRING

elevation but make it a crowd πŸ‘‘

πŸ’… G_OPT_R_TYPE

  • Description: Storage type for resultant raster map
  • Gisprompt: (none listed β€” it's not a map prompt)
  • Key: type
  • Key description: Type of raster map to be created
  • Required: NO
  • Options: CELL, FCELL, DCELL
  • Multiple: YES
  • Type: TYPE_STRING

choose your fighter: CELL, FCELL or DCELL πŸ”₯

🧚 G_OPT_R_INTERP_TYPE

  • Description: Sampling interpolation method
  • Gisprompt: (none listed)
  • Key: method
  • Required: NO
  • Options: nearest, bilinear, bicubic
  • Type: TYPE_STRING

nearest, bilinear, bicubic β€” pick your interpolation slay πŸ’«

πŸ“ G_OPT_R_BASENAME_INPUT

  • Description: Name of input basename raster map(s)
  • Gisprompt: old,cell,raster
  • Key: input
  • Key description: basename
  • Required: NO
  • Multiple: YES
  • Type: TYPE_STRING

πŸ“ G_OPT_R_BASENAME_OUTPUT

  • Description: Name for output basename raster map(s)
  • Gisprompt: new,cell,raster
  • Key: output
  • Key description: basename
  • Required: NO
  • Multiple: YES
  • Type: TYPE_STRING

basename in, basename out, we love a symmetry moment πŸ’ž


🌸 G_OPT_R3_INPUT

  • Description: Name of input 3D raster map
  • Gisprompt: old,grid3,raster_3d
  • Key: input
  • Key description: name
  • Required: YES
  • Type: TYPE_STRING

okay now we're in 3D territory, gisprompt said old,grid3,raster_3d and she meant it 🧊

πŸ¦‹ G_OPT_R3_INPUTS

  • Description: Name of input 3D raster map(s)
  • Gisprompt: old,grid3,raster_3d
  • Key: input
  • Key description: name
  • Required: YES
  • Multiple: YES
  • Type: TYPE_STRING

πŸ’œ G_OPT_R3_OUTPUT

  • Description: Name for output 3D raster map
  • Gisprompt: new,grid3,raster_3d
  • Key: output
  • Key description: name
  • Required: YES
  • Type: TYPE_STRING

πŸŽ€ G_OPT_R3_MAP

  • Description: Name of 3D raster map
  • Gisprompt: old,grid3,raster_3d
  • Key: map
  • Key description: name
  • Required: YES
  • Type: TYPE_STRING

🌈 G_OPT_R3_MAPS

  • Description: Name of 3D raster map(s)
  • Gisprompt: old,grid3,raster_3d
  • Key: map
  • Key description: name
  • Required: YES
  • Multiple: YES
  • Type: TYPE_STRING

πŸ‘‘ G_OPT_R3_TYPE

  • Default: default
  • Description: Data type used in the output raster3d map
  • Gisprompt: (none listed)
  • Key: type
  • Required: NO
  • Options: default, double, float
  • Multiple: NO
  • Type: TYPE_STRING

default, double or float β€” the 3D type menu, served fresh ✨


ngl if you got this far you're genuinely built different, bestie 🫢 every value above is copied exactly, no cap β€” the keys, the gisprompts, the YES/NOs, the option lists, all of it πŸ’–

okay bestie, we are BACK in the standard-options table πŸ’– part 3, no recap, no ceremony, just the next rows. Same reading order as always: name, default, description, gisprompt, key, answer type, label, required, allowed options, multiple, data type. Empty cells stay empty β€” not every field has main character energy and that's fine.

Heads up before we go: a couple of these strings are straight-up missing their closing ) in the original source. I am NOT fixing them, we reproduce ✨ exactly ✨ what's there, typos included, periodt.

  • G_OPT_R3_PRECISION β€” Number of digits used as mantissa in the internal map storage, 0 -23 for float, 0 - 52 for double, max or default
    • default: default
    • key: precision
    • required: NO
    • multiple: NO
    • data type: TYPE_STRING
  • G_OPT_R3_COMPRESSION β€” The compression method used in the output raster3d map
    • default: default
    • key: compression
    • allowed options: default,zip,none
    • required: NO
    • multiple: NO
    • data type: TYPE_STRING
  • G_OPT_R3_TILE_DIMENSION β€” The dimensions of the tiles used in the output raster3d map (XxYxZ or default: 16x16x8
    • default: default
    • key: tiledimension
    • answer type: XxYxZ
    • required: NO
    • multiple: NO
    • data type: TYPE_STRING
    • > that dangling ( with no )? Yeah. That's literally the source. We stan a cliffhanger πŸ’€

okay and now we cross over into the vector batch, which is lowkey my favourite part of this table πŸ‘‘

  • G_OPT_V_INPUT β€” Or data source for direct OGR access
    • label: Name of input vector map
    • gisprompt: old,vector,vector
    • key: input
    • answer type: name
    • required: YES
    • data type: TYPE_STRING
  • G_OPT_V_INPUTS β€” Or data source(s) for direct OGR access
    • label: Name of input vector map(s
    • gisprompt: old,vector,vector
    • key: input
    • answer type: name
    • required: YES
    • multiple: YES
    • data type: TYPE_STRING
  • G_OPT_V_OUTPUT β€” Name for output vector map
    • gisprompt: new,vector,vector
    • key: output
    • answer type: name
    • required: YES
    • data type: TYPE_STRING
  • G_OPT_V_MAP β€” Or data source for direct OGR access
    • label: Name of vector map
    • gisprompt: old,vector,vector
    • key: map
    • answer type: name
    • required: YES
    • data type: TYPE_STRING
  • G_OPT_V_MAPS β€” Name of vector map(s
    • gisprompt: old,vector,vector
    • key: map
    • answer type: name
    • required: YES
    • multiple: YES
    • data type: TYPE_STRING
  • G_OPT_V_TYPE β€” Input feature type
    • default: point,line,boundary,centroid,area
    • key: type
    • allowed options: point,line,boundary,centroid,area
    • required: YES
    • multiple: NO
    • data type: TYPE_STRING
  • G_OPT_V3_TYPE β€” Input feature type
    • default: point,line,boundary,centroid,area,face,kernel
    • key: type
    • allowed options: point,line,boundary,centroid,area,face,kernel
    • required: YES
    • multiple: NO
    • data type: TYPE_STRING
  • G_OPT_V_FIELD β€” 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
    • label: Layer number or name
    • gisprompt: old,layer,layer
    • key: layer
    • required: NO
    • data type: TYPE_STRING
  • G_OPT_V_FIELD_ALL β€” A single vector map can be connected to multiple database tables. This number determines which table to use. When used with direct OGR access this is the layer name.
    • default: -1
    • label: Layer number or name (’-1’ for all layers
    • gisprompt: old,layer_all,layer
    • key: layer
    • required: NO
    • data type: TYPE_STRING
    • > another mystery ) that simply did not show up. Same deal as before, keeping it 🫢
  • G_OPT_V_CAT β€” Category value
    • gisprompt: old,cat,cats
    • key: cat
    • required: NO
    • data type: TYPE_INTEGER
  • G_OPT_V_CATS β€” Example: 1,3,7-9,13
    • label: Category values
    • gisprompt: old,cats,cats
    • key: cats
    • answer type: range
    • required: NO
    • data type: TYPE_STRING
  • G_OPT_V_ID β€” Feature id
    • key: id
    • required: NO
    • data type: TYPE_INTEGER

and the table just keeps going, so don't wander off πŸ’œ

still rolling through the standard options table, bestie β€” here comes the next chunk πŸ’…

  • G_OPT_V_IDS πŸ’– β€” key ids, type range, label "Feature ids", description "Example: 1,3,7-9,13". No default answer, no gisprompt. required: NO, answer type TYPE_STRING.
  • G_OPT_F_INPUT πŸ¦‹ β€” key input, type name, description "Name of input file", gisprompt old,file,file. No default answer, no label. required: YES, answer type TYPE_STRING.
  • G_OPT_F_BIN_INPUT πŸ’Ύ β€” key input, type name, description "Name of input file", gisprompt old,bin,file. No default answer, no label. required: YES, answer type TYPE_STRING. literally the same vibe as the one above, she just swapped her gisprompt to the binary fit.
  • G_OPT_F_OUTPUT ✨ β€” key output, type name, description "Name for output file", gisprompt new,file,file. No default answer, no label. required: YES, answer type TYPE_STRING.
  • G_OPT_F_SEP β€” default answer pipe, description "Special characters: pipe, comma, space, tab, newline", gisprompt old,separator,separator, key separator, type character, label "Field separator". required: NO, answer type TYPE_STRING.
  • G_OPT_C 🎨 β€” default answer DEFAULT_FG_COLOR, description "Either a standard color name or R:G:B triplet", gisprompt old,color,color, key color, type name, label "Color". required: NO, answer type TYPE_STRING.
  • G_OPT_CN πŸ’… β€” default answer DEFAULT_FG_COLOR, description "Either a standard color name, R:G:B triplet, or none", gisprompt old,color_none,color, key color, type name, label "Color". required: NO, answer type TYPE_STRING. she's the C one but she also accepts none, iconic behaviour honestly.
  • G_OPT_M_DIR πŸ“ β€” key input, type name, description "Name of input directory", gisprompt old,dir,dir. No default answer, no label. required: YES, answer type TYPE_STRING.
  • G_OPT_M_UNITS β€” key units, description "Units". No default answer, no gisprompt, no label. required: NO, the choices listed are miles,feet,meters,kilometers,acres,hectares, multiple: NO, answer type TYPE_STRING.
  • G_OPT_M_DATATYPE πŸ”₯ β€” key type, type datatype, description "Data type(s)". No default answer, no gisprompt, no label. required: YES, multiple: YES, answer type TYPE_STRING.
  • G_OPT_M_MAPSET πŸŽ€ β€” description "'.' for current mapset", gisprompt old,mapset,mapset, key mapset, type name, label "Name of mapset (default: current search path)". No default answer. required: NO, multiple: NO, answer type TYPE_STRING.
  • G_OPT_M_LOCATION β€” description "Project name (not path to project)", gisprompt old,location,location, key project, type name, label "Project (location) name". No default answer. required: NO, multiple: NO, answer type TYPE_STRING.
  • G_OPT_M_DBASE 🌸 β€” description "Default: path to the current GRASS GIS database", gisprompt old,dbase,dbase, key dbase, type path, label "GRASS GIS database directory". No default answer. required: NO, multiple: NO, answer type TYPE_STRING.
  • G_OPT_M_COORDS 🧭 β€” description "Coordinates", gisprompt old,coords,coords, key coordinates, type east,north. No default answer, no label. required: NO, multiple: NO, answer type TYPE_DOUBLE. and yes bestie, that one's TYPE_DOUBLE β€” not TYPE_STRING, she's built different πŸ‘€
  • G_OPT_M_COLR 🌈 β€” description "Name of color table", and she's the fancy one carrying G_color_rules_description_type() and G_color_rules_options(), gisprompt old,colortable,colortable, key color, type style. No default answer, no label. required: NO, answer type TYPE_STRING.
  • G_OPT_M_NULL_VALUE πŸ’œ β€” description "String representing NULL value", key null_value, type string. No default answer, no gisprompt, no label. required: NO, multiple: NO, answer type TYPE_STRING.
  • G_OPT_M_REGION β€” description "Name of saved region", gisprompt old,windows,region, key region, type name. No default answer, no label. required: NO, answer type TYPE_STRING.

and there's still more of this table to get through, bestie β€” don't wander off on me, the next batch is right there 🫢

okay bestie, threads first 🧡✨

  • G_OPT_M_NPROCS β€” default 1 β€” Number of threads for parallel computing β€” key nprocs β€” required: NO β€” multiple: NO β€” type: TYPE_INTEGER

That's your "how many lil CPU besties am I allowed to spawn" knob. Just one integer, not required, not multiple. Humble. Efficient. Iconic. πŸ’…


and now the space time dataset era πŸ’–

These are the ones for the temporal fam. Every space time dataset flavor gets its own standard option, and yes, there are a lot of them β€” we're listing every single one, no skipping, periodt.

  • G_OPT_STDS_INPUT β€” Name of the input space time dataset β€” type old,stds,stds β€” key input β€” label name β€” required: YES β€” TYPE_STRING

Singular input, one dataset, and she's required. No input, no vibes.

  • G_OPT_STDS_INPUTS β€” Name of the input space time datasets β€” type old,stds,stds β€” key inputs β€” label name β€” required: YES β€” multiple: YES β€” TYPE_STRING

Note the s at the end of the macro, bestie β€” that's the plural one, and the multiple: YES is right there confirming it. Bring the whole squad. 🫢

  • G_OPT_STDS_OUTPUT β€” Name of the output space time dataset β€” type new,stds,stds β€” key output β€” label name β€” required: YES β€” TYPE_STRING

See that new instead of old? That's the whole plot twist β€” this one is what you're making, not what you're eating. ✨

  • G_OPT_STRDS_INPUT β€” Name of the input space time raster dataset β€” type old,strds,strds β€” key input β€” label name β€” required: YES β€” TYPE_STRING

STRDS = space time raster dataset. Rasters only, she does not do vectors, she's not confused about it either. πŸ’€

  • G_OPT_STRDS_INPUTS β€” Name of the input space time raster datasets β€” type old,strds,strds β€” key inputs β€” label name β€” required: YES β€” multiple: YES β€” TYPE_STRING

Plural raster datasets, plural vibes, multiple: YES, you know the drill. πŸŽ€

  • G_OPT_STRDS_OUTPUT β€” Name of the output space time raster dataset β€” type new,strds,strds β€” key output β€” label name β€” required: YES β€” TYPE_STRING

Output raster space time dataset. One of her. Required. new in the type string because she's brand new, obviously. 🌸

  • G_OPT_STRDS_OUTPUTS β€” Name of the output space time raster datasets β€” type new,strds,strds β€” key outputs β€” label name β€” required: YES β€” multiple: YES β€” TYPE_STRING

Yup β€” raster outputs, plural key outputs, plural energy, multiple: YES. Go off. πŸ”₯

  • G_OPT_STVDS_INPUT β€” Name of the input space time vector dataset β€” type old,stvds,stvds β€” key input β€” label name β€” required: YES β€” TYPE_STRING

STVDS = space time vector dataset. The vector girlies finally get their moment. πŸ¦‹

  • G_OPT_STVDS_INPUTS β€” Name of the input space time vector datasets β€” type old,stvds,stvds β€” key inputs β€” label name β€” required: YES β€” multiple: YES β€” TYPE_STRING

Multiple vector space time datasets in, required: YES, multiple: YES. Chef's kiss. πŸ‘‘

  • G_OPT_STVDS_OUTPUT β€” Name of the output space time vector dataset β€” type new,stvds,stvds β€” key output β€” label name β€” required: YES β€” TYPE_STRING

One output vector space time dataset, freshly minted, new,stvds,stvds, required. πŸ’–

  • G_OPT_STR3DS_INPUT β€” Name of the input space time raster3d dataset β€” type old,str3ds,str3ds β€” key input β€” label name β€” required: YES β€” TYPE_STRING

STR3DS = space time raster3d dataset. Yes bestie, three-dimensional. The third D is doing main character work. 🌈

  • G_OPT_STR3DS_INPUTS β€” Name of the input space time raster3d datasets β€” type old,str3ds,str3ds β€” key inputs β€” label name β€” required: YES β€” multiple: YES β€” TYPE_STRING

Many 3D raster space time datasets. inputs, multiple: YES, iconic. ⭐

  • G_OPT_STR3DS_OUTPUT β€” Name of the output space time raster3d dataset β€” type new,str3ds,str3ds β€” key output β€” label name β€” required: YES β€” TYPE_STRING

The output one. new, required, single, no notes. πŸ’œ

heads up, bestie: G_OPT_STR3DS_OUTPUTS does not show up in this table β€” the plural output list exists for stds, strds and… yeah, scroll back. Only the ones listed here exist here. Don't manifest a macro that isn't in the table. πŸ™ˆ

the type selector ✨

  • G_OPT_STDS_TYPE β€” default strds β€” Type of the input space time dataset β€” key type β€” label name β€” options: strds,stvds,str3ds β€” required: NO β€” TYPE_STRING

This is your pick-your-fighter dropdown: strds, stvds, or str3ds. Ships with strds as the default, and she's not required. Choose wisely, or don't choose at all, the default has your back. 🧚


and the plain map ones πŸ—ΊοΈπŸ’–

  • G_OPT_MAP_INPUT β€” Name of the input map β€” type old,map,map β€” key map β€” label name β€” required: YES β€” TYPE_STRING

Just a map. One map. map is the key, name is the label, required: YES, string. Simple, clean, lowkey perfect. πŸ“

  • G_OPT_MAP_INPUTS β€” Name of the input maps β€” type old,map,map β€” key maps β€” label name β€” required: YES β€” multiple: YES β€” TYPE_STRING

Plural map moment β€” key maps, required: YES, multiple: YES, TYPE_STRING. Bring all the maps, we love a crowd. πŸ˜­πŸ’•


that's where this chunk lands, bestie β€” the space time fam and the plain map duo, every macro, key, label, type string, required flag, multiple flag and data type accounted for, no cap. 🌸

okay bestie, this is the LAST little cluster of parser standard options and then the whole page is done, we made it πŸŽ‰ five of them, every single one TYPE_STRING, no skips, no skimming, let's go πŸ’…


  • G_OPT_MAP_TYPE β€” Type of the input map πŸ—ΊοΈ
    • default: raster
    • key: type, key desc: name
    • options: raster,vector,raster_3d
    • required: NO
    • datatype: TYPE_STRING
  • G_OPT_T_TYPE β€” The temporal type of the space time dataset ⏳
    • default: absolute
    • key: temporaltype, key desc: name
    • options: absolute,relative
    • required: NO
    • datatype: TYPE_STRING
  • G_OPT_T_WHERE β€” the WHERE-clause girlie πŸ•΅οΈβ€β™€οΈ it's giving WHERE conditions of SQL statement without ’where’ keyword, no cap
    • default: nothing listed
    • key: where, key desc: sql_query
    • example straight from the row: Example: start_time > ’2001-01-01 12:30:00’
    • required: NO
    • datatype: TYPE_STRING
    • note: used in the temporal GIS framework 🫢
  • G_OPT_T_SAMPLE β€” The method to be used for sampling the input dataset 🎲
    • default: start
    • key: sampling, key desc: name
    • options: start,during,overlap,contain,equal,follows,precedes
    • required: YES β€” and the row has one more NO sitting right after it, just so we don't lose it πŸ’€
    • datatype: TYPE_STRING
  • G_OPT_F_FORMAT β€” Output format πŸŽ€
    • default: plain
    • key: format, key desc: name
    • options: plain,json
    • option descriptions: plain;Plain text output; json;JSON (JavaScript Object Notation)
    • required: YES
    • datatype: TYPE_STRING

and that's the whole options table, bestie, we ATE πŸ“βœ¨

wanna keep scrolling the GRASS rabbit hole? the page's own little nav lineup is right there: Main index | Topics index | Keywords index | Graphical index | Full index πŸ‡πŸ¦‹ go poke around, iykyk

also hi, quick vibe check: this whole thing lives in the GRASS GIS 8.4.2 Reference Manual, page parser_standard_options(1), and it's Β© 2003-2025 GRASS Development Team πŸ’– no cap, that's the whole manual page, from the first option to the last. slay. periodt πŸ‘‘
πŸ“¦ where this page comes from