From: Mark Cave-Ayland Date: Thu, 11 Sep 2008 12:04:36 +0000 (+0000) Subject: Documentation fixes to allow PDF documents to be generated from Docbook source using... X-Git-Tag: 1.4.0b1~748 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=37c221f600a393430408b7502033bc8b3f727ace;p=postgis Documentation fixes to allow PDF documents to be generated from Docbook source using OpenJade - OpenJade seems a lot more strict than xsltproc when generating output :( git-svn-id: http://svn.osgeo.org/postgis/trunk@2956 b70326c6-7e19-0410-871a-916f4a2858ee --- diff --git a/doc/reference_new.xml b/doc/reference_new.xml index 5e887f70a..d7495cd8c 100644 --- a/doc/reference_new.xml +++ b/doc/reference_new.xml @@ -109,7 +109,7 @@ 'MULTILINESTRING'. - + This method implements the OpenGIS Simple Features Implementation Specification for SQL. @@ -213,7 +213,7 @@ Check constraints: row in the geometry_columns table. - + This method implements the OpenGIS Simple Features Implementation Specification for SQL. @@ -1345,10 +1345,10 @@ SELECT userpoints.id, ST_MakeLine(startpoint, endpoint) As drawn_line Description - >Creates a 2d,3dz or 4d point geometry (geometry with measure). ST_MakePoint while not being + Creates a 2d,3dz or 4d point geometry (geometry with measure). ST_MakePoint while not being OGC compliant is generally faster and more precise than ST_GeomFromText and ST_PointFromText. It is also easier to use if you have raw coordinates rather than WKT. - Note x is longitude and y is latitude + Note x is longitude and y is latitude @@ -2232,9 +2232,9 @@ NOTICE: Self-intersection at or near point 0 0 Description Returns the spatial reference identifier for the ST_Geometry as defined in spatial_ref_sys table. - spatial_ref_sys + spatial_ref_sys table is a table that catalogs all spatial reference systems known to PostGIS and is used for transformations from one spatial - reference system to another. So verifying you have the right spatial reference system identifier is important if you plan to ever transform your geometries. + reference system to another. So verifying you have the right spatial reference system identifier is important if you plan to ever transform your geometries. @@ -2621,7 +2621,7 @@ SELECT ST_AsText(ST_SetPoint('LINESTRING(-1 2,-1 3)', 1, 'POINT(-1 1)')); - + This method implements the OpenGIS Simple Features Implementation Specification for SQL. @@ -2965,7 +2965,7 @@ CREATE INDEX idx_the_geom_26986_parcels The WKT spec does not include the SRID. To get the OGC WKT format use ST_AsText - + WKT format does not maintain precision so to prevent floating truncation, use ST_AsBinary or ST_AsEWKB format for transport. @@ -3331,7 +3331,7 @@ SRID=4326;POLYGON((0 0,0 1,1 1,1 0,0 0)) The WKT spec does not include the SRID. To get the SRID as part of the data, use the non-standard PostGIS - + WKT format does not maintain precision so to prevent floating truncation, use ST_AsBinary or ST_AsEWKB format for transport. @@ -3381,6 +3381,7 @@ F000000000000000000000000000000000000000000000000'); Operators +   @@ -3749,7 +3750,6 @@ st_area Do not call with a GEOMETRYCOLLECTION as an argument - This function call will automatically include a bounding box @@ -3758,17 +3758,18 @@ st_area - + This method implements the OpenGIS Simple Features Implementation Specification for SQL: 1.1: s2.1.13.3 - + This method implements the SQL/MM specification: SQL-MM 3: 5.1.29 - + + Examples @@ -3905,7 +3906,7 @@ WHERE ST_Crosses(roads.the_geom, highways.the_geom); boolean, not an integer. - + This method implements the OGC SPEC s2.1.1.2 //s2.1.13.3 - a.Relate(b, 'FF*FF****') @@ -3961,14 +3962,14 @@ SELECT ST_Disjoint('POINT(0 0)'::geometry, 'LINESTRING ( 0 0, 0 2 )'::geometry); projected units. - + This method implements the OpenGIS Simple Features Implementation Specification for SQL. - + This method implements the SQL/MM specification: SQL-MM 3: 5.1.23 @@ -4031,7 +4032,7 @@ SELECT ST_Disjoint('POINT(0 0)'::geometry, 'LINESTRING ( 0 0, 0 2 )'::geometry); - + This method implements the OpenGIS Simple Features Implementation Specification for SQL. @@ -4102,7 +4103,7 @@ SELECT s.gid, s.school_name - + This method implements the OpenGIS Simple Features Implementation Specification for SQL OGC SPEC s2.1.1.2 @@ -4190,13 +4191,13 @@ SELECT ST_Equals(ST_Reverse(ST_GeomFromText('LINESTRING(0 0, 10 10)')), boolean, not an integer. - + This method implements the OpenGIS Simple Features Implementation Specification for SQL - + OGC SPEC s2.1.1.2 //s2.1.13.3 - ST_Intersects(g1, g2 ) --> Not (ST_Disjoint(g1, g2 )) @@ -4310,7 +4311,7 @@ st_length - + This method implements the SQL/MM specification: SQL-MM 3: 5.1.43 @@ -4385,7 +4386,7 @@ SELECT ST_OrderingEquals(ST_Reverse(ST_GeomFromText('LINESTRING(0 0, 10 10)')), OGC SPEC s2.1.1.2 // s2.1.13.3 - + This method implements the SQL/MM specification: SQL-MM 3: 5.1.32 @@ -4857,14 +4858,17 @@ FROM (SELECT ST_Buffer(ST_GeomFromText('POINT(1 2)'), 10) As smallc, Linear Referencing +   Long Transactions Support +   Misc +   - \ No newline at end of file + diff --git a/doc/using_postgis.xml b/doc/using_postgis.xml index 90d8a1eeb..98f62617e 100644 --- a/doc/using_postgis.xml +++ b/doc/using_postgis.xml @@ -512,7 +512,7 @@ SELECT AddGeometryColumn( 'roads', 'roads_geom', -1, 'GEOMETRY', 3 );Most of the functions implemented by the GEOS library rely on the assumption that your geometries are valid as specified by the OpenGIS Simple Feature Specification. To check validity of geometries you can - use the IsValid() function: + use the IsValid() function: gisdb=# select isvalid('LINESTRING(0 0, 1 1)'), isvalid('LINESTRING(0 0,0 0)'); @@ -540,7 +540,7 @@ SELECT AddGeometryColumn( 'roads', 'roads_geom', -1, 'GEOMETRY', 3 ); Strictly compliant OGC geometries cannot have Z or M values. The - IsValid() function won't consider + IsValid() function won't consider higher dimensioned geometries invalid! Invocations of AddGeometryColumn() will add a constraint checking geometry dimensions, so it is enough to specify 2