Opened 15 years ago
Last modified 13 years ago
#1473 reopened patch
3dz/3dm/4d support
| Reported by: | jef | Owned by: | jef |
|---|---|---|---|
| Priority: | minor: annoyance | Milestone: | Version 1.7.0 |
| Component: | Vectors | Version: | Trunk |
| Keywords: | Cc: | bitner@… | |
| Must Fix for Release: | No | Platform: | All |
| Platform Version: | Awaiting user input: | no |
Description
attached a patch that add 3dz/3dz/4d vector support to core and the postgres provider.
Attachments (3)
Change History (17)
comment:1 by , 15 years ago
| Summary: | 3dz/3dz/4d support → 3dz/3dm/4d support |
|---|
by , 15 years ago
comment:2 by , 15 years ago
follow-up: 5 comment:4 by , 15 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.
comment:5 by , 15 years ago
Replying to jef:
I uploaded it to http://buten.norbit.de/~jef/2d+.diff.
updated the patch to r10066
comment:6 by , 15 years ago
| Milestone: | → Version 1.0.1 |
|---|
by , 15 years ago
| Attachment: | 2d+.diff.gz added |
|---|
comment:8 by , 15 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
The patch should have been applied, so I'm closing this ticket. Reopen if necessary.
follow-up: 10 comment:9 by , 15 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
this patch has not been applied.
follow-up: 11 comment:10 by , 15 years ago
Replying to 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.
comment:11 by , 15 years ago
comment:12 by , 14 years ago
| Cc: | added |
|---|---|
| Milestone: | Version 1.0.3 |
I am happy to provide either testing or sample datasets for this feature if it gets pulled back up. This is very important for anyone who needs to carry through Z and M data even if they are not using it in all situations.
follow-up: 14 comment:13 by , 14 years ago
| Milestone: | → Version 1.6.0 |
|---|
bitner (or others), please provide sample data for testing and eventually apply the patch
comment:14 by , 13 years ago
Replying to 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)
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.
Martin