1
.TH "pgsql2shp" "1" "" "" "PostGIS"
4
pgsql2shp - postgis to shapefile dumper
7
pgsql2shp [\fIoptions\fR] \fIdatabase\fR [\fIschema\fR\fB.\fR]\fItable\fR
9
pgsql2shp [\fIoptions\fR] \fIdatabase\fR \fIquery\fR
12
The pgsql2shp table dumper connects directly to the database and converts a table (possibly created by user query) into a shape file. It is compatible with
13
all versions of PostGIS.
16
The commandline options are:
19
\fB\-f\fR <\fIfilename\fR>
20
Write the output to a particular filename.
23
\fB\-h\fR <\fIhost\fR>
24
The database host to connect to.
27
\fB\-p\fR <\fIport\fR>
28
The port to connect to on the database host.
32
\fB\-P\fR <\fIpassword\fR>
33
The password to use when connecting to the database.
37
\fB\-u\fR <\fIuser\fR>
38
The username to use when connecting to the database.
41
\fB\-g\fR <\fIgeometry column\fR>
42
In the case of tables with multiple geometry columns, the geometry column to use when writing the shape file.
46
Use a binary cursor. When used on pre\-1.0.0 PostGIS versions this will reduce the likelihood of coordinate drift due to conversion to and from WKT format.
47
Coordinate drifts will not occur with PostGIS 1.0.0 and newer versions.
48
It will be slightly faster, but might fail if any NON\-gemetry column lacks
53
Raw mode. Do not drop the gid field, or escape column names.
57
For backward compatibility: write a 3\-dimensional shape file when dumping from old (pre\-1.0.0) postgis databases (the default is to write a 2\-dimensional shape file in that case). Starting from postgis\-1.0.0+, dimensions are fully encoded.
62
Originally written by Jeff Lounsbury <jeffloun@refractions.net>.
63
Improved and maintained by Sandro Santilli <strk@refractions.net>.
65
This application uses functionality from shapelib 1.2.9
66
by Frank Warmerdam <warmerda@gdal.velocet.ca> to write to ESRI Shape files.
added
removed
doc/man/pgsql2shp.1
