Please sign in to comment.
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix errors and inconsistencies resulting from adding M values to
a dataset with a ****25D wkb type Previously we did not handle adding M values to any "25d" WKB type (as there's no such thing as Point25DM, etc). But being strict like this turns out to be wrong, because it results in corrupted/ inconsistent geometries as a result of calls to QgsAbstractGeometry.addMValue() whenever the original geometry is a 25D type. In this situation, the M values were being added but the WKB type wasn't being updated to reflect this and would remain at the original *25D type. Ultimately, this causes GDAL to reject any wkb generated for the geometries and failures to write features into an output dataset. This is especially the case with GDB files, where the dataset can sometimes be reported as a ZM type while individual features are only 25D types (for whatever archiac reasons!) (cherry picked from commit 6c30a46)
- Loading branch information
Showing with 19 additions and 14 deletions.