gvSIG bugs #4183
PRJ file when using "Reproject" geoprocess is created with the origin CRS
Status: | New | % Done: | 0% | |
---|---|---|---|---|
Priority: | Normal | Spent time: | - | |
Assignee: | - | |||
Category: | Geoprocess | |||
Target version: | - | |||
Severity: | Minor | Add-on version: | ||
gvSIG version: | 2.3.0 | Add-on build: | ||
gvSIG build: | 2425 | Add-on resolve version: | ||
Operative System: | Add-on resolve build: | |||
Keywords: | Proyecto: | |||
Has patch: | Hito: | |||
Add-on name: | Unknown |
Description
When we use "Reproject" geoprocess tool for a layer, the Origin CRS is the same than the View where the layer is, and we have to indicate the destination CRS for the layer.
The problem is that it creates the PRJ file with the CRS of the View (the origin CRS), so when the new layer is loaded in a View, it's not loaded correctly.
The PRJ should be created with the new CRS, the destination CRS.
Related issues
History
#1 Updated by Álvaro Anguix almost 8 years ago
- Status changed from New to Invalid
Duplicated: https://redmine.gvsig.net/redmine/issues/2539
#2 Updated by Cesar Martinez Izquierdo over 7 years ago
- Status changed from Invalid to New
Reopening as it is not exactly the same problem as in #2539 (that one is related with the CRS used to load the layers after created, while this one is related with the .prj file created on the process).
#3 Updated by Cesar Martinez Izquierdo over 7 years ago
- Related to gvSIG bugs #4324: Reproject tool generates wrong .prj file added
#4 Updated by Cesar Martinez Izquierdo over 7 years ago
- Related to gvSIG bugs #2539: Outputs of Reproject geoprocess in view CRS added
#5 Updated by Álvaro Anguix about 4 years ago
- Target version set to 2.5.1-3044
#6 Updated by Álvaro Anguix about 4 years ago
- Target version deleted (
2.5.1-3044)