Changes between Version 20 and Version 21 of WKTRaster/GDALDriverSpecificationWorking

Timestamp:

02/17/11 14:47:14 (14 years ago)

Author:

pracine

Comment:

—

WKTRaster/GDALDriverSpecificationWorking

@@ -93 +93 @@
 Currently, the natural block oriented r/w method is the one implemented for the driver. This is a limitation for 2 reasons:
   * Obviously, it only fits one raster arrangement
-  * 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). 
+  * 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). 
 
 '''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.