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

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

@@ -0,0 +1,341 @@
+.\" 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-CLEAN-COVERAGE" "1" "Aug 18, 2026" "" "GDAL"
+.SH NAME
+gdal-vector-clean-coverage \- Remove gaps and overlaps from a polygon dataset
+.sp
+Added in version 3.12.
+
+.SH SYNOPSIS
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.EX
+Usage: gdal vector clean\-coverage [OPTIONS] <INPUT> <OUTPUT>
+
+Alter polygon boundaries to make shared edges identical, removing gaps and overlaps
+
+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]
+  \-\-active\-layer <ACTIVE\-LAYER>                        Set active layer (if not specified, all)
+  \-\-snapping\-distance <SNAPPING\-DISTANCE>              Distance tolerance for snapping nodes
+  \-\-merge\-strategy <MERGE\-STRATEGY>                    Algorithm to assign overlaps to neighboring polygons. MERGE\-STRATEGY=longest\-border|max\-area|min\-area|min\-index
+  \-\-maximum\-gap\-width <MAXIMUM\-GAP\-WIDTH>              Maximum width of a gap to be closed
+
+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 clean\-coverage\fP modifies boundaries of a
+polygonal dataset, such that gaps and overlaps between features are removed and
+shared edges are defined using the same vertices. The resulting dataset will
+form a polygonal coverage that can be used with \fI\%gdal vector simplify\-coverage\fP\&.
+.sp
+This command can also be used as a step of \fI\%gdal vector pipeline\fP, although it
+requires loading the entire dataset into memory at once.
+.sp
+\fBNOTE:\fP
+.INDENT 0.0
+.INDENT 3.5
+This command requires a GDAL build against the GEOS library (version 3.14 or greater).
+.UNINDENT
+.UNINDENT
+.SH GDALG OUTPUT (ON-THE-FLY / STREAMED DATASET)
+.sp
+This program supports serializing the command line as a JSON file using the \fBGDALG\fP output format.
+The resulting file can then be opened as a vector dataset using the
+\fI\%GDALG: GDAL Streamed Algorithm\fP driver, and apply the specified pipeline in a on\-the\-fly /
+streamed way.
+.sp
+\fBNOTE:\fP
+.INDENT 0.0
+.INDENT 3.5
+However this algorithm is not natively streaming compatible. Consequently a
+in\-memory temporary dataset will be generated, which may cause significant processing
+time at opening.
+.UNINDENT
+.UNINDENT
+.SH PROGRAM-SPECIFIC OPTIONS
+.INDENT 0.0
+.TP
+.B \-\-input\-layer
+Specifies the name of the layer to process. By default, all layers will be processed.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-maximum\-gap\-width <MAXIMUM\-GAP\-WIDTH>
+Defines the largest area that should be considered a \(dqgap\(dq and merged into
+an adjacent polygon. Gaps will be merged unless a circle with radius larger
+than the specified tolerance can be inscribed within the gap. The default
+maximum gap width is zero, meaning that gaps are not closed.
+.INDENT 7.0
+.INDENT 2.5
+[image]
+Polygon dataset before cleaning (left), after cleaning with default parameters (center),
+and after cleaning with \fB\-\-maximum\-gap\-width 1\fP (right)..UNINDENT
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-merge\-strategy <MERGE\-STRATEGY>
+Method by which overlaps or gaps should be added to adjacent polygons. Options include:
+.INDENT 7.0
+.IP \(bu 2
+longest\-border (default): add areas to the polygon with which the longest border is shared
+.IP \(bu 2
+max\-area: add areas to the largest adjacent polygon
+.IP \(bu 2
+min\-area: add areas to the smallest adjacent polygon
+.IP \(bu 2
+min\-index: add areas to the adjacent polygon that was read first
+.UNINDENT
+.INDENT 7.0
+.INDENT 2.5
+[image]
+Polygon dataset before cleaning (left), after cleaning with \(dqlongest\-border\(dq merge strategy (center) and \fB\-\-merge\-strategy max\-area\fP (right)..UNINDENT
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-output\-layer
+Specifies the name of the layer to which features will be written.
+By default, the names of the output layers will be the same as the
+names of the input layers.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-snapping\-distance <SNAPPING\-DISTANCE>
+Controls the node snapping step, when nearby vertices are snapped together.
+By default, an automatic snapping distance is determined based on an
+analysis of the input. Set to zero to turn off all snapping.
+.INDENT 7.0
+.INDENT 2.5
+[image]
+Polygon dataset before cleaning (left), after cleaning with default snapping distance (center), and a more aggressive \fB\-\-snapping\-distance 0.2\fP (right). Note the movement in the
+upper\-left corner of the polygon on the right..UNINDENT
+.UNINDENT
+.UNINDENT
+.SH STANDARD OPTIONS
+.INDENT 0.0
+.TP
+.B \-\-active\-layer <ACTIVE\-LAYER>
+Set the active layer. When it is specified, only the layer specified by
+its name will be subject to the processing. Other layers will be not
+modified.
+If this option is not specified, all layers will be subject to the
+processing.
+.UNINDENT
+.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 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 EXAMPLES
+.SS Example 1: Create and then simplify a polygonal coverage
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.EX
+$ gdal vector pipeline read ne_10m_admin_0_countries.shp ! \e
+                       make\-valid ! \e
+                       clean\-coverage ! \e
+                       simplify\-coverage \-\-tolerance 1 ! \e
+                       write countries.shp
+.EE
+.UNINDENT
+.UNINDENT
+.SH AUTHOR
+Dan Baston <dbaston@gmail.com>
+.SH COPYRIGHT
+1998-2026
+.\" Generated by docutils manpage writer.
+.

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

@@ -0,0 +1,358 @@
+.\" 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-CLIP" "1" "Aug 18, 2026" "" "GDAL"
+.SH NAME
+gdal-vector-clip \- Clip a vector dataset
+.sp
+Added in version 3.11.
+
+.SH SYNOPSIS
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.EX
+Usage: gdal vector clip [OPTIONS] <INPUT> <OUTPUT>
+
+Clip a vector dataset.
+
+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]
+  \-\-active\-layer <ACTIVE\-LAYER>                        Set active layer (if not specified, all)
+  \-\-bbox <BBOX>                                        Clipping bounding box as xmin,ymin,xmax,ymax
+                                                       Mutually exclusive with \-\-geometry, \-\-like
+  \-\-bbox\-crs <BBOX\-CRS>                                CRS of clipping bounding box
+  \-\-geometry <GEOMETRY>                                Clipping geometry (WKT or GeoJSON)
+                                                       Mutually exclusive with \-\-bbox, \-\-like
+  \-\-geometry\-crs <GEOMETRY\-CRS>                        CRS of clipping geometry
+  \-\-like <DATASET>                                     Dataset to use as a template for bounds
+                                                       Mutually exclusive with \-\-bbox, \-\-geometry
+  \-\-like\-sql <SELECT\-STATEMENT>                        SELECT statement to run on the \(aqlike\(aq dataset
+                                                       Mutually exclusive with \-\-like\-where
+  \-\-like\-layer <LAYER\-NAME>                            Name of the layer of the \(aqlike\(aq dataset
+  \-\-like\-where <WHERE\-EXPRESSION>                      WHERE SQL clause to run on the \(aqlike\(aq dataset
+                                                       Mutually exclusive with \-\-like\-sql
+
+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 clip\fP can be used to clip a vector dataset using
+georeferenced coordinates.
+.sp
+Either \fI\%\-\-bbox\fP, \fI\%\-\-geometry\fP or \fI\%\-\-like\fP must be specified.
+.sp
+\fBclip\fP can also be used as a step of \fI\%gdal vector pipeline\fP\&.
+.sp
+Clipping sometimes results in geometries that are of a type not compatible
+with the geometry type. This program splits multi\-geometries or geometry
+collections into their parts for layers that are of a single geometry type
+(such as point, linestring, polygon) and only keeps the parts that are of that
+type. It also promotes single geometry types (e.g. polygons) to multi
+geometry types (e.g. multi\-polygons). If the user needs to preserve any type of
+intersection, the layer must use the \fBwkbUnknown\fP (any geometry) type.
+.SH PROGRAM-SPECIFIC OPTIONS
+.INDENT 0.0
+.TP
+.B \-\-bbox <xmin>,<ymin>,<xmax>,<ymax>
+Bounds to which to clip the dataset. They are assumed to be in the CRS of
+the input dataset, unless \fI\%\-\-bbox\-crs\fP is specified.
+The X and Y axis are the \(dqGIS friendly ones\(dq, that is X is longitude or easting,
+and Y is latitude or northing.
+Mutually exclusive with \fI\%\-\-like\fP and \fI\%\-\-geometry\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-bbox\-crs <CRS>
+CRS in which the <xmin>,<ymin>,<xmax>,<ymax> values of \fI\%\-\-bbox\fP
+are expressed. If not specified, it is assumed to be the CRS of the input
+dataset.
+Note that specifying \-\-bbox\-crs does not involve doing vector reprojection.
+Instead, the bounds are reprojected from the bbox\-crs to the CRS of the
+input dataset.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-geometry <WKT_or_GeoJSON>
+Geometry as a WKT or GeoJSON string to which to clip the dataset.
+If the input geometry is GeoJSON, its CRS is assumed to be WGS84, unless there is
+a CRS defined in the GeoJSON geometry or \fI\%\-\-geometry\-crs\fP is specified.
+If the input geometry is WKT, its CRS is assumed to be the one of the input dataset,
+unless \fI\%\-\-geometry\-crs\fP is specified.
+The X and Y axis are the \(dqGIS friendly ones\(dq, that is X is longitude or easting,
+and Y is latitude or northing.
+Mutually exclusive with \fI\%\-\-bbox\fP and \fI\%\-\-like\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-geometry\-crs <CRS>
+CRS in which the coordinates values of \fI\%\-\-geometry\fP
+are expressed. If not specified, it is assumed to be the CRS of the input
+dataset.
+Note that specifying \-\-geometry\-crs does not involve doing vector reprojection.
+Instead, the bounds are reprojected from the geometry\-crs to the CRS of the
+input dataset.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-like <DATASET>
+Vector or raster dataset to use as a template for bounds.
+If the specified dataset is a raster, its rectangular bounds are used as
+the clipping geometry.
+If the specified dataset is a vector dataset, its polygonal geometries
+are unioned together to form the clipping geometry (beware that the result
+union might not be perfect if there are gaps between individual polygon
+features). If several layers are present,
+\fI\%\-\-like\-sql\fP or \fI\%\-\-like\-layer\fP must be specified.
+Mutually exclusive with \fI\%\-\-bbox\fP and \fI\%\-\-geometry\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-like\-layer <LAYER\-NAME>
+Select the named layer from the vector clip dataset.
+Mutually exclusive with \fI\%\-\-like\-sql\fP
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-like\-sql <SELECT\-STATEMENT>
+Select desired geometries from the vector clip dataset using an SQL query.
+e.g \fBSELECT geom FROM my_layer WHERE country = \(aqFrance\(aq\fP\&.
+Mutually exclusive with \fI\%\-\-like\-layer\fP and \fI\%\-\-like\-where\fP
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-like\-where <WHERE\-EXPRESSION>
+Restrict desired geometries from vector clip dataset layer based on an attribute query.
+e.g \fBcountry = \(aqFrance\(aq\fP\&.
+.UNINDENT
+.SH STANDARD OPTIONS
+.INDENT 0.0
+.TP
+.B \-\-active\-layer <ACTIVE\-LAYER>
+Set the active layer. When it is specified, only the layer specified by
+its name will be subject to the processing. Other layers will be not
+modified.
+If this option is not specified, all layers will be subject to the
+processing.
+.UNINDENT
+.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 \-\-input\-layer <INPUT\-LAYER>
+Specifies the name of one or more layers to process. By default, all layers will be processed. To read and write all layers but only
+process a subset, use \fI\%\-\-active\-layer\fP\&.
+.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\-layer <NAME>
+Specifies the name of the layer to which features will be written. If not
+specified, output layer names will be the same as input layer names.
+.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 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 EXAMPLES
+.SS Example 1: Clip a GeoPackage file to the bounding box from longitude 2, latitude 49, to longitude 3, latitude 50 in WGS 84
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.EX
+$ gdal vector clip \-\-bbox=2,49,3,50 \-\-bbox\-crs=EPSG:4326 in.gpkg out.gpkg \-\-overwrite
+.EE
+.UNINDENT
+.UNINDENT
+.SH AUTHOR
+Even Rouault <even.rouault@spatialys.com>
+.SH COPYRIGHT
+1998-2026
+.\" Generated by docutils manpage writer.
+.