Changes between Version 49 and Version 50 of WKTRaster/GDALDriverSpecificationWorking


Ignore:
Timestamp:
07/28/12 09:29:28 (12 years ago)
Author:
jorgearevalo
Comment:

Question answered

Legend:

Unmodified
Added
Removed
Modified

  • WKTRaster/GDALDriverSpecificationWorking

    v49 v50  
    8686  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?
    8787
     88    Jorge: The driver looks for the requested table. This is the higher resolution version of the raster, and the driver works with that table, unless the user asks for a lower resolution. This happens, for example, when the user specify -outsize option in [http://www.gdal.org/gdal_translate.html gdal_translate]. The R/W GDAL functions include a buffer with the needed size to store the data requested with the resolution asked. If, by default, you use the lower resolution table, regardless the user's desire, you must implement decimation by overwritting the R/W GDAL functions. In general, you shouldn't implement decimation (it shouldn't be necessary)
     89
    8890----
    8991=== Topic: !Reading/Writing raster data ===