Doco on "enhancement" per robe, closes #3097

git-svn-id: http://svn.osgeo.org/postgis/trunk@16128 b70326c6-7e19-0410-871a-916f4a2858ee

diff --git a/NEWS b/NEWS
index 252ed325f71d728daa423bbbde6f879e531116b2..ecac7ba041d60d63014ba65ea5b23c501796c294 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -24,6 +24,7 @@ PostGIS 2.5.0
     #1855, #1946, #3718, #3838
   - #3234, Do not accept EMPTY points as topology nodes (Sandro Santilli)
   - #1014, Hashable geometry, allowing direct use in CTE signatures (Paul Ramsey)
+  - #3097, Really allow MULTILINESTRING blades in ST_Split() (Paul Ramsey)
 
 
 PostGIS 2.4.0

diff --git a/doc/reference_processing.xml b/doc/reference_processing.xml
index f1ad7700157d8d2a9f0d89094c0417b7e566aaca..8289759b9b06b7460330954836b8b2e43fc0632f 100644 (file)
--- a/doc/reference_processing.xml
+++ b/doc/reference_processing.xml
@@ -3084,6 +3084,8 @@ LINESTRING M (5 2 3.40282346638529e+38,3 8 29,6 20 1.5,7 25 49.5,10 10 3.4028234
             <para>Availability: 2.0.0</para>
             <para>Changed: 2.2.0 support for splitting a line by a multiline, a multipoint or (multi)polygon boundary was introduced.</para>
 
+               <para>Enhanced: 2.5.0 support for MULTILINESTRING split blades.</para>
+
             <note><para>To improve the robustness of ST_Split it may be convenient to <xref linkend="ST_Snap"/> the input to the blade in advance using a very low tolerance. Otherwise the internally used coordinate grid may cause tolerance problems, where coordinates of input and blade do not fall onto each other and the input is not being split correctly (see <ulink url="http://trac.osgeo.org/postgis/ticket/2192">#2192</ulink>).</para></note>
 
             <note><para>