1gdal_retile(1)              General Commands Manual             gdal_retile(1)
2
3
4

NAME

6       gdal_retileRetiles a set of tiles and/or build tiled pyramid levels.
7

SYNOPSIS

9       gdal_retile.py [-v] [-co NAME=VALUE]* [-of out_format] [-ps pixelWidth pixelHeight]
10                      [-overlap val_in_pixel]
11                      [-ot  {Byte/Int16/UInt16/UInt32/Int32/Float32/Float64/
12                             CInt16/CInt32/CFloat32/CFloat64}]'
13                      [ -tileIndex tileIndexName [-tileIndexField tileIndexFieldName]]
14                      [ -csv fileName [-csvDelim delimiter]]
15                      [-s_srs srs_def]  [-pyramidOnly]
16                      [-r {near/bilinear/cubic/cubicspline/lanczos}]
17                      -levels numberoflevels
18                      [-useDirForEachRow]
19                      -targetDir TileDirectory input_files.fi
20

DESCRIPTION

22       This utility will retile a set of input tile(s). All the input tile(s)
23       must be georeferenced in the same coordinate system and have a matching
24       number of bands. Optionally pyramid levels are generated. It is
25       possible to generate shape file(s) for the tiled output.
26
27       If your number of input tiles exhausts the command line buffer, use the
28       general --optfile option
29
30       -targetDir directory:
31           The directory where the tile result is created. Pyramids are stored
32           in sub-directories numbered from 1. Created tile names have a
33           numbering schema and contain the name of the source tiles(s)
34
35       -of format:
36           Output format, defaults to GeoTIFF (GTiff).
37
38       -co NAME=VALUE:
39           Creation option for output file. Multiple options can be specified.
40           See format specific documentation for legal creation options for
41           each format
42
43       -ot datatype:
44           Force the output image bands to have a specific type. Use type
45           names (i.e. Byte, Int16,...)
46
47       -ps pixelsize_x pixelsize_y:
48           Pixel size to be used for the output file. If not specified, 256 x
49           256 is the default
50
51       -overlap val_in_pixel:
52           (GDAL >= 2.2) Overlap in pixels between consecutive tiles. If not
53           specified, 0 is the default
54
55       -levels numberOfLevels:
56           Number of pyramids levels to build.
57
58       -v:
59           Generate verbose output of tile operations as they are done.
60
61       -pyramidOnly:
62           No retiling, build only the pyramids
63
64       -r algorithm:
65           Resampling algorithm, default is near
66
67       -s_srs srs_def:
68           Source spatial reference to use. The coordinate systems that can be
69           passed are anything supported by the
70           OGRSpatialReference.SetFromUserInput() call, which includes EPSG,
71           PCS, and GCSes (i.e. EPSG:4296), PROJ.4 declarations (as above), or
72           the name of a .prj file containing well known text. If no srs_def
73           is given, the srs_def of the source tiles is used (if there is
74           any). The srs_def will be propagated to created tiles (if possible)
75           and to the optional shape file(s)
76
77       -tileIndex tileIndexName:
78           The name of shape file containing the result tile(s) index
79
80       -tileIndexField tileIndexFieldName:
81           The name of the attribute containing the tile name
82
83       -csv csvFileName:
84           The name of the csv file containing the tile(s) georeferencing
85           information. The file contains 5 columns:
86           tilename,minx,maxx,miny,maxy
87
88       -csvDelim column delimiter:
89           The column delimiter used in the CSV file, default value is a
90           semicolon ';'
91
92       -useDirForEachRow:
93           Normally the tiles of the base image are stored as described in
94           -targetDir. For large images, some file systems have performance
95           problems if the number of files in a directory is to big, causing
96           gdal_retile not to finish in reasonable time. Using this parameter
97           creates a different output structure. The tiles of the base image
98           are stored in a sub-directory called 0, the pyramids in sub-
99           directories numbered 1,2,.... Within each of these directories
100           another level of sub-directories is created, numbered from 0...n,
101           depending of how many tile rows are needed for each level. Finally,
102           a directory contains only the tiles for one row for a specific
103           level. For large images a performance improvement of a factor N
104           could be achieved.
105
106       NOTE: gdal_retile.py is a Python script, and will only work if GDAL was
107       built with Python support.
108

AUTHORS

110       Christian Mueller christian.mueller@nvoe.at
111
112
113
114GDAL                            Tue Mar 3 2020                  gdal_retile(1)
Impressum