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

package/dist/prebuilt/wasi-wasm32-st-release/share/man/man1/ogr2ogr.1

@@ -0,0 +1,1078 @@
+.\" 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 "OGR2OGR" "1" "Aug 18, 2026" "" "GDAL"
+.SH NAME
+ogr2ogr \- Converts simple features data between file formats.
+.SH SYNOPSIS
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.EX
+Usage: ogr2ogr [\-\-help] [\-\-long\-usage] [\-\-help\-general]
+               [\-of <output_format>] [\-dsco <NAME>=<VALUE>]...
+               [\-lco <NAME>=<VALUE>]...
+               [[\-append]|[\-upsert]|[\-overwrite]]
+               [\-update] [\-sql <statement>|@<filename>] [\-dialect <dialect>]
+               [\-spat <xmin> <ymin> <xmax> <ymax>]
+               [\-where <restricted_where>|@<filename>] [\-select <field_list>]
+               [\-nln <name>] [\-nlt <type>]... [\-s_srs <srs_def>]
+               [[\-a_srs <srs_def>]|[\-t_srs <srs_def>]]
+               <dst_dataset_name> <src_dataset_name> [<layer_name>]...
+
+Field related options:
+               [\-addfields] [\-relaxedFieldNameMatch]
+               [\-fieldTypeToString All|<type1>[,<type2>]...]
+               [\-mapFieldType <srctype>|All=<dsttype>[,<srctype2>=<dsttype2>]...]
+               [\-fieldmap <field_1>[,<field_2>]...] [\-splitlistfields]
+               [\-maxsubfields <n>] [\-emptyStrAsNull] [\-forceNullable]
+               [\-unsetFieldWidth] [\-unsetDefault] [\-resolveDomains]
+               [\-dateTimeTo UTC|UTC(+|\-)<HH>|UTC(+|\-)<HH>:<MM>] [\-noNativeData]
+
+Advanced geometry and SRS related options:
+               [\-dim layer_dim|2|XY|3|XYZ|XYM|XYZM] [\-s_coord_epoch <epoch>]
+               [\-a_coord_epoch <epoch>] [\-t_coord_epoch <epoch>]
+               [\-ct <pipeline_def>] [\-ct_opt <NAME>=<VALUE>]...
+               [\-spat_srs <srs_def>] [\-geomfield <name>]
+               [\-segmentize <max_dist>] [\-simplify <tolerance>] [\-makevalid]
+               [\-skipinvalid] [\-wrapdateline] [\-datelineoffset <val_in_degree>]
+               [\-clipsrc [<xmin> <ymin> <xmax> <ymax>]|<WKT>|<datasource>|spat_extent]
+               [\-clipsrcsql <sql_statement>] [\-clipsrclayer <layername>]
+               [\-clipsrcwhere <expression>]
+               [\-clipdst [<xmin> <ymin> <xmax> <ymax>]|<WKT>|<datasource>]
+               [\-clipdstsql <sql_statement>] [\-clipdstlayer <layername>]
+               [\-clipdstwhere <expression>] [\-explodecollections]
+               [\-zfield <name>]
+               [\-gcp <ungeoref_x> <ungeoref_y> <georef_x> <georef_y> [<elevation>]]...
+               [\-tps] [\-order 1|2|3] [\-xyRes <val>[ m|mm|deg]]
+               [\-zRes <val>[ m|mm]] [\-mRes <val>] [\-unsetCoordPrecision]
+
+Other options:
+               [\-\-quiet] [\-progress] [\-if <format>]... [\-oo <NAME>=<VALUE>]...
+               [\-doo <NAME>=<VALUE>]...
+               [\-fid <FID>] [\-preserve_fid] [\-unsetFid]
+               [[\-skipfailures]|[\-gt <n>|unlimited]]
+               [\-limit <nb_features>] [\-ds_transaction] [\-mo <NAME>=<VALUE>]...
+               [\-nomd]
+.EE
+.UNINDENT
+.UNINDENT
+.SH DESCRIPTION
+.sp
+\fBogr2ogr\fP 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.
+.sp
+\fBTIP:\fP
+.INDENT 0.0
+.INDENT 3.5
+Equivalent in new \(dqgdal\(dq command line interface:
+.INDENT 0.0
+.IP \(bu 2
+\fI\%gdal vector clip\fP for spatial subsetting
+.IP \(bu 2
+\fI\%gdal vector convert\fP for format translation
+.IP \(bu 2
+\fI\%gdal vector explode\-collections\fP to explode geometries of type collection
+.IP \(bu 2
+\fI\%gdal vector make\-valid\fP to fix geometry validity
+.IP \(bu 2
+\fI\%gdal vector reproject\fP for reprojection
+.IP \(bu 2
+\fI\%gdal vector segmentize\fP to segmentize geometries
+.IP \(bu 2
+\fI\%gdal vector select\fP to select a subset of fields
+.IP \(bu 2
+\fI\%gdal vector set\-field\-type\fP to change the type of an attribute field
+.IP \(bu 2
+\fI\%gdal vector set\-geom\-type\fP to change the type of a geometry field
+.IP \(bu 2
+\fI\%gdal vector simplify\fP to simplify geometries
+.IP \(bu 2
+\fI\%gdal vector sql\fP to run SQL query
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-help
+Show this help message and exit
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-\-help\-general
+Gives a brief usage message for the generic GDAL commandline options and exit.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-q, \-\-quiet
+Suppress progress messages and other non\-error output.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-if <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
+Added in version 3.2.
+
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-of <format_name>, \-f <format_name>
+Output file format name, e.g. \fBESRI Shapefile\fP, \fBMapInfo File\fP,
+\fBPostgreSQL\fP\&. If not specified, the format is guessed from the extension.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-append
+Append to existing layer instead of creating new. This option also enables
+\fI\%\-update\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-upsert
+Added in version 3.6.
+
+.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 is a \(dqsignificant\(dq (that is 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 (\fI\%\-unsetFid\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
+.INDENT 0.0
+.TP
+.B \-overwrite
+Delete the output layer and recreate it empty
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-update
+Open existing output datasource in update mode rather than trying to create
+a new one
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-select <field_list>
+Comma\-delimited list of fields from input layer to copy to the new layer.
+.sp
+Starting with GDAL 3.9, field names with spaces, commas or double\-quote
+should be surrounded with a starting and ending double\-quote character, and
+double\-quote characters in a field name should be escaped with backslash.
+.sp
+Depending on the shell used, this might require further quoting. For example,
+to select \fBregular_field\fP, \fBa_field_with space, and comma\fP and
+\fBa field with \(dq double quote\fP with a Unix shell:
+.INDENT 7.0
+.INDENT 3.5
+.sp
+.EX
+\-select \(dqregular_field,\e\(dqa_field_with space, and comma\e\(dq,\e\(dqa field with \e\e\e\(dq double quote\e\(dq\(dq
+.EE
+.UNINDENT
+.UNINDENT
+.sp
+A field is only selected once, even if mentioned several times in the list
+and if the input layer has duplicate field names.
+.sp
+Geometry fields can also be specified in the list.
+.sp
+All fields are selected when \-select is not specified. Specifying the
+empty string can be used to disable selecting any attribute field, and only
+keep geometries.
+.sp
+Note this setting cannot be used together with \fB\-append\fP\&. To control the
+selection of fields when appending to a layer, use \fB\-fieldmap\fP or \fB\-sql\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-progress
+Display progress on terminal. Only works if input layers have the \(dqfast
+feature count\(dq capability.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-sql <sql_statement>|@<filename>
+SQL statement to execute. The resulting table/layer will be saved to the
+output. The \fB@filename\fP syntax can be used to
+indicate that the content is in the pointed filename. (Cannot be used with \fI\%\-spat_srs\fP\&.)
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-dialect <dialect>
+SQL dialect. In some cases can be used to use the (unoptimized) \fI\%OGR SQL dialect\fP instead
+of the native SQL of an RDBMS by passing the \fBOGRSQL\fP dialect value.
+The \fI\%SQL SQLite dialect\fP dialect can be chosen with the \fBSQLITE\fP
+and \fBINDIRECT_SQLITE\fP dialect values, and this can be used with any datasource.
+(\fI\%\-dialect\fP is ignored with \fI\%\-where\fP\&. Use \fI\%\-sql\fP instead.)
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-where <restricted_where>|@<filename>
+Attribute query (like SQL WHERE). The \fB@filename\fP
+syntax can be used to indicate that the content is in the pointed filename.
+(\fI\%\-dialect\fP is ignored with \fI\%\-where\fP\&. Use \fI\%\-sql\fP instead.)
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-skipfailures
+Continue after a failure, skipping the failed feature. Note that this option
+overrides the value of \fI\%\-gt\fP to 1, which may
+cause severe slowdown when inserting into databases.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-spat <xmin> <ymin> <xmax> <ymax>
+spatial query extents, in the SRS of the source layer(s) (or the one
+specified with \fB\-spat_srs\fP). Only features whose geometry intersects the
+extents will be selected. The geometries will not be clipped unless
+\fB\-clipsrc\fP is specified.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-spat_srs <srs_def>
+Override spatial filter SRS. (Cannot be used with \fI\%\-sql\fP\&.)
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-geomfield <field>
+Name of the geometry field on which the spatial filter operates on.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-dsco <NAME>=<VALUE>
+Dataset creation option (format specific)
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-lco <NAME>=<VALUE>
+Layer creation option (format specific)
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-nln <name>
+Assign an alternate name to the new layer
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-nlt <type>
+Define the geometry type for the created layer. One of \fBNONE\fP,
+\fBGEOMETRY\fP, \fBPOINT\fP, \fBLINESTRING\fP, \fBPOLYGON\fP,
+\fBGEOMETRYCOLLECTION\fP, \fBMULTIPOINT\fP, \fBMULTIPOLYGON\fP,
+\fBMULTILINESTRING\fP, \fBCIRCULARSTRING\fP, \fBCOMPOUNDCURVE\fP,
+\fBCURVEPOLYGON\fP, \fBMULTICURVE\fP, and \fBMULTISURFACE\fP non\-linear geometry
+types. Add \fBZ\fP, \fBM\fP, or \fBZM\fP to the type name to specify coordinates
+with elevation, measure, or elevation and measure. \fBPROMOTE_TO_MULTI\fP 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.
+\fBCONVERT_TO_LINEAR\fP can be used to to convert non\-linear geometry types
+into linear geometry types by approximating them, and \fBCONVERT_TO_CURVE\fP to
+promote a non\-linear type to its generalized curve type (\fBPOLYGON\fP to
+\fBCURVEPOLYGON\fP, \fBMULTIPOLYGON\fP to \fBMULTISURFACE\fP, \fBLINESTRING\fP to
+\fBCOMPOUNDCURVE\fP, \fBMULTILINESTRING\fP to \fBMULTICURVE\fP). Starting with
+version 2.1 the type can be defined as measured (\(dq25D\(dq remains as an alias for
+single \(dqZ\(dq). Some forced geometry conversions may result in invalid
+geometries, for example when forcing conversion of multi\-part multipolygons
+with \fB\-nlt POLYGON\fP, the resulting polygon will break the Simple Features
+rules.
+.sp
+Starting with GDAL 3.0.5, \fB\-nlt CONVERT_TO_LINEAR\fP and \fB\-nlt PROMOTE_TO_MULTI\fP
+can be used simultaneously.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-dim <val>
+Force the coordinate dimension to val (valid values are \fBXY\fP, \fBXYZ\fP,
+\fBXYM\fP, and \fBXYZM\fP \- for backwards compatibility \fB2\fP is an alias for
+\fBXY\fP and \fB3\fP is an alias for \fBXYZ\fP). This affects both the layer
+geometry type, and feature geometries. The value can be set to \fBlayer_dim\fP
+to instruct feature geometries to be promoted to the coordinate dimension
+declared by the layer.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-a_srs <srs_def>
+Assign an output SRS, but without reprojecting (use \fI\%\-t_srs\fP
+to reproject)
+.sp
+The coordinate reference systems that can be passed are anything supported by the
+\fI\%OGRSpatialReference::SetFromUserInput()\fP 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.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-a_coord_epoch <epoch>
+Added in version 3.4.
+
+.sp
+Assign a coordinate epoch, linked with the output SRS. Useful when the
+output SRS is a dynamic CRS. Only taken into account if \fI\%\-a_srs\fP
+is used.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-t_srs <srs_def>
+Reproject/transform to this SRS on output, and assign it as output SRS.
+.sp
+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 \fI\%\-s_srs\fP
+.sp
+The coordinate reference systems that can be passed are anything supported by the
+\fI\%OGRSpatialReference::SetFromUserInput()\fP 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.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-t_coord_epoch <epoch>
+Added in version 3.4.
+
+.sp
+Assign a coordinate epoch, linked with the output SRS. Useful when the
+output SRS is a dynamic CRS. Only taken into account if \fI\%\-t_srs\fP
+is used. It is also mutually exclusive with  \fI\%\-a_coord_epoch\fP\&.
+.sp
+Before PROJ 9.4, \fI\%\-s_coord_epoch\fP and \fI\%\-t_coord_epoch\fP were
+mutually exclusive, due to lack of support for transformations between two dynamic CRS.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-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 \fI\%\-t_srs\fP
+to reproject.
+.sp
+The coordinate reference systems that can be passed are anything supported by the
+\fI\%OGRSpatialReference::SetFromUserInput()\fP 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.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-xyRes \(dq<val>[ m|mm|deg]\(dq
+Added in version 3.9.
+
+.sp
+Set/override the geometry X/Y coordinate resolution. If only a numeric value
+is specified, it is assumed to be expressed in the units of the target SRS.
+The m, mm or deg suffixes can be specified to indicate that the value must be
+interpreted as being in meter, millimeter or degree.
+.sp
+When specifying this option, the \fI\%OGRGeometry::SetPrecision()\fP
+method is run on geometries (that are not curves) before passing them to the
+output driver, to avoid generating invalid geometries due to the potentially
+reduced precision (unless the \fI\%OGR_APPLY_GEOM_SET_PRECISION\fP
+configuration option is set to \fBNO\fP)
+.sp
+If neither this option nor \fI\%\-unsetCoordPrecision\fP are specified, the
+coordinate resolution of the source layer, if available, is used.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-zRes \(dq<val>[ m|mm]\(dq
+Added in version 3.9.
+
+.sp
+Set/override the geometry Z coordinate resolution. If only a numeric value
+is specified, it is assumed to be expressed in the units of the target SRS.
+The m or mm suffixes can be specified to indicate that the value must be
+interpreted as being in meter or millimeter.
+If neither this option nor \fI\%\-unsetCoordPrecision\fP are specified, the
+coordinate resolution of the source layer, if available, is used.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-mRes <val>
+Added in version 3.9.
+
+.sp
+Set/override the geometry M coordinate resolution.
+If neither this option nor \fI\%\-unsetCoordPrecision\fP are specified, the
+coordinate resolution of the source layer, if available, is used.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-unsetCoordPrecision
+Added in version 3.9.
+
+.sp
+Prevent the geometry coordinate resolution from being set on target layer(s).
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-s_coord_epoch <epoch>
+Added in version 3.4.
+
+.sp
+Assign a coordinate epoch, linked with the source SRS. Useful when the
+source SRS is a dynamic CRS. Only taken into account if \fI\%\-s_srs\fP
+is used.
+.sp
+Before PROJ 9.4, \fI\%\-s_coord_epoch\fP and \fI\%\-t_coord_epoch\fP were
+mutually exclusive, due to lack of support for transformations between two dynamic CRS.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-ct <string>
+Added in version 3.0.
+
+.sp
+A PROJ string (single step operation or multiple step string starting with
++proj=pipeline), a WKT2 string describing a CoordinateOperation, or a
+\fI\%urn:ogc:def:coordinateOperation:EPSG::XXXX\fP URN overriding the default
+transformation from the source to the target CRS.
+.sp
+It must take into account the axis order of the source and target CRS, that
+is typically include a \fBstep proj=axisswap order=2,1\fP at the beginning of
+the pipeline if the source CRS has northing/easting axis order, and/or at
+the end of the pipeline if the target CRS has northing/easting axis order.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-ct_opt <NAME>=<VALUE>
+Added in version 3.11.
+
+.sp
+Specify a coordinate operation option that influences how PROJ selects
+coordinate operations when \fI\%\-ct\fP is \fInot\fP set.
+.sp
+The following options are available:
+.INDENT 7.0
+.IP \(bu 2
+\fBONLY_BEST\(ga\(ga=\(ga\(gaYES\fP/\fBNO\fP\&. By default (at least in the PROJ 9.x series), PROJ may use
+coordinate operations that are not the \(dqbest\(dq if resources
+(typically grids) needed to use them are missing. It will then
+fallback to other coordinate operations that have a lesser
+accuracy, for example using Helmert transformations, or in the
+absence of such operations, to ones with potential very rough
+accuracy, using \(dqballpark\(dq transformations (see
+\X'tty: link https://proj.org/glossary.html'\fI\%https://proj.org/glossary.html\fP\X'tty: link').
+When calling this method with YES, PROJ will only consider the
+\(dqbest\(dq operation, and error out (at Transform() time) if they
+cannot be used. This method may be used together with
+\fBALLOW_BALLPARK\(ga\(ga=\(ga\(gaNO\fP to only allow best operations that have a known
+accuracy. Note that this method has no effect on PROJ versions
+before 9.2. The default value for this option can be also set with
+the \fBPROJ_ONLY_BEST_DEFAULT\fP environment variable, or with the
+\fBonly_best_default\fP setting of proj.ini. Setting
+ONLY_BEST=YES/NO overrides such default value.
+.IP \(bu 2
+\fBALLOW_BALLPARK\(ga\(ga=\(ga\(gaYES\fP/\fBNO\fP\&. Whether ballpark coordinate operations are
+allowed. Default is YES.
+.IP \(bu 2
+\fBWARN_ABOUT_DIFFERENT_COORD_OP\(ga\(ga=\(ga\(gaYES\fP/\fBNO\fP\&. Can be set to NO to avoid GDAL
+warning when different coordinate operations are used to transform the
+different geometries of the dataset (or part of the same geometry).
+Default is YES.
+.UNINDENT
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-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 \fB\-unsetFid\fP\&.
+This option is not compatible with \fB\-explodecollections\fP\&.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-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 \(aqfid\(aq is a special field recognized by OGR SQL. So,
+\fI\-where \(dqfid in (1,3,5)\(dq\fP would select features 1, 3 and 5.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-limit <nb_features>
+Limit the number of features per layer.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-oo <NAME>=<VALUE>
+Dataset open option (format specific).
+.sp
+If a driver supports the \fBOGR_SCHEMA\fP open option, it can be used to
+partially or completely override the auto\-detected schema (i.e. which
+fields are read, with which types, subtypes, length, precision etc.)
+of the dataset.
+.sp
+The value of this option is a JSON string or a path to a JSON file that
+complies with the \X'tty: link https://raw.githubusercontent.com/OSGeo/gdal/refs/heads/master/ogr/data/ogr_fields_override.schema.json'\fI\%OGR_SCHEMA open option schema definition\fP\X'tty: link'
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-doo <NAME>=<VALUE>
+Destination dataset open option (format specific), only valid in \-update mode.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-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. \fBn\fP can be set to unlimited to load the data into a single
+transaction.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-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.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-clipsrc [<xmin> <ymin> <xmax> <ymax>]|WKT|<datasource>|spat_extent
+Clip geometries (before potential reprojection) to one of the following:
+.INDENT 7.0
+.IP \(bu 2
+the specified bounding box (expressed in source SRS)
+.IP \(bu 2
+a WKT geometry (POLYGON or MULTIPOLYGON expressed in source SRS)
+.IP \(bu 2
+one or more geometries selected from a datasource
+.IP \(bu 2
+the spatial extent of the \-spat option if you use the spat_extent keyword.
+.UNINDENT
+.sp
+When specifying a datasource, you will generally want to use \-clipsrc in
+combination of the \-clipsrclayer, \-clipsrcwhere or \-clipsrcsql options.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-clipsrcsql <sql_statement>
+Select desired geometries from the source clip datasource using an SQL query.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-clipsrclayer <layername>
+Select the named layer from the source clip datasource.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-clipsrcwhere <expression>
+Restrict desired geometries from the source clip layer based on an attribute query.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-clipdst [<xmin> <ymin> <xmax> <ymax>]|<WKT>|<datasource>
+Clip geometries (after potential reprojection) to one of the following:
+.INDENT 7.0
+.IP \(bu 2
+the specified bounding box (expressed in destination SRS)
+.IP \(bu 2
+a WKT geometry (POLYGON or MULTIPOLYGON expressed in destination SRS)
+.IP \(bu 2
+one or more geometries selected from a datasource
+.UNINDENT
+.sp
+When specifying a datasource, you will generally want to use \-clipdst in
+combination with the \-clipdstlayer, \-clipdstwhere or \-clipdstsql options.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-clipdstsql <sql_statement>
+Select desired geometries from the destination clip datasource using an SQL query.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-clipdstlayer <layername>
+Select the named layer from the destination clip datasource.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-clipdstwhere <expression>
+Restrict desired geometries from the destination clip layer based on an attribute query.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-wrapdateline
+Split geometries crossing the dateline meridian (long. = +/\- 180deg)
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-datelineoffset
+Offset from dateline in degrees (default long. = +/\- 10deg, geometries
+within 170deg to \-170deg will be split)
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-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.
+.sp
+The specified value of this option is the tolerance used to merge
+consecutive points of the output geometry using the
+\fI\%OGRGeometry::SimplifyPreserveTopology()\fP method
+The unit of the distance is in
+georeferenced units of the source vector dataset.
+This option is applied before the reprojection implied by \fI\%\-t_srs\fP
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-segmentize <max_dist>
+The specified value of this option is the maximum distance between two
+consecutive points of the output geometry before intermediate points are added.
+The unit of the distance is georeferenced units of the source layer.
+This option is applied before the reprojection implied by \fI\%\-t_srs\fP
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-makevalid
+Run the \fI\%OGRGeometry::MakeValid()\fP operation, followed by
+\fI\%OGRGeometryFactory::removeLowerDimensionSubGeoms()\fP, on geometries
+to ensure they are valid regarding the rules of the Simple Features specification.
+.sp
+Added in version 3.1: (requires GEOS)
+
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-skipinvalid
+Run the \fI\%OGRGeometry::IsValid()\fP operation on geometries to check if
+they are valid regarding the rules of the Simple Features specification.
+If they are not, the feature is skipped. This check is done after all other
+geometry operations.
+.sp
+Added in version 3.10: (requires GEOS)
+
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-fieldTypeToString All|<type1>[,<type2>]...
+Converts any field of the specified type to a field of type string in the
+destination layer. Valid types are : \fBInteger\fP, \fBInteger64\fP, \fBReal\fP, \fBString\fP,
+\fBDate\fP, \fBTime\fP, \fBDateTime\fP, \fBBinary\fP, \fBIntegerList\fP, \fBInteger64List\fP, \fBRealList\fP,
+\fBStringList\fP\&. Special value \fBAll\fP 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.
+Also note that this option is without effects on fields whose presence and
+type is hard\-coded in the output driver (e.g KML, GPX).
+For an alternative way to manipulate field types earlier in the process while they
+are read from the input dataset see \fI\%\-oo\fP \fBOGR_SCHEMA\fP (only available
+for a limited set of formats).
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-mapFieldType {<srctype>|All=<dsttype>[,<srctype2>=<dsttype2>]...}
+Converts any field of the specified type to another type. Valid types are :
+\fBInteger\fP, \fBInteger64\fP, \fBReal\fP, \fBString\fP,
+\fBDate\fP, \fBTime\fP, \fBDateTime\fP, \fBBinary\fP, \fBIntegerList\fP, \fBInteger64List\fP, \fBRealList\fP,
+\fBStringList\fP\&. Types can also include
+subtype between parenthesis, such as \fBInteger(Boolean)\fP, \fBReal(Float32)\fP, ...
+Special value \fBAll\fP 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.
+Also note that this option is without effects on fields whose presence and
+type is hard\-coded in the output driver (e.g KML, GPX).
+For an alternative way to manipulate field types earlier in the process while they
+are read from the input dataset see \fI\%\-oo\fP \fBOGR_SCHEMA\fP (only available
+for a limited set of formats).
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-dateTimeTo {UTC|UTC(+|\-)<HH>|UTC(+|\-)<HH>:<MM>}
+Added in version 3.7.
+
+.sp
+Converts date time values from the timezone specified in the source value
+to the target timezone expressed with \fI\%\-dateTimeTo\fP\&.
+Datetime whose timezone is unknown or localtime are not modified.
+.sp
+HH must be in the [0,14] range and MM=00, 15, 30 or 45.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-unsetFieldWidth
+Set field width and precision to 0.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-splitlistfields
+Split fields of type StringList, RealList or IntegerList into as many
+fields of type String, Real or Integer as necessary.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-maxsubfields <val>
+To be combined with \fB\-splitlistfields\fP to limit the number of subfields
+created for each split field.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-explodecollections
+Produce one feature for each geometry in any kind of geometry collection in
+the source file, applied after any \fB\-sql\fP option. This options is not
+compatible with \fB\-preserve_fid\fP but \fB\-sql \(dqSELECT fid AS original_fid, * FROM ...\(dq\fP
+can be used to store the original FID if needed.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-zfield <field_name>
+Uses the specified field to fill the Z coordinate of geometries.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-gcp <ungeoref_x> <ungeoref_y> <georef_x> <georef_y> [<elevation>]
+Use the indicated ground control point to compute a coordinate transformation.
+The transformation method can be selected by specifying the \fI\%\-order\fP
+or \fI\%\-tps\fP options.
+Note that unlike raster tools such as gdal_edit or gdal_translate, GCPs
+are not added to the output dataset.
+This option may be provided multiple times to provide a set of GCPs (at
+least 2 GCPs are needed).
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-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.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-tps
+Force use of thin plate spline transformer based on available GCPs.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-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 \(aqidentity\(aq setting
+to specify that the fields should be transferred by using the same order.
+This setting should be used along with the \fB\-append\fP setting.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-addfields
+This is a specialized version of \fB\-append\fP\&. Contrary to \fB\-append\fP,
+\fB\-addfields\fP 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\(aqt 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.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-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.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-forceNullable
+Do not propagate not\-nullable constraints to target layer if they exist in
+source layer.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-unsetDefault
+Do not propagate default field values to target layer if they exist in
+source layer.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-unsetFid
+Can be specified to prevent the name of the source FID column and source
+feature IDs from being reused for the target layer. This option can for
+example be useful if selecting source features with a ORDER BY clause.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-emptyStrAsNull
+Added in version 3.3.
+
+.sp
+Treat empty string values as null.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-resolveDomains
+Added in version 3.3.
+
+.sp
+When this is specified, any selected field that is linked to a coded field
+domain will be accompanied by an additional field (\fB{dstfield}_resolved\fP),
+that will contain the description of the coded value.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-nomd
+To disable copying of metadata from source dataset and layers into target
+dataset and layers, when supported by output driver.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-mo <META\-TAG>=<VALUE>
+Passes a metadata key and value to set on the output dataset, when
+supported by output driver.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B \-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.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B <dst_dataset_name>
+Output dataset name.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B <src_dataset_name>
+Source dataset name.
+.UNINDENT
+.INDENT 0.0
+.TP
+.B <layer_name>
+One or more source layer names to copy to the output dataset. If no layer
+names are passed, then all source layers are copied.
+.UNINDENT
+.SH PERFORMANCE HINTS
+.sp
+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.
+.sp
+For PostgreSQL, the \fI\%PG_USE_COPY\fP config option can be set to YES for a
+significant insertion performance boost. See the PG driver documentation page.
+.sp
+More generally, consult the documentation page of the input and output drivers
+for performance hints.
+.SH KNOWN ISSUES
+.sp
+Starting with GDAL 3.8, ogr2ogr uses internally an Arrow array based API
+(cf \fI\%RFC 86: Column\-oriented read API for vector layers\fP) for some source formats (in particular GeoPackage or FlatGeoBuf),
+and for the most basic types of operations, to improve performance.
+This substantial change in the ogr2ogr internal logic has required a number of
+fixes throughout the GDAL 3.8.x bugfix releases to fully stabilize it, and we believe
+most issues are resolved with GDAL 3.9.
+If you hit errors not met with earlier GDAL versions, you may specify
+\fB\-\-config OGR2OGR_USE_ARROW_API NO\fP on the ogr2ogr command line to opt for the
+classic algorithm using an iterative feature based approach. If that flag is
+needed with GDAL >= 3.9, please file an issue on the
+\X'tty: link https://github.com/OSGeo/gdal/issues'\fI\%GDAL issue tracker\fP\X'tty: link'\&.
+.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 C API
+.sp
+This utility is also callable from C with \fI\%GDALVectorTranslate()\fP\&.
+.SH EXAMPLES
+.SS Example 1: Appending to an existing layer
+.INDENT 0.0
+.INDENT 3.5
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.EX
+ogr2ogr \-append \-f PostgreSQL PG:dbname=warmerda abc.tab
+.EE
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.SS Example 2: Clip input layer with a bounding box
+.INDENT 0.0
+.INDENT 3.5
+The bounding box is specified as \fB<xmin> <ymin> <xmax> <ymax>\fP:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.EX
+ogr2ogr \-spat \-13.931 34.886 46.23 74.12 output.gpkg natural_earth_vector.gpkg
+.EE
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.SS Example 3: Filter Features by a \-where clause
+.INDENT 0.0
+.INDENT 3.5
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.EX
+ogr2ogr \-where \(dq\e\(dqPOP_EST\e\(dq < 1000000\(dq \e
+  output.gpkg natural_earth_vector.gpkg ne_10m_admin_0_countries
+.EE
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.sp
+More examples are given in the individual format pages.
+.SH ADVANCED EXAMPLES
+.SS Example 4: Reprojecting from ETRS_1989_LAEA_52N_10E to EPSG:4326 and clipping to a bounding box
+.INDENT 0.0
+.INDENT 3.5
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.EX
+ogr2ogr \-wrapdateline \-t_srs EPSG:4326 \-clipdst \-5 40 15 55 france_4326.shp europe_laea.shp
+.EE
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.SS Example 5: Outputting geometries with the CSV driver.
+.sp
+By default this driver does not preserve geometries upon layer creation.
+An explicit layer creation option is needed:
+.INDENT 0.0
+.INDENT 3.5
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.EX
+ogr2ogr \-lco GEOMETRY=AS_XYZ TrackWaypoint.csv TrackWaypoint.kml
+.EE
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.SS Example 6: Extracting only geometries
+.sp
+There are different situations, depending if the input layer has a named geometry
+column, or not. First check, with \fBogrinfo\fP if there is a reported geometry column.
+.INDENT 0.0
+.INDENT 3.5
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.EX
+$ ogrinfo \-so CadNSDI.gdb.zip PLSSPoint | grep \(aqGeometry Column\(aq
+Geometry Column = SHAPE
+.EE
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.sp
+In that situation where the input format is a FileGeodatabase, it is called SHAPE
+and can thus be referenced directly in a SELECT statement.
+.INDENT 0.0
+.INDENT 3.5
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.EX
+ogr2ogr \-sql \(dqSELECT SHAPE FROM PLSSPoint\(dq \e
+  \-lco GEOMETRY=AS_XY \-f CSV /vsistdout/ CadNSDI.gdb.zip
+.EE
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.sp
+For a shapefile with a unnamed geometry column, \fB_ogr_geometry_\fP can be used as
+a special name to designate the implicit geometry column, when using the default
+\fI\%OGR SQL\fP dialect. The name begins with
+an underscore and SQL syntax requires that it must appear between double quotes.
+In addition the command line interpreter may require that double quotes are
+escaped and the final SELECT statement could look like:
+.INDENT 0.0
+.INDENT 3.5
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.EX
+ogr2ogr \-sql \(dqSELECT \e\(dq_ogr_geometry_\e\(dq FROM PLSSPoint\(dq \e
+  \-lco GEOMETRY=AS_XY \-f CSV /vsistdout/ CadNSDI.shp
+.EE
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.sp
+If using the \fI\%SQL SQLite\fP dialect, the special geometry
+name is \fBgeometry\fP when the source geometry column has no name.
+.INDENT 0.0
+.INDENT 3.5
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.EX
+ogr2ogr \-sql \(dqSELECT geometry FROM PLSSPoint\(dq \-dialect SQLite \e
+  \-lco GEOMETRY=AS_XY \-f CSV /vsistdout/ CadNSDI.shp
+.EE
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.SH AUTHOR
+Frank Warmerdam <warmerdam@pobox.com>, Silke Reimer <silke@intevation.de>
+.SH COPYRIGHT
+1998-2026
+.\" Generated by docutils manpage writer.
+.