[postgis-tickets] r15694 - Numerous doc fixes from Andreas Schild via transifex
Regina Obe
lr at pcorp.us
Mon Sep 11 14:19:15 PDT 2017
Author: robe
Date: 2017-09-11 14:19:15 -0700 (Mon, 11 Sep 2017)
New Revision: 15694
Modified:
trunk/doc/extras_topology.xml
trunk/doc/reference_constructor.xml
trunk/doc/reference_processing.xml
trunk/doc/reference_raster.xml
trunk/doc/using_postgis_dataman.xml
Log:
Numerous doc fixes from Andreas Schild via transifex
Closes #3824 for PostGIS 2.4.0
Modified: trunk/doc/extras_topology.xml
===================================================================
--- trunk/doc/extras_topology.xml 2017-09-11 20:43:21 UTC (rev 15693)
+++ trunk/doc/extras_topology.xml 2017-09-11 21:19:15 UTC (rev 15694)
@@ -1283,7 +1283,7 @@
</para>
<para>
-Refuses to remove an edge partecipating in the definition of an
+Refuses to remove an edge participating in the definition of an
existing TopoGeometry.
Refuses to heal two faces if any TopoGeometry is defined by only
one of them (and not the other).
@@ -1621,7 +1621,7 @@
<refnamediv>
<refname>ST_MoveIsoNode</refname>
- <refpurpose>Moves an isolated node in a topology from one point to another. If new <varname>apoint</varname> geometry exists as a node an error is thrown. REturns description of move.</refpurpose>
+ <refpurpose>Moves an isolated node in a topology from one point to another. If new <varname>apoint</varname> geometry exists as a node an error is thrown. Returns description of move.</refpurpose>
</refnamediv>
<refsynopsisdiv>
@@ -2715,7 +2715,7 @@
<refsection>
<title>Examples: Form from existing edges</title>
- <para>Create a topogeom in ri_topo schema for layer 2 (our ri_roads), of type (2) LINE, for the first edge (we loaded in <varname>ST_CreateTopoGeo</varname>.</para>
+ <para>Create a topogeom in ri_topo schema for layer 2 (our ri_roads), of type (2) LINE, for the first edge (we loaded in <varname>ST_CreateTopoGeo</varname>).</para>
<programlisting>INSERT INTO ri.ri_roads(road_name, topo) VALUES('Unknown', topology.CreateTopoGeom('ri_topo',2,2,'{{1,2}}'::topology.topoelementarray);</programlisting>
</refsection>
Modified: trunk/doc/reference_constructor.xml
===================================================================
--- trunk/doc/reference_constructor.xml 2017-09-11 20:43:21 UTC (rev 15693)
+++ trunk/doc/reference_constructor.xml 2017-09-11 21:19:15 UTC (rev 15694)
@@ -1478,11 +1478,11 @@
</para>
<para>&Z_support;</para>
-
+
<para>Availability: 2.3.0 - Support for multipoint input elements was introduced</para>
<para>Availability: 2.0.0 - Support for linestring input elements was introduced</para>
<para>Availability: 1.4.0 - ST_MakeLine(geomarray) was introduced. ST_MakeLine aggregate functions was enhanced to handle more points faster.</para>
-
+
</refsection>
<refsection>
@@ -2315,7 +2315,7 @@
<!-- optionally mention that this function uses indexes if appropriate -->
<note>
- <para>ST_Polygon is similar to first version oST_MakePolygon except it also sets the spatial ref sys (SRID) of the polygon. Will not work with MULTILINESTRINGS
+ <para>ST_Polygon is similar to first version of ST_MakePolygon except it also sets the spatial ref sys (SRID) of the polygon. Will not work with MULTILINESTRINGS
so use LineMerge to merge multilines. Also does not create polygons with holes. Use ST_MakePolygon for that.</para>
</note>
Modified: trunk/doc/reference_processing.xml
===================================================================
--- trunk/doc/reference_processing.xml 2017-09-11 20:43:21 UTC (rev 15693)
+++ trunk/doc/reference_processing.xml 2017-09-11 21:19:15 UTC (rev 15694)
@@ -244,7 +244,7 @@
<programlisting>--A buffered point approximates a circle
-- A buffered point forcing approximation of (see diagram)
--- 2 points per circle is poly with 8 sides (see diagram)
+-- 2 points per quarter circle is poly with 8 sides (see diagram)
SELECT ST_NPoints(ST_Buffer(ST_GeomFromText('POINT(100 90)'), 50)) As promisingcircle_pcount,
ST_NPoints(ST_Buffer(ST_GeomFromText('POINT(100 90)'), 50, 2)) As lamecircle_pcount;
@@ -1810,7 +1810,7 @@
<para>Do not call with a <varname>GEOMETRYCOLLECTION</varname> as an argument</para>
</important>
- <warning><para>This function will drop the M coorindate values if present.</para></warning>
+ <warning><para>This function will drop the M coordinate values if present.</para></warning>
<warning><para>If working with 3D geometries, you may want to use SFGCAL based <xref linkend="ST_3DIntersection" /> which does a proper 3D intersection for 3D geometries. Although this function works with Z-coordinate, it does an averaging of Z-Coordinate values when <code>postgis.backend=geos</code>. <code>postgis.backend=sfcgal</code>, it will return a 2D geometry regardless ignoring the Z-Coordinate. Refer to <xref linkend="postgis_backend" /> for details.</para></warning>
Modified: trunk/doc/reference_raster.xml
===================================================================
--- trunk/doc/reference_raster.xml 2017-09-11 20:43:21 UTC (rev 15693)
+++ trunk/doc/reference_raster.xml 2017-09-11 21:19:15 UTC (rev 15694)
@@ -588,7 +588,7 @@
<listitem><para><varname>num_bands</varname> number of bands</para></listitem>
<listitem><para><varname>pixel_types</varname> reads array of pixel types for each band ensure all band n have same pixel type</para></listitem>
<listitem><para><varname>regular_blocking</varname> sets spatially unique (no two rasters can be spatially the same) and coverage tile (raster is aligned to a coverage) constraints</para></listitem>
- <listitem><para><varname>same_alignment</varname> ensures they all have same alignment meaning any two tiles you compare will return true for. Refer to <xref linkend="RT_ST_SameAlignment" /></para></listitem>
+ <listitem><para><varname>same_alignment</varname> ensures they all have same alignment meaning any two tiles you compare will return true for. Refer to <xref linkend="RT_ST_SameAlignment" />.</para></listitem>
<listitem><para><varname>srid</varname> ensures all have same srid</para></listitem>
<listitem><para>More -- any listed as inputs into the above functions</para></listitem>
</itemizedlist>
@@ -6214,7 +6214,7 @@
<refentry id="RT_ST_SetUpperLeft">
<refnamediv>
<refname>ST_SetUpperLeft</refname>
- <refpurpose>Sets the value of the upper left corner of the pixel to projected X and Y coordinates.</refpurpose>
+ <refpurpose>Sets the value of the upper left corner of the pixel of the raster to projected X and Y coordinates.</refpurpose>
</refnamediv>
<refsynopsisdiv>
@@ -6231,7 +6231,7 @@
<refsection>
<title>Description</title>
- <para>Set the value of the upper left corner of raster to the projected X coordinates</para>
+ <para>Set the value of the upper left corner of raster to the projected X and Y coordinates</para>
</refsection>
<refsection>
Modified: trunk/doc/using_postgis_dataman.xml
===================================================================
--- trunk/doc/using_postgis_dataman.xml 2017-09-11 20:43:21 UTC (rev 15693)
+++ trunk/doc/using_postgis_dataman.xml 2017-09-11 21:19:15 UTC (rev 15694)
@@ -2240,7 +2240,7 @@
syntax for building a BRIN index on a "geography" column is as follows:</para>
<para><programlisting>CREATE INDEX [indexname] ON [tablename] USING BRIN ( [geographyfield] ); </programlisting></para>
- <para>The above syntax will always build a 2D-index for geospatial objetcs on the spheroid. </para>
+ <para>The above syntax will always build a 2D-index for geospatial objects on the spheroid. </para>
<para>Currently, just the "inclusion support" is considered here, meaning
that just <varname>&&</varname>, <varname>~</varname> and
More information about the postgis-tickets
mailing list