ogrtindex – ogrtindex creates a tileindex
ogrtindex [-lnum n]… [-lname name]… [-f output_format] [-write_absolute_path] [-skip_different_projection] output_dataset src_dataset…
The ogrtindex program can be used to create a tileindex – a file
containing a list of the identities of a bunch of other files along
with there spatial extents. This is primarily intended to be used with
MapServer for tiled access to layers using the OGR connection type.
Add layer number ‘n’ from each source file in the tile index.
Add the layer named ‘name’ from each source file in the tile index.
Select an output format name. The default is to create a shapefile.
The name to use for the dataset name. Defaults to LOCATION.
Filenames are written with absolute paths
Only layers with same projection ref as layers already inserted in
the tileindex will be inserted.
If no -lnum or -lname arguments are given it is assumed that all layers
in source datasets should be added to the tile index as independent
If the tile index already exists it will be appended to, otherwise it
will be created.
It is a flaw of the current ogrtindex program that no attempt is made
to copy the coordinate system definition from the source datasets to
the tile index (as is expected by MapServer when PROJECTION AUTO is in
This example would create a shapefile (tindex.shp) containing a tile
index of the BL2000_LINK layers in all the NTF files in the wrk
% ogrtindex tindex.shp wrk/*.NTF
Frank Warmerdam firstname.lastname@example.org, Silke Reimer email@example.com
GDAL Tue Apr 5 2016 ogrtindex