[postgis-tickets] r14497 - fix typos in docs
Daniel Baston
dbaston at gmail.com
Thu Dec 17 16:55:54 PST 2015
Author: dbaston
Date: 2015-12-17 16:55:54 -0800 (Thu, 17 Dec 2015)
New Revision: 14497
Modified:
branches/2.2/doc/introduction.xml
branches/2.2/doc/reference_constructor.xml
branches/2.2/doc/reference_editor.xml
branches/2.2/doc/reference_measure.xml
branches/2.2/doc/reference_output.xml
branches/2.2/doc/reference_raster.xml
Log:
fix typos in docs
Modified: branches/2.2/doc/introduction.xml
===================================================================
--- branches/2.2/doc/introduction.xml 2015-12-18 00:53:20 UTC (rev 14496)
+++ branches/2.2/doc/introduction.xml 2015-12-18 00:55:54 UTC (rev 14497)
@@ -250,6 +250,7 @@
Azavea,
Cadcorp,
CampToCamp,
+CartoDB,
City of Boston (DND),
Clever Elephant Solutions,
Cooperativa Alveo,
@@ -277,7 +278,6 @@
UC Davis Center for Vectorborne Diseases,
University of Laval,
U.S Department of State (HIU),
-CartoDB,
Zonar Systems</para>
</listitem>
</varlistentry>
Modified: branches/2.2/doc/reference_constructor.xml
===================================================================
--- branches/2.2/doc/reference_constructor.xml 2015-12-18 00:53:20 UTC (rev 14496)
+++ branches/2.2/doc/reference_constructor.xml 2015-12-18 00:55:54 UTC (rev 14497)
@@ -575,7 +575,7 @@
<para>Return a geometry from a GeoHash string. The geometry will be a polygon representing the GeoHash bounds.</para>
- <para>If no <varname>precision</varname> is specficified ST_GeomFromGeoHash returns a polygon based on full precision of the input GeoHash string.</para>
+ <para>If no <varname>precision</varname> is specified ST_GeomFromGeoHash returns a polygon based on full precision of the input GeoHash string.</para>
<para>If <varname>precision</varname> is specified ST_GeomFromGeoHash will use that many characters from the GeoHash to create the polygon.</para>
@@ -2122,7 +2122,7 @@
<para>Return a point from a GeoHash string. The point represents the center point of the GeoHash.</para>
- <para>If no <varname>precision</varname> is specficified ST_PointFromGeoHash returns a point based on full precision of the input GeoHash string.</para>
+ <para>If no <varname>precision</varname> is specified ST_PointFromGeoHash returns a point based on full precision of the input GeoHash string.</para>
<para>If <varname>precision</varname> is specified ST_PointFromGeoHash will use that many characters from the GeoHash to create the point.</para>
Modified: branches/2.2/doc/reference_editor.xml
===================================================================
--- branches/2.2/doc/reference_editor.xml 2015-12-18 00:53:20 UTC (rev 14496)
+++ branches/2.2/doc/reference_editor.xml 2015-12-18 00:55:54 UTC (rev 14497)
@@ -1280,7 +1280,7 @@
The version taking a geometry as the <varname>factor</varname> parameter
allows passing a 2d, 3dm, 3dz or 4d point to set scaling factor for all
supported dimensions. Missing dimensions in the <varname>factor</varname>
-point are equivalant to no scaling the corresponding dimension.
+point are equivalent to no scaling the corresponding dimension.
</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>
Modified: branches/2.2/doc/reference_measure.xml
===================================================================
--- branches/2.2/doc/reference_measure.xml 2015-12-18 00:53:20 UTC (rev 14496)
+++ branches/2.2/doc/reference_measure.xml 2015-12-18 00:55:54 UTC (rev 14497)
@@ -1530,7 +1530,7 @@
returns <varname>TRUE</varname> if their intersection "spatially cross", that is, the
geometries have some, but not all interior points in common. The
intersection of the interiors of the geometries must not be the empty
- set and must have a dimensionality less than the the maximum dimension
+ set and must have a dimensionality less than the maximum dimension
of the two input geometries. Additionally, the intersection of the two
geometries must not equal either of the source geometries. Otherwise, it
returns <varname>FALSE</varname>.</para>
Modified: branches/2.2/doc/reference_output.xml
===================================================================
--- branches/2.2/doc/reference_output.xml 2015-12-18 00:53:20 UTC (rev 14496)
+++ branches/2.2/doc/reference_output.xml 2015-12-18 00:55:54 UTC (rev 14497)
@@ -798,7 +798,7 @@
</listitem>
<listitem>
- <para>2: Output coordinates in GeoSpatial GeoCoordinates. This option will throw an error if geometries are not in WGS 84 long lat (srid: 4326). This is currenlty the only GeoCoordinate type supported. <ulink url="http://www.web3d.org/documents/specifications/19775-1/V3.2/Part01/components/geodata.html#Specifyingaspatialreference">Refer to X3D specs specifying a spatial reference system.</ulink>. Default output will be <code>GeoCoordinate geoSystem='"GD" "WE" "longitude_first"'</code>. If
+ <para>2: Output coordinates in GeoSpatial GeoCoordinates. This option will throw an error if geometries are not in WGS 84 long lat (srid: 4326). This is currently the only GeoCoordinate type supported. <ulink url="http://www.web3d.org/documents/specifications/19775-1/V3.2/Part01/components/geodata.html#Specifyingaspatialreference">Refer to X3D specs specifying a spatial reference system.</ulink>. Default output will be <code>GeoCoordinate geoSystem='"GD" "WE" "longitude_first"'</code>. If
you prefer the X3D default of <code>GeoCoordinate geoSystem='"GD" "WE" "latitude_first"'</code> use <code>(2 + 1)</code> = <code>3</code> </para>
</listitem>
</itemizedlist>
@@ -973,7 +973,7 @@
<para>Return a GeoHash representation (<ulink url="http://en.wikipedia.org/wiki/Geohash">http://en.wikipedia.org/wiki/Geohash</ulink>) of the geometry. A GeoHash encodes a point into a text form that is sortable and searchable based on prefixing. A shorter GeoHash is a less precise representation of a point. It can also be thought of as a box, that contains the actual point.</para>
- <para>If no <varname>maxchars</varname> is specficified ST_GeoHash returns a GeoHash based on full precision of the input geometry type. Points return a GeoHash with 20 characters of precision (about enough to hold the full double precision of the input). Other types return a GeoHash with a variable amount of precision, based on the size of the feature. Larger features are represented with less precision, smaller features with more precision. The idea is that the box implied by the GeoHash will always contain the input feature.</para>
+ <para>If no <varname>maxchars</varname> is specified ST_GeoHash returns a GeoHash based on full precision of the input geometry type. Points return a GeoHash with 20 characters of precision (about enough to hold the full double precision of the input). Other types return a GeoHash with a variable amount of precision, based on the size of the feature. Larger features are represented with less precision, smaller features with more precision. The idea is that the box implied by the GeoHash will always contain the input feature.</para>
<para>If <varname>maxchars</varname> is specified ST_GeoHash returns a GeoHash with at most that many characters so a possibly lower precision representation of the input geometry. For non-points, the starting point of the calculation is the center of the bounding box of the geometry.</para>
Modified: branches/2.2/doc/reference_raster.xml
===================================================================
--- branches/2.2/doc/reference_raster.xml 2015-12-18 00:53:20 UTC (rev 14496)
+++ branches/2.2/doc/reference_raster.xml 2015-12-18 00:55:54 UTC (rev 14497)
@@ -2083,7 +2083,7 @@
</para>
<para>
- If <varname>padwithnodata</varname> = FALSE, edge tiles on the right and bottom sides of the raster may have different dimensions than the rest of the tiles. If <varname>padwithnodata</varname> = TRUE, all tiles will have the same dimensions with the possibilty that edge tiles being padded with NODATA values. If raster band(s) do not have NODATA value(s) specified, one can be specified by setting <varname>nodataval</varname>.
+ If <varname>padwithnodata</varname> = FALSE, edge tiles on the right and bottom sides of the raster may have different dimensions than the rest of the tiles. If <varname>padwithnodata</varname> = TRUE, all tiles will have the same dimensions with the possibility that edge tiles being padded with NODATA values. If raster band(s) do not have NODATA value(s) specified, one can be specified by setting <varname>nodataval</varname>.
</para>
<note>
@@ -2267,7 +2267,7 @@
</para>
<para>
- If <varname>srid</varname> is NULL, the function will try to autmatically assign the SRID from the GDAL raster. If <varname>srid</varname> is provided, the value provided will override any automatically assigned SRID.
+ If <varname>srid</varname> is NULL, the function will try to automatically assign the SRID from the GDAL raster. If <varname>srid</varname> is provided, the value provided will override any automatically assigned SRID.
</para>
<para>Availability: 2.1.0</para>
More information about the postgis-tickets
mailing list