Changes between Version 51 and Version 52 of WKTRaster/GDALDriverSpecificationWorking


Ignore:
Timestamp:
08/01/13 02:29:06 (11 years ago)
Author:
tkump
Comment:

InDB rasters and GDALDataset creation.

Legend:

Unmodified
Added
Removed
Modified

  • WKTRaster/GDALDriverSpecificationWorking

    v51 v52  
    7575  * Open the dataset (create db connection)
    7676  * Determine, in a 1st, very fast query to the db, by looking in the raster_overview view, what lower resolution table are available for the requested raster table
    77   * Determine, in a 2nd, fast enough query to the db, the extent and the maximum number of bands of the requested raster be aggregating the extents of all the rasters. This takes about 1 second on 360000 tiles even if there is no index. '''[DONE]'''
     77  * Determine, in a 2nd, fast enough query to the db, the extent and the maximum number of bands of the requested raster be aggregating the extents of all the rasters. This takes about 1 second on 360000 tiles even if there is no index. '''[DONE]''' Is this really solved for the InDB rasters? As far what I have tested with the GDAL 1.10 and QGIS it's really slow to calculate values from the wktraster data column.
    7878  * Determine, in a 3rd, very fast query to the db, the pixel size & rotation, the band types and the nodata value for each band of ONLY ONE raster (LIMIT 1). The driver should assume those values will be the same for every other rasters in the table. If when fetching the other tiles, it realizes one does not, we must say that we do not support this arrangement. '''[DONE]'''
    7979