Changes between Version 18 and Version 19 of WKTRaster/SpecificationWorking03

Timestamp:

02/23/10 11:13:01 (15 years ago)

Author:

dzwarg

Comment:

Removed setters that copy settings from a raster parameter for ST_SetPixelSize, ST_SetRotation, and ST_SetUpperLeft

WKTRaster/SpecificationWorking03

@@ -26 +26 @@
  Variant 1: ST_SetPixelSize(raster, xsize, ysize)
 
- Variant 2: ST_SetPixelSize(raster, raster)
-
- Set the pixel size (cell size) on the specified raster. The base method sets the X and Y pixel size to the same value. The first variant sets the pixel sizes to the individually specified x and y sizes.  The second variant sets the pixel size to the pixel size of the 2nd raster parameter.
+ ~~Variant 2: ST_SetPixelSize(raster, raster)~~
+
+ Set the pixel size (cell size) on the specified raster. The base method sets the X and Y pixel size to the same value. The first variant sets the pixel sizes to the individually specified x and y sizes.  ~~The second variant sets the pixel size to the pixel size of the 2nd raster parameter.~~
 
  '''Open Question:'''
   DZ: Should there be corresponding methods for X/Y sizes?  ST_SetXPixelSize(...) and ST_SetYPixelSize(...)
     PR: In addition to ST_SetPixelSize(raster, xsize, ysize) or in replacement of?
-      DZ: In addition to?
+      DZ: In addition to?[[BR]]
       PR: Maybe we are fine with ST_SetPixelSize(raster, xsize, ysize)...
 
   PR: Could you provide a full SQL example of ST_SetPixelSize(raster, raster)? And in general of a function getting arguments for the first raster from another raster (like the below ST_Resample(raster, method, raster))
     DZ: A SQL example for this is in the regression tests in patch #431: test/regress/rt_set_properties.sql, line 52. I can come up with some more examples, if needed.
+      DZ: After discussion, will drop the variant that copies the pixel size from a raster parameter.
 
 '''ST_SetNoDataValue(raster, band, value)'''
@@ -55 +56 @@
  Variant 1: ST_SetRotation(raster, rotationx, rotation y)
 
- Variant 2: ST_SetRotation(raster, raster)
-
- Set the rotation of the raster. The base method sets the X and Y rotation to the same value. The first variant sets the rotation to the individually specified x and y rotations. The second variant sets the rotation to the rotation taken from the 2nd raster parameter.
+ ~~Variant 2: ST_SetRotation(raster, raster)~~
+
+ Set the rotation of the raster. The base method sets the X and Y rotation to the same value. The first variant sets the rotation to the individually specified x and y rotations. ~~The second variant sets the rotation to the rotation taken from the 2nd raster parameter.~~
 
  '''Open Question:'''
   DZ: Should there be corresponding methods for X/Y rotations in addition to this general method?  ST_SetXRotation(...) and ST_SetYRotation(...)?
+    DZ: No, follow the pattern for ST_SetPixelSize
 
 '''ST_SetUpperLeft(raster, left, top)'''
- Variant 1: ST_SetUpperLeft(raster, raster)'''
-
- Set the location of the upper left pixel (cell). The base method sets the X and Y coordinates to the individually specified left and top coordinates.  The first variant sets the upper left coordinate to the upper left coordinate taken from the 2nd raster parameter.
+ ~~Variant 1: ST_SetUpperLeft(raster, raster)~~
+
+ Set the location of the upper left pixel (cell). The base method sets the X and Y coordinates to the individually specified left and top coordinates.  ~~The first variant sets the upper left coordinate to the upper left coordinate taken from the 2nd raster parameter.~~
 
  '''Open Question:'''
   DZ: Should there be corresponding methods for X/Y rotations in addition to this general method?  ST_SetUpperLeftX(...) and ST_SetUpperLeftY()?
-
+    DZ: No, follow the pattern for ST_SetPixelSize
 ----
 == '''Objective B03b - Being able to reproject a raster.''' ==