]> granicus.if.org Git - postgis/commitdiff
Flag ST_Segmentize(geography..) as changed, minor change in News
authorRegina Obe <lr@pcorp.us>
Sun, 4 Sep 2016 07:29:00 +0000 (07:29 +0000)
committerRegina Obe <lr@pcorp.us>
Sun, 4 Sep 2016 07:29:00 +0000 (07:29 +0000)
git-svn-id: http://svn.osgeo.org/postgis/trunk@15055 b70326c6-7e19-0410-871a-916f4a2858ee

NEWS
doc/reference_editor.xml

diff --git a/NEWS b/NEWS
index 8ed50dcd960af9ecaafd04b60603b659392d4f84..6a2b03c678474bac694f9d6da6344c005d0e2a46 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -46,6 +46,7 @@ PostGIS 2.3.0
                Should resolve once and for all for extensions #3494, #3486, #3076 
                
   - #3547, Update tiger geocoder to support TIGER 2016
+   and to support both http and ftp.
 
  * Performance Enhancements *
 
index d99267e1b3270a78621e02a8fb5c4ce1bc456aa1..741d252662c2c5a7d4135c24c4f654c4ff48f9e8 100644 (file)
@@ -1416,6 +1416,7 @@ SELECT ST_AsEWKT(ST_Scale(ST_GeomFromEWKT('LINESTRING(1 2 3, 1 1 1)'), 0.5, 0.75
                        given <varname>max_segment_length</varname>.  Distance computation is performed in 2d
                        only. For geometry, length units are in units of spatial reference.  For geography, units are in meters.</para>
                        <para>Availability: 1.2.2</para>
+                       <para>Enhanced: 2.3.0 Segmentize geography now uses equal length segments</para>
                        <para>Enhanced: 2.1.0 support for geography was introduced.</para>
                        <para>Changed: 2.1.0 As a result of the introduction of geography support: The construct <code>SELECT ST_Segmentize('LINESTRING(1 2, 3 4)',0.5);</code> will result in ambiguous function error.  You need to have properly typed object e.g. a geometry/geography column, use ST_GeomFromText, ST_GeogFromText or
                                <code>SELECT ST_Segmentize('LINESTRING(1 2, 3 4)'::geometry,0.5);</code></para>