JoinDB: FUSION R command line interface - Combines columns from two...

View source: R/JoinDB.R

JoinDBR Documentation

FUSION R command line interface – Combines columns from two data files into a single data file.

Description

JoinDB creates command lines for the FUSION JoinDB program and optionally executes them.

Usage

JoinDB(
  basefile = NULL,
  basefield = NULL,
  addfile = NULL,
  addfield = NULL,
  startfield = NULL,
  outputfile = NULL,
  quiet = FALSE,
  verbose = FALSE,
  version = FALSE,
  newlog = FALSE,
  log = NULL,
  locale = FALSE,
  noheader = FALSE,
  runCmd = TRUE,
  saveCmd = TRUE,
  cmdFile = NULL,
  cmdClear = FALSE,
  echoCmd = FALSE,
  comment = NULL
)

Arguments

basefile

character (required): Primary data file in CSV format.

basefield

numeric: Field in basefile that will be matched to records in addfile.

addfile

character: Secondary data file in CSV format.

addfield

numeric: Field in addfile that will be matched to records in basefile.

startfield

numeric: Starting field in addfile. All fields (columns) starting with the startfield will be added to records in the outputfile.

outputfile

character: Name for the new data file. The extension specifies the desired format (.csv). outputfile can be the same as basefile. outputfile cannot be the same as addfile.

quiet

boolean: Suppress all output during the run.

verbose

boolean: Display all status information during the run.

version

boolean: Report version information and exit with no processing.

newlog

boolean: Erase the existing log file and start a new log

log

character: Use the name specified for the log file.

locale

boolean: Adjust program logic to input and output locale-specific numeric formats (e.g. use a comma for the decimal separator).

noheader

boolean: Treat the first line of the basefile and addfile as data. Default behavior assumes the first line of each file contains column names. Valid for CSV format files only.

runCmd

boolean: indicates command line should be executed.

saveCmd

boolean: indicates command line should be written to a file.

cmdFile

character: contains the name of the file to which commands should be written.

cmdClear

boolean: indicates file for commands should be deleted (cleared) before the command line is written.

echoCmd

boolean: indicates command line should be displayed.

comment

character string containing comment to be written to command file before writing the actual command. Only used when runCmd = FALSE and saveCmd = TRUE. When written, there is always a blank line before the comment line in the command file.

Value

Return value depends on runCmd. if runCmd = TRUE, return value is the (invisible) integer value return from the operating system after running the command. if runCmd = FALSE, return value is the (invisible) command line.

Multiple Commands

LTKFunctions generate a separate command for each item when the required parameters are lists. This is useful when you want to use the same command and options but different input data and output files. However, this works only when the switches and options are the same for all commands (not lists). If you try to use a list of switches and/or options and a list of input files, you will produce commands using all sets of switches and/or options for every input file.

See Also

Other LTKFunctions: CSV2Grid(), CanopyMaxima(), CanopyModel(), Catalog(), ClipDTM(), ClipData(), CloudMetrics(), Cover(), DTMDescribe(), DensityMetrics(), FilterData(), FirstLastReturn(), GridMetrics(), GridSample(), GridSurfaceCreate(), GridSurfaceStats(), GroundFilter(), IntensityImage(), MergeDTM(), MergeData(), MergeRaster(), RepairGridDTM(), ReturnDensity(), SplitDTM(), SurfaceSample(), SurfaceStats(), TINSurfaceCreate(), ThinData(), TopoMetrics(), TreeSeg(), fusionwrapr-package

Examples

## Not run: 
JoinDB("attribs.csv", 4, "base.csv", 1, 2, "new.csv")

## End(Not run)

bmcgaughey1/fusionwrapr documentation built on Dec. 1, 2024, 7:13 a.m.