A GDAL tile index is an OGR-readable data source of boundary information. PDAL provides a similar concept for PDAL-readable point cloud data. You can use the tindex application to generate tile index files in any format that OGR supports writing. Once you have the tile index, you can then use the readers.tindex driver to automatically merge and query the data described by the tiles.

Basic Example

Given a tile index that was generated with the following scenario:

pdal tindex index.sqlite \
    "/Users/hobu/dev/git/pdal/test/data/las/interesting.las" \
    -f "SQLite" \
    --lyr_name "pdal" \
    --t_srs "EPSG:4326"

Use the following Pipeline example to read and automatically merge the data.

      "filter_srs":"+proj=lcc +lat_1=43 +lat_2=45.5 +lat_0=41.75 +lon_0=-120.5 +x_0=399999.9999999999 +y_0=0 +ellps=GRS80 +units=ft +no_defs",
      "where":"location LIKE \'%nteresting.las%\'",
      "polygon":"POLYGON ((635629.85000000 848999.70000000, 635629.85000000 853535.43000000, 638982.55000000 853535.43000000, 638982.55000000 848999.70000000, 635629.85000000 848999.70000000))"


OGROpen’able raster file to read [Required]
The OGR layer name for the data source to use to fetch the tile index information.
The column in the layer that provides the SRS information for the file. Use this if you wish to override or set coordinate system information for files.
The column name that defines the file location for the tile index file. [Default: location]
OGR SQL to use to define the tile index layer.
A 2D box to pre-filter the tile index. If it is set, it will override any wkt option.
A geometry to pre-filter the tile index using OGR
Reproject the layer SRS, otherwise default to the tile index layer’s SRS.
Transforms any wkt or boundary option to this coordinate system before filtering or reading data.
OGR SQL filter clause to use on the layer. It only works in combination with tile index layers that are defined with lyr_name
OGR SQL dialect to use when querying tile index layer [Default: OGRSQL]