[postgis-tickets] r15055 - Flag ST_Segmentize(geography..) as changed, minor change in News
Regina Obe
lr at pcorp.us
Sun Sep 4 00:29:00 PDT 2016
Author: robe
Date: 2016-09-04 00:29:00 -0700 (Sun, 04 Sep 2016)
New Revision: 15055
Modified:
trunk/NEWS
trunk/doc/reference_editor.xml
Log:
Flag ST_Segmentize(geography..) as changed, minor change in News
Modified: trunk/NEWS
===================================================================
--- trunk/NEWS 2016-09-04 07:11:35 UTC (rev 15054)
+++ trunk/NEWS 2016-09-04 07:29:00 UTC (rev 15055)
@@ -46,6 +46,7 @@
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 *
Modified: trunk/doc/reference_editor.xml
===================================================================
--- trunk/doc/reference_editor.xml 2016-09-04 07:11:35 UTC (rev 15054)
+++ trunk/doc/reference_editor.xml 2016-09-04 07:29:00 UTC (rev 15055)
@@ -1416,6 +1416,7 @@
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>
More information about the postgis-tickets
mailing list