This is an automated email from the git hooks/post-receive script.

sebastic-guest pushed a commit to branch master
in repository postgis.

commit e7fb6bfd70630a941780406762db708fe5ff587d
Author: Bas Couwenberg <>
Date:   Fri Apr 4 17:08:20 2014 +0200

    Add man page for raster2pgsql.
 debian/changelog        |   2 +
 debian/postgis.manpages |   1 +
 debian/raster2pgsql.1   | 130 ++++++++++++++++++++++++++++++++++++++++++++++++
 3 files changed, 133 insertions(+)

diff --git a/debian/changelog b/debian/changelog
index 8d32d03..b8620fc 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -7,6 +7,8 @@ postgis (2.1.2+dfsg-1) UNRELEASED; urgency=low
   * Restructure control file with cme.
   * Add gbp.conf to use pristine-tar by default.
   * Add lintian override for untranslatable-debconf-templates false positive.
+  * Add man page for raster2pgsql.
+    (closes: #717307)
  -- Bas Couwenberg <>  Fri, 04 Apr 2014 15:36:30 +0200
diff --git a/debian/postgis.manpages b/debian/postgis.manpages
index c64b403..dd10bf5 100644
--- a/debian/postgis.manpages
+++ b/debian/postgis.manpages
@@ -1,3 +1,4 @@
diff --git a/debian/raster2pgsql.1 b/debian/raster2pgsql.1
new file mode 100644
index 0000000..799a380
--- /dev/null
+++ b/debian/raster2pgsql.1
@@ -0,0 +1,130 @@
+.\" DO NOT MODIFY THIS FILE!  It was generated by help2man 1.45.1.
+.TH RASTER2PGSQL "1" "April 2014" "raster2pgsql RELEASE: 2.1.2 
GDAL_VERSION=110 (r12389)" "User Commands"
+raster2pgsql \- loads GDAL supported raster formats into a PostGIS raster table
+raster2pgsql is a raster loader executable that loads GDAL supported raster 
formats into sql suitable for loading into a PostGIS raster table. It is 
capable of loading folders of raster files as well as creating overviews of 
+Since the raster2pgsql is compiled as part of PostGIS most often (unless you 
compile your own GDAL library), the raster types supported by the executable 
will be the same as those compiled in the GDAL dependency library. To get a 
list of raster types your particular raster2pgsql supports use the \-G switch. 
These should be the same as those provided by your PostGIS install documented 
here ST_GDALDrivers if you are using the same gdal library for both.
+raster2pgsql [<options>] <raster>[ <raster>[ ...]] [[<schema>.]<table>]
+Multiple rasters can also be specified using wildcards (*,?).
+\fB\-s\fR <srid> Set the raster's SRID. Defaults to 0. If SRID not
+provided or is 0, raster's metadata will be checked to
+determine an appropriate SRID.
+\fB\-b\fR <band> Index (1\-based) of band to extract from raster. For more
+than one band index, separate with comma (,). Ranges can be
+defined by separating with dash (\-). If unspecified, all bands
+of raster will be extracted.
+\fB\-t\fR <tile size> Cut raster into tiles to be inserted one per
+table row. <tile size> is expressed as WIDTHxHEIGHT.
+<tile size> can also be "auto" to allow the loader to compute
+an appropriate tile size using the first raster and applied to
+all rasters.
+\fB\-P\fR Pad right\-most and bottom\-most tiles to guarantee that all tiles
+have the same width and height.
+Register the raster as an out\-of\-db (filesystem) raster. Provided
+raster should have absolute path to the file
+(\fB\-d\fR|a|c|p) These are mutually exclusive options:
+Drops the table, then recreates it and populates
+it with current raster data.
+Appends raster into current table, must be
+exactly the same table schema.
+Creates a new table and populates it, this is the
+default if you do not specify any options.
+Prepare mode, only creates the table.
+\fB\-f\fR <column> Specify the name of the raster column
+Add a column with the filename of the raster.
+\fB\-n\fR <column> Specify the name of the filename column. Implies \fB\-F\fR.
+\fB\-l\fR <overview factor> Create overview of the raster. For more than
+one factor, separate with comma(,). Overview table name follows
+the pattern o_<overview factor>_<table>. Created overview is
+stored in the database and is not affected by \fB\-R\fR.
+Wrap PostgreSQL identifiers in quotes.
+Create a GIST spatial index on the raster column. The ANALYZE
+command will automatically be issued for the created index.
+Run VACUUM ANALYZE on the table of the raster column. Most
+useful when appending raster to existing table with \fB\-a\fR.
+Set the standard set of constraints on the raster
+column after the rasters are loaded. Some constraints may fail
+if one or more rasters violate the constraint.
+Disable setting the max extent constraint. Only applied if
+\fB\-C\fR flag is also used.
+Set the constraints (spatially unique and coverage tile) for
+regular blocking. Only applied if \fB\-C\fR flag is also used.
+\fB\-T\fR <tablespace> Specify the tablespace for the new table.
+Note that indices (including the primary key) will still use
+the default tablespace unless the \fB\-X\fR flag is also used.
+\fB\-X\fR <tablespace> Specify the tablespace for the table's new index.
+This applies to the primary key and the spatial index if
+the \fB\-I\fR flag is used.
+\fB\-N\fR <nodata> NODATA value to use on bands without a NODATA value.
+Skip NODATA value checks for each raster band.
+\fB\-E\fR <endian> Control endianness of generated binary output of
+raster. Use 0 for XDR and 1 for NDR (default). Only NDR
+is supported at this time.
+\fB\-V\fR <version> Specify version of output WKB format. Default
+is 0. Only 0 is supported at this time.
+Execute each statement individually, do not use a transaction.
+Use COPY statements instead of INSERT statements.
+Print the supported GDAL raster formats.
+Display the help screen.

Alioth's /usr/local/bin/git-commit-notice on 

Pkg-grass-devel mailing list

Reply via email to