[postgis-tickets] r14948 - style only change: remove trailing spaces
Sandro Santilli
strk at kbt.io
Wed Jun 15 02:49:39 PDT 2016
Author: strk
Date: 2016-06-15 02:49:39 -0700 (Wed, 15 Jun 2016)
New Revision: 14948
Modified:
trunk/doc/reference_editor.xml
Log:
style only change: remove trailing spaces
Modified: trunk/doc/reference_editor.xml
===================================================================
--- trunk/doc/reference_editor.xml 2016-06-15 09:27:56 UTC (rev 14947)
+++ trunk/doc/reference_editor.xml 2016-06-15 09:49:39 UTC (rev 14948)
@@ -476,7 +476,7 @@
<para>Enhanced: 2.0.0 support for Polyhedral surfaces was introduced.</para>
<para>Availability: 1.2.2, prior to 1.3.4 this function will crash with Curves. This is fixed in 1.3.4+</para>
<para>Changed: 2.1.0. Up to 2.0.x this was called ST_Force_Collection.</para>
-
+
<para>&P_support;</para>
<para>&Z_support;</para>
<para>&curve_support;</para>
@@ -502,7 +502,7 @@
(1 row)
</programlisting>
-
+
<programlisting>
-- POLYHEDRAL example --
SELECT ST_AsEWKT(ST_ForceCollection('POLYHEDRALSURFACE(((0 0 0,0 0 1,0 1 1,0 1 0,0 0 0)),
@@ -763,10 +763,10 @@
<note><para>
Prior to 1.5.3 this function returned non-collection inputs untouched, no matter type.
-In 1.5.3 non-matching single geometries result in a NULL return.
+In 1.5.3 non-matching single geometries result in a NULL return.
In of 2.0.0 every case of missing match results in a typed EMPTY return.
</para></note>
-
+
<warning><para>When specifying 3 == POLYGON a multipolygon is returned even when the edges are shared. This results in an invalid multipolygon for many cases
such as applying this function on an <xref linkend="ST_Split" /> result.</para></warning>
@@ -794,7 +794,7 @@
<para><xref linkend="ST_Multi" />, <xref linkend="ST_Dump" />, <xref linkend="ST_CollectionHomogenize" /></para>
</refsection>
</refentry>
-
+
<refentry id="ST_CollectionHomogenize">
<refnamediv>
<refname>ST_CollectionHomogenize</refname>
@@ -819,27 +819,27 @@
<para>
Given a geometry collection, returns the "simplest" representation of the contents. Singletons will be returned as singletons. Collections that are homogeneous will be returned as the appropriate multi-type.
</para>
-
+
<warning><para>When specifying 3 == POLYGON a multipolygon is returned even when the edges are shared. This results in an invalid multipolygon for many cases
such as applying this function on an <xref linkend="ST_Split" /> result.</para></warning>
<para>Availability: 2.0.0</para>
-
+
</refsection>
<refsection>
<title>Examples</title>
<programlisting>
- SELECT ST_AsText(ST_CollectionHomogenize('GEOMETRYCOLLECTION(POINT(0 0))'));
+ SELECT ST_AsText(ST_CollectionHomogenize('GEOMETRYCOLLECTION(POINT(0 0))'));
st_astext
------------
POINT(0 0)
(1 row)
- SELECT ST_AsText(ST_CollectionHomogenize('GEOMETRYCOLLECTION(POINT(0 0),POINT(1 1))'));
+ SELECT ST_AsText(ST_CollectionHomogenize('GEOMETRYCOLLECTION(POINT(0 0),POINT(1 1))'));
st_astext
---------------------
@@ -852,8 +852,8 @@
<title>See Also</title>
<para><xref linkend="ST_Multi" />, <xref linkend="ST_CollectionExtract" /></para>
</refsection>
- </refentry>
-
+ </refentry>
+
<refentry id="ST_Multi">
<refnamediv>
<refname>ST_Multi</refname>
@@ -1019,7 +1019,7 @@
<para>&curve_support;</para>
<para>&P_support;</para>
<para>&T_support;</para>
-
+
</refsection>
@@ -1139,11 +1139,11 @@
<para>Availability: 1.1.2. Name changed from RotateY to ST_RotateY in 1.2.2</para>
<para>Enhanced: 2.0.0 support for Polyhedral surfaces, Triangles and TIN was introduced.</para>
-
+
<para>&P_support;</para>
<para>&Z_support;</para>
<para>&T_support;</para>
-
+
</refsection>
@@ -1194,7 +1194,7 @@
is short-hand for <code>SELECT ST_Affine(geomA, cos(rotRadians), -sin(rotRadians), 0, sin(rotRadians), cos(rotRadians), 0, 0, 0, 1, 0, 0, 0)</code>.</para></note>
<para>Enhanced: 2.0.0 support for Polyhedral surfaces, Triangles and TIN was introduced.</para>
-
+
<para>Availability: 1.1.2. Name changed from RotateZ to ST_RotateZ in 1.2.2</para>
<note><para>Prior to 1.3.4, this function crashes if used with geometries that contain CURVES. This is fixed in 1.3.4+</para></note>
@@ -1444,7 +1444,7 @@
SELECT ST_AsText(ST_SetPoint(g, -3, p))
FROM ST_GEomFromText('LINESTRING(0 0, 1 1, 2 2, 3 3, 4 4)') AS g
- , ST_PointN(g,1) as p;
+ , ST_PointN(g,1) as p;
st_astext
-----------------------
LINESTRING(0 0,1 1,0 0,3 3,4 4)
@@ -1494,7 +1494,7 @@
<para>&sfs_compliant;</para>
<para>&curve_support;</para>
</refsection>
-
+
<refsection>
<title>Examples</title>
<para>-- Mark a point as WGS 84 long lat --</para>
@@ -1697,14 +1697,14 @@
<note>
<para>
The returned geometry might lose its simplicity (see
- <xref linkend="ST_IsSimple" />) and validity (see
+ <xref linkend="ST_IsSimple" />) and validity (see
<xref linkend="ST_IsValid" />).
</para>
</note>
<para>Availability: 2.0.0 requires GEOS >= 3.3.0.</para>
</refsection>
-
+
<refsection>
<title>Examples</title>
<informaltable>
@@ -1730,19 +1730,19 @@
<imageobject>
<imagedata fileref="images/st_snap02.png" />
</imageobject>
- <caption><para>A multipolygon snapped to linestring to tolerance: 1.01 of distance.
+ <caption><para>A multipolygon snapped to linestring to tolerance: 1.01 of distance.
The new multipolygon is shown with reference linestring</para></caption>
</mediaobject>
</informalfigure>
<programlisting>
SELECT ST_AsText(ST_Snap(poly,line, ST_Distance(poly,line)*1.01)) AS polysnapped
-FROM (SELECT
+FROM (SELECT
ST_GeomFromText('MULTIPOLYGON(
((26 125, 26 200, 126 200, 126 125, 26 125 ),
- ( 51 150, 101 150, 76 175, 51 150 )),
+ ( 51 150, 101 150, 76 175, 51 150 )),
(( 151 100, 151 200, 176 175, 151 100 )))') As poly,
ST_GeomFromText('LINESTRING (5 107, 54 84, 101 100)') As line
-
+
) As foo;
polysnapped
@@ -1756,7 +1756,7 @@
<imageobject>
<imagedata fileref="images/st_snap04.png" />
</imageobject>
- <caption><para>A multipolygon snapped to linestring to tolerance: 1.25 of distance.
+ <caption><para>A multipolygon snapped to linestring to tolerance: 1.25 of distance.
The new multipolygon is shown with reference linestring</para></caption>
</mediaobject>
</informalfigure>
@@ -1764,13 +1764,13 @@
SELECT ST_AsText(
ST_Snap(poly,line, ST_Distance(poly,line)*1.25)
) AS polysnapped
-FROM (SELECT
+FROM (SELECT
ST_GeomFromText('MULTIPOLYGON(
(( 26 125, 26 200, 126 200, 126 125, 26 125 ),
( 51 150, 101 150, 76 175, 51 150 )),
(( 151 100, 151 200, 176 175, 151 100 )))') As poly,
ST_GeomFromText('LINESTRING (5 107, 54 84, 101 100)') As line
-
+
) As foo;
polysnapped
@@ -1786,7 +1786,7 @@
<imageobject>
<imagedata fileref="images/st_snap03.png" />
</imageobject>
- <caption><para>The linestring snapped to the original multipolygon at tolerance 1.01 of distance.
+ <caption><para>The linestring snapped to the original multipolygon at tolerance 1.01 of distance.
The new linestring is shown with reference multipolygon</para></caption>
</mediaobject>
</informalfigure>
@@ -1794,10 +1794,10 @@
SELECT ST_AsText(
ST_Snap(line, poly, ST_Distance(poly,line)*1.01)
) AS linesnapped
-FROM (SELECT
+FROM (SELECT
ST_GeomFromText('MULTIPOLYGON(
((26 125, 26 200, 126 200, 126 125, 26 125),
- (51 150, 101 150, 76 175, 51 150 )),
+ (51 150, 101 150, 76 175, 51 150 )),
((151 100, 151 200, 176 175, 151 100)))') As poly,
ST_GeomFromText('LINESTRING (5 107, 54 84, 101 100)') As line
) As foo;
@@ -1813,7 +1813,7 @@
<imageobject>
<imagedata fileref="images/st_snap05.png" />
</imageobject>
- <caption><para>The linestring snapped to the original multipolygon at tolerance 1.25 of distance.
+ <caption><para>The linestring snapped to the original multipolygon at tolerance 1.25 of distance.
The new linestring is shown with reference multipolygon</para></caption>
</mediaobject>
</informalfigure>
@@ -1821,12 +1821,12 @@
SELECT ST_AsText(
ST_Snap(line, poly, ST_Distance(poly,line)*1.25)
) AS linesnapped
-FROM (SELECT
+FROM (SELECT
ST_GeomFromText('MULTIPOLYGON(
(( 26 125, 26 200, 126 200, 126 125, 26 125 ),
- (51 150, 101 150, 76 175, 51 150 )),
+ (51 150, 101 150, 76 175, 51 150 )),
((151 100, 151 200, 176 175, 151 100 )))') As poly,
- ST_GeomFromText('LINESTRING (5 107, 54 84, 101 100)') As line
+ ST_GeomFromText('LINESTRING (5 107, 54 84, 101 100)') As line
) As foo;
linesnapped
---------------------------------------
@@ -1892,7 +1892,7 @@
<refsection>
<title>Description</title>
- <para>Returns a new geometry with its coordinates transformed to
+ <para>Returns a new geometry with its coordinates transformed to
a different spatial reference system. The destination spatial
reference <varname>to_srid</varname> may be identified by a valid
SRID integer parameter (i.e. it must exist in the
@@ -1900,12 +1900,12 @@
Alternatively, a spatial reference defined as a PROJ.4 string
can be used for <varname>to_proj</varname> and/or
<varname>from_proj</varname>, however these methods are not
- optimized. If the destination spatial reference system is
+ optimized. If the destination spatial reference system is
expressed with a PROJ.4 string instead of an SRID, the SRID of the
output geometry will be set to zero. With the exception of functions with
<varname>from_proj</varname>, input geometries must have a defined SRID.
</para>
-
+
<para>ST_Transform is often confused with ST_SetSRID(). ST_Transform actually changes the coordinates
of a geometry from one spatial reference system to another, while ST_SetSRID() simply changes the SRID identifier of
the geometry.</para>
@@ -1982,7 +1982,7 @@
--------------------------------------------------------------------------------
POLYGON((-170 74.053793645338,-141 73.4268621378904,-141 68,-170 68,-170 74.053793645338))
</programlisting>
-
+
</refsection>
<refsection>
<title>Configuring transformation behaviour</title>
More information about the postgis-tickets
mailing list