From: Bborie Park Date: Wed, 17 Oct 2012 19:30:47 +0000 (+0000) Subject: Cleanup description for ST_SetValues() X-Git-Tag: 2.1.0beta2~514 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=598bf28de8fee12d7cf326ee4ef1c8c44c75166c;p=postgis Cleanup description for ST_SetValues() git-svn-id: http://svn.osgeo.org/postgis/trunk@10459 b70326c6-7e19-0410-871a-916f4a2858ee --- diff --git a/doc/reference_raster.xml b/doc/reference_raster.xml index 299d72b55..5a5c17602 100644 --- a/doc/reference_raster.xml +++ b/doc/reference_raster.xml @@ -4180,7 +4180,11 @@ GROUP BY (foo.geomval).val; - For Variant 1, the specific pixels to be set are determined by the columnx, rowy pixel coordinates and the dimensions of the newvalueset array. noset can be used to prevent pixels with values present in newvalueset from being set (due to PostgreSQL not permitting ragged/jagged arrays). If keepnodata is TRUE, those pixels whose values are NODATA will not be set with the corresponding value in newvalueset. See example Variant 1. + If keepnodata is TRUE, those pixels whose values are NODATA will not be set with the corresponding value in newvalueset. + + + + For Variant 1, the specific pixels to be set are determined by the columnx, rowy pixel coordinates and the dimensions of the newvalueset array. noset can be used to prevent pixels with values present in newvalueset from being set (due to PostgreSQL not permitting ragged/jagged arrays). See example Variant 1. @@ -4188,7 +4192,7 @@ GROUP BY (foo.geomval).val; - For Variant 3, the specific pixels to be set are determined by the columnx, rowy pixel coordinates, width and height. If keepnodata is TRUE, those pixels whose values are NODATA will not be set with the corresponding value in newvalueset. See example Variant 3. + For Variant 3, the specific pixels to be set are determined by the columnx, rowy pixel coordinates, width and height. See example Variant 3.