[postgis-tickets] r15119 - doc corrections from ruvyn for PostGIS 2.2.3

[Regina Obe]

Author: robe
Date: 2016-09-18 21:55:14 -0700 (Sun, 18 Sep 2016)
New Revision: 15119

Modified:
   branches/2.2/NEWS
   branches/2.2/doc/faq_raster.xml
   branches/2.2/doc/reference_constructor.xml
   branches/2.2/doc/reference_raster.xml
Log:
doc corrections from ruvyn for PostGIS 2.2.3
closes #3581
closes #3580
closes #3586
closes #3575

Modified: branches/2.2/NEWS
===================================================================
--- branches/2.2/NEWS	2016-09-19 04:54:41 UTC (rev 15118)
+++ branches/2.2/NEWS	2016-09-19 04:55:14 UTC (rev 15119)
@@ -28,6 +28,7 @@
            (Christian Quest / Dan Baston)
   - #3501 use ST_Union instead of ST_Collect to compute 
           raster max extent constraint
+  - Numerous documentation corrections from ruvyn
 
 
 PostGIS 2.2.2

Modified: branches/2.2/doc/faq_raster.xml
===================================================================
--- branches/2.2/doc/faq_raster.xml	2016-09-19 04:54:41 UTC (rev 15118)
+++ branches/2.2/doc/faq_raster.xml	2016-09-19 04:55:14 UTC (rev 15119)
@@ -264,7 +264,7 @@
       </question>
 
       <answer>
-        <para>The function is not unique error happens if one of your arguments is a textual representation of a geometry instead of a geometry.  In these cases, PostgreSQL marks the textual representation as an unknown type, which means it can fall into the st_intersects(raster, geometry) or st_intersects(raster,raster) thus resulting in a non-unique case since both functions can in theory support your request.  To prevent this, you need to cast the geometry to a geometry.</para>
+        <para>The function is not unique error happens if one of your arguments is a textual representation of a geometry instead of a geometry.  In these cases, PostgreSQL marks the textual representation as an unknown type, which means it can fall into the st_intersects(raster, geometry) or st_intersects(raster,raster) thus resulting in a non-unique case since both functions can in theory support your request.  To prevent this, you need to cast the textual representation of the geometry to a geometry.</para>
         <para>For example if your code looks like this:</para>
         <programlisting>SELECT rast
  FROM my_raster

Modified: branches/2.2/doc/reference_constructor.xml
===================================================================
--- branches/2.2/doc/reference_constructor.xml	2016-09-19 04:54:41 UTC (rev 15118)
+++ branches/2.2/doc/reference_constructor.xml	2016-09-19 04:55:14 UTC (rev 15119)
@@ -425,7 +425,7 @@
 \\312Q\\300\\366{b\\235*!E@\\225|\\354.P\\312Q
 \\300p\\231\\323e1!E@');</programlisting>
 
-		<note><para>In PostgreSQL 9.1+ - standard_conforming_strings is set to on by default, where as in past versions it was set to on.  You can change defaults as needed
+		<note><para>In PostgreSQL 9.1+ - standard_conforming_strings is set to on by default, where as in past versions it was set to off.  You can change defaults as needed
 		    for a single query or at the database or server level.  Below is how you would do it with standard_conforming_strings = on.  In this case we escape the ' with standard ansi ',
 		    but slashes are not escaped</para></note>
 	<programlisting>

Modified: branches/2.2/doc/reference_raster.xml
===================================================================
--- branches/2.2/doc/reference_raster.xml	2016-09-19 04:54:41 UTC (rev 15118)
+++ branches/2.2/doc/reference_raster.xml	2016-09-19 04:55:14 UTC (rev 15119)
@@ -6423,12 +6423,17 @@
 					<title>Examples</title>
 					<para>A simple example reskewing a raster from a skew of 0.0 to a skew of 0.0015.</para>
 					
-					<programlisting>-- the original raster pixel size
-SELECT ST_Rotation(ST_AddBand(ST_MakeEmptyRaster(100, 100, 0, 0, 0.001, -0.001, 0, 0, 4269), '8BUI'::text, 1, 0))
+					<programlisting>-- the original raster non-rotated
+SELECT ST_Rotation(ST_AddBand(ST_MakeEmptyRaster(100, 100, 0, 0, 0.001, -0.001, 0, 0, 4269), '8BUI'::text, 1, 0));
+
+-- result
+0
 					
--- the rescaled raster raster pixel size
-SELECT ST_Rotation(ST_Reskew(ST_AddBand(ST_MakeEmptyRaster(100, 100, 0, 0, 0.001, -0.001, 0, 0, 4269), '8BUI'::text, 1, 0), 0.0015))
-                    </programlisting>
+-- the reskewed raster raster rotation
+SELECT ST_Rotation(ST_Reskew(ST_AddBand(ST_MakeEmptyRaster(100, 100, 0, 0, 0.001, -0.001, 0, 0, 4269), '8BUI'::text, 1, 0), 0.0015));
+
+-- result
+-0.982793723247329</programlisting>
 					
 			</refsection>
 
@@ -6506,12 +6511,16 @@
 					<title>Examples</title>
 					<para>A simple example snapping a raster to a slightly different grid.</para>
 					
-					<programlisting>-- the original raster pixel size
-SELECT ST_UpperLeftX(ST_AddBand(ST_MakeEmptyRaster(10, 10, 0, 0, 0.001, -0.001, 0, 0, 4269), '8BUI'::text, 1, 0))
+					<programlisting>-- the original raster upper left X
+SELECT ST_UpperLeftX(ST_AddBand(ST_MakeEmptyRaster(10, 10, 0, 0, 0.001, -0.001, 0, 0, 4269), '8BUI'::text, 1, 0));
+-- result
+0
 					
--- the rescaled raster raster pixel size
-SELECT ST_UpperLeftX(ST_SnapToGrid(ST_AddBand(ST_MakeEmptyRaster(10, 10, 0, 0, 0.001, -0.001, 0, 0, 4269), '8BUI'::text, 1, 0), 0.0002, 0.0002))
-                    </programlisting>
+-- the upper left of raster after snapping
+SELECT ST_UpperLeftX(ST_SnapToGrid(ST_AddBand(ST_MakeEmptyRaster(10, 10, 0, 0, 0.001, -0.001, 0, 0, 4269), '8BUI'::text, 1, 0), 0.0002, 0.0002));
+
+--result
+-0.0008</programlisting>
 					
 			</refsection>