[GRASS-dev] importing & projecting

[Anna Petrášová]

On Tue, Sep 22, 2015 at 4:18 PM, Markus Neteler <neteler at osgeo.org> wrote:

> On Tue, Sep 22, 2015 at 8:37 PM, Martin Landa <landa.martin at gmail.com>
> wrote:
> > Hi,
> >
> > 2015-09-22 18:25 GMT+02:00 Moritz Lennert <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. 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. 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). Does something like that sounds
better?

Anna

>
> Markus
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20150922/fa090610/attachment.html>