From: Daniel Baston Date: Fri, 18 Dec 2015 00:53:20 +0000 (+0000) Subject: fix typos in docs X-Git-Tag: 2.3.0beta1~325 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=0e2f622cd817cd2890545cc3b1c2e0aea5ca3020;p=postgis fix typos in docs git-svn-id: http://svn.osgeo.org/postgis/trunk@14496 b70326c6-7e19-0410-871a-916f4a2858ee --- 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 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( Return a geometry from a GeoHash string. The geometry will be a polygon representing the GeoHash bounds. - If no precision is specficified ST_GeomFromGeoHash returns a polygon based on full precision of the input GeoHash string. + If no precision is specified ST_GeomFromGeoHash returns a polygon based on full precision of the input GeoHash string. If precision is specified ST_GeomFromGeoHash will use that many characters from the GeoHash to create the polygon. @@ -2121,7 +2121,7 @@ SELECT ST_Transform(ST_SetSRID(ST_Point(3637510, 3014852),2273),4326)::geography Return a point from a GeoHash string. The point represents the center point of the GeoHash. - If no precision is specficified ST_PointFromGeoHash returns a point based on full precision of the input GeoHash string. + If no precision is specified ST_PointFromGeoHash returns a point based on full precision of the input GeoHash string. If precision is specified ST_PointFromGeoHash will use that many characters from the GeoHash to create the point. 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 factor parameter allows passing a 2d, 3dm, 3dz or 4d point to set scaling factor for all supported dimensions. Missing dimensions in the factor -point are equivalant to no scaling the corresponding dimension. +point are equivalent to no scaling the corresponding dimension. Prior to 1.3.4, this function crashes if used with geometries that contain CURVES. This is fixed in 1.3.4+ 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 TRUE 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 FALSE. 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 - 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. Refer to X3D specs specifying a spatial reference system.. Default output will be GeoCoordinate geoSystem='"GD" "WE" "longitude_first"'. If + 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. Refer to X3D specs specifying a spatial reference system.. Default output will be GeoCoordinate geoSystem='"GD" "WE" "longitude_first"'. If you prefer the X3D default of GeoCoordinate geoSystem='"GD" "WE" "latitude_first"' use (2 + 1) = 3 @@ -973,7 +973,7 @@ x3dfrag Return a GeoHash representation (http://en.wikipedia.org/wiki/Geohash) 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. - If no maxchars 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. + If no maxchars 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. If maxchars 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. 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 - If padwithnodata = FALSE, edge tiles on the right and bottom sides of the raster may have different dimensions than the rest of the tiles. If padwithnodata = 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 nodataval. + If padwithnodata = FALSE, edge tiles on the right and bottom sides of the raster may have different dimensions than the rest of the tiles. If padwithnodata = 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 nodataval. @@ -2267,7 +2267,7 @@ raster coverage (tab, col). - If srid is NULL, the function will try to autmatically assign the SRID from the GDAL raster. If srid is provided, the value provided will override any automatically assigned SRID. + If srid is NULL, the function will try to automatically assign the SRID from the GDAL raster. If srid is provided, the value provided will override any automatically assigned SRID. Availability: 2.1.0