1OGRTINDEX(1) GDAL OGRTINDEX(1)
2
3
4
6 ogrtindex - Creates a tileindex.
7
9 ogrtindex [-lnum n]... [-lname name]... [-f output_format]
10 [-write_absolute_path] [-skip_different_projection]
11 [-t_srs target_srs]
12 [-src_srs_name field_name] [-src_srs_format [AUTO|WKT|EPSG|PROJ]
13 [-accept_different_schemas]
14 <output_dataset> <src_dataset>...
15
17 ogrtindex program can be used to create a tileindex - a file containing
18 a list of the identities of a bunch of other files along with their
19 spatial extents. This is primarily intended to be used with MapServer
20 for tiled access to layers using the OGR connection type.
21
22 -lnum <n>
23 Add layer number n from each source file in the tile index.
24
25 -lname <name>
26 Add the layer named name from each source file in the tile in‐
27 dex.
28
29 -f <output_format>
30 Select an output format name. The default is to create a shape‐
31 file.
32
33 -tileindex <field_name>
34 The name to use for the dataset name. Defaults to LOCATION.
35
36 -write_absolute_path
37 Filenames are written with absolute paths
38
39 -skip_different_projection
40 Only layers with same projection ref as layers already inserted
41 in the tileindex will be inserted.
42
43 -t_srs <target_srs>
44 Extent of input files will be transformed to the desired target
45 coordinate reference system. Using this option generates files
46 that are not compatible with MapServer < 7.2. Default creates
47 simple rectangular polygons in the same coordinate reference
48 system as the input vector layers.
49
50 New in version 2.2.0.
51
52
53 -src_srs_name <field_name>
54 The name of the field to store the SRS of each tile. This field
55 name can be used as the value of the TILESRS keyword in
56 MapServer >= 7.2.
57
58 New in version 2.2.0.
59
60
61 -src_srs_format <format>
62 The format in which the SRS of each tile must be written.
63 Available formats are: AUTO, WKT, EPSG, PROJ.
64
65 New in version 2.2.0.
66
67
68 -accept_different_schemas
69 By default ogrtindex checks that all layers inserted into the
70 index have the same attribute schemas. If you specify this op‐
71 tion, this test will be disabled. Be aware that resulting index
72 may be incompatible with MapServer!
73
74 If no -lnum or -lname arguments are given it is assumed that all layers
75 in source datasets should be added to the tile index as independent
76 records.
77
78 If the tile index already exists it will be appended to, otherwise it
79 will be created.
80
82 This example would create a shapefile (tindex.shp) containing a tile
83 index of the BL2000_LINK layers in all the NTF files in the wrk direc‐
84 tory:
85
86 ogrtindex tindex.shp wrk/*.NTF 1069148.900,419873.100 1069147.500,419870.200
87 1069146.400,419862.100 1069143.000,419860 1069142,419854.900
88 1069138.600,419850 1069135,419848.800 1069134.100,419843
89 1069130,419836.200 1069127.600,419824.600 1069123.800,419820.200
90 1069126.900,419815.500 1069126.900,419808.200 1069116.500,419798.700
91 1069117.600,419794.100 1069115.100,419796.300 1069109.100,419801.800
92 1069106.800,419805.000 1069107.300)
93
95 Frank Warmerdam <warmerdam@pobox.com>, Silke Reimer <silke@inteva‐
96 tion.de>
97
99 1998-2023
100
101
102
103
104 Oct 30, 2023 OGRTINDEX(1)