Changes between Version 149 and Version 150 of WKTRaster/PlanningAndFunding

Timestamp:

Jul 24, 2012, 2:49:39 PM (12 years ago)

Author:

pracine

Comment:

—

WKTRaster/PlanningAndFunding

@@ -74 +74 @@
  * Write a "Best practices for storing raster in PostGIS"
  * Write a "Best practices for third party applications wishing to read raster stored in PostGIS"
- * Break up RASTER_mapAlgebra2 so that the main engine is in rt_core instead of rt_pg.  This is needed for C-based aggregate functions that run against MapAlgebra.
- * Optimized version of two rasters ST_MapAlgebra setting pixel areas when possible instead of just pixels by pixels
+ * Work on ST_MapAlgebra()
+  * Break up RASTER_mapAlgebra2 so that the main engine is in rt_core instead of rt_pg.  This is needed for C-based aggregate functions that run against MapAlgebra.
+  * Optimized version of two rasters ST_MapAlgebra setting pixel areas when possible instead of just pixels by pixels
+  * MultiBand MapAlgebra(raster, raster)
+  * ST_MapAlgebraFctNbg working on a tiled coverage
  * Multi-band ST_AddBand()
  * Different variant of ST_SetValues()
  * C version of the ST_Union(raster) aggregate
  * ST_UnionToRaster() and ST_BurnToRaster()
- * MultiBand MapAlgebra(raster, raster)
  * ST_CreateOverview(), ST_IsRegularlyTiled(), ST_HasOverlaps(), ST_HasGaps(), ST_HasTileSameSize(), ST_HasTileAligned()
  * ST_Retile()