Changes between Version 94 and Version 95 of WKTRaster/SpecificationWorking03


Ignore:
Timestamp:
05/30/11 08:20:11 (13 years ago)
Author:
dustymugs
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • WKTRaster/SpecificationWorking03

    v94 v95  
    855855 
    856856
    857 '''ST_Union(raster|geometry, raster|geometry, ¿raster¿|¿geometry¿) -> raster/geometry'''[[BR]]
    858 '''ST_Accum(raster set|geometry set, ¿raster¿|¿geometry¿) -> raster/geometry'''
     857'''ST_Union(raster|geometry, raster|geometry, 'raster'|'geometry') -> raster/geometry'''[[BR]]
     858'''ST_Accum(raster set|geometry set, 'raster'|'geometry') -> raster/geometry'''
    859859
    860860
     
    13181318 The 3rd or 3rd-6th parameters define the pixel size of the resampling operation. For the 3rd parameter variant, the pixel size is taken from the pixel size of the raster parameter. For the 3rd-6th parameter variant, the pixel origin and dimensions are explicitly defined.
    13191319
    1320 '''ST_SelectByValue(raster|geometry, ¿expression¿) -> same type as first argument'''[[BR]]
     1320'''ST_SelectByValue(raster|geometry, 'expression') -> same type as first argument'''[[BR]]
    13211321~~'''ST_Reclass(raster|geometry,string) -> same type as first argument'''[[BR]]~~
    13221322
    13231323~~Bborie: Implementation has been moved to FV.01 above.~~
    13241324
    1325 '''ST_MapAlgebra(raster|geometry, [raster|geometry,¿] ¿mathematical expression¿, ¿raster¿ |¿geometry¿) -> raster/geometry'''
    1326 
    1327  Variant 1: ST_MapAlgebra(raster|geometry, [raster|geometry,¿] ¿mathematical expression¿, ¿raster¿ |¿geometry¿, originx, originy, pixelsizex, pixelsizey) -> raster/geometry
    1328 
    1329  Variant 2: ST_MapAlgebra(raster|geometry, [raster|geometry,¿] 'mathematical expression', 'raster' |'geometry', integer) ->raster/geometry
    1330 
    1331  Variant 3: ST_MapAlgebra(raster|geometry, [raster|geometry,¿] 'mathematical expression', 'raster' |'geometry', raster) ->raster/geometry
     1325'''ST_MapAlgebra(raster|geometry, [raster|geometry, ...] 'mathematical expression', 'raster' |'geometry') -> raster/geometry'''
     1326
     1327 Variant 1: ST_MapAlgebra(raster|geometry, [raster|geometry, ...] 'mathematical expression', 'raster' |'geometry', originx, originy, pixelsizex, pixelsizey) -> raster/geometry
     1328
     1329 Variant 2: ST_MapAlgebra(raster|geometry, [raster|geometry, ...] 'mathematical expression', 'raster' |'geometry', integer) ->raster/geometry
     1330
     1331 Variant 3: ST_MapAlgebra(raster|geometry, [raster|geometry, ...] 'mathematical expression', 'raster' |'geometry', raster) ->raster/geometry
    13321332
    13331333 ST_MapAlgebra performs the specified mathematical expression on the input rasters, returning a raster or geometry.  Both rasters must have the same SRID.  If both rasters do not have the same SRID, ST_MapAlgebra will return an error:
     
    13391339  4 additional parameters are passed specifying the origin, cell size, and raster rotation.
    13401340
    1341  This function implicitly calls ST_Intersects(raster|geometry, [raster|geometry,¿]) to detect if the rasters are overlapping before performing any computation. Additionally, the resulting raster will have the same extent as the result of ST_Intersection(raster, integer, geometry).
     1341 This function implicitly calls ST_Intersects(raster|geometry, [raster|geometry, ...]) to detect if the rasters are overlapping before performing any computation. Additionally, the resulting raster will have the same extent as the result of ST_Intersection(raster, integer, geometry).
    13421342
    13431343 One of the implications of the ST_Intersects inclusion is that:
     
    13481348 '''Open Question:'''
    13491349      DZ: Should ST_MapAlgebra resample rasters internally, or produce a raster that can be processed by ST_Resample? If so, variant 1 and variant 3 can be removed, and all ST_MapAlgebra results can be processed through ST_Resample, like:
    1350   ST_Resample(ST_MapAlgebra(raster, [raster,¿] 'mathematical expression', integer), originx, originy, pixelsizex, pixelsizey)[[BR]]
    1351   ST_Resample(ST_MapAlgebra(raster, [raster,¿] 'mathematical expression', integer), rastergrid)
     1350  ST_Resample(ST_MapAlgebra(raster, [raster, ...] 'mathematical expression', integer), originx, originy, pixelsizex, pixelsizey)[[BR]]
     1351  ST_Resample(ST_MapAlgebra(raster, [raster, ...] 'mathematical expression', integer), rastergrid)
    13521352        PR: I think this would greatly contribute to simplify the API.
    13531353
    13541354'''ST_Clip(raster|geometry,geometry) -> same type as first argument'''[[BR]]
    1355 '''ST_Flip(raster|geometry, ¿vertical¿|¿horizontal¿) -> same type as first argument'''
     1355'''ST_Flip(raster|geometry, 'vertical'|'horizontal') -> same type as first argument'''
    13561356
    13571357----
     
    13921392'''ST_Buffer(raster|geometry, double) -> same type as first arg.'''[[BR]]
    13931393'''ST_Difference(raster|geometry A, raster|geometry B) -> same type as first argument'''[[BR]]
    1394 '''ST_SymDifference(raster|geometry,raster|geometry,¿raster¿|¿geometry¿) -> raster/geometry'''
     1394'''ST_SymDifference(raster|geometry,raster|geometry,'raster'|'geometry') -> raster/geometry'''
    13951395 
    13961396----
     
    14091409== '''Objective FV.13 - Being able to edit a raster''' ==
    14101410 
    1411 '''ST_Affine(raster|geometry,¿) -> same type as input'''[[BR]]
    1412 '''ST_Translate(raster|geometry,¿) -> same type as input'''[[BR]]
    1413 '''ST_Scale(raster|geometry,¿) -> same type as input'''[[BR]]
    1414 '''ST_TransScale(raster|geometry,¿) -> same type as input'''[[BR]]
     1411'''ST_Affine(raster|geometry, ...) -> same type as input'''[[BR]]
     1412'''ST_Translate(raster|geometry, ...) -> same type as input'''[[BR]]
     1413'''ST_Scale(raster|geometry, ...) -> same type as input'''[[BR]]
     1414'''ST_TransScale(raster|geometry, ...) -> same type as input'''[[BR]]
    14151415'''ST_RotateZ,Y,Z(raster|geometry, float8) -> same type as input'''
    14161416