[postgis-tickets] [PostGIS] #2755: 4 regression failures for sfcgal

PostGIS trac at osgeo.org
Wed Jun 4 22:01:39 PDT 2014


#2755: 4 regression failures for sfcgal
---------------------+------------------------------------------------------
 Reporter:  robe     |       Owner:  colivier     
     Type:  defect   |      Status:  new          
 Priority:  blocker  |   Milestone:  PostGIS 2.2.0
Component:  sfcgal   |     Version:  trunk        
 Keywords:           |  
---------------------+------------------------------------------------------

Comment(by robe):

 At a quick glance (regress_sfcgal): I honestly can't see a difference so
 maybe its white space.


 {{{
 --- regress_sfcgal_expected     2014-06-02 18:12:37 -0400
 +++ /projects/postgis/tmp/2.2_pg9.4w32/test_95_out      2014-06-05
 00:39:04 -0400
 @@ -3,7 +3,7 @@
  ST_3DArea|1
  ST_Extrude_point|LINESTRING Z (0 0 0,1 0 0)
  ST_Extrude_line|POLYHEDRALSURFACE Z (((0 0 0,1 0 0,1 1 0,0 1 0,0 0 0)))
 -ST_Extrude_surface|POLYHEDRALSURFACE Z (((1 1 0,1 0 0,0 1 0,1 1 0)),((0 1
 1,1 0 1,1 1 1,0 1 1)),((1 0 0,0 0 0,0 1 0,1 0 0)),((0 1 1,0 0 1,1 0 1,0 1
 1)),((1 0 0,1 1 0,1 1 1,1 0 1,1 0 0)),((1 1 0,0 1 0,0 1 1,1 1 1,1 1
 0)),((0 1 0,0 0 0,0 0 1,0 1 1,0 1 0)),((0 0 0,1 0 0,1 0 1,0 0 1,0 0 0)))
 +ST_Extrude_surface|POLYHEDRALSURFACE Z (((0 1 0,1 1 0,1 0 0,0 1 0)),((0 1
 1,1 0 1,1 1 1,0 1 1)),((0 1 0,1 0 0,0 0 0,0 1 0)),((0 1 1,0 0 1,1 0 1,0 1
 1)),((1 0 0,1 1 0,1 1 1,1 0 1,1 0 0)),((1 1 0,0 1 0,0 1 1,1 1 1,1 1
 0)),((0 1 0,0 0 0,0 0 1,0 1 1,0 1 0)),((0 0 0,1 0 0,1 0 1,0 0 1,0 0 0)))
  ST_ForceLHR|POLYGON((0 0,1 0,1 1,0 1,0 0))
  ST_Orientation_1|-1
  ST_Orientation_2|1
 }}}

 other something weird with I guess how empty is compared.  Might only be a
 windows issue:


 {{{
 --- sfcgal/empty_expected       2014-06-02 18:12:34 -0400
 +++ /projects/postgis/tmp/2.2_pg9.4w32/test_96_out      2014-06-05
 00:39:04 -0400
 @@ -26,11 +26,11 @@
  ST_Buffer(empty, tolerance) == empty|010300000000000000
  ST_Union(geometry, empty) ==
 geometry|0103000000010000000400000000000000000000000000000000000000000000000000244000000000000000000000000000001440000000000000144000000000000000000000000000000000
  ST_Union(empty, empty) == empty|010300000000000000
 -ST_Intersection(geometry, empty) == geometry|010700000000000000
 -ST_Intersection(empty, empty) == empty|010700000000000000
 +ST_Intersection(geometry, empty) == geometry|010300000000000000
 +ST_Intersection(empty, empty) == empty|010300000000000000
  ST_Difference(geometry, empty) ==
 geometry|0103000000010000000400000000000000000000000000000000000000000000000000244000000000000000000000000000001440000000000000144000000000000000000000000000000000
  ST_Difference(empty, geometry) == empty|010300000000000000
 -ST_Distance(geometry, empty) == NULL|inf
 +ST_Distance(geometry, empty) == NULL|
  ST_DWithin(geometry, empty, tolerance) == FALSE|f
  ST_Within(geometry, empty) == FALSE|f
  ST_Contains(empty, geometry) == FALSE|f
 }}}

 -- regress_ogc_expected - whacked -- there is such a thing as a -0 ? I
 think my result should be right :)


 {{{
 --- sfcgal/regress_ogc_expected 2014-06-02 18:12:34 -0400
 +++ /projects/postgis/tmp/2.2_pg9.4w32/test_101_out     2014-06-05
 00:39:05 -0400
 @@ -62,7 +62,7 @@
  NOTICE:  Self-intersection
  isvalid|f
  isvalid|t
 -intersection|POINT(-0 -0)
 +intersection|POINT(0 0)
  difference|MULTILINESTRING((0 10,0 2),(0 -2,0 -10))
  boundary|MULTILINESTRING((0 0,0 10,10 10,10 0,0 0),(2 2,2 4,4 4,4 2,2 2))
  symdifference|GEOMETRYCOLLECTION(LINESTRING(2 2,4 4),LINESTRING(10 10,20
 20),POLYGON((0 0,0 10,10 10,10 0,0 0),(4 4,2 4,2 2,4 2,4 4)))

 }}}

 sfcgal_tickets -- don't even know what to make of this:


 {{{
 --- sfcgal/tickets_expected     2014-06-02 18:12:34 -0400
 +++ /projects/postgis/tmp/2.2_pg9.4w32/test_103_out     2014-06-05
 00:39:06 -0400
 @@ -15,7 +15,7 @@
  #73|GEOMETRYCOLLECTION(CIRCULARSTRING(1 1,2 3,4 5,6 7,5 6))
  #80|MULTILINESTRING((0 0,1 1))
  #83|MULTICURVE(CIRCULARSTRING(220268 150415,220227 150505,220227 150406))
 -ERROR:  LWGEOM2SFCGAL: Unknown geometry type !
 +#85|0
  #112|GEOMETRYCOLLECTION(POINT(-10 50))
  NOTICE:  ST_Locate_Between_Measures and ST_Locate_Along_Measure are
 deprecated. Use ST_LocateAlong and ST_LocateBetween.
  ERROR:  Geometry argument does not have an 'M' ordinate
 @@ -40,7 +40,7 @@
  #179a|
  NOTICE:  No points or linestrings in input array
  #179b|
 -#183|CIRCULARSTRING(0 0,0.5 1.2071067812,0 1)
 +#183|COMPOUNDCURVE(CIRCULARSTRING(0 0,0.5 1.2071067812,1 0),(1 0,0 1))
  #210a|
  NOTICE:  No points or linestrings in input array
  #210b|
 @@ -95,7 +95,7 @@
  #835.11|MULTILINESTRING EMPTY
  #835.12|MULTIPOLYGON EMPTY
  #650|MULTIPOINT(0 0,1 1,2 2)
 -#667|SRID=4326;CURVEPOLYGON(CIRCULARSTRING(30 40,-49.2314112161292
 32.1963871193548,30 40))
 +#667|SRID=4326;CURVEPOLYGON(CIRCULARSTRING(30 40,-50 39.9999999999999,30
 40))
  #677|1121395
  #680|01d107000000000000000024c000000000000049400000000000000040
  #681a|
 @@ -129,7 +129,7 @@
  #723|0101000020E61000006284F068E33826C00100000000804B40
  #804|<gml:Point srsName="urn:ogc:def:crs:EPSG::4326"><gml:pos
 srsDimension="2">0 0</gml:pos></gml:Point>
  #845|t
 -#834|GEOMETRYCOLLECTION(POINT(0 0),LINESTRING(10 0,10 10))
 +#834|GEOMETRYCOLLECTION(POINT(0 0 5),LINESTRING(10 10 5,10 0 5))
  #884|1|f
  #884|2|t
  #938|
 @@ -225,8 +225,8 @@
  #1791|4.7
  ERROR:  ST_Segmentize: invalid max_distance 0 (must be >= 0)
  ERROR:  invalid GML representation
 -#1957|inf
 -#1978|3.1413
 +#1957|1
 +#1978|3.1416
  #1996|{"type":"Point","coordinates":[]}
  #2001|POLYGON((0 0,0 1,1 1,0 0))
  #2028|TIN(((0 0,0 1,1 1,0 0)))
 }}}

 Anyway if someone else can conrim that these are true errors or bugs in
 our regress tests itself, that would be appreciated.

 I compiled with


 {{{
 select postgis_full_version() || ' ' || version();

 POSTGIS="2.2.0dev r12605" GEOS="3.5.0dev-CAPI-1.9.0 r3985" SFCGAL="1.0.4"
 PROJ="Rel. 4.8.0, 6 March 2012" GDAL="GDAL 1.11.0, released 2014/04/16
 GDAL_DATA not found" LIBXML="2.7.8" LIBJSON="UNKNOWN" RASTER

 }}}

 I built SFCGAL using CGAL 4.2, Boost 1.53.0, mpfr 3.1.2, gmp 5.1.2

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/2755#comment:1>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.


More information about the postgis-tickets mailing list