[GRASS-dev] Re: g.proj and datum information (and gis.m)

Moritz Lennert mlennert at club.worldonline.be
Tue Oct 24 03:49:49 EDT 2006

On Sat, October 21, 2006 03:03, Paul Kelly wrote:
> Hi Moritz
> Quite a few issues here but I'll try and address them
> On Sat, 21 Oct 2006, Moritz Lennert wrote:

>> - gis.m reproduces the above message and datum choice prompt in the
>> output
>> window, but the user can't do anything about it.
> I haven't used gis.m, but why can the output window not accept user input?
> I think it would be cool if GRASS could work a bit like AutoCAD and Matlab
> which, while mostly GUI-oriented, still have a command line available.
> the way Radim integrated GRASS with QGIS on Windows with the GRASS shell
> inside QGIS worked something like this?
>> - v.in.ogr with location= does not ask for datum information. In my eyes
>> 'g.proj -c' and 'v.in.ogr location=' should be consistent in their
>> behaviour.
>> Or is there a reason for the contrary ?
> Yes they should. Are you using them with the same input data? They both
> call
> GPJ_osr_to_grass() in interactive mode so if there is a datum name but not
> parameters they should prompt the user. You can avoid this by either
> passing no datum information at all (not even a name) or fully-specified
> (i.e. including transformation parameters).

Don't know how I came to the contrary conclusion, but v.in.ogr actually
behaves exactly like g.proj. Sorry for that.

> I guess that doesn't help much but hope it explains why things are the way
> they are

I does and I think it is logical. We "just" have to find a way to solve
the issue with gis.m.


More information about the grass-dev mailing list