GDAL的OGR工具ogr2ogr使用参数说明

sqlite转tab

ogr2ogr -f ‘MapInfo File’ output.tab -a_srs wgs84 -lco encoding=gbk -nln $table input.db -sql ‘$sql’

tab转pg

ogr2ogr -append -f ‘PostgreSQL’ PG:’dbname=$db user=$user port=$port host=$host ‘ -a_srs WGS84 GBK:input.tab -nln $table

sqlite转pg

ogr2ogr -append -f ‘PostgreSQL’ PG:’host=$host dbname=$db user=$user port=$port’ input.db -a_srs WGS84 -lco GEOMETRY_NAME=shape –config PG_USE_COPY YES -lco GEOM_TYPE=geometry -a_srs wgs84 -sql ‘$sql’ -nln $table

pg转sqlite

ogr2ogr -append -f SQLite output.db -dsco SPATIALITE=NO -lco FORMAT=WKT -nln $table PG:’host=$host dbname=$db user=$user port=$port’ -sql ‘$sql’

数据转换
(1)MapInfo ==> ESRI Shape

[postgres@localhost ~]$ ogr2ogr -f “ESRI Shapefile” mydata.shp mydata.tab

(2)ESRI Shape ==>MapInfo

[postgres@localhost ~]$ ogr2ogr -f “MapInfo File” tabsites.tab sites.shp

(3)MapInfo ==> PostGIS

[postgres@localhost ~]$ ogr2ogr -f “PostgreSQL” PG:”host=localhost user=postgres dbname=postgis password=123456″

(4)postgis==>ESRI Shapefile

[postgres@localhost ~]$ ogr2ogr -f “ESRI Shapefile” mydata.shp PG:”host=localhost dbname=postgis user=postgres password=123456″ “mytable”

(5)PostGIS ==> KML

[postgres@localhost ~]$ ogr2ogr -f “KML” neighborhoods.kml PG:”host=localhost dbname=postgis user=postgres password=123456″ -sql “select gid,name,the_geom from neighborhoods”

(6)批量转换
将postgis中所有的表都导出到mydatadump文件夹下，导出格式是ESRI Shapefile

[postgres@localhost ~]$  ogr2ogr -f “ESRI Shapefile” mydatadump PG:”host=myhost user=myloginname dbname=mydbname password=mypassword”

部分导出，将指定的表导出到mydatadump中，格式为ESRI Shapefile

[postgres@localhost ~]$ ogr2ogr -f “ESRI Shapefile” mydatadump PG:”host=myhost user=myloginname dbname=mydbname password=mypassword” neighborhood parcels

(7)ESRI GeoDatabase (*.mdb) ==>PostGIS

[postgres@localhost ~]$ ogr2ogr -f “PostgreSQL” PG:”host=localhost user=someuser dbname=somedb password=somepassword port=5432″ C:\GISData\Geonames.mdb -a_srs EPSG:26986

导入指定的featureclass，重投影，重命名geometry列

[postgres@localhost ~]$ ogr2ogr -f “PostgreSQL” PG:”host=localhost user=someuser dbname=somedb”

/home/postgres/Data/Geonames.mdb GEONAMES_ANNO_HYDRO -a_srs EPSG: 26986 -t_srs EPSG:4269 -nln ma_hydro -lco GEOMETRY_NAME=the_geom_4269

(8)ESRI Shapefile ==>MySQL

[postgres@localhost ~]$ ogr2ogr -f “MySQL” MYSQL:”mydb,host=myhost,user=mylogin,password=mypassword,port=3306″ -nln “world” -a_srs “EPSG:4326″ path/to/world_adm0.shp

(9)Non-spatial Data ==>PostgreSQL

[postgres@localhost ~]$  ogr2ogr -f “PostgreSQL” PG:”host=myserver user=myusername dbname=mydbname password=mypassword” sometable.dbf -nln “sometable”

下面是如何将shp和tab文件导入到postgis数据库中的命令方式

[postgres@localhost ~]$ ogr2ogr -f PostgreSQL PG:”host=localhost dbname=postgis user=postgres password=850315″ sites.shp

[postgres@localhost ~]$ ogr2ogr -f PostgreSQL PG:”host=localhost dbname=postgis user=postgres password=850315″ mytabfile.tab

通过 -nln指定导入数据库中的表名，而不是默认的文件名作为表名

[postgres@localhost ~]$ ogr2ogr -f “PostgreSQL” PG:”host=myhost user=myloginname dbname=mydbname password=mypassword” mytabfile.tab -nln newtablename

