Bug report #4176
Cannot edit 3D PostGIS table in QGIS
| Status: | Closed | ||
|---|---|---|---|
| Priority: | Normal | ||
| Assignee: | - | ||
| Category: | Data Provider/PostGIS | ||
| Affected QGIS version: | master | Regression?: | No |
| Operating System: | Easy fix?: | No | |
| Pull Request or Patch supplied: | No | Resolution: | fixed/implemented |
| Crashes QGIS or corrupts data: | No | Copied to github as #: | 14152 |
Description
Load a 3D shapefile into PostGIS using shp2pgsql. This will result in a table with a constraint on the number of geometry dimensions == 3. Now fire up QGIS, look at they layer (renders right!) start editing (starts!) add a new feature (add!), and then save your edits (uh oh!). The new geometry does not appear to be 3D, so it fails the table constraint and the edits cannot be saved.
History
#1
Updated by Paul Ramsey about 13 years ago
This is true for adding new features and also for moving existing vertices and moving existing features. Implies that the dimensions are being stripped at some point in the chain.
#2
Updated by Giovanni Manghi almost 13 years ago
- Target version set to Version 1.7.4
#3
Updated by Paolo Cavallini over 12 years ago
- Crashes QGIS or corrupts data set to No
- Target version changed from Version 1.7.4 to Version 1.8.0
- Affected QGIS version set to master
#4
Updated by Paolo Cavallini about 12 years ago
- Target version changed from Version 1.8.0 to Version 2.0.0
#5
Updated by Jürgen Fischer over 10 years ago
- Target version changed from Version 2.0.0 to Future Release - Lower Priority
#6
Updated by Jürgen Fischer over 9 years ago
- Category changed from Data Provider to Data Provider/PostGIS
#7
Updated by Hugo Mercier over 8 years ago
This should have been fixed in 2.14.
#8
Updated by Nyall Dawson over 8 years ago
- Resolution set to fixed/implemented
- Status changed from Open to Closed