Re: [postgis-users] ST_Polygonize give different results on same set of linestrings

2017-09-08 Thread Sandro Santilli
On Thu, Sep 07, 2017 at 01:46:18PM +, Pierre Racine wrote: > Hi, > > Is it normal that ST_Polygonize() gives two different results depending on if > the linestrings are ST_Union() before calling it or not? ST_Polygonize only works when the input is noded (no line interior intersects any

Re: [postgis-users] ST_Polygonize give different results on same set of linestrings

2017-09-07 Thread Pierre Racine
Users Discussion <postgis-users@lists.osgeo.org> Objet : [postgis-users] ST_Polygonize give different results on same set of linestrings Hi, Is it normal that ST_Polygonize() gives two different results depending on if the linestrings are ST_Union() before calling it or not? In the fol

[postgis-users] ST_Polygonize give different results on same set of linestrings

2017-09-07 Thread Pierre Racine
Hi, Is it normal that ST_Polygonize() gives two different results depending on if the linestrings are ST_Union() before calling it or not? In the following example, test 1 (no union) and 3 (ST_Collect) give the same result, constructing two overlapping polygons. Test 2 (ST_Union) on the other