Changes between Version 32 and Version 33 of PostGIS_Raster_SoC_Idea_2012/Distance_Analysis_Tools/document

Timestamp:

Jul 15, 2012, 8:19:46 PM (12 years ago)

Author:

qliu

Comment:

—

PostGIS_Raster_SoC_Idea_2012/Distance_Analysis_Tools/document

@@ -91 +91 @@
 {{{
 Comments from Mentor:
-Not really. If the raster HAS to be in the extent of the point coverage, as stated in the cons, it means it could not correspond to the arbitrary alignment/extent of an existing coverage. This is probably the main reason the third approach is preferable to the TIN one.
+Not really. If the raster HAS to be in the extent of the point coverage, as stated in the cons, it means 
+it could not correspond to the arbitrary alignment/extent of an existing coverage. This is probably 
+the main reason the third approach is preferable to the TIN one.
 }}}
 
@@ -116 +118 @@
 AS $$
 BEGIN
-      SELECT ST_Distance (ST_GeomFromText('POINT(columnx rowy)',ST_SRID(rast)), ST_Transform(sourcegeom, Find_SRID(dbschema,sourcetable,sourcegeomcolumn), ST_SRID(rast)) as eucliean_dist
+      SELECT ST_Distance (ST_GeomFromText('POINT(columnx rowy)',ST_SRID(rast)), 
+ST_Transform(sourcegeom, Find_SRID(dbschema,sourcetable,sourcegeomcolumn), ST_SRID(rast)) as eucliean_dist
       FROM sourcetable
       ORDER BY $1 <-> $2
@@ -168 +171 @@
 {{{
 #!sql
-ST_EuclideanDistance(text dbschema, text sourcetable, text sourcegeomcolumn, double precision scalex, double precision scaley, double precision gridx, double precision gridy, text pixeltype, double precision nodataval=0, double precision skewx=0, double precision skewy=0)
+ST_EuclideanDistance(text dbschema, text sourcetable, text sourcegeomcolumn, 
+                                 double precision scalex, double precision scaley, 
+                                 double precision gridx, double precision gridy, text pixeltype, 
+                                 double precision nodataval=0, double precision skewx=0, double precision skewy=0)
 }}}