Changes between Version 20 and Version 21 of WKTRaster/GDALDriverSpecificationWorking


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

Legend:

Unmodified
Added
Removed
Modified
  • WKTRaster/GDALDriverSpecificationWorking

    v20 v21  
    9393Currently, the natural block oriented r/w method is the one implemented for the driver. This is a limitation for 2 reasons:
    9494  * Obviously, it only fits one raster arrangement
    95   * Each ReadBlock call forces a new server round, constructing a Box and getting the raster row that contains it. This can be really slow, in case of huge raster coverages (question raised in ticket #497 too).
     95  * Each !ReadBlock call forces a new server round, constructing a Box and getting the raster row that contains it. This can be really slow, in case of huge raster coverages (question raised in ticket #497 too).
    9696
    9797'''Open question''': How to get the needed metadata in case of ONE_RASTER_PER_TABLE arrangement. As argued in ticket #497, executing ''ST_Extent'' or ''ST_Metadata'' without limits over a big table can be a really heavy process.