通过 -a_srs 选项指定输出的投影

[postgres@localhost ~]$ ogr2ogr -f “PostgreSQL” -a_srs “EPSG:2249″ PG:”host=myhost user=myloginname dbname=mydbname password=mypassword” mytabfile.tab

通过-sql 选项后面的SQL语句对postgis中的数据经行筛选后到处到shp文件中

ogr2ogr -f “ESRI Shapefile” mydata.shp PG:”host=myhost user=myloginname dbname=mydbname password=mypassword” -sql “SELECT name, the_geom FROM neighborhoods”

可以通过ogrinfo命令来查看元数据

[postgres@localhost ~]$ ogrinfo sites.shp

official site:

http://www.gdal.org/ogr2ogr.html

converts simple features data between file formats

SYNOPSIS

Usage:

Usage: ogr2ogr [--help-general] [-skipfailures] [-append] [-update]
               [-select field_list] [-where restricted_where] 
               [-progress] [-sql <sql statement>] [-dialect dialect]
               [-preserve_fid] [-fid FID]
               [-spat xmin ymin xmax ymax] [-geomfield field]
               [-a_srs srs_def] [-t_srs srs_def] [-s_srs srs_def]
               [-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]
               [-dim 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]]
               [-addfields]
               [-fieldTypeToString All|(type1[,type2]*)] [-unsetFieldWidth]
               [-fieldmap identity | index1[,index2]*]
               [-splitlistfields] [-maxsubfields val]
               [-explodecollections] [-zfield field_name]
               [-gcp pixel line easting northing [elevation]]* [-order n | -tps]

DESCRIPTION

This program can be used to convert simple features data between file formats performing various operations during the process such as spatial or attribute selections, reducing the set of attributes, setting the output coordinate system or even
reprojecting the features during translation.

-f format_name:

output file format name (default is ESRI Shapefile), some possible values are:

     -f "ESRI Shapefile"
     -f "TIGER"
     -f "MapInfo File"
     -f "GML"
     -f "PostgreSQL"
	 

-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.) Starting with OGR 1.11, geometry fields can also be specified in the list.

-progress:

(starting with GDAL 1.7.0) 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.

-dialect dialect:

SQL dialect. In some cases can be used to use (unoptimized) OGR SQL instead of the native SQL of an RDBMS by passing OGRSQL. Starting with GDAL 1.10, the “SQLITE” dialect can also be used with any datasource.

-where restricted_where:

Attribute query (like SQL WHERE)

-skipfailures:

Continue after a failure, skipping the failed feature.

-spat xmin ymin xmax ymax:

spatial query extents. Only features whose geometry intersects the extents will be selected. The geometries will not be clipped unless -clipsrc is specified

-geomfield field:

(OGR >= 1.11) 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 or MULTILINESTRING. And CIRCULARSTRING, COMPOUNDCURVE, CURVEPOLYGON, MULTICURVE and MULTISURFACE for GDAL 2.0
non-linear geometry types. Add “25D” to the name to get 2.5D versions. Starting with GDAL 1.10, 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 usefull when converting shapefiles to PostGIS (and other target drivers) that implements strict checks for geometry type. Starting with GDAL 2.0, CONVERT_TO_LINEAR can be used to to convert non-linear geometries types into linear
geometries by approximating them.

-dim val:

(starting with GDAL 1.10) Force the coordinate dimension to val (valid values are 2 or 3). This affects both the layer geometry type, and feature geometries. Starting with GDAL 1.11, the value can be set to “layer_dim” to instruct feature geometries to
be promoted to the coordinate dimension declared by the layer.

-a_srs srs_def:

Assign an output SRS

-t_srs srs_def:

Reproject/transform to this SRS on output

-s_srs srs_def:

Override source SRS

-preserve_fid:

Use the FID of the source features instead of letting the output driver to automatically assign a new one.

-fid fid:

If provided, only the feature with this feature id will be reported. 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.

Srs_def can be a full WKT definition (hard to escape properly), or a well known definition (ie. EPSG:4326) or a file with a WKT definition.

% ogr2ogr -update -append -f PostgreSQL PG:dbname=warmerda abc.tab

% ogr2ogr -wrapdateline -t_srs EPSG:4326 -clipdst -5 40 15 55 france_4326.shp europe_laea.shp

% ogr2ogr -append -fieldmap 2,-1,4 dst.shp src.shp