Opened 12 years ago
Closed 12 years ago
#1822 closed defect (fixed)
wxGUI location wizard imports 3D Shapefile as 2D
Reported by: | marisn | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | 7.0.0 |
Component: | Startup | Version: | svn-trunk |
Keywords: | v.in.ogr | Cc: | |
CPU: | Unspecified | Platform: | Unspecified |
Description
When creating a new location based on a Shapefile, location wizard imports it into the new location, still it's done in 2D mode thus losing all Z coordinates of dataset.
This is worse than not importing at all as when user is forced to use import module (v.in.ogr), it might notice -z option and enable it. Current behaviour might lead to data loss (delete shapefile without checking metadata in GRASS) or wrong conclusions that GRASS doesn't support 3D shapefiles (WRONG!).
Change History (3)
follow-up: 2 comment:1 by , 12 years ago
Keywords: | v.in.ogr added |
---|
comment:2 by , 12 years ago
Replying to martinl:
Probably
v.in.ogr
in GRASS 7 could import 3D data automatically when OGR layer is detected as 3D (2.5D) without specifying any extra flag (in other words, no need for-z
flag).
Done in r54189. By default, a 3D vector is created if any input geometry is 3D, otherwise the output is 2D. 2D output can be forced with the new -2 flag (I have seen shapefiles that are 3D even if all z coordinates are zero, thus fake 3D). The -z flag has been removed.
Markus M
comment:3 by , 12 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Probably
v.in.ogr
in GRASS 7 could import 3D data automatically when OGR layer is detected as 3D (2.5D) without specifying any extra flag (in other words, no need for-z
flag).