Changes between Version 183 and Version 184 of WKTRaster/SpecificationWorking03

Timestamp:

Nov 29, 2011, 2:44:20 PM (12 years ago)

Author:

pracine

Comment:

—

WKTRaster/SpecificationWorking03

@@ -539 +539 @@
 The major changes concerning the raster_column table are as follow:
 
- * There will be a flexible ApplyRasterConstraint() function trying to apply a set of constraint on a table. As for any constraint, the constraints will be successfully applied only when all the rows of the table fulfil the constraint. The list of potential constraint applied by the C loader (using the ApplyRasterConstraint function) and hence the list of column available in the raster_column view will be: srid int, scalex float8, scaley float8, width int, height int, alignment (align on a upperleft x and y), numberofband int, pixeltypes text[], nodatavalues float[] in addition to the 'r_table_catalog', 'r_table_schema', 'r_table_name' and 'r_column' columns.
+ * There will be a flexible !ApplyRasterConstraint() function trying to apply a set of constraint on a table. As for any constraint, the constraints will be successfully applied only when all the rows of the table fulfil the constraint. The list of potential constraint applied by the C loader (using the !ApplyRasterConstraint function) and hence the list of column available in the raster_column view will be: srid int, scalex float8, scaley float8, width int, height int, alignment (align on a upperleft x and y), numberofband int, pixeltypes text[], nodatavalues float[] in addition to the 'r_table_catalog', 'r_table_schema', 'r_table_name' and 'r_column' columns.
 
 There is still discussion to know if extent as a geometry should be added to this list. Comments are welcomes.
@@ -559 +559 @@
  * We are working on a new C importer to get rid of any Python, Numpy and Python GDAL binding dependency.
 
- * This new loader will attempt to apply the constraint on the loaded table using the ApplyRasterConstraint()function. There will be an option to NOT trying to apply the constraint for applications not wishing to use the raster_column table. 
+ * This new loader will attempt to apply the constraint on the loaded table using the !ApplyRasterConstraint()function. There will be an option to NOT trying to apply the constraint for applications not wishing to use the raster_column table. 
 
  * This new importer will NOT have any option to create the raster_overview view, nor to create overview tables. We think that it is more important to be able to create overview in SQL as a post process query so overviews can be updated/recreated when rasters tiles are edited, added or deleted.