[GRASS-dev] importing & projecting

[Moritz Lennert]

On 22/09/15 23:46, Anna Petrášová wrote:
>
>
> On Tue, Sep 22, 2015 at 4:18 PM, Markus Neteler <neteler at osgeo.org
> <mailto:neteler at osgeo.org>> wrote:
>
>     On Tue, Sep 22, 2015 at 8:37 PM, Martin Landa
>     <landa.martin at gmail.com <mailto:landa.martin at gmail.com>> wrote:
>     > Hi,
>     >
>     > 2015-09-22 18:25 GMT+02:00 Moritz Lennert <mlennert at club.worldonline.be <mailto:mlennert at club.worldonline.be>>:
>     >> IMHO, the best solution, as Paulo already said, would be to have
>     >> r.in.gdal/v.in.ogr as the default import modules used by the import dialog.
>     >> A checkbox (unchecked by default) could propose to "Reproject maps to
>     >> current projection system before import" or something like that.
>
>     yes
>
>     >> For now, I propose to revert import_export.py to r65634 and to see if
>     >> everyone agrees with the above proposal of how to integrate the *.import
>     >> modules.
>     >
>     > instead of simply reverting I would be happier if anyone here would
>     > implement the suggestion above.
>
>     +1 .. I agree with Martin
>
>
> Disasters happened when people were trying to import data in different
> projection and because it "didn't work", they just checked override
> projection.

I agree that this is another path to disaster. ;-)

> So I am convinced it should stay there but just improved.
> What is currently missing is the choice of which reprojection method to
> use. So we could dynamically (based on if it's needed or not) add there
> a widget for selecting the reprojection method. And maybe also the
> output resolution which is by default estimated.

So this sounds somewhat like the "pop-up" solution Michael proposed.

What I really find important is that there is a big red sign flashing 
when reprojection happens. And I would like the user to have to at least 
click on "ok" to confirm that this is what she wants.

It's the fact that things are happening quietly without informing the 
user, and without giving a choice, that bothers me right now. And the 
fact that it happened without discussion. To repeat myself: I think that 
such fundamental changes as were introduced by replacing 
r.in.gdal/v.in.ogr by the *.import modules in the import wizard should 
be discussed (at least announced with sufficient time for others to 
react) before implementation.

And I readily admit that I don't have the wxGUI knowledge to code that 
myself, at least not in the limited time I have available for that right 
now. But I don't think that this takes away the right to question the 
current choice.

> I am not sure whether
> the import dialog should be still associated with r.in.gdal (when you
> open r.in.gdal from gui command line, it opens this custom dialog).

So, you propose to associate the gui dialog with the *.import modules 
and to put r.in.gdal and v.in.ogr back into "normal" module status with 
their module GUI launched when called ?

Sounds ok to me, although we should be aware that this will mean quite a 
lot of changes in existing documentation. But I think it is worth the 
effort.

Moritz