liquid_feedback_core
changeset 530:6bc81898fd3b
Fixed typo in documentation and comments: "indicies" -> "indices"; Marked make-doc.sh as executable
author | jbe |
---|---|
date | Sun Aug 21 16:28:21 2016 +0200 (2016-08-21) |
parents | 96ee2db56bec |
children | 37d6d15919f1 |
files | pgLatLon/README.html pgLatLon/README.mkd pgLatLon/latlon-v0001.c pgLatLon/make-doc.sh |
line diff
1.1 --- a/pgLatLon/README.html Thu Aug 18 20:19:58 2016 +0200 1.2 +++ b/pgLatLon/README.html Sun Aug 21 16:28:21 2016 +0200 1.3 @@ -8,7 +8,7 @@ 1.4 <p>While many other spatial databases still use imprecise bounding boxes for many 1.5 operations, pgLatLon supports more precise geometric calculations for all 1.6 implemented operators. Efficient indexing of geometric objects is provided 1.7 -using fractal indicies. Optimizations on bit level (including logarithmic 1.8 +using fractal indices. Optimizations on bit level (including logarithmic 1.9 compression) allow for a highly memory-efficient non-overlapping index suitable 1.10 for huge datasets.</p> 1.11 1.12 @@ -161,13 +161,13 @@ 1.13 1.14 <p>Two kinds of indices are supported: B-tree and GiST indices.</p> 1.15 1.16 -<h4>B-tree indicies</h4> 1.17 +<h4>B-tree indices</h4> 1.18 1.19 <p>A B-tree index can be used for simple equality searches and is supported by the 1.20 <code>epoint</code>, <code>ebox</code>, and <code>ecircle</code> data types. B-tree indices can not be used for 1.21 geographic searches.</p> 1.22 1.23 -<h4>GiST indicies</h4> 1.24 +<h4>GiST indices</h4> 1.25 1.26 <p>For geographic searches, GiST indices must be used. The <code>epoint</code>, <code>ecircle</code>, 1.27 and <code>ecluster</code> data types support GiST indexing. A GiST index for geographic 1.28 @@ -180,10 +180,10 @@ 1.29 CREATE INDEX name_of_index ON tbl USING gist (loc); 1.30 </code></pre> 1.31 1.32 -<p>GiST indicies also support nearest neighbor searches when using the distance 1.33 +<p>GiST indices also support nearest neighbor searches when using the distance 1.34 operator (<code><-></code>) in the ORDER BY clause.</p> 1.35 1.36 -<h4>Indicies on other data types (e.g. GeoJSON)</h4> 1.37 +<h4>Indices on other data types (e.g. GeoJSON)</h4> 1.38 1.39 <p>Note that further types can be indexed by using an index on an expression with 1.40 a conversion function. One conversion function provided by pgLatLon is the
2.1 --- a/pgLatLon/README.mkd Thu Aug 18 20:19:58 2016 +0200 2.2 +++ b/pgLatLon/README.mkd Sun Aug 21 16:28:21 2016 +0200 2.3 @@ -8,7 +8,7 @@ 2.4 While many other spatial databases still use imprecise bounding boxes for many 2.5 operations, pgLatLon supports more precise geometric calculations for all 2.6 implemented operators. Efficient indexing of geometric objects is provided 2.7 -using fractal indicies. Optimizations on bit level (including logarithmic 2.8 +using fractal indices. Optimizations on bit level (including logarithmic 2.9 compression) allow for a highly memory-efficient non-overlapping index suitable 2.10 for huge datasets. 2.11 2.12 @@ -158,13 +158,13 @@ 2.13 2.14 Two kinds of indices are supported: B-tree and GiST indices. 2.15 2.16 -#### B-tree indicies 2.17 +#### B-tree indices 2.18 2.19 A B-tree index can be used for simple equality searches and is supported by the 2.20 `epoint`, `ebox`, and `ecircle` data types. B-tree indices can not be used for 2.21 geographic searches. 2.22 2.23 -#### GiST indicies 2.24 +#### GiST indices 2.25 2.26 For geographic searches, GiST indices must be used. The `epoint`, `ecircle`, 2.27 and `ecluster` data types support GiST indexing. A GiST index for geographic 2.28 @@ -176,10 +176,10 @@ 2.29 2.30 CREATE INDEX name_of_index ON tbl USING gist (loc); 2.31 2.32 -GiST indicies also support nearest neighbor searches when using the distance 2.33 +GiST indices also support nearest neighbor searches when using the distance 2.34 operator (`<->`) in the ORDER BY clause. 2.35 2.36 -#### Indicies on other data types (e.g. GeoJSON) 2.37 +#### Indices on other data types (e.g. GeoJSON) 2.38 2.39 Note that further types can be indexed by using an index on an expression with 2.40 a conversion function. One conversion function provided by pgLatLon is the
3.1 --- a/pgLatLon/latlon-v0001.c Thu Aug 18 20:19:58 2016 +0200 3.2 +++ b/pgLatLon/latlon-v0001.c Sun Aug 21 16:28:21 2016 +0200 3.3 @@ -2384,7 +2384,7 @@ 3.4 PG_RETURN_POINTER(out); 3.5 } 3.6 3.7 -/* GiST "compress" support function for indicies on points */ 3.8 +/* GiST "compress" support function for indicis on points */ 3.9 PG_FUNCTION_INFO_V1(pgl_gist_compress_epoint); 3.10 Datum pgl_gist_compress_epoint(PG_FUNCTION_ARGS) { 3.11 GISTENTRY *entry = (GISTENTRY *) PG_GETARG_POINTER(0); 3.12 @@ -2411,7 +2411,7 @@ 3.13 PG_RETURN_POINTER(retval); 3.14 } 3.15 3.16 -/* GiST "compress" support function for indicies on circles */ 3.17 +/* GiST "compress" support function for indicis on circles */ 3.18 PG_FUNCTION_INFO_V1(pgl_gist_compress_ecircle); 3.19 Datum pgl_gist_compress_ecircle(PG_FUNCTION_ARGS) { 3.20 GISTENTRY *entry = (GISTENTRY *) PG_GETARG_POINTER(0); 3.21 @@ -2438,7 +2438,7 @@ 3.22 PG_RETURN_POINTER(retval); 3.23 } 3.24 3.25 -/* GiST "compress" support function for indicies on clusters */ 3.26 +/* GiST "compress" support function for indices on clusters */ 3.27 PG_FUNCTION_INFO_V1(pgl_gist_compress_ecluster); 3.28 Datum pgl_gist_compress_ecluster(PG_FUNCTION_ARGS) { 3.29 GISTENTRY *entry = (GISTENTRY *) PG_GETARG_POINTER(0); 3.30 @@ -2467,7 +2467,7 @@ 3.31 PG_RETURN_POINTER(retval); 3.32 } 3.33 3.34 -/* GiST "decompress" support function for indicies */ 3.35 +/* GiST "decompress" support function for indices */ 3.36 PG_FUNCTION_INFO_V1(pgl_gist_decompress); 3.37 Datum pgl_gist_decompress(PG_FUNCTION_ARGS) { 3.38 /* return passed pointer without transformation */