Changes between Version 33 and Version 34 of PostGIS_Raster_SoC_Idea_2012/Distance_Analysis_Tools/document
- Timestamp:
- Jul 15, 2012, 8:20:47 PM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
PostGIS_Raster_SoC_Idea_2012/Distance_Analysis_Tools/document
v33 v34 180 180 {{{ 181 181 #!sql 182 ST_EuclideanDistance(text dbschema, text sourcetable, text sourcegeomcolumn, geometry geom, integer width, integer height, double precision gridx, double precision gridy, text pixeltype, double precision nodataval=0, double precision skewx=0, double precision skewy=0) 182 ST_EuclideanDistance(text dbschema, text sourcetable, text sourcegeomcolumn, 183 geometry geom, integer width, integer height, 184 double precision gridx, double precision gridy, text pixeltype, 185 double precision nodataval=0, double precision skewx=0, double precision skewy=0) 183 186 }}} 184 187 … … 186 189 {{{ 187 190 #!sql 188 ST_EuclideanDistance(text dbschema, text sourcetable, text sourcegeomcolumn, raster ref, text pixeltype, double precision nodataval=0, double precision maxdistance) 191 ST_EuclideanDistance(text dbschema, text sourcetable, text sourcegeomcolumn, 192 raster ref, text pixeltype, double precision nodataval=0, double precision maxdistance) 189 193 }}} 190 194 {{{ 191 195 Comments from Mentor: 192 You should integrate this parameter in the more generic signature instead. The idea is to create a generic function with the most complete signature and then to create variants assuming default value for some of the parameters. Only the most complete has to be implemented in C. 196 You should integrate this parameter in the more generic signature instead. The idea is to 197 create a generic function with the most complete signature and then to create variants 198 assuming default value for some of the parameters. Only the most complete has to be implemented in C. 193 199 }}}