<para>An example of a topologically based GIS database is the <ulink url="http://www.census.gov/geo/www/tiger/overview.html">US Census Topologically Integrated Geographic Encoding and Reference System (TIGER)</ulink> database.</para>
<para>The PostGIS topology module has existed in prior versions of PostGIS but was never part of the Official PostGIS documentation.
In PostGIS 2.0.0 major cleanup is going on to remove use of all deprecated functions in it, fix known usability issues, better document the features and functions, add new functions, and enhance to closer conform to SQL-MM standards.</para>
- <para>Details of this project can be found at <ulink url="http://trac.osgeo.org/postgis/wiki/UsersWikiPostgisTopology">PostGIS Tology Wiki</ulink></para>
+ <para>Details of this project can be found at <ulink url="http://trac.osgeo.org/postgis/wiki/UsersWikiPostgisTopology">PostGIS Topology Wiki</ulink></para>
<para>All functions and tables associated with this module are installed in a schema called <varname>topology</varname>.</para>
<para>Functions that are defined in SQL/MM standard are prefixed with ST_ and functions specific to PostGIS are not prefixed.</para>
<para>To build PostGIS 2.0 with topology support, compile with the --with-topology option as described in <xref linkend="postgis_installation"/>. Some functions depend on GEOS 3.3+ so you should compile with GEOS 3.3+ to fully utilize the topology support.</para>
</para>
<note><para>
-The new rows in topology.layer will contain synthetized values for schema_name, table_name and feature_column. This is because the TopoGeometry will only exist as a definition but won't be available in any user-level table yet.
+The new rows in topology.layer will contain synthesized values for schema_name, table_name and feature_column. This is because the TopoGeometry will only exist as a definition but won't be available in any user-level table yet.
</para></note>
<!-- use this format if new function -->
<answer>
<para>You can use MapServer compiled with GDAL 1.7+ and PostGIS Raster driver support to view Raster data.
In theory any tool that renders data using GDAL can support PostGIS raster data or
- support it with fairly minimal effort. Again for Windows
Tamas binaries <ulink url="http://vbkto.dyndns.org/sdk/">http://vbkto.dyndns.org/sdk/</ulink> are a good choice if you don't want the hassle of having to setup to compile your own.</para>
+ support it with fairly minimal effort. Again for Windows
, Tamas' binaries <ulink url="http://vbkto.dyndns.org/sdk/">http://vbkto.dyndns.org/sdk/</ulink> are a good choice if you don't want the hassle of having to setup to compile your own.</para>
</answer>
</qandaentry>
<term>Chris Hodgson</term>
<listitem>
- <para>General development, site and buildbot maintainance, OSGeo incubation management</para>
+ <para>General development, site and buildbot maintenance, OSGeo incubation management</para>
</listitem>
</varlistentry>
<term>Kevin Neufeld</term>
<listitem>
<para>Prior PSC Member. Documentation and documentation support tools, advanced user support
- on PostGIS newsgroup, and postgis maintenance function enhancements.</para>
+ on PostGIS newsgroup, and PostGIS maintenance function enhancements.</para>
</listitem>
</varlistentry>
Use a binary cursor. When used on pre\-1.0.0 PostGIS versions this will
reduce the likelihood of coordinate drift due to conversion to and from
WKT format. Coordinate drifts will not occur with PostGIS 1.0.0 and newer
-versions. It will be slightly faster, but might fail if any NON\-gemetry
+versions. It will be slightly faster, but might fail if any NON\-geometry
column lacks a cast to text.
.TP
\fB\-r\fR
<para>The target_percent is the target percent of area of convex hull the PostGIS solution will try to approach before giving up or exiting.
One can think of the concave hull as the geometry you get by vacuum sealing a set of geometries. The
target_percent of 1 will give you the same answer as the convex hull. A target_percent
- between 0 and 0.99 will give you something that should have a smaller area than the convex ull. This is different from a convex hull which is more like wrapping a rubber band around the set of geometries.</para>
+ between 0 and 0.99 will give you something that should have a smaller area than the convex hull. This is different from a convex hull which is more like wrapping a rubber band around the set of geometries.</para>
<para>It is usually used with MULTI and Geometry Collections.
Although it is not an aggregate - you can use it in conjunction
<para>It is often used with MULTI and Geometry Collections.
Although it is not an aggregate - you can use it in conjunction
- with ST_Collect to get the minimum bounding cirlce of a set of geometries.
+ with ST_Collect to get the minimum bounding circle of a set of geometries.
ST_MinimumBoundingCircle(ST_Collect(somepointfield)).</para>
<para>The ratio of the area of a polygon divided by the area of its Minimum Bounding Circle is often referred to as the Roeck test.</para>
<title>Description</title>
<para>Returns a single band of an existing raster as a new raster. Useful for building new rasters from existing rasters or export of only selected
- bands of a raster. If no band is specified, band 1 is assumed. Used as a helper function in various functons suc as for deleting a band.</para>
+ bands of a raster. If no band is specified, band 1 is assumed. Used as a helper function in various functions such as for deleting a band.</para>
<para>Availability: 2.0.0</para>
</refsection>
<refsection>
<title>Description</title>
- <para>Set the value of the uppler left corner of raster to the projected x coordinates</para>
+ <para>Set the value of the upper left corner of raster to the projected x coordinates</para>
</refsection>
<refsection>
<listitem>
<varname>nbands</varname> is an array of bands to export (note that max is 3 for PNG) and the order of the bands is RGB. e.g ARRAY[3,2,1] means map band 3 to Red, band 2 to green and band 1 to blue
</listitem>
- <listitem><varname>compression</varname> Compression expression -- JPEG90 (or someother percent), LZW, JPEG, DEFLATE9. </listitem>
+ <listitem><varname>compression</varname> Compression expression -- JPEG90 (or some other percent), LZW, JPEG, DEFLATE9. </listitem>
<listitem><varname>options</varname> text Array of GDAL create options as defined for GTiff (look at create_options for GTiff of <xref linkend="RT_ST_GDALDrivers" />). or refer to <ulink url="http://www.gdal.org/frmt_various.html">GDAL Raster format options</ulink> for more details. </listitem>
<listitem><varname>srid</varname> srid of spatial_ref_sys of the raster. This is used to populate the georeference information </listitem>
</itemizedlist>
projects / postgis / commitdiff