Commit 7c689f00 authored by Regina Obe's avatar Regina Obe

we have too many new functions (those polyhedral things that should really be...

we have too many new functions (those polyhedral things that should really be marked as enhancements) and we are going to have a lot of breaking changes.  Revise what's new section to have a really new, enhanced, and behavior changed section

git-svn-id: http://svn.osgeo.org/postgis/[email protected] b70326c6-7e19-0410-871a-916f4a2858ee
parent 79f3c033
......@@ -35,7 +35,7 @@
<para>This function also indicates if the geometry is measured,
by returning a string of the form 'POINTM'.</para>
</note>
<para>Availability: 2.0.0 support for Polyhedral surfaces was introduced.</para>
<para>Enhanced: 2.0.0 support for Polyhedral surfaces was introduced.</para>
<para>&sfs_compliant;</para>
<para>&curve_support;</para>
<para>&Z_support;</para>
......@@ -222,7 +222,7 @@ MULTIPOINT(-1 1 1,1 1 0.75)
</para>
<para>&sqlmm_compliant; SQL-MM 3: 5.1.2</para>
<para>Availability: 2.0.0 support for Polyhedral surfaces was introduced. No longer throws an exception if given empty geometry.</para>
<para>Enhanced: 2.0.0 support for Polyhedral surfaces was introduced. No longer throws an exception if given empty geometry.</para>
<note> <para>Prior to 2.0.0, this function throws an exception if used with empty geometry. </para></note>
<para>&P_support;</para>
</refsection>
......@@ -487,7 +487,7 @@ LINESTRING(0 0 1,1 1 1,1 2 1,1 1 1,0 0 1)
<note>
<para>If you want to extract all geometries, of a geometry, ST_Dump is more efficient and will also work for singular geoms.</para>
</note>
<para>Availability: 2.0.0 support for Polyhedral surfaces was introduced.</para>
<para>Enhanced: 2.0.0 support for Polyhedral surfaces was introduced.</para>
<para>&sfs_compliant;</para>
<para>&sqlmm_compliant; SQL-MM 3: 9.1.5</para>
<para>&Z_support;</para>
......@@ -556,7 +556,7 @@ WHERE n &lt;= ST_NumGeometries(the_geom);
<para>Returns the type of the geometry as a string. EG: 'ST_Linestring', 'ST_Polygon','ST_MultiPolygon' etc. This function differs from GeometryType(geometry) in the case of the string and ST in front that is returned, as well as the fact that it will not indicate whether the geometry is measured.</para>
<para>Availability: 2.0.0 support for Polyhedral surfaces was introduced.</para>
<para>Enhanced: 2.0.0 support for Polyhedral surfaces was introduced.</para>
<para>&sqlmm_compliant; SQL-MM 3: 5.1.4</para>
<para>&Z_support;</para>
<para>&P_support;</para>
......@@ -681,7 +681,7 @@ FROM (SELECT ST_BuildArea(
<para>&Z_support;</para>
<para>&curve_support;</para>
<para>Availability: 2.0.0 support for Polyhedral surfaces was introduced.</para>
<para>Enhanced: 2.0.0 support for Polyhedral surfaces was introduced.</para>
<para>&P_support;</para>
......@@ -1367,7 +1367,7 @@ SELECT * FROM ST_IsValidDetail('LINESTRING(220227 150406,2220227 150407,222020 1
<title>Description</title>
<para>Return the number of points in a geometry. Works for all geometries.</para>
<para>Availability: 2.0.0 support for Polyhedral surfaces was introduced.</para>
<para>Enhanced: 2.0.0 support for Polyhedral surfaces was introduced.</para>
<note><para>Prior to 1.3.4, this function crashes if used with geometries that contain CURVES. This is fixed in 1.3.4+</para></note>
<para>&Z_support;</para>
<para>&curve_support;</para>
......@@ -1461,7 +1461,7 @@ SELECT ST_NPoints(ST_GeomFromEWKT('LINESTRING(77.29 29.07 1,77.42 29.26 0,77.27
<para>Returns the number of Geometries. If geometry is a GEOMETRYCOLLECTION (or MULTI*) return the
number of geometries, otherwise return NULL.</para>
<para>Availability: 2.0.0 Support for Polyhedral surfaces was introduced.</para>
<para>Enhanced: 2.0.0 support for Polyhedral surfaces was introduced.</para>
<para>&sqlmm_compliant; SQL-MM 3: 9.1.4</para>
<para>&Z_support;</para>
<para>&P_support;</para>
......
......@@ -38,8 +38,10 @@
<!-- use this format if new function -->
<para>Availability: version goes here - requires GEOS &gt;= 3.3.0. </para>
<!-- use this format if not a new function but functionality was changed or enhanced -->
<para>Availability: 2.0.0 support for Polyhedral surfaces, Triangles and TIN was introduced.</para>
<!-- use this format if not a new function but functionality enhanced -->
<para>Enhanced: 2.0.0 support for Polyhedral surfaces, Triangles and TIN was introduced.</para>
<!-- use this format if function behavior has changed that could pose backward compatibility issues -->
<para>Changed: 2.0.0 support for Polyhedral surfaces, Triangles and TIN was introduced.</para>
<!-- Optionally mention OpenGIS compliancy if appropriate -->
<para>&sfs_compliant;</para>
......
......@@ -407,10 +407,10 @@
</sect1>
<sect1 id="NewFunctions">
<title>New PostGIS Functions</title>
<title>New, Enhanced or changed PostGIS Functions</title>
<sect2 id="NewFunctions_2_0">
<title>PostGIS Functions new, behavior changed, or enhanced in 2.0</title>
<para>The functions given below are PostGIS functions that were introduced or enhanced in 2.0 releases.</para>
<para>The functions given below are PostGIS functions that were added, enhanced, or have breaking changes in 2.0 releases.</para>
<itemizedlist>
<!-- Pull out the purpose section for each ref entry and strip whitespace and put in a variable to be tagged unto each function comment -->
<xsl:for-each select='sect1/refentry'>
......@@ -439,6 +439,56 @@
</xsl:for-each>
</xsl:for-each>
</itemizedlist>
<para>The functions given below are PostGIS functions that are enhanced in PostGIS 2.0.</para>
<itemizedlist>
<!-- Pull out the purpose section for each ref entry -->
<xsl:for-each select='sect1/refentry'>
<xsl:sort select="@id"/>
<xsl:variable name="refid">
<xsl:value-of select="@id" />
</xsl:variable>
<xsl:variable name="refname">
<xsl:value-of select="refnamediv/refname" />
</xsl:variable>
<!-- For each section if there is note about enhanced in this version -->
<xsl:for-each select="refsection">
<xsl:for-each select="para">
<xsl:choose>
<xsl:when test="contains(.,'Enhanced: 2.0')">
<listitem><simpara><link linkend="{$refid}"><xsl:value-of select="$refname" /></link> - <xsl:value-of select="." /></simpara></listitem>
</xsl:when>
</xsl:choose>
</xsl:for-each>
</xsl:for-each>
</xsl:for-each>
</itemizedlist>
<para>The functions given below are PostGIS functions that are changed and may be breaking changes in PostGIS 2.0.</para>
<itemizedlist>
<!-- Pull out the purpose section for each ref entry -->
<xsl:for-each select='sect1/refentry'>
<xsl:sort select="@id"/>
<xsl:variable name="refid">
<xsl:value-of select="@id" />
</xsl:variable>
<xsl:variable name="refname">
<xsl:value-of select="refnamediv/refname" />
</xsl:variable>
<!-- For each section if there is note about enhanced in this version -->
<xsl:for-each select="refsection">
<xsl:for-each select="para">
<xsl:choose>
<xsl:when test="contains(.,'Changed: 2.0')">
<listitem><simpara><link linkend="{$refid}"><xsl:value-of select="$refname" /></link> - <xsl:value-of select="." /></simpara></listitem>
</xsl:when>
</xsl:choose>
</xsl:for-each>
</xsl:for-each>
</xsl:for-each>
</itemizedlist>
</sect2>
<sect2 id="NewFunctions_1_5">
<title>PostGIS Functions new, behavior changed, or enhanced in 1.5</title>
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment