gvSIG bugs #2241
Saving a raster doesn't save the CRS
| Status: | Won't fix | % Done: | 0% | |
|---|---|---|---|---|
| Priority: | Normal | Spent time: | - | |
| Assignee: |  Ignacio Brodín | |||
| Category: | Raster | |||
| Target version: | 2.1.0-2219-testing | |||
| Severity: | Add-on version: | |||
| gvSIG version: | 2.1.0 | Add-on build: | ||
| gvSIG build: | 2217 | Add-on resolve version: | ||
| Operative System: | Add-on resolve build: | |||
| Keywords: | crs, raster, save as | Proyecto: | ||
| Has patch: | No | Hito: | ||
| Add-on name: | Tools: Raster tools (org.gvsig.raster.tools.app.basic) |
Description
Same issue of gvSIG 1.x (#960). When the user saves a raster layer (from the contextual menu of the layer in the ToC or from the "Export to raster" menu), the view CRS should be applied on it at least. Instead, running gdalinfo or opening its properties, we can see that the coordinate system is null.
40.png (334 KB)
History
#1
Updated by Álvaro Anguix over 10 years ago
- Assignee set to Ignacio Brodín
#2
Updated by Álvaro Anguix over 10 years ago
- Target version changed from 2.1.0-2223-rc1 to 2.1.0-2219-testing
#3
Updated by Ignacio Brodín about 10 years ago
- File 40.png added
- Status changed from New to Won't fix
With the option "Save As" the new layer will have the same projection that the old one. This projection is saved in the header of the file if it is supported. As you can see in the attached capture, a gdalinfo command reports the CRS information of this new layer.
If you need create a new layer with the view projection, first you will have to assign the view projection to the source. In the menu "Geographic Tranformations" exists an option to do that (That option only writes the RMF file and not the header. I prefer don't write the existing data). That is because you are exporting the layer and not the view.
#4
Updated by Antonio Falciano about 10 years ago
Hi Nacho,
I cannot verify it at the moment, because build 2218 doesn't let me load GeoTIFFs (at least on win), even if I have updated all the recommended raster plugins. I don't know if this behavior is correlated to #2273 and #2274. Should I open a new ticket about this? Or is it just fixed for the next version?
#5
Updated by Álvaro Anguix about 10 years ago
It's just fixed for the next version
#6
Updated by Ignacio Brodín about 10 years ago
Hi Antonio,
I think that it will be better wait to the next build (2219). It is comming soon, probably the next week. My apologies for the problems loading raster in windows. There was a problem with the packages, although this should work with the new ones. I don't know why it does not work for your system. Anyway, you can test this ticket in the 2217 and check if you get the behavior that you are waiting for.