@crossbind/port-gdal-wasi 2.0.0-beta.50

package/dist/prebuilt/wasi-wasm32-st-release/share/man/man1/gdal-vector-combine.1

@@ -0,0 +1,398 @@
+'\" t
+.\" Man page generated from reStructuredText.
+.
+.
+.nr rst2man-indent-level 0
+.
+.de1 rstReportMargin
+\\$1 \\n[an-margin]
+level \\n[rst2man-indent-level]
+level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
+-
+\\n[rst2man-indent0]
+\\n[rst2man-indent1]
+\\n[rst2man-indent2]
+..
+.de1 INDENT
+.\" .rstReportMargin pre:
+. RS \\$1
+. nr rst2man-indent\\n[rst2man-indent-level] \\n[an-margin]
+. nr rst2man-indent-level +1
+.\" .rstReportMargin post:
+..
+.de UNINDENT
+. RE
+.\" indent \\n[an-margin]
+.\" old: \\n[rst2man-indent\\n[rst2man-indent-level]]
+.nr rst2man-indent-level -1
+.\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
+.in \\n[rst2man-indent\\n[rst2man-indent-level]]u
+..
+.TH "GDAL-VECTOR-COMBINE" "1" "Aug 18, 2026" "" "GDAL"
+.SH NAME
+gdal-vector-combine \- Combine geometries into geometry collections
+.sp
+Added in version 3.13.
+
+.SH SYNOPSIS
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.EX
+Usage: gdal vector combine [OPTIONS] <INPUT> <OUTPUT>
+
+Combine features into collections
+
+Positional arguments:
+  \-i, \-\-input <INPUT>                                  Input vector datasets [required] [not available in pipelines]
+  \-o, \-\-output <OUTPUT>                                Output vector dataset [required] [not available in pipelines]
+
+Common Options:
+  \-h, \-\-help                                           Display help message and exit
+  \-\-json\-usage                                         Display usage as JSON document and exit
+  \-\-config <KEY>=<VALUE>                               Configuration option [may be repeated]
+  \-q, \-\-quiet                                          Quiet mode (no progress bar or warning message) [not available in pipelines]
+
+Options:
+  \-l, \-\-layer, \-\-input\-layer <INPUT\-LAYER>             Input layer name(s) [may be repeated] [not available in pipelines]
+  \-f, \-\-of, \-\-format, \-\-output\-format <OUTPUT\-FORMAT>  Output format (\(dqGDALG\(dq allowed) [not available in pipelines]
+  \-\-co, \-\-creation\-option <KEY>=<VALUE>                Creation option [may be repeated] [not available in pipelines]
+  \-\-lco, \-\-layer\-creation\-option <KEY>=<VALUE>         Layer creation option [may be repeated] [not available in pipelines]
+  \-\-overwrite                                          Whether overwriting existing output dataset is allowed [not available in pipelines]
+  \-\-update                                             Whether to open existing dataset in update mode [not available in pipelines]
+  \-\-overwrite\-layer                                    Whether overwriting existing output layer is allowed [not available in pipelines]
+  \-\-append                                             Whether appending to existing layer is allowed [not available in pipelines]
+                                                       Mutually exclusive with \-\-upsert
+  \-\-output\-layer <OUTPUT\-LAYER>                        Output layer name [not available in pipelines]
+  \-\-skip\-errors                                        Skip errors when writing features [not available in pipelines]
+  \-\-group\-by <GROUP\-BY>                                Names of field(s) by which inputs should be grouped [may be repeated]
+  \-\-keep\-nested                                        Avoid combining the components of multipart geometries
+  \-\-add\-extra\-fields <ADD\-EXTRA\-FIELDS>                Whether to add extra fields, depending on if they have identical values within each group. ADD\-EXTRA\-FIELDS=no|sometimes\-identical|always\-identical (default: no)
+
+Advanced Options:
+  \-\-if, \-\-input\-format <INPUT\-FORMAT>                  Input formats [may be repeated] [not available in pipelines]
+  \-\-oo, \-\-open\-option <KEY>=<VALUE>                    Open options [may be repeated] [not available in pipelines]
+  \-\-output\-oo, \-\-output\-open\-option <KEY>=<VALUE>      Output open options [may be repeated] [not available in pipelines]
+  \-\-upsert                                             Upsert features (implies \(aqappend\(aq) [not available in pipelines]
+                                                       Mutually exclusive with \-\-append
+.EE
+.UNINDENT
+.UNINDENT
+.SH DESCRIPTION
+.sp
+\fBgdal vector combine\fP combines geometries into geometry collections.
+.sp
+The \fI\%\-\-group\-by\fP argument can be used to determine which features are combined.
+.sp
+By default, the parts of multipart geometries will be combined into an
+un\-nested collection of the most specific type possible (e.g., \fBMultiPolygon\fP
+rather than \fBGeometryCollection\fP).  For example, a Polygon and a two\-part
+MultiPolygon would be combined into a three\-part MultiPoygon. This is done
+because many GIS file formats and software packages do not handle nested
+GeometryCollections types. If the nested representation in the manner of
+PostGIS\(aq \fBST_Collect\fP is preferred (a two\-component GeometryCollection
+containing the Polygon and MultiPolygon), then \fI\%\-\-keep\-nested\fP can be
+used.
+.sp
+\fBcombine\fP can be used as a step of \fI\%gdal vector pipeline\fP\&.
+.SH PROGRAM-SPECIFIC OPTIONS
+.INDENT 0.0
+.TP
+.B \-\-group\-by <FIELD_NAMES>
+The names of fields whose unique values will be used to collect
+input geometries. Any fields not listed in \fI\%\-\-group\-by\fP will be
+removed from the source layer. If \fI\%\-\-group\-by\fP is omitted, the
+entire layer will be combined into a single feature.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-keep\-nested
+If input geometries have multiple parts, combine them into a GeometryCollection
+of the input geometries.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-add\-extra\-fields no|sometimes\-identical|always\-identical
+Whether fields from source features that have the same value among the features
+belonging to a same group are copied to the corresponding output feature.
+.sp
+By default, \fBno\fP, only fields listed in \fI\%\-\-group\-by\fP are copied to
+the output layer.
+.sp
+When specifying \fBsometimes\-identical\fP, fields, for which all input
+features within at least one output group have the same value, will be
+copied to the output layer schema. The value of the field is the value that
+is common for all input features of a group. If the input features within
+some group are not identical, the field value in the output for this group
+will be set to null.
+.sp
+When specifying \fBalways\-identical\fP, fields for which all input features
+within a given output group have the same value are copied to the output layer,
+provided this condition holds for all output groups.
+.sp
+For example, let\(aqs suppose we have four input features with the following
+content, and we group them by \fBcountry\fP
+.SH INPUT FEATURES
+.TS
+box center;
+l|l|l|l.
+T{
+name
+T}	T{
+country
+T}	T{
+country_fr
+T}	T{
+type
+T}
+_
+T{
+Mainland France
+T}	T{
+France
+T}	T{
+France
+T}	T{
+continental
+T}
+_
+T{
+Corsica
+T}	T{
+France
+T}	T{
+France
+T}	T{
+island
+T}
+_
+T{
+Mainland USA
+T}	T{
+USA
+T}	T{
+Etats\-Unis d\(aqAmérique
+T}	T{
+continental
+T}
+_
+T{
+Alaska
+T}	T{
+USA
+T}	T{
+Etats\-Unis d\(aqAmérique
+T}	T{
+continental
+T}
+.TE
+.sp
+With \fBsometimes\-identical\fP, the output will be:
+.SH OUTPUT WITH SOMETIMES-IDENTICAL
+.TS
+box center;
+l|l|l.
+T{
+country
+T}	T{
+country_fr
+T}	T{
+type
+T}
+_
+T{
+France
+T}	T{
+France
+T}	T{
+T}
+_
+T{
+USA
+T}	T{
+Etats\-Unis d\(aqAmérique
+T}	T{
+continental
+T}
+.TE
+.sp
+The \fBname\fP field has been removed because it is distinct for each
+input feature. The \fBtype\fP field appears as an output field, because at
+least for the USA, the two grouped input features that makes it have the
+same value. For France, its content is set to null, because its value is
+different in the two input features.
+.sp
+With \fBalways\-identical\fP, the output will be:
+.SH OUTPUT WITH ALWAYS-IDENTICAL
+.TS
+box center;
+l|l.
+T{
+country
+T}	T{
+country_fr
+T}
+_
+T{
+France
+T}	T{
+France
+T}
+_
+T{
+USA
+T}	T{
+Etats\-Unis d\(aqAmérique
+T}
+.TE
+.sp
+The \fBtype\fP field has been removed because its value is different in the two input
+features of France.
+.UNINDENT
+.SH RETURN STATUS CODE
+.sp
+The program returns status code 0 in case of success, and non\-zero in case of
+error (non\-blocking errors emitted as warnings are considered as a successful
+execution).
+.SH STANDARD OPTIONS
+.INDENT 0.0
+.TP
+.B \-\-append
+Whether appending features to existing layer(s) is allowed.
+This also creates the output dataset if it does not exist yet.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-co, \-\-creation\-option <NAME>=<VALUE>
+Many formats have one or more optional dataset creation options that can be
+used to control particulars about the file created. For instance,
+the GeoPackage driver supports creation options to control the version.
+.sp
+May be repeated.
+.sp
+The dataset creation options available vary by format driver, and some
+simple formats have no creation options at all. A list of options
+supported for a format can be listed with the
+\fI\%\-\-formats\fP
+command line option but the documentation for the format is the
+definitive source of information on driver creation options.
+See \fI\%Vector drivers\fP format
+specific documentation for legal creation options for each format.
+.sp
+Note that dataset creation options are different from layer creation options.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-if, \-\-input\-format <format>
+Format/driver name to be attempted to open the input file(s). It is generally
+not necessary to specify it, but it can be used to skip automatic driver
+detection, when it fails to select the appropriate driver.
+This option can be repeated several times to specify several candidate drivers.
+Note that it does not force those drivers to open the dataset. In particular,
+some drivers have requirements on file extensions.
+.sp
+May be repeated.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-lco, \-\-layer\-creation\-option <NAME>=<VALUE>
+Many formats have one or more optional layer creation options that can be
+used to control particulars about the layer created. For instance,
+the GeoPackage driver supports layer creation options to control the
+feature identifier or geometry column name, setting the identifier or
+description, etc.
+.sp
+May be repeated.
+.sp
+The layer creation options available vary by format driver, and some
+simple formats have no layer creation options at all. A list of options
+supported for a format can be listed with the
+\fI\%\-\-formats\fP
+command line option but the documentation for the format is the
+definitive source of information on driver creation options.
+See \fI\%Vector drivers\fP format
+specific documentation for legal creation options for each format.
+.sp
+Note that layer creation options are different from dataset creation options.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-oo, \-\-open\-option <NAME>=<VALUE>
+Dataset open option (format specific).
+.sp
+May be repeated.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-f, \-\-of, \-\-format, \-\-output\-format <OUTPUT\-FORMAT>
+Which output vector format to use. Allowed values may be given by
+\fBgdal \-\-formats | grep vector | grep rw | sort\fP
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-output\-open\-option, \-\-output\-oo <NAME>=<VALUE>
+Added in version 3.12.
+
+.sp
+Dataset open option for output dataset (format specific).
+.sp
+May be repeated.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-overwrite
+Allow program to overwrite existing target file or dataset.
+Otherwise, by default, \fBgdal\fP errors out if the target file or
+dataset already exists.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-overwrite\-layer
+Whether overwriting the existing output vector layer is allowed.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-skip\-errors
+Added in version 3.12.
+
+.sp
+Whether failures to write feature(s) should be ignored. Note that this option
+sets the size of the transaction unit to one feature at a time, which may
+cause severe slowdown when inserting into databases.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-update
+Whether to open an existing output dataset in update mode.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-upsert
+Added in version 3.12.
+
+.sp
+Variant of \fI\%\-\-append\fP where the \fI\%OGRLayer::UpsertFeature()\fP
+operation is used to insert or update features instead of appending with
+\fI\%OGRLayer::CreateFeature()\fP\&.
+.sp
+This is currently implemented only in a few drivers:
+\fI\%GPKG \-\- GeoPackage vector\fP, \fI\%Elasticsearch: Geographically Encoded Objects for Elasticsearch\fP and \fI\%MongoDBv3\fP
+(drivers that implement upsert expose the \fI\%GDAL_DCAP_UPSERT\fP
+capability).
+.sp
+The upsert operation uses the FID of the input feature, when it is set
+(and the FID column name is not the empty string),
+as the key to update existing features. It is crucial to make sure that
+the FID in the source and target layers are consistent.
+.sp
+For the GPKG driver, it is also possible to upsert features whose FID is unset
+or non\-significant (the \fB\-\-unset\-fid\fP option of \fI\%gdal vector edit\fP
+can be used to ignore the FID from the source feature), when there is a
+UNIQUE column that is not the integer primary key.
+.UNINDENT
+.SH AUTHOR
+Dan Baston <dbaston@gmail.com>
+.SH COPYRIGHT
+1998-2026
+.\" Generated by docutils manpage writer.
+.