Bug report #8579
Raster to vector create new CRS
| Status: | Closed | ||
|---|---|---|---|
| Priority: | Normal | ||
| Assignee: | - | ||
| Category: | Rasters | ||
| Affected QGIS version: | master | Regression?: | No |
| Operating System: | Windows 8 | Easy fix?: | No |
| Pull Request or Patch supplied: | No | Resolution: | up-/downstream |
| Crashes QGIS or corrupts data: | No | Copied to github as #: | 17322 |
Description
Converting a rasterlayer with crs EPSG:25832 - ETRS89 / UTM zone 32N to a vectorlayer. The vectorlayer crs transform to EPSG:3044 - ETRS89 / ETRS-TM32
History
#1
Updated by Giovanni Manghi about 11 years ago
- Status changed from Open to Feedback
please attach sample data
#2
Updated by Lene Fischer about 11 years ago
- File Differ_over_5_vektor.zip added
Sample data Raster Diffe_Over5m.tif
Differ_Over5mVektor.zip
#3
Updated by Giovanni Manghi about 11 years ago
Lene Fischer wrote:
Sample data Raster Diffe_Over5m.tif
Differ_Over5mVektor.zip
in the zip there is only the vector.
#4
Updated by Lene Fischer about 11 years ago
The raster missed - comming right now
#5
Updated by Lene Fischer about 11 years ago
- File Raster_vector.zip added
The file was too large.
Now raster and vector in a zip.
Regards
Lene
#6
Updated by Giovanni Manghi about 11 years ago
- Status changed from Feedback to Closed
- Resolution set to up-/downstream
if you run the process from the command line
gdal_polygonize.py /home/giovanni/Desktop/Raster1 -f "ESRI Shapefile" /home/giovanni/Desktop/lixo/test.shp test DN
you will notice that it is gdal_polygonize.py that created the output with such CRS, QGIS in this case it is just an interface.
The ticket should be filed in the gdal/ogr bug tracker.
Cheers!
#7
Updated by Lene Fischer about 11 years ago
But I run it from the Rastermenu. And here it gives this result. Has you transfered the bug to gdal/ogr?
regards
Lene
#8
Updated by Giovanni Manghi about 11 years ago
Lene Fischer wrote:
But I run it from the Rastermenu. And here it gives this result.
all the tools formerly known as "gdal tools" are GUIs for the gdal utilities
Has you transfered the bug to gdal/ogr?
no