diff --git a/doc/README b/doc/README index 2dcafea..d7df892 100644 --- a/doc/README +++ b/doc/README @@ -2,7 +2,7 @@ Overview ==================================================== -Postgis documentation is written in docbook xml. The input file is postgis.xml, +PostGIS documentation is written in docbook xml. The input file is postgis.xml, which in turn includes all the individual chapter xml files. From that file we can convert to chunked html, single-file html and pdf. @@ -11,11 +11,11 @@ Make targets are: make # defaults to creating # - the images used in the generated documentation # - the documentation as a single html file - # - a sql script used to apply COMMENTS for every postgis function + # - a sql script used to apply COMMENTS for every PostGIS function make html/postgis.html # generates a single-file html file called html/postgis.html make chunked-html # generates a separate html file for every chapter or section break - make pdf # generates a single pdf file with the postgis version as a filename + make pdf # generates a single pdf file with the PostGIS version as a filename make images # generates all the images used in the html and pdf targets make comments # generates a sql script that add COMMENTs for every function (derived from the documentation) make doxygen # generates the developer's documentation using Doxygen diff --git a/doc/extras_tigergeocoder.xml b/doc/extras_tigergeocoder.xml index cd33796..3269bc6 100644 --- a/doc/extras_tigergeocoder.xml +++ b/doc/extras_tigergeocoder.xml @@ -83,7 +83,7 @@ --------+---------------------------+------+---------+------+--------+----+------- 0 | POINT(-71.05518 42.36311) | 226 | Hanover | St | Boston | MA | 02113 -Can handle misspellings and provides more than one possible solution with ratings and takes longer (4 seconds on fairly crappy single processor 3GIG RAM XP box, but 453 ms on windows 2003 8 GIG ram 2 processor quad core server) . +Can handle misspellings and provides more than one possible solution with ratings and takes longer (4 seconds on fairly crappy single processor 3GIG RAM XP box, but 453 ms on windows 2003 8 GIG ram 2 processor quad core server). SELECT g.rating, ST_AsText(ST_SnapToGrid(g.geomout,0.00001)) As wktlonlat, (addy).address As stno, (addy).streetname As street, (addy).streettypeabbrev As styp, (addy).location As city, (addy).stateabbrev As st,(addy).zip diff --git a/doc/faq.xml b/doc/faq.xml index 8f71817..2d3b4ce 100644 --- a/doc/faq.xml +++ b/doc/faq.xml @@ -85,7 +85,7 @@ SELECT MAX(ST_NPoints(geom)) FROM sometable; Your questions are too deep and complex to be adequately answered in this section. Please refer to our - . + . diff --git a/doc/faq_raster.xml b/doc/faq_raster.xml index 38d35d6..e2dbb91 100644 --- a/doc/faq_raster.xml +++ b/doc/faq_raster.xml @@ -39,7 +39,7 @@ The easiest is to download binaries for PostGIS and Raster which are currently available for windows and latest versions of Mac OSX. - First you need a working PostGIS 1.3.5 or above and be running PostgreSQL 8.3, 8.4, or 9.0. Note in POstGIS 2.0 PostGIS Raster is fully integrated, so it will be compiled when you compile PostGIS. + First you need a working PostGIS 1.3.5 or above and be running PostgreSQL 8.3, 8.4, or 9.0. Note in PostGIS 2.0 PostGIS Raster is fully integrated, so it will be compiled when you compile PostGIS. If you are on windows, you can compile yourself, or use the pre-compiled @@ -90,8 +90,8 @@ - Any that your gdal library supports. GDAL supported formats are documented GDAL File Formats. - Your particular gdal install may not support all formats. To verify the ones supported by your particular gdal install, you can use + Any that your GDAL library supports. GDAL supported formats are documented GDAL File Formats. + Your particular GDAL install may not support all formats. To verify the ones supported by your particular GDAL install, you can use gdalinfo --formats @@ -109,13 +109,13 @@ If you are compiling from source, you need to include in your configure --with-pg=path/to/pg_config to enable the driver. Refer to GDAL Build Hints for tips - on building gdal against in various OS platforms. + on building GDAL against in various OS platforms. If your version of GDAL is compiled with the PostGIS Raster driver you should see PostGIS Raster in list when you do gdalinfo --formats - To get a summary about your raster via gdal use gdalinfo: + To get a summary about your raster via GDAL use gdalinfo: gdalinfo "PG:host=localhost port=5432 dbname='mygisdb' user='postgres' password='whatever' schema='someschema' table=sometable" @@ -142,7 +142,7 @@ We know for sure the following windows binaries have PostGIS Raster built in. FWTools latest stable version for Windows is compiled with Raster support. PostGIS Raster is undergoing many changes. If you want to get the latest nightly build for Windows -- then check out - the Tamas Szekeres nightly builds built with Visual Studio which contain GDAL trunk, Python Bindings and Mapserver executables and PostGIS Raster driver built-in. Just + the Tamas Szekeres nightly builds built with Visual Studio which contain GDAL trunk, Python Bindings and MapServer executables and PostGIS Raster driver built-in. Just click the SDK bat and run your commands from there. http://vbkto.dyndns.org/sdk/. Also available are VS project files. @@ -162,16 +162,16 @@ - How can I add a PostGIS raster layer to my Mapserver map? + How can I add a PostGIS raster layer to my MapServer map? You can much like you can with any other raster. - Refer to Mapserver Raster processing options - for list of various processing functions you can use with Mapserver raster layers. + Refer to MapServer Raster processing options + for list of various processing functions you can use with MapServer raster layers. What makes PostGIS raster data particularly interesting, is that since each tile can have various standard database columns, you can segment it in your data source - Below is an example of how you would define a PostGIS raster layer in Mapserver. + Below is an example of how you would define a PostGIS raster layer in MapServer. -- displaying raster with standard raster options LAYER diff --git a/doc/geography.txt b/doc/geography.txt index 74dc5a0..976e6f0 100644 --- a/doc/geography.txt +++ b/doc/geography.txt @@ -140,7 +140,7 @@ You can also add SRID restrictions to a column, though at this point (with only Using Input/Output Functions ============================ -There are only four intput/output functions at this time supporting the OGC well-known text (WKT) and well-known binary (WKB) formats. Adding further output formats (GML, GeoJSON) should be straight-forward, borrowing code from the geometry implementations. +There are only four input/output functions at this time supporting the OGC well-known text (WKT) and well-known binary (WKB) formats. Adding further output formats (GML, GeoJSON) should be straight-forward, borrowing code from the geometry implementations. * ST_AsText(geography) returns text * ST_AsBinary(geography) returns bytea diff --git a/doc/installation.xml b/doc/installation.xml index c3f520d..43527d4 100644 --- a/doc/installation.xml +++ b/doc/installation.xml @@ -796,7 +796,7 @@ Failed: 0 - Before attempting to upgrade postgis, it is always worth to backup your + Before attempting to upgrade PostGIS, it is always worth to backup your data. If you use the -Fc flag to pg_dump you will always be able to restore the dump with an HARD UPGRADE. @@ -807,7 +807,7 @@ Failed: 0 After compiling you should find several postgis_upgrade*.sql files. Install the one for your version of PostGIS. For example postgis_upgrade_13_to_15.sql should be used if you are upgrading - from postgis 1.3 to 1.5. + from PostGIS 1.3 to 1.5. $ psql -f postgis_upgrade_13_to_15.sql -d your_spatial_database @@ -834,7 +834,7 @@ Failed: 0 By HARD UPGRADE we intend full dump/reload of postgis-enabled databases. - You need an HARD UPGRADE when postgis objects' internal storage changes + You need an HARD UPGRADE when PostGIS objects' internal storage changes or when SOFT UPGRADE is not possible. The Release Notes appendix reports for each version whether you need a dump/reload (HARD @@ -855,7 +855,7 @@ Failed: 0 $ pg_dump -Fc olddb > olddb.dump - Restore the dump contextually upgrading postgis into a new database. The + Restore the dump contextually upgrading PostGIS into a new database. The new database doesn't have to exist. postgis_restore accepts createdb parameters after the dump file name, and that can for instance be used if you are using a non-default character encoding for your database. diff --git a/doc/reference_accessor.xml b/doc/reference_accessor.xml index c384010..6069728 100644 --- a/doc/reference_accessor.xml +++ b/doc/reference_accessor.xml @@ -845,7 +845,7 @@ postgis=# SELECT ST_IsCollection('GEOMETRYCOLLECTION(POINT(0 0))'::geometry); ST_IsEmpty - Returns true if this Geometry is an empty geometry . If + Returns true if this Geometry is an empty geometry. If true, then this Geometry represents the empty point set - i.e. GEOMETRYCOLLECTION(EMPTY). @@ -863,7 +863,7 @@ postgis=# SELECT ST_IsCollection('GEOMETRYCOLLECTION(POINT(0 0))'::geometry); Description - Returns true if this Geometry is an empty geometry . If + Returns true if this Geometry is an empty geometry. If true, then this Geometry represents an empty geometry collection, polygon, point etc. SQL-MM defines the result of ST_IsEmpty(NULL) to be 0, while diff --git a/doc/reference_lrs.xml b/doc/reference_lrs.xml index 2dccd12..eda4f97 100644 --- a/doc/reference_lrs.xml +++ b/doc/reference_lrs.xml @@ -209,7 +209,7 @@ FROM (SELECT ST_GeomFromText('LINESTRING(1 2, 4 5, 6 7)') As the_line) As foo; unspecified values. - Availability: 1.1.0 , Z and M supported added in 1.1.1 + Availability: 1.1.0, Z and M supported added in 1.1.1 &Z_support; diff --git a/doc/reference_misc.xml b/doc/reference_misc.xml index db72441..fb1ab15 100644 --- a/doc/reference_misc.xml +++ b/doc/reference_misc.xml @@ -595,7 +595,7 @@ fulltable_size geomsize pergeom ST_Point_Inside_Circle - Is the point geometry insert circle defined by center_x, center_y , radius + Is the point geometry insert circle defined by center_x, center_y, radius diff --git a/doc/reference_output.xml b/doc/reference_output.xml index e8110a8..40bd07d 100644 --- a/doc/reference_output.xml +++ b/doc/reference_output.xml @@ -827,7 +827,7 @@ SELECT ST_AsGML(3, ST_GeomFromEWKT('POLYHEDRALSURFACE( ((0 0 0, 0 0 1, 0 1 1, 0 geometries are delimited by semicolons (";"). - Availability: 1.2.2 . Availability: 1.4.0 Changed in PostGIS 1.4.0 to include L command in absolute path to conform to Availability: 1.2.2. Availability: 1.4.0 Changed in PostGIS 1.4.0 to include L command in absolute path to conform to http://www.w3.org/TR/SVG/paths.html#PathDataBNF diff --git a/doc/reference_processing.xml b/doc/reference_processing.xml index fca2622..228d6bf 100644 --- a/doc/reference_processing.xml +++ b/doc/reference_processing.xml @@ -2392,7 +2392,7 @@ MULTILINESTRING((1 3 2.75,1 4 2),(1 1 3,1 2 2.25)) Description - Output type can be a MULTI* , single geometry, or Geometry Collection. Comes in 2 variants. Variant 1 unions 2 geometries resulting in a new geometry with no intersecting regions. + Output type can be a MULTI*, single geometry, or Geometry Collection. Comes in 2 variants. Variant 1 unions 2 geometries resulting in a new geometry with no intersecting regions. Variant 2 is an aggregate function that takes a set of geometries and unions them into a single ST_Geometry resulting in no intersecting regions. @@ -2403,7 +2403,7 @@ MULTILINESTRING((1 3 2.75,1 4 2),(1 1 3,1 2 2.25)) functions do. Non-Aggregate version: This function returns a geometry being a union of two - input geometries. Output type can be a MULTI* ,NON-MULTI or + input geometries. Output type can be a MULTI*, NON-MULTI or GEOMETRYCOLLECTION. ST_Collect and ST_Union are often interchangeable. diff --git a/doc/reference_raster.xml b/doc/reference_raster.xml index dbc1068..c1734d8 100644 --- a/doc/reference_raster.xml +++ b/doc/reference_raster.xml @@ -828,7 +828,7 @@ FROM dummy_rast; ST_Raster2WorldCoordX - Returns the geometric x coordinate upper left of a raster , column and row. Numbering of columns + Returns the geometric x coordinate upper left of a raster, column and row. Numbering of columns and rows starts at 1. @@ -902,7 +902,7 @@ FROM (SELECT rid, ST_SetSkew(rast,100.5,0) As rast FROM dummy_rast) As foo; ST_Raster2WorldCoordY - Returns the geometric y coordinate upper left corner of a raster , column and row. Numbering of columns + Returns the geometric y coordinate upper left corner of a raster, column and row. Numbering of columns and rows starts at 1. diff --git a/doc/release_notes.xml b/doc/release_notes.xml index 1b99e23..8296bea 100644 --- a/doc/release_notes.xml +++ b/doc/release_notes.xml @@ -26,7 +26,7 @@ Making spatial indexes 3D aware - in progress (Paul Ramsey, Mark Cave-Ayland) Topology support improved, documented, testing (Sandro Santilli / Faunalia for RT-SIGTA, Regina Obe, Andrea Peri) 3D relationship support functions (Nicklas Avén) - ST_3DDistance, ST_3DClosestPoint, ST_3DIntersects, ST_3DShortestLine and more .. + ST_3DDistance, ST_3DClosestPoint, ST_3DIntersects, ST_3DShortestLine and more... ST_Split (Sandro Santilli / Faunalia for RT-SIGTA) ST_isValidDetail (Sandro Santilli / Faunalia for RT-SIGTA) ST_MakeValid (Sandro Santilli / Faunalia for RT-SIGTA) @@ -236,7 +236,7 @@ Release date: 2008/12/15 This release is a bug fix release to address a failure in ST_Force_Collection and related functions that critically - affects using Mapserver with LINE layers. + affects using MapServer with LINE layers. diff --git a/doc/using_postgis_dataman.xml b/doc/using_postgis_dataman.xml index f5472f8..63b44d3 100644 --- a/doc/using_postgis_dataman.xml +++ b/doc/using_postgis_dataman.xml @@ -133,7 +133,7 @@ geometry = ST_GeometryFromText(text WKT, SRID); - MULTICURVE( (0 0, 5 5) ,CIRCULARSTRING(4 0, 4 4, 8 4) ) + MULTICURVE( (0 0, 5 5), CIRCULARSTRING(4 0, 4 4, 8 4) ) diff --git a/doc/xsl/postgis_aggs_mm.xml.xsl b/doc/xsl/postgis_aggs_mm.xml.xsl index 66a8842..46a8026 100644 --- a/doc/xsl/postgis_aggs_mm.xml.xsl +++ b/doc/xsl/postgis_aggs_mm.xml.xsl @@ -323,7 +323,7 @@ - +