Bug report #14142
M ordinate is lost on shapefile update
| Status: | Closed | ||
|---|---|---|---|
| Priority: | Normal | ||
| Assignee: | - | ||
| Category: | Data Provider/OGR | ||
| Affected QGIS version: | master | Regression?: | No |
| Operating System: | Easy fix?: | No | |
| Pull Request or Patch supplied: | No | Resolution: | up/downstream |
| Crashes QGIS or corrupts data: | No | Copied to github as #: | 22144 |
Description
Opening an XYM or XYMZ shapefile and editing its attributes results in loosing the M ordinate value from the original shapefile.
This is an unwarned lossy operation, pretty bad for an unaware user.
This ticket is a spin-off of #11422
Either M support should be added to OGR or QGIS should print a big warning and ask if the user wants to continue with the destructive operation.
History
#1
Updated by Matthias Kuhn almost 9 years ago
Is there already a ticket against GDAL?
#2
Updated by Sandro Santilli almost 9 years ago
I Just filed one: https://trac.osgeo.org/gdal/ticket/6331
#3
Updated by Even Rouault about 8 years ago
- Resolution set to up/downstream
- Status changed from Open to Closed
Has been fixed with GDAL 2.1