neulab/tldr huggingface dataset:
is_not_null (class=typing #args=1): False if argument is null (empty or absent), true otherwise.
is_null (class=typing #args=1): True if argument is null (empty or absent), false otherwise.
is_numeric (class=typing #args=1): True if field is present with value inferred to be int or float
is_present (class=typing #args=1): True if field is present in input, false otherwise.
is_string (class=typing #args=1): True if field is present with string (including empty-string) value
asserting_absent (class=typing #args=1): Returns argument if it is absent in the input data, else throws an error.
asserting_bool (class=typing #args=1): Returns argument if it is present with boolean value, else throws an error.
asserting_boolean (class=typing #args=1): Returns argument if it is present with boolean value, else throws an error.
asserting_empty (class=typing #args=1): Returns argument if it is present in input with empty value, else throws an error.
asserting_empty_map (class=typing #args=1): Returns argument if it is a map with empty value, else throws an error.
asserting_float (class=typing #args=1): Returns argument if it is present with float value, else throws an error.
asserting_int (class=typing #args=1): Returns argument if it is present with int value, else throws an error.
asserting_map (class=typing #args=1): Returns argument if it is a map, else throws an error.
asserting_nonempty_map (class=typing #args=1): Returns argument if it is a non-empty map, else throws an error.
asserting_not_empty (class=typing #args=1): Returns argument if it is present in input with non-empty value, else throws an error.
asserting_not_map (class=typing #args=1): Returns argument if it is not a map, else throws an error.
asserting_not_null (class=typing #args=1): Returns argument if it is non-null (non-empty and non-absent), else throws an error.
asserting_null (class=typing #args=1): Returns argument if it is null (empty or absent), else throws an error.
asserting_numeric (class=typing #args=1): Returns argument if it is present with int or float value, else throws an error.
asserting_present (class=typing #args=1): Returns argument if it is present in input, else throws an error.
asserting_string (class=typing #args=1): Returns argument if it is present with string (including empty-string) value, else throws an error.
boolean (class=conversion #args=1): Convert int/float/bool/string to boolean.
float (class=conversion #args=1): Convert int/float/bool/string to float.
fmtnum (class=conversion #args=2): Convert int/float/bool to string using printf-style format string, e.g. '$s = fmtnum($n, "%06lld")'. WARNING: Miller numbers are all long long or double. If you use formats like %d or %f, behavior is undefined.
hexfmt (class=conversion #args=1): Convert int to string, e.g. 255 to "0xff".
int (class=conversion #args=1): Convert int/float/bool/string to int.
string (class=conversion #args=1): Convert int/float/bool/string to string.
typeof (class=conversion #args=1): Convert argument to type of argument (e.g. MT_STRING). For debug.
depth (class=maps #args=1): Prints maximum depth of hashmap: ''. Scalars have depth 0.
haskey (class=maps #args=2): True/false if map has/hasn't key, e.g. 'haskey($*, "a")' or ’haskey(mymap, mykey)'. Error if 1st argument is not a map.
joink (class=maps #args=2): Makes string from map keys. E.g. 'joink($*, ",")'.
joinkv (class=maps #args=3): Makes string from map key-value pairs. E.g. 'joinkv(@v[2], "=", ",")'
joinv (class=maps #args=2): Makes string from map values. E.g. 'joinv(mymap, ",")'.
leafcount (class=maps #args=1): Counts total number of terminal values in hashmap. For single-level maps, same as length.
length (class=maps #args=1): Counts number of top-level entries in hashmap. Scalars have length 1.
mapdiff (class=maps variadic): With 0 args, returns empty map. With 1 arg, returns copy of arg. With 2 or more, returns copy of arg 1 with all keys from any of remaining argument maps removed.
mapexcept (class=maps variadic): Returns a map with keys from remaining arguments, if any, unset. E.g. 'mapexcept({1:2,3:4,5:6}, 1, 5, 7)' is '{3:4}'.
mapselect (class=maps variadic): Returns a map with only keys from remaining arguments set. E.g. 'mapselect({1:2,3:4,5:6}, 1, 5, 7)' is '{1:2,5:6}'.
mapsum (class=maps variadic): With 0 args, returns empty map. With >= 1 arg, returns a map with key-value pairs from all arguments. Rightmost collisions win, e.g. 'mapsum({1:2,3:4},{1:5})' is '{1:5,3:4}'.
splitkv (class=maps #args=3): Splits string by separators into map with type inference. E.g. 'splitkv("a=1,b=2,c=3", "=", ",")' gives '{"a" : 1, "b" : 2, "c" : 3}'.
splitkvx (class=maps #args=3): Splits string by separators into map without type inference (keys and values are strings). E.g. 'splitkv("a=1,b=2,c=3", "=", ",")' gives ’{"a" : "1", "b" : "2", "c" : "3"}'.
splitnv (class=maps #args=2): Splits string by separator into integer-indexed map with type inference. E.g. 'splitnv("a,b,c" , ",")' gives '{1 : "a", 2 : "b", 3 : "c"}'.
splitnvx (class=maps #args=2): Splits string by separator into integer-indexed map without type inference (values are strings). E.g. 'splitnv("4,5,6" , ",")' gives '{1 : "4", 2 : "5", 3 : "6"}'.
all all: used in "emit", "emitp", and "unset" as a synonym for @*
begin begin: defines a block of statements to be executed before input records are ingested. The body statements must be wrapped in curly braces. Example: 'begin { @count = 0 }'
bool bool: declares a boolean local variable in the current curly-braced scope. Type-checking happens at assignment: 'bool b = 1' is an error.
break break: causes execution to continue after the body of the current for/while/do-while loop.
call call: used for invoking a user-defined subroutine. Example: 'subr s(k,v) { print k . " is " . v} call s("a", $a)'
continue continue: causes execution to skip the remaining statements in the body of the current for/while/do-while loop. For-loop increments are still applied.
do do: with "while", introduces a do-while loop. The body statements must be wrapped in curly braces.
dump dump: prints all currently defined out-of-stream variables immediately to stdout as JSON.
With >, >>, or |, the data do not become part of the output record stream but are instead redirected.
The > and >> are for write and append, as in the shell, but (as with awk) the file-overwrite for > is on first write, not per record. The | is for piping to a process which will process the data. There will be one open file for each distinct file name (for > and >>) or one subordinate process for each distinct value of the piped-to command (for |). Output-formatting flags are taken from the main command line.
Example: mlr --from f.dat put -q '@v[NR]=$*; end { dump }' Example: mlr --from f.dat put -q '@v[NR]=$*; end { dump >  "mytap.dat"}' Example: mlr --from f.dat put -q '@v[NR]=$*; end { dump >> "mytap.dat"}' Example: mlr --from f.dat put -q '@v[NR]=$*; end { dump | "jq .[]"}'
edump edump: prints all currently defined out-of-stream variables immediately to stderr as JSON.
Example: mlr --from f.dat put -q '@v[NR]=$*; end { edump }'
elif elif: the way Miller spells "else if". The body statements must be wrapped in curly braces.
else else: terminates an if/elif/elif chain. The body statements must be wrapped in curly braces.
emit emit: inserts an out-of-stream variable into the output record stream. Hashmap indices present in the data but not slotted by emit arguments are not output.
You can use any of the output-format command-line flags, e.g. --ocsv, --ofs, etc., to control the format of the output if the output is redirected. See also mlr -h.
Example: mlr --from f.dat put 'emit >  "/tmp/data-".$a, $*' Example: mlr --from f.dat put 'emit >  "/tmp/data-".$a, mapexcept($*, "a")' Example: mlr --from f.dat put '@sums[$a][$b]+=$x; emit @sums' Example: mlr --from f.dat put --ojson '@sums[$a][$b]+=$x; emit > "tap-".$a.$b.".dat", @sums' Example: mlr --from f.dat put '@sums[$a][$b]+=$x; emit @sums, "index1", "index2"' Example: mlr --from f.dat put '@sums[$a][$b]+=$x; emit @*, "index1", "index2"' Example: mlr --from f.dat put '@sums[$a][$b]+=$x; emit >  "mytap.dat", @*, "index1", "index2"' Example: mlr --from f.dat put '@sums[$a][$b]+=$x; emit >> "mytap.dat", @*, "index1", "index2"' Example: mlr --from f.dat put '@sums[$a][$b]+=$x; emit | "gzip > mytap.dat.gz", @*, "index1", "index2"' Example: mlr --from f.dat put '@sums[$a][$b]+=$x; emit > stderr, @*, "index1", "index2"' Example: mlr --from f.dat put '@sums[$a][$b]+=$x; emit | "grep somepattern", @*, "index1", "index2"'
Please see http://johnkerl.org/miller/doc for more information.
emitf emitf: inserts non-indexed out-of-stream variable(s) side-by-side into the output record stream.
Example: mlr --from f.dat put '@a=$i;@b+=$x;@c+=$y; emitf @a' Example: mlr --from f.dat put --oxtab '@a=$i;@b+=$x;@c+=$y; emitf > "tap-".$i.".dat", @a' Example: mlr --from f.dat put '@a=$i;@b+=$x;@c+=$y; emitf @a, @b, @c' Example: mlr --from f.dat put '@a=$i;@b+=$x;@c+=$y; emitf > "mytap.dat", @a, @b, @c' Example: mlr --from f.dat put '@a=$i;@b+=$x;@c+=$y; emitf >> "mytap.dat", @a, @b, @c' Example: mlr --from f.dat put '@a=$i;@b+=$x;@c+=$y; emitf > stderr, @a, @b, @c' Example: mlr --from f.dat put '@a=$i;@b+=$x;@c+=$y; emitf | "grep somepattern", @a, @b, @c' Example: mlr --from f.dat put '@a=$i;@b+=$x;@c+=$y; emitf | "grep somepattern > mytap.dat", @a, @b, @c'
emitp emitp: inserts an out-of-stream variable into the output record stream. Hashmap indices present in the data but not slotted by emitp arguments are output concatenated with ":".
Example: mlr --from f.dat put '@sums[$a][$b]+=$x; emitp @sums' Example: mlr --from f.dat put --opprint '@sums[$a][$b]+=$x; emitp > "tap-".$a.$b.".dat", @sums' Example: mlr --from f.dat put '@sums[$a][$b]+=$x; emitp @sums, "index1", "index2"' Example: mlr --from f.dat put '@sums[$a][$b]+=$x; emitp @*, "index1", "index2"' Example: mlr --from f.dat put '@sums[$a][$b]+=$x; emitp >  "mytap.dat", @*, "index1", "index2"' Example: mlr --from f.dat put '@sums[$a][$b]+=$x; emitp >> "mytap.dat", @*, "index1", "index2"' Example: mlr --from f.dat put '@sums[$a][$b]+=$x; emitp | "gzip > mytap.dat.gz", @*, "index1", "index2"' Example: mlr --from f.dat put '@sums[$a][$b]+=$x; emitp > stderr, @*, "index1", "index2"' Example: mlr --from f.dat put '@sums[$a][$b]+=$x; emitp | "grep somepattern", @*, "index1", "index2"'
end end: defines a block of statements to be executed after input records are ingested. The body statements must be wrapped in curly braces. Example: 'end { emit @count }' Example: 'end { eprint "Final count is " . @count }'
eprint eprint: prints expression immediately to stderr. Example: mlr --from f.dat put -q 'eprint "The sum of x and y is ".($x+$y)' Example: mlr --from f.dat put -q 'for (k, v in $*) { eprint k . " => " . v }' Example: mlr --from f.dat put  '(NR % 1000 == 0) { eprint "Checkpoint ".NR}'
eprintn eprintn: prints expression immediately to stderr, without trailing newline. Example: mlr --from f.dat put -q 'eprintn "The sum of x and y is ".($x+$y); eprint ""'
false false: the boolean literal value.
filter filter: includes/excludes the record in the output record stream.
Example: mlr --from f.dat put 'filter (NR == 2 || $x > 5.4)'
Instead of put with 'filter false' you can simply use put -q.  The following uses the input record to accumulate data but only prints the running sum without printing the input record:
Example: mlr --from f.dat put -q '@running_sum += $x * $y; emit @running_sum'
float float: declares a floating-point local variable in the current curly-braced scope. Type-checking happens at assignment: 'float x = 0' is an error.
for for: defines a for-loop using one of three styles. The body statements must be wrapped in curly braces. For-loop over stream record: Example:  'for (k, v in $*) { ... }' For-loop over out-of-stream variables: Example: 'for (k, v in @counts) { ... }' Example: 'for ((k1, k2), v in @counts) { ... }' Example: 'for ((k1, k2, k3), v in @*) { ... }' C-style for-loop: Example:  'for (var i = 0, var b = 1; i < 10; i += 1, b *= 2) { ... }'
func func: used for defining a user-defined function. Example: 'func f(a,b) { return sqrt(a**2+b**2)} $d = f($x, $y)'
if if: starts an if/elif/elif chain. The body statements must be wrapped in curly braces.
in in: used in for-loops over stream records or out-of-stream variables.
int int: declares an integer local variable in the current curly-braced scope. Type-checking happens at assignment: 'int x = 0.0' is an error.
map map: declares an map-valued local variable in the current curly-braced scope. Type-checking happens at assignment: 'map b = 0' is an error. map b = {} is always OK. map b = a is OK or not depending on whether a is a map.
num num: declares an int/float local variable in the current curly-braced scope. Type-checking happens at assignment: 'num b = true' is an error.
print print: prints expression immediately to stdout. Example: mlr --from f.dat put -q 'print "The sum of x and y is ".($x+$y)' Example: mlr --from f.dat put -q 'for (k, v in $*) { print k . " => " . v }' Example: mlr --from f.dat put  '(NR % 1000 == 0) { print > stderr, "Checkpoint ".NR}'
printn printn: prints expression immediately to stdout, without trailing newline. Example: mlr --from f.dat put -q 'printn "."; end { print "" }'
return return: specifies the return value from a user-defined function. Omitted return statements (including via if-branches) result in an absent-null return value, which in turns results in a skipped assignment to an LHS.
stderr stderr: Used for tee, emit, emitf, emitp, print, and dump in place of filename to print to standard error.
stdout stdout: Used for tee, emit, emitf, emitp, print, and dump in place of filename to print to standard output.
str str: declares a string local variable in the current curly-braced scope. Type-checking happens at assignment.
subr subr: used for defining a subroutine. Example: 'subr s(k,v) { print k . " is " . v} call s("a", $a)'
tee tee: prints the current record to specified file. This is an immediate print to the specified file (except for pprint format which of course waits until the end of the input stream to format all output).
You can use any of the output-format command-line flags, e.g. --ocsv, --ofs, etc., to control the format of the output. See also mlr -h.
emit with redirect and tee with redirect are identical, except tee can only output $*.
Example: mlr --from f.dat put 'tee >  "/tmp/data-".$a, $*' Example: mlr --from f.dat put 'tee >> "/tmp/data-".$a.$b, $*' Example: mlr --from f.dat put 'tee >  stderr, $*' Example: mlr --from f.dat put -q 'tee | "tr [a-z\] [A-Z\]", $*' Example: mlr --from f.dat put -q 'tee | "tr [a-z\] [A-Z\] > /tmp/data-".$a, $*' Example: mlr --from f.dat put -q 'tee | "gzip > /tmp/data-".$a.".gz", $*' Example: mlr --from f.dat put -q --ojson 'tee | "gzip > /tmp/data-".$a.".gz", $*'
true true: the boolean literal value.
unset unset: clears field(s) from the current record, or an out-of-stream or local variable.
Example: mlr --from f.dat put 'unset $x' Example: mlr --from f.dat put 'unset $*' Example: mlr --from f.dat put 'for (k, v in $*) { if (k =~ "a.*") { unset $[k] } }' Example: mlr --from f.dat put '...; unset @sums' Example: mlr --from f.dat put '...; unset @sums["green"]' Example: mlr --from f.dat put '...; unset @*'
var var: declares an untyped local variable in the current curly-braced scope. Examples: 'var a=1', 'var xyz=""'
while while: introduces a while loop, or with "do", introduces a do-while loop. The body statements must be wrapped in curly braces.
ENV ENV: access to environment variables by name, e.g. '$home = ENV["HOME"]'
FILENAME FILENAME: evaluates to the name of the current file being processed.
FILENUM FILENUM: evaluates to the number of the current file being processed, starting with 1.
FNR FNR: evaluates to the number of the current record within the current file being processed, starting with 1. Resets at the start of each file.
IFS IFS: evaluates to the input field separator from the command line.
IPS IPS: evaluates to the input pair separator from the command line.
IRS IRS: evaluates to the input record separator from the command line, or to LF or CRLF from the input data if in autodetect mode (which is the default).
M_E M_E: the mathematical constant e.
M_PI M_PI: the mathematical constant pi.
NF NF: evaluates to the number of fields in the current record.
NR NR: evaluates to the number of the current record over all files being processed, starting with 1. Does not reset at the start of each file.
OFS OFS: evaluates to the output field separator from the command line.
OPS OPS: evaluates to the output pair separator from the command line.
ORS ORS: evaluates to the output record separator from the command line, or to LF or CRLF from the input data if in autodetect mode (which is the default).
Miller is written by John Kerl <kerl.john.r@gmail.com>.
This manual page has been composed from Miller's help output by Eric MSP Veith <eveith@veith-m.de>.
awk(1), sed(1), cut(1), join(1), sort(1), RFC 4180: Common Format and MIME Type for Comma-Separated Values (CSV) Files, the miller website http://johnkerl.org/miller/doc
acme(1)                      General Commands Manual                     acme(1)
acme - Multi-platform cross assembler for 6502/6510/65816 CPU
ACME - the ACME Crossassembler for Multiple Environments
Usage: acme [OPTION...] [FILE]...
-f, --format FORMAT set output file format
-o, --outfile FILE set output file name
-r, --report FILE set report file name
-l, --symbollist FILE set symbol list file name
--labeldump (old name for --symbollist)
--vicelabels FILE set file name for label dump in VICE format
--setpc NUMBER set program counter
--cpu CPU set target processor
--initmem NUMBER define 'empty' memory
--maxerrors NUMBER set number of errors before exiting
--maxdepth NUMBER set recursion depth for macro calls and !src
-vDIGIT set verbosity level
-DSYMBOL=VALUE define global symbol
-Wno-label-indent suppress warnings about indented labels
-Wno-old-for suppress warnings about old "!for" syntax
-Wtype-mismatch enable type checking (warn about type mismatch)
--use-stdout fix for 'Relaunch64' IDE (see docs)
--msvc set output error message format to that of MS Visual Studio
--color enable colored error output using ANSI escape codes
-V, --version show version and exit
Platform independent version.
PIDOF(8)               Linux System Administrator's Manual              PIDOF(8)
pidof -- find the process ID of a running program.
pidof [-s] [-c] [-n] [-x] [-o omitpid[,omitpid..]]  [-o omitpid[,omitpid..]..]  program [program..]
Pidof finds the process id's (pids) of the named programs. It prints those id's on the standard output. This program is on some systems used in run-level change scripts, especially when the system has a System-V like rc structure. In that case these scripts are located in /etc/rc?.d, where ? is the runlevel. If the system has a start-stop-daemon (8) program that should be used instead.
-s     Single shot - this instructs the program to only return one pid.
-c     Only return process ids that are running with the same root directory.  This option is ignored for non-root users, as they will be unable to check the current root directory of processes they do not own.
-n     Avoid stat(2) system function call on all binaries which are located on network based file systems like NFS.  Instead of using this option the the variable PIDOF_NETFS may be set and exported.
-x     Scripts too - this causes the program to also return process id's of shells running the named scripts.
-o omitpid Tells pidof to omit processes with that process id. The special pid %PPID can be used to name the parent process of the pidof program, in other words the calling shell or shell script.
0      At least one program was found with the requested name.
1      No program was found with the requested name.
pidof is actually the same program as killall5; the program behaves according to the name under which it is called.
When pidof is invoked with a full pathname to the program it should find the pid of, it is reasonably safe. Otherwise it is possible that it returns pids of running programs that happen to have the same name as the program you're after but are actually other programs. Note that that the executable name of running processes is calculated with readlink(2), so symbolic links to executables will also match.
shutdown(8), init(8), halt(8), reboot(8), killall5(8)
Miquel van Smoorenburg, miquels@cistron.nl
PIPX(1)                           User Commands                          PIPX(1)
pipx - install and execute apps from Python packages
pipx [-h] [--version] SUBCOMMAND [OPTION]...
Binaries can either be installed globally into isolated virtual environments or run directly in a temporary virtual environment.
OPTIONAL ARGUMENTS -h, --help Show a help message and exit
Each of the following has a corresponding man page: for example, pipx-install(1) for “pipx install”.  Or, get help for commands with pipx COMMAND --help.
pipx install Install a package
pipx inject Install packages into an existing virtual environment
pipx upgrade Upgrade a package
pipx upgrade-all Upgrade all packages.  Runs pip install -U pkgname for each package.
pipx uninstall Uninstall a package
pipx uninstall-all Uninstall all packages
pipx reinstall Reinstall a package
pipx reinstall-all Reinstall all packages
pipx list List installed packages
pipx run Download the latest version of a package to a temporary virtual environment, then run an app from it.  Also compatible with local __pypackages__ directory (experimental).
pipx runpip Run pip in an existing pipx(1)-managed virtual environment
pipx ensurepath Ensure directories necessary for pipx(1) operation are in your PATH environment variable.
pipx completions Print instructions on enabling shell completions for pipx(1)
Optional environment variables:
PIPX_HOME Overrides default pipx(1) location.  Virtual environments will be installed to $PIPX_HOME/venvs.
PIPX_BIN_DIR Overrides location of app installations.  Apps are symlinked or copied here.
USE_EMOJI Overrides emoji behavior.  Default value varies based on platform.
PIPX_DEFAULT_PYTHON Overrides default python used for commands.
Virtual environment location is $HOME/.local/pipx/venvs by default. Symlinks to apps are placed in $HOME/.local/bin by default.  See also the ENVIRONMENT section.
pip(1)
python(1)
pipx-completions(1), pipx-ensurepath(1), pipx-inject(1), pipx-install(1), pipx-list(1), pipx-reinstall(1), pipx-reinstall-all(1), pipx-run(1), pipx-runpip(1), pipx-uninstall(1), pipx-uninstall-all(1), pipx-upgrade(1), pipx-upgrade-all(1)
OGR2OGR(1)                            GDAL                            OGR2OGR(1)
ogr2ogr - Converts simple features data between file formats.
ogr2ogr [--help-general] [-skipfailures] [-append] [-update] [-select field_list] [-where restricted_where|\@filename] [-progress] [-sql <sql statement>|\@filename] [-dialect dialect] [-preserve_fid] [-fid FID] [-limit nb_features] [-spat xmin ymin xmax ymax] [-spat_srs srs_def] [-geomfield field] [-a_srs srs_def] [-t_srs srs_def] [-s_srs srs_def] [-ct string] [-f format_name] [-overwrite] [[-dsco NAME=VALUE] ...] dst_datasource_name src_datasource_name [-lco NAME=VALUE] [-nln name] [-nlt type|PROMOTE_TO_MULTI|CONVERT_TO_LINEAR|CONVERT_TO_CURVE] [-dim XY|XYZ|XYM|XYZM|2|3|layer_dim] [layer [layer ...]]
# Advanced options [-gt n] [[-oo NAME=VALUE] ...] [[-doo NAME=VALUE] ...] [-clipsrc [xmin ymin xmax ymax]|WKT|datasource|spat_extent] [-clipsrcsql sql_statement] [-clipsrclayer layer] [-clipsrcwhere expression] [-clipdst [xmin ymin xmax ymax]|WKT|datasource] [-clipdstsql sql_statement] [-clipdstlayer layer] [-clipdstwhere expression] [-wrapdateline] [-datelineoffset val] [[-simplify tolerance] | [-segmentize max_dist]] [-makevalid] [-addfields] [-unsetFid] [-emptyStrAsNull] [-relaxedFieldNameMatch] [-forceNullable] [-unsetDefault] [-fieldTypeToString All|(type1[,type2]*)] [-unsetFieldWidth] [-mapFieldType type1|All=type2[,type3=type4]*] [-fieldmap identity | index1[,index2]*] [-splitlistfields] [-maxsubfields val] [-resolveDomains] [-explodecollections] [-zfield field_name] [-gcp ungeoref_x ungeoref_y georef_x georef_y [elevation]]* [-order n | -tps] [-nomd] [-mo "META-TAG=VALUE"]* [-noNativeData]
ogr2ogr can be used to convert simple features data between file formats. It can also perform various operations during the process, such as spatial or attribute selection, reducing the set of attributes, setting the output coordinate system or even reprojecting the features during translation.
-f <format_name> Output file format name, e.g. ESRI Shapefile, MapInfo File, PostgreSQL.  Starting with GDAL 2.3, if not specified, the format is guessed from the extension (previously was ESRI Shapefile).
-append Append to existing layer instead of creating new
-overwrite Delete the output layer and recreate it empty
-update Open existing output datasource in update mode rather than trying to create a new one
-select <field_list> Comma-delimited list of fields from input layer to copy to the new layer. A field is skipped if mentioned previously in the list even if the input layer has duplicate field names. (Defaults to all; any field is skipped if a subsequent field with same name is found.) Geometry fields can also be specified in the list.
Note this setting cannot be used together with -append. To control the selection of fields when appending to a layer, use -fieldmap or -sql.
-progress Display progress on terminal. Only works if input layers have the "fast feature count" capability.
-sql <sql_statement> SQL statement to execute. The resulting table/layer will be saved to the output. Starting with GDAL 2.1, the @filename syntax can be used to indicate that the content is in the pointed filename.
-dialect <dialect> SQL dialect. In some cases can be used to use (unoptimized) ogr_sql_dialect instead of the native SQL of an RDBMS by passing the OGRSQL dialect value.  The sql_sqlite_dialect dialect can be select with the SQLITE and INDIRECT_SQLITE dialect values, and this can be used with any datasource.
-where restricted_where Attribute query (like SQL WHERE). Starting with GDAL 2.1, the @filename syntax can be used to indicate that the content is in the pointed filename.
-skipfailures Continue after a failure, skipping the failed feature.
-spat <xmin> <ymin> <xmax> <ymax> spatial query extents, in the SRS of the source layer(s) (or the one specified with -spat_srs). Only features whose geometry intersects the extents will be selected. The geometries will not be clipped unless -clipsrc is specified.
-spat_srs <srs_def> Override spatial filter SRS.
-geomfield <field> Name of the geometry field on which the spatial filter operates on.
-dsco NAME=VALUE Dataset creation option (format specific)
-lco NAME=VALUE Layer creation option (format specific)
-nln <name> Assign an alternate name to the new layer
-nlt <type> Define the geometry type for the created layer. One of NONE, GEOMETRY, POINT, LINESTRING, POLYGON, GEOMETRYCOLLECTION, MULTIPOINT, MULTIPOLYGON, MULTILINESTRING, CIRCULARSTRING, COMPOUNDCURVE, CURVEPOLYGON, MULTICURVE, and MULTISURFACE non-linear geometry types. Add Z, M, or ZM to the type name to specify coordinates with elevation, measure, or elevation and measure. PROMOTE_TO_MULTI can be used to automatically promote layers that mix polygon or multipolygons to multipolygons, and layers that mix linestrings or multilinestrings to multilinestrings. Can be useful when converting shapefiles to PostGIS and other target drivers that implement strict checks for geometry types.  CONVERT_TO_LINEAR can be used to to convert non-linear geometry types into linear geometry types by approximating them, and CONVERT_TO_CURVE to promote a non-linear type to its generalized curve type (POLYGON to CURVEPOLYGON, MULTIPOLYGON to MULTISURFACE, LINESTRING to COMPOUNDCURVE, MULTILINESTRING to MULTICURVE). Starting with version 2.1 the type can be defined as measured ("25D" remains as an alias for single "Z"). Some forced geometry conversions may result in invalid geometries, for example when forcing conversion of multi-part multipolygons with -nlt POLYGON, the resulting polygon will break the Simple Features rules.
Starting with GDAL 3.0.5, -nlt CONVERT_TO_LINEAR and -nlt PROMOTE_TO_MULTI can be used simultaneously.
-dim <val> Force the coordinate dimension to val (valid values are XY, XYZ, XYM, and XYZM - for backwards compatibility 2 is an alias for XY and 3 is an alias for XYZ). This affects both the layer geometry type, and feature geometries. The value can be set to layer_dim to instruct feature geometries to be promoted to the coordinate dimension declared by the layer. Support for M was added in GDAL 2.1.
-a_srs <srs_def> Assign an output SRS, but without reprojecting (use -t_srs to reproject)
The coordinate reference systems that can be passed are anything supported by the OGRSpatialReference.SetFromUserInput() call, which includes EPSG Projected, Geographic or Compound CRS (i.e. EPSG:4296), a well known text (WKT) CRS definition, PROJ.4 declarations, or the name of a .prj file containing a WKT CRS definition.
-t_srs <srs_def> Reproject/transform to this SRS on output, and assign it as output SRS.
A source SRS must be available for reprojection to occur. The source SRS will be by default the one found in the source layer when it is available, or as overridden by the user with -s_srs
-s_srs <srs_def> Override source SRS. If not specified the SRS found in the input layer will be used. This option has only an effect if used together with -t_srs to reproject.
-ct <string> A PROJ string (single step operation or multiple step string starting with +proj=pipeline), a WKT2 string describing a CoordinateOperation, or a urn:ogc:def:coordinateOperation:EPSG::XXXX URN overriding the default transformation from the source to the target CRS. It must take into account the axis order of the source and target CRS.
New in version 3.0.
-preserve_fid Use the FID of the source features instead of letting the output driver automatically assign a new one (for formats that require a FID). If not in append mode, this behavior is the default if the output driver has a FID layer creation option, in which case the name of the source FID column will be used and source feature IDs will be attempted to be preserved. This behavior can be disabled by setting -unsetFid.
-fid fid If provided, only the feature with the specified feature id will be processed.  Operates exclusive of the spatial or attribute queries. Note: if you want to select several features based on their feature id, you can also use the fact the 'fid' is a special field recognized by OGR SQL. So, -where "fid in (1,3,5)" would select features 1, 3 and 5.
-limit nb_features Limit the number of features per layer.
-oo NAME=VALUE Input dataset open option (format specific).
-doo NAME=VALUE Destination dataset open option (format specific), only valid in -update mode.
-gt n  Group n features per transaction (default 100 000). Increase the value for better performance when writing into DBMS drivers that have transaction support. n can be set to unlimited to load the data into a single transaction.
-ds_transaction Force the use of a dataset level transaction (for drivers that support such mechanism), especially for drivers such as FileGDB that only support dataset level transaction in emulation mode.
-clipsrc [xmin ymin xmax ymax]|WKT|datasource|spat_extent Clip geometries to the specified bounding box (expressed in source SRS), WKT geometry (POLYGON or MULTIPOLYGON), from a datasource or to the spatial extent of the -spa.. option if you use the spat_extent keyword. When specifying a datasource, you will generally want to use it in combination of the -clipsrclayer, -clipsrcwhere or -clipsrcsql options
-clipsrcsql <sql_statement> Select desired geometries using an SQL query instead.
-clipsrclayer <layername> Select the named layer from the source clip datasource.
-clipsrcwhere <expression> Restrict desired geometries based on attribute query.
-clipdst <xmin> <ymin> <xmax> <ymax> Clip geometries after reprojection to the specified bounding box (expressed in dest SRS), WKT geometry (POLYGON or MULTIPOLYGON) or from a datasource.  When specifying a datasource, you will generally want to use it in combination of the -clipdstlayer, -clipdstwhere or -clipdstsq.. options
-clipdstsql <sql_statement> Select desired geometries using an SQL query instead.
-clipdstlayer <layername> Select the named layer from the destination clip datasource.
-clipdstwhere <expression> Restrict desired geometries based on attribute query.
-wrapdateline Split geometries crossing the dateline meridian (long. = +/- 180deg)
-datelineoffset Offset from dateline in degrees (default long. = +/- 10deg, geometries within 170deg to -170deg will be split)
-simplify <tolerance> Distance tolerance for simplification. Note: the algorithm used preserves topology per feature, in particular for polygon geometries, but not for a whole layer.
-segmentize <max_dist> Maximum distance between 2 nodes. Used to create intermediate points.
-makevalid Run the OGRGeometry::MakeValid() operation, followed by OGRGeometryFactory::removeLowerDimensionSubGeoms(), on geometries to ensure they are valid regarding the rules of the Simple Features specification.
-fieldTypeToString type1,... Converts any field of the specified type to a field of type string in the destination layer. Valid types are : Integer, Integer64, Real, String, Date, Time, DateTime, Binary, IntegerList, Integer64List, RealList, StringList. Special value All can be used to convert all fields to strings.  This is an alternate way to using the CAST operator of OGR SQL, that may avoid typing a long SQL query. Note that this does not influence the field types used by the source driver, and is only an afterwards conversion.
-mapFieldType srctype|All=dsttype,... Converts any field of the specified type to another type. Valid types are : Integer, Integer64, Real, String, Date, Time, DateTime, Binary, IntegerList, Integer64List, RealList, StringList. Types can also include subtype between parenthesis, such as Integer(Boolean), Real(Float32), ...  Special value All can be used to convert all fields to another type. This is an alternate way to using the CAST operator of OGR SQL, that may avoid typing a long SQL query. This is a generalization of -fieldTypeToString.  Note that this does not influence the field types used by the source driver, and is only an afterwards conversion.
-unsetFieldWidth Set field width and precision to 0.
-splitlistfields Split fields of type StringList, RealList or IntegerList into as many fields of type String, Real or Integer as necessary.
-maxsubfields <val> To be combined with -splitlistfields to limit the number of subfields created for each split field.
-explodecollections Produce one feature for each geometry in any kind of geometry collection in the source file, applied after any -sql option.
-zfield <field_name> Uses the specified field to fill the Z coordinate of geometries.
-gcp <ungeoref_x> <ungeoref_y> <georef_x> <georef_y> <elevation> Add the indicated ground control point. This option may be provided multiple times to provide a set of GCPs.
-order <n> Order of polynomial used for warping (1 to 3). The default is to select a polynomial order based on the number of GCPs.
-tps   Force use of thin plate spline transformer based on available GCPs.
-fieldmap Specifies the list of field indexes to be copied from the source to the destination. The (n)th value specified in the list is the index of the field in the target layer definition in which the n(th) field of the source layer must be copied. Index count starts at zero. To omit a field, specify a value of -1. There must be exactly as many values in the list as the count of the fields in the source layer. We can use the 'identity' setting to specify that the fields should be transferred by using the same order. This setting should be used along with the -append setting.
-addfields This is a specialized version of -append. Contrary to -append, -addfields has the effect of adding, to existing target layers, the new fields found in source layers. This option is useful when merging files that have non-strictly identical structures. This might not work for output formats that don't support adding fields to existing non-empty layers. Note that if you plan to use -addfields, you may need to combine it with -forceNullable, including for the initial import.
-relaxedFieldNameMatch Do field name matching between source and existing target layer in a more relaxed way if the target driver has an implementation for it.
-forceNullable Do not propagate not-nullable constraints to target layer if they exist in source layer.
-unsetDefault Do not propagate default field values to target layer if they exist in source layer.
-unsetFid Can be specified to prevent the name of the source FID column and source feature IDs from being re-used for the target layer. This option can for example be useful if selecting source features with a ORDER BY clause.
-emptyStrAsNull New in version 3.3.
Treat empty string values as null.
-resolveDomains New in version 3.3.
When this is specified, any selected field that is linked to a coded field domain will be accompanied by an additional field ({dstfield}_resolved), that will contain the description of the coded value.
-nomd  To disable copying of metadata from source dataset and layers into target dataset and layers, when supported by output driver.
-mo META-TAG=VALUE Passes a metadata key and value to set on the output dataset, when supported by output driver.
-noNativeData To disable copying of native data, i.e. details of source format not captured by OGR abstraction, that are otherwise preserved by some drivers (like GeoJSON) when converting to same format.
New in version 2.1.
When writing into transactional DBMS (SQLite/PostgreSQL,MySQL, etc...), it might be beneficial to increase the number of INSERT statements executed between BEGIN TRANSACTION and COMMIT TRANSACTION statements. This number is specified with the -gt option. For example, for SQLite, explicitly defining -gt 65536 ensures optimal performance while populating some table containing many hundreds of thousands or millions of rows. However, note that -skipfailures overrides -gt and sets the size of transactions to 1.
For PostgreSQL, the PG_USE_COPY config option can be set to YES for a significant insertion performance boost. See the PG driver documentation page.
More generally, consult the documentation page of the input and output drivers for performance hints.
This utility is also callable from C with GDALVectorTranslate().
Basic conversion from Shapefile to GeoPackage:
ogr2ogr \ -f GPKG output.gpkg \ input.shp
Change the coordinate reference system from EPSG:4326 to EPSG:3857:
ogr2ogr \ -s_srs EPSG:4326 \ -t_srs EPSG:3857 \ -f GPKG output.gpkg \ input.gpkg
Example appending to an existing layer (both -update and -append flags need to be used):
ogr2ogr -update -append -f PostgreSQL PG:dbname=warmerda abc.tab
Clip input layer with a bounding box (<xmin> <ymin> <xmax> <ymax>):
ogr2ogr \ -spat -13.931 34.886 46.23 74.12 \ -f GPKG output.gpkg \ natural_earth_vector.gpkg
Filter Features by a -where clause:
ogr2ogr \ -where "\"POP_EST\" < 1000000" \ -f GPKG output.gpkg \ natural_earth_vector.gpkg \ ne_10m_admin_0_countries
Example reprojecting from ETRS_1989_LAEA_52N_10E to EPSG:4326 and clipping to a bounding box:
ogr2ogr -wrapdateline -t_srs EPSG:4326 -clipdst -5 40 15 55 france_4326.shp europe_laea.shp
Example for using the -fieldmap setting. The first field of the source layer is used to fill the third field (index 2 = third field) of the target layer, the second field of the source layer is ignored, the third field of the source layer used to fill the fifth field of the target layer.
ogr2ogr -append -fieldmap 2,-1,4 dst.shp src.shp
More examples are given in the individual format pages.
Frank Warmerdam <warmerdam@pobox.com>, Silke Reimer <silke@intevation.de>
p4(1)                        General Commands Manual                       p4(1)
p4 - portable programs for parallel processors - release 1.4
p4 is a package of procedures that support development of parallel programs in C or Fortran that are portable across a wide variety of architectures.  For the shared-memory model of parallel computation, p4 provides a set of primitives from which monitors can be constructed, as well as a set of useful monitors.  For the distributed-memory model, p4 provides typed send and receive operations, and creation of processes according to a text file describing files to be executed on by created processes and the machines to execute them on.  A complete User's Guide is available in the doc subdirectory of the p4 distribution.  It is written in LaTeXinfo, so that it can produce either an info file (included) or a printed version.
#include "p4.h"
Several command line options are available to any program linked to the p4 package.
-p4help        get this information
-p4pg <filename> procgroup file
-p4dbg n       set debug level
-p4rdbg n      set remote debug level
-p4gm n   set globmemsize
-p4dmn <name>       domainname
-p4out <file>   output file for master
-p4rout <file>  output file prefix for remote masters
-p4ssport <port#> private port number for secure server
-p4log          enable internal p4 logging by alog
-p4version     print the current p4 version number
-p4norem  prompt user to start remote processes by hand
p4.h, libp4.a - see your systems administrator for the installed location
p4 generates a wide variety of diagnostic messages.  See the user manual for more details.
To invoke a program linked with p4 using a procgroup file: myprogram -pg procgroup_file_name
socket,etc.
There are no known bugs at this time, but stay tuned.
GML2GV,GV2GML(1)             General Commands Manual            GML2GV,GV2GML(1)
gml2gv,gv2gml - GML-DOT converters
gml2gv [ -?v ] [ -ggname ] [ -ooutfile ] [ files ] gv2gml [ -?  ] [ -ooutfile ] [ files ]
gml2gv converts a graph specified in the GML format to a graph in the GV (formerly DOT) format.  gv2gml converts a graph specified in the GV format to a graph in the GML format.
-v     Turns on verbose mode
-ggname The string gname is used as the name of the generated graph.  If multiple graphs are generated, subsequent graphs use the name gname appended with an integer.
-ooutfile Prints output to the file outfile. If not given, gml2gv uses stdout.
files   Names of files containing 1 or more graphs in GML.  If no files operand is specified, the standard input will be used.
As both the graph and graphics models of GV and GML differ significantly, the conversion is at best approximate. In particular, it is not clear how multiedges are differentiated in GML, so multiedges are created in GV with no user-available key. Also, no attribute information is lost, in that any GML attributes that aren't converted to GV equivalents are retained as attributes in the output graph.
At present, gv2gml does not support subgraphs and clusters. In addition, there does not appear to be a standard mechanism for specifying default node and edge attributes in GML, so any attributes are repeated for every node and edge.
dot(1), libcgraph(3)
rapper(1)                    General Commands Manual                   rapper(1)
rapper - Raptor RDF parsing and serializing utility
rapper [OPTIONS] INPUT-URI [INPUT-BASE-URI]
rapper -o ntriples http://planetrdf.com/guide/rss.rdf rapper -i rss-tag-soup -o rss-1.0 pile-of-rss.xml http://example.org/base/ rapper --count http://example.org/index.rdf
The rapper utility allows parsing of RDF content by the Raptor RDF parser toolkit emitting the results as RDF triples in a choice of syntaxes.  The INPUT-URI can be a file name, '-' for standard input or if Raptor is built with a WWW retrieval library, a general URI.  The optional INPUT- BASE-URI is used as the document parser base URI if present otherwise defaults to the INPUT-URI.  A value of '-' means no base URI.
rapper uses the usual GNU command line syntax, with long options starting with two dashes (`-') if supported by the getopt_long function. Otherwise the short options are only available.
-h, --help Show a summary of the options.
-i, --input FORMAT Set the input FORMAT to one of 'rdfxml' (RDF/XML, default), 'ntriples' (N-Triples, see below), 'turtle' (Turtle, see below) or 'rss-tag-soup' (RSS Tag Soup).  The RSS Tag Soup parser can turn the many XML RSS formats and Atom 0.3 into RDF triples.
The list of parsers depends on how libraptor(3) was built.  The list of supported parsers is given in the help summary given by -h.
-I, --input-uri URI Set the input/parser base URI or use value '-' for no base.  The default is the INPUT-URI argument value.
-o, --output FORMAT Set the output FORMAT to 'ntriples' (N-Triples, default), 'rdfxml' (RDF/XML), 'rdfxml-abbrev' (RDF/XML with abbreviations) or 'rss-1.0' (RSS 1.0, also an RDF/XML syntax).
The list of serializers depends on how libraptor(3) was built. The list of supported serializers is given in the help summary given by -h.
-O, --output-uri URI Set the output/serializer base URI or use value '-' for no base. The default is the input base uri, either set by the argument INPUT-BASE-URI or via options -I, --input-uri URI
-c, --count Only count the triples and produce no other output.
-e, --ignore-errors Ignore errors, do not emit the messages and try to continue parsing.
-f, --feature FEATURE[=VALUE] Set a parser or serializer feature FEATURE to a value, or to 1 if VALUE is omitted, Use -f help to get lists of valid parser and serializer features.
If the form -f 'xmlns:prefix="uri"' is used, the prefix and namespace uri given will be set for serializing.  The syntax matches XML in that either or both of prefix or uri can be omitted.
-g, --guess Guess the parser to use from the source-URI rather than use the -i FORMAT.
-q, --quiet No extra information messages.
-r, --replace-newlines Replace newlines in multi-line literals with spaces.
--show-graphs Print graph names (URIs) as they are seen in the input.  This only has a meaning for parsers that support graph names such as the TRiG parser.
--show-namespaces Print namespaces as they are seen in the input.
-t, --trace Print URIs retrieved during parsing.  Especially useful for monitoring what the guess and GRDDL parsers are doing.
-w, --ignore-warnings Ignore warnings, do not emit the messages.
-v, --version Print the raptor version and exit.
rapper -q -i ntriples -o rdfxml -f 'xmlns:rss="http://purl.org/rss/1.0/"' -f 'xmlns:ex="http://example.org/"' tests/test.nt rapper -q -o rdfxml -f 'xmlns:rdfs="http://www.w3.org/2000/01/rdf- schema#"' tests/rdf-schema.rdf 'http://www.w3.org/2000/01/rdf-schema#'
RDF/XML Syntax (Revised), W3C Recommendation, http://www.w3.org/TR/rdf- syntax-grammar/ ⟨http://www.w3.org/TR/rdf-syntax-grammar/⟩
N-Triples, in RDF Test Cases, Jan Grant and Dave Beckett (eds.), W3C Recommendation, http://www.w3.org/TR/rdf-testcases/#ntriples ⟨http://www.w3.org/TR/rdf-testcases/#ntriples⟩
Turtle Terse RDF Triple Language, Dave Beckett, http://www.dajobe.org/2004/01/turtle/ ⟨http://www.dajobe.org/2004/01/turtle/⟩
RDFA in XHTML: Syntax and Processing, Ben Adida, Mark Birbeck, Shane McCarron and Steven Pemberton (eds.), W3C Candidate Recommendation, 20 June 2008 http://www.w3.org/TR/2008/CR-rdfa-syntax-20080620/ ⟨http://www.w3.org/TR/2008/CR-rdfa-syntax-20080620/⟩
RDF Site Summary (RSS) 1.0, 2000-12-06 http://purl.org/rss/1.0/spec ⟨http://purl.org/rss/1.0/spec⟩
libraptor(3),raptor-config(1)
2.0.0 Removed -a option that did nothing.
Removed -m option from rapper but it was never documented here.
Removed -n option that was long hidden.
Removed -s option that was equivalent to -f scanForRDF
1.4.16 Added -I/--input-uri and -O/--output-uri to set the input and output (parser and serializer) base URIs separately.
1.4.15 Added -t/--trace to do URI traces.
1.4.5 Updated to add serializer rdfxml-abbrev
1.4.3 Updated potential parser and serializers and described -f for defining namespaces.
1.3.0 Added -f for features. Added -g for guessing the parser to use.
1.1.0 Removed -a, --assume since rdf:RDF is now always optional.
Dave Beckett - http://www.dajobe.org/ ⟨http://www.dajobe.org/⟩
GIT-REMOTE(1)                      Git Manual                      GIT-REMOTE(1)
git-remote - Manage set of tracked repositories