1GDAL_RETILE(1)                       GDAL                       GDAL_RETILE(1)
2
3
4

NAME

6       gdal_retile - Retiles 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] [-resume]
19                         -targetDir TileDirectory input_files
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  pos‐
25       sible 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
32              stored in  sub-directories   numbered   from   1.  Created  tile
33              names have a numbering schema and contain the name of the source
34              tiles(s)
35
36       -of <format>
37              Select the output format. Starting with GDAL 2.3, if not  speci‐
38              fied,  the  format is guessed from the extension (previously was
39              GTiff). Use the short format name.
40
41       -co <NAME=VALUE>
42              Many formats have one or more optional creation options that can
43              be  used  to control particulars about the file created. For in‐
44              stance, the GeoTIFF driver supports creation options to  control
45              compression, and whether the file should be tiled.
46
47              The  creation  options available vary by format driver, and some
48              simple formats have no creation options at all. A  list  of  op‐
49              tions  supported  for  a format can be listed with the --formats
50              command line option but the documentation for the format is  the
51              definitive  source  of  information  on driver creation options.
52              See Raster drivers format specific documentation for legal  cre‐
53              ation options for each format.
54
55       -ot <type>
56              Force  the  output image bands to have a specific data type sup‐
57              ported by the driver, which may be one of the  following:  Byte,
58              UInt16,  Int16, UInt32, Int32, Float32, Float64, CInt16, CInt32,
59              CFloat32 or CFloat64.
60
61       -ps <pixelsize_x> <pixelsize_y>
62              Pixel size to be used for the output file.   If  not  specified,
63              256 x 256 is the default
64
65       -overlap< <val_in_pixel>
66              Overlap in pixels between consecutive tiles. If not specified, 0
67              is the default
68
69              New in version 2.2.
70
71
72       -levels <numberOfLevels>
73              Number of pyramids levels to build.
74
75       -v     Generate verbose output of tile operations as they are done.
76
77       -pyramidOnly
78              No retiling, build only the pyramids
79
80       -r <algorithm>
81              Resampling algorithm, default is near
82
83       -s_srs <srs_def>
84              Source spatial reference to use. The  coordinate  systems   that
85              can  be passed  are  anything  supported by the OGRSpatialRefer‐
86              ence.SetFromUserInput()  call, which  includes  EPSG,  PCS,  and
87              GCSes  (i.e.  EPSG:4296), PROJ.4 declarations (as above), or the
88              name of a .prj file containing well known text.  If  no  srs_def
89              is   given,   the srs_def  of the source tiles is used (if there
90              is any).  The srs_def will be propagated to  created  tiles  (if
91              possible) and  to  the  optional shape file(s)
92
93       -tileIndex <tileIndexName>
94              The name of shape file containing the result tile(s) index
95
96       -tileIndexField <tileIndexFieldName>
97              The name of the attribute containing the tile name
98
99       -csv <csvFileName>
100              The  name  of the csv file containing the tile(s) georeferencing
101              information.    The   file    contains    5    columns:    tile‐
102              name,minx,maxx,miny,maxy
103
104       -csvDelim <column delimiter>
105              The  column  delimiter  used in the CSV file, default value is a
106              semicolon ";"
107
108       -useDirForEachRow
109              Normally the tiles of the base image are stored as described  in
110              -targetDir.   For  large  images, some file systems have perfor‐
111              mance problems if the number of files in a directory is to  big,
112              causing  gdal_retile  not  to  finish in reasonable time.  Using
113              this parameter creates a different output structure.  The  tiles
114              of  the  base  image are stored in a sub-directory called 0, the
115              pyramids in sub-directories numbered 1,2,....   Within  each  of
116              these  directories  another level of sub-directories is created,
117              numbered from 0...n, depending of how many tile rows are  needed
118              for each level. Finally, a directory contains only the tiles for
119              one row for a specific level. For large images a performance im‐
120              provement of a factor N could be achieved.
121
122       -resume
123              Resume mode. Generate only missing files.
124
125       NOTE:
126          gdal_retile.py  is  a  Python script, and will only work if GDAL was
127          built with Python support.
128

AUTHOR

130       Christian Mueller <christian.mueller@nvoe.at>
131
133       1998-2022
134
135
136
137
138                                 Sep 02, 2022                   GDAL_RETILE(1)
Impressum