Changes between Version 2 and Version 3 of WKTRaster/GDALDriverSpecificationWorking

Timestamp:

02/17/11 13:57:31 (14 years ago)

Author:

pracine

Comment:

—

WKTRaster/GDALDriverSpecificationWorking

@@ -18 +18 @@
 The driver is:
  * Able to read in-db evenly blocked rasters (all blocks with same size)
+
  * Able to read in-db one-row-rasters:
+
    - If the table really has more than one row: using -where clause in connection string
+
    - If the table has more than one row: the table must have been marked as "regularly blocked table", with -k in loader
- * Able to manage two working modes:
+
+ * Able to produce generate two kind of raster object based on two modes:
+
    - ONE_RASTER_PER_ROW ('mode = 1' in connection string, or nothing): The default mode. Each table row is considered as an independent raster. If the table required has more than one row, and no -where clause has been specified in connection string, all the table rows will be considered as reported as Subdatasets. Unless you specify the other working mode
+
    - ONE_RASTER_PER_TABLE ('mode = 2' in connection string): Each table is considered as a raster coverage, and each row is a raster tile. 
+
  * Too slow (Reads the entire table metadata for constructing the [http://www.gdal.org/classGDALDataset.html GDALDataset object], and needs one server round per [http://www.gdal.org/classGDALRasterBand.html GDALRasterBand::IReadBlock] call)