Changes between Version 45 and Version 46 of WKTRaster/GDALDriverSpecificationWorking


Ignore:
Timestamp:
04/16/12 03:48:30 (13 years ago)
Author:
pracine
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • WKTRaster/GDALDriverSpecificationWorking

    v45 v46  
    114114'''Open Question''': If in the first query we find a lower resolution table, does the rest of the work must be performed with this lower resolution table? At least these 3 queries, until we want to read the actual raster data to burn it into the buffer. The queries should be faster in an overview table, but the pixel size will not be the same using an overview table instead the normal resolution table. And you don't read from overviews unless you want to implement decimation because your buffer size is different from your raster size. Am I right?
    115115
     116  Pierre: Yes to the first question. This is why we query the overview table first. Yes you're right: I guest the driver must be demanding for a lower resolution only when a specific pixel size is requested from an application. right? Otherwise it request only the highest resolution one or all of them (in the case of gdal_translate for example) right? Hos does the driver knows if he has to produce only a specific resolution, only the best one or all of them?
     117
    116118----
    117119=== Topic: !Reading/Writing raster data ===