Bug report #9651
PostGIS polyhedral and TIN layers not handled anymore
| Status: | Closed | ||
|---|---|---|---|
| Priority: | Normal | ||
| Assignee: | |||
| Category: | Data Provider/PostGIS | ||
| Affected QGIS version: | 2.2.0 | Regression?: | No | 
| Operating System: | Easy fix?: | No | |
| Pull Request or Patch supplied: | No | Resolution: | |
| Crashes QGIS or corrupts data: | No | Copied to github as #: | 18219 | 
Description
  PostGIS tables with geometries of type PolyhedralSurface or TIN cannot be loaded anymore :
	
- no correct type is detected when using "add a postgres layer" (should be MultiPolygon)
 - whatever type is manually selected, it segfaults in QgsGeometry when parsing the wkb
 
Related issues
Associated revisions
postgres provider: consider TIN and POLYHEDRALSURFACE as MULTIPOLYGONM (instead of POLYGONM) (fixes #9651)
postgres provider: restore behaviour to keep 3d wkb (refs #9651,
followup bd311c8)
postgres provider: restore behaviour to keep 3d wkb (refs #9651,
followup bd311c8)
History
#1
    
    Updated by Jürgen Fischer over 11 years ago
    Please attach some data.
#2
    
    Updated by Jürgen Fischer over 11 years ago
    - Status changed from Open to Feedback
 
#3
    
    Updated by Hugo Mercier over 11 years ago
    Data sample, one table with a polyhedral and the other with a TIN :
create table test_polyhedral ( id serial );
select addgeometrycolumn('test_polyhedral', 'geom', 4326, 'POLYHEDRALSURFACE', 3);
insert into test_polyhedral (id,geom) values (1, 'SRID=4326;POLYHEDRALSURFACE Z(((0 0 0,0 1 0,1 1 0,1 0 0,0 0 0)))'::geometry);
create table test_tin ( id serial );
select addgeometrycolumn('test_tin', 'geom', 4326, 'TIN', 3);
insert into test_tin (id,geom) values (1, 'SRID=4326;TIN(((0 0 0,0 1 0,1 1 0,0 0 0)))'::geometry);
#4
    
    Updated by Jürgen Fischer over 11 years ago
    - Status changed from Feedback to Closed
 
Fixed in changeset cb919e972e11573fe2a0e58f4d946c6a30c9f792.
#5
    
    Updated by Sandro Santilli over 11 years ago
    Is commit:c3a28177 the backport to 2.2 branch ?
#6
    
    Updated by Jürgen Fischer over 11 years ago
    Sandro Santilli wrote:
Is commit:c3a28177 the backport to 2.2 branch ?
$ git branch --contains c3a28177 release-2_2