Feature request #1473
|Pull Request or Patch supplied:||No||Resolution:|
|Easy fix?:||No||Copied to github as #:||11533|
attached a patch that add 3dz/3dz/4d vector support to core and the postgres provider.
#1 Updated by Martin Dobias over 12 years ago
Hi Juergen, I've took a brief look on your patch - I see there's quite big amount of work in it! :)
From the technical side, may I suggest you to leave QgsPoint as class for 3D points (X,Y,Z) and derive QgsPointM class from it which would operate also with M coordinates? I have the impression that these 'measure' dimension is used so rarely that it would cause unnecessary memory overhead in usual case.
#3 Updated by Jürgen Fischer over 12 years ago
I was about to update the patch - but it has grown to large to attach.
I uploaded it to http://buten.norbit.de/~jef/2d+.diff.
The patch now contains rewritten WKB parsing and creation code and uses QVector instead of QList to keep points. It reduces the need for reallocations and copying of memory.
#9 Updated by Giovanni Manghi almost 12 years ago
Replying to [comment:10 jef]:
Replying to [comment:9 jef]:
this patch has not been applied.
I've no application for 2d+ data - and therefore this hasn't been tested enough to be applied.
thanks for the feedback. Is this on the developers agenda for the next future?
#12 Updated by bitner - over 10 years ago
Replying to [comment:13 pcav]:
bitner (or others), please provide sample data for testing and eventually apply the patch
Just now saw this.... Attaching a shapefile that has Z and M Coordinates. (shp2pgsql will bring it in with Z and M dimensions intact -- OGR will drop them)
#14 Updated by Alister Hood almost 10 years ago
- Pull Request or Patch supplied set to No
This seems like a feature that would be good to have in QGIS 2.0
A lot of the existing patch fails to apply to the current code. I presume someone would need to work through it all manually - you haven't got a local branch in sync with the current trunk or anything, have you Jürgen?