gvSIG bugs #2539
Outputs of Reproject geoprocess in view CRS
| Status: | New | % Done: | 0% | |
|---|---|---|---|---|
| Priority: | High | Spent time: | - | |
| Assignee: | - | |||
| Category: | Geoprocess | |||
| Target version: | - | |||
| Severity: | Minor | Add-on version: | ||
| gvSIG version: | 2.1.0 | Add-on build: | ||
| gvSIG build: | 2227 | Add-on resolve version: | ||
| Operative System: | Add-on resolve build: | |||
| Keywords: | reproject, reprojection | Proyecto: | ||
| Has patch: | No | Hito: | ||
| Add-on name: | Unknown |
Description
After the execution of Reproject geoprocess, the output layers are added in the view considering the view CRS and not the layer one. So it would seem that the reprojection has not gone succesfully, instead the results are right but not added in the view in the right way. This bug was already in gvSIG 1.12.
How to reproduce this bug:
How to reproduce this bug:
- create and open a view in EPSG:23032;
- for instance, add reg2011_g.shp [1] in EPSG:23032 (in order to have a reference layer defined in the same CRS of the view);
- open the Geoprocess toolbox and execute the Reproject algorithm, choosing reg2011_g.shp as input layer, EPSG:23032 as source CRS and EPSG:23033 as target one (a simple conversion of coordinates).
Finally, the result layer is added in EPSG:23032 (view CRS) instead of EPSG:23033 (layer CRS), as it should be.
Related issues
History
#1
Updated by Álvaro Anguix almost 10 years ago
- Assignee set to Ignacio Brodín
#2
Updated by Álvaro Anguix over 8 years ago
- Assignee deleted (
Ignacio Brodín)
#3
Updated by Cesar Martinez Izquierdo over 7 years ago
- Related to gvSIG bugs #4183: PRJ file when using "Reproject" geoprocess is created with the origin CRS added