Changes between Version 29 and Version 30 of WKTRaster/GDALDriverSpecificationWorking


Ignore:
Timestamp:
Feb 17, 2011, 3:56:14 PM (13 years ago)
Author:
pracine
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • WKTRaster/GDALDriverSpecificationWorking

    v29 v30  
    132132  If there is only one row fetched and the metadata of this raster fits the required tile metadata (meaning we are querying based on the natural block size)
    133133
    134    just copy the values as a block (memcopy) (is this possible? Should we have, Isn't there a ST_Bytea() SQL function?)
     134     just copy the values as a block (memcopy) (is this possible? Should we have, Isn't there a ST_Bytea() SQL function?)
    135135       
    136136  If not iterate on the required tile
    137     copy pixel values one by one from each raster fetched (that means if there is overlaps, only the pixels of the last raster fetched is burned. We can enhace this later by providing a BLENDING_MODE with the driver)
     137
     138     copy pixel values one by one from each raster fetched (that means if there is overlaps, only the pixels of the last raster fetched is burned. We can enhace this later by providing a BLENDING_MODE with the driver)
    138139     
    139140