Changes between Version 25 and Version 26 of PostGIS_Raster_SoC_Idea_2012/Distance_Analysis_Tools/document


Ignore:
Timestamp:
Jul 12, 2012, 11:16:35 PM (12 years ago)
Author:
qliu
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • PostGIS_Raster_SoC_Idea_2012/Distance_Analysis_Tools/document

    v25 v26  
    9090 * __This approach fulfills constraint 7 in that it would allow easy implementation of other interpolation methods.__
    9191{{{
    92 Comments from the mentor:
     92Comments from Mentor:
    9393Not 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.
    9494}}}
     
    9797 * __We have no idea for now about the algorithm and performance of building TIN from source geometries in PostGIS if the number of source point is very large (Constraint 7 & 8)__
    9898{{{
    99 Comments from the Mentor:
     99Comments from Mentor:
    100100Right, ST_Within(raster, geometry) does not exist. But you would work with the centroid of the pixel, which is a point and the triangle of the TIN which are polygons and there is no problem doing that with ST_Within. If you would include the pixel centroid in the TIN as stated above, you would nort even have to do that as the centroid and the points would all be in the same TIN structure allowing fast find of neighbors.
    101101}}}
     
    133133
    134134'''Cons:'''
    135  * Might not be as light as Approach 1 in case there is only one point in the source table (Constraint 1) or there are very small number of source points and the requested raster is relatively small too (Constraint 5)
    136  * Have no idea how to deal with Constraint 9.
     135 * __Might not be as light as Approach 1 in case there is only one point in the source table (Constraint 1) or there are very small number of source points and the requested raster is relatively small too (Constraint 5)__
     136{{{
     137Comments from Mentor:
     138In that case, should be fast anyway. We could optimize if there is only one source point.
     139}}}
    137140
    138141[[BR]][[BR]]
     
    172175 * For Constraint 6: (just write down the function that takes a reference raster for example)
    173176{{{
    174 #!c
     177#!c++
    175178ST_EuclideanDistance(text dbschema, text sourcetable, text sourcegeomcolumn, raster ref, text pixeltype, double precision value=1, double precision nodataval=0, double precision maxdistance)
    176179}}}
     180{{{
     181Comments from Mentor:
     182You 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.
     183}}}