Changes between Version 8 and Version 9 of PostGIS_Raster_SoC_Idea_2012/Distance_Analysis_Tools/document

Timestamp:

Jul 12, 2012, 10:37:32 PM (12 years ago)

Author:

qliu

Comment:

—

PostGIS_Raster_SoC_Idea_2012/Distance_Analysis_Tools/document

@@ -20 +20 @@
 3.      Sometimes the resolution of the desired raster is so high that the whole raster coverage cannot be stored in one PostgreSQL row. The approach must be able to produce a tiled raster coverage stored into many rows.[[BR]]
 4.      Source geometries might be outside the extent of the desired raster.[[BR]]
-5.      The approach should work well in a number of situations: [[BR]]
-  a.    small number of sources vs low resolution raster[[BR]]
-  b.    small number of sources vs high resolution raster [[BR]]
-  c.    large number of sources vs low resolution [[BR]]
-  d.    large number of sources vs high resolution Large raster coverage[[BR]]
+5.      The approach should work well in a number of situations:
+  a.    small number of sources vs low resolution raster
+  b.    small number of sources vs high resolution raster
+  c.    large number of sources vs low resolution
+  d.    large number of sources vs high resolution Large raster coverage
 6.      The user can specify a maximum distance to the source. When the source is too far from the geometry it gets assigned a nodata value.[[BR]]
 7.      We want the implementation to be generic enough to be reused to implement more general interpolation methods like nearest neighbor, IDW, spline or kriging. Otherwise we want it to be generic enough to be reused to implement more general cost distance methods.[[BR]]