gvSIG bugs #3925: Corrupted export - Application: gvSIG desktop - gvSIG

gvSIG bugs #3925

Corrupted export

Added by Andrea Antonello over 8 years ago. Updated about 8 years ago.

Status:

Closed

% Done:

Priority:

High

Spent time:

Assignee:

Category:

CRS

Target version:

2.3.0-2419 (rev. org.gvsig.desktop-2.0.125)

Severity:

Major

Add-on version:

gvSIG version:

2.2.0

Add-on build:

gvSIG build:

Add-on resolve version:

Operative System:

Add-on resolve build:

Keywords:

Proyecto:

Has patch:

Hito:

Add-on name:

Unknown

Description

I am not sure if this is already fixed for gvSIG 2.3, to be sure i report it, since it creates a lot of confusion.

How to reproduce it:

create a new view using some projection (ex. 32632)
load a layer A in that projection
then load a layer B in a different projection (ex. 4326) asking to reproject on the fly
data a properly displayed
select a portion of the features of the layer B and export them to a new shapefile

I would expect the layer to be exported in its original projection, but instead it is exported in the projection of the view, without writing the proper prj file.

I think there should be at least a warning about that. And sure thing the prj should be written (but I know this will be done in 2.3).

Related issues

Associated revisions

Revision 42676
Added by Daniel Martinez over 8 years ago

refs #3925 Added new panel to export wizard to select target projection

Revision 527
Added by Daniel Martinez over 8 years ago

refs #3925 KML mustn't show the new panel to show target projection

Revision 528
Added by Daniel Martinez about 8 years ago

refs #3925 Updated to last version from org.gvsig.desktop

History

#1 Updated by Álvaro Anguix over 8 years ago

Hi Andrea,
I agree about re-written the prj of the layer, but export the layer in the projection of the View is similar in another GIS (Arc***, etc.). I think that the "normal" user expects this performance.

#2 Updated by Andrea Antonello over 8 years ago

Hmmmm, ok, I am used to uDig, where in the export window there was the possibility to choose a projection to export to. the default proposed was the original projection of the dataset.

I do not like that data are changed without telling me. For me reprojecting on the fly means that it reprojects for rendering (because uDig was like that), not that it changes the data without writing them somewhere, but then exporting them in some different projection.

Consider also that the projection it exports to might not even have a precise transformation, which means that the exported sub-dataset would be persisted as wrong, while exporting in the original projection would keep the dataset unaltered.

These are just thoughts, I don't want to push here. But some users might be confused. And remember that there are not only Arc** users around :-)
What I would do is issue a small warning while exporting. In the above case I wanted to just export a subset in the same projection. This is not possible in gvSIG and I need to be advised.