From 0e2f622cd817cd2890545cc3b1c2e0aea5ca3020 Mon Sep 17 00:00:00 2001
From: Daniel Baston <dbaston@gmail.com>
Date: Fri, 18 Dec 2015 00:53:20 +0000
Subject: [PATCH] fix typos in docs
git-svn-id: http://svn.osgeo.org/postgis/trunk@14496 b70326c6-7e19-0410-871a-916f4a2858ee
---
doc/introduction.xml | 2 +-
doc/reference_constructor.xml | 4 ++--
doc/reference_editor.xml | 2 +-
doc/reference_measure.xml | 2 +-
doc/reference_output.xml | 4 ++--
doc/reference_raster.xml | 4 ++--
6 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/doc/introduction.xml b/doc/introduction.xml
index 5c5f6455b..39b639da0 100644
--- a/doc/introduction.xml
+++ b/doc/introduction.xml
@@ -251,6 +251,7 @@ Avencia,
Azavea,
Cadcorp,
CampToCamp,
+CartoDB,
City of Boston (DND),
Clever Elephant Solutions,
Cooperativa Alveo,
@@ -278,7 +279,6 @@ Stadt Uster,
UC Davis Center for Vectorborne Diseases,
University of Laval,
U.S Department of State (HIU),
-CartoDB,
Zonar Systems</para>
</listitem>
</varlistentry>
diff --git a/doc/reference_constructor.xml b/doc/reference_constructor.xml
index 5f113c1b7..b9225c480 100644
--- a/doc/reference_constructor.xml
+++ b/doc/reference_constructor.xml
@@ -575,7 +575,7 @@ SELECT ST_GeomFromEWKT('POLYHEDRALSURFACE(
<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>
@@ -2121,7 +2121,7 @@ SELECT ST_Transform(ST_SetSRID(ST_Point(3637510, 3014852),2273),4326)::geography
<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>
diff --git a/doc/reference_editor.xml b/doc/reference_editor.xml
index c00060e44..6af835b8f 100644
--- a/doc/reference_editor.xml
+++ b/doc/reference_editor.xml
@@ -1280,7 +1280,7 @@ FROM (SELECT ST_LineToCurve(ST_Buffer(ST_GeomFromText('POINT(234 567)'), 3)) As
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>
diff --git a/doc/reference_measure.xml b/doc/reference_measure.xml
index f3232538d..94c299453 100644
--- a/doc/reference_measure.xml
+++ b/doc/reference_measure.xml
@@ -1530,7 +1530,7 @@ FROM (SELECT ST_Buffer(ST_GeomFromText('POINT(1 2)'), 10) As smallc,
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>
diff --git a/doc/reference_output.xml b/doc/reference_output.xml
index 96b116a2c..c477a2e4d 100644
--- a/doc/reference_output.xml
+++ b/doc/reference_output.xml
@@ -798,7 +798,7 @@ SELECT ST_AsGML(3, ST_GeomFromEWKT('POLYHEDRALSURFACE( ((0 0 0, 0 0 1, 0 1 1, 0
</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 @@ x3dfrag
<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>
diff --git a/doc/reference_raster.xml b/doc/reference_raster.xml
index d4ff50dc7..8c61c74ce 100644
--- a/doc/reference_raster.xml
+++ b/doc/reference_raster.xml
@@ -2083,7 +2083,7 @@ FROM (SELECT rid, ST_MetaData(rast) As md
</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 @@ raster coverage (<varname>tab</varname>, <varname>col</varname>).
</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>
--
2.40.0