Ken Mankoff wrote
> On Sun, Oct 8, 2017 at 2:58 PM, Markus Neteler
> neteler@
> wrote:
>
>> Please let us know where to improve the documentation for this.
>>
>
> I'm embarrassed to say this is operator error, not software error. I don't
> use the GUI so I didn't think to look there. I think
On Sun, Oct 8, 2017 at 2:58 PM, Markus Neteler wrote:
> Please let us know where to improve the documentation for this.
>
I'm embarrassed to say this is operator error, not software error. I don't
use the GUI so I didn't think to look there. I think the g.proj page is
fine. I
Dear Ken,
On Oct 8, 2017 12:38 PM, "Ken Mankoff" wrote:
>
> Dear Moritz and Helmut,
>
> Thank you for letting me know that the GRASS GUI (and g.proj) have the
ability to work directly with proj4 strings.
>
>
Please let us know where to improve the documentation for this.
Dear Moritz and Helmut,
Thank you for letting me know that the GRASS GUI (and g.proj) have the
ability to work directly with proj4 strings.
-k.
On Fri, Oct 6, 2017 at 10:34 AM, Helmut Kudrnovsky wrote:
> Ken Mankoff wrote
> > Dear List,
> >
> > Most of the time when I work
Ken Mankoff wrote
> Dear List,
>
> Most of the time when I work with data in GRASS it is a provided on a
> standard GIS grid (EPSG code) and I can work with it easily. I create a
> location using the "-c" option when I start GRASS, or I import it into an
> existing mapset with r.import.
>
> I'm
Le 6 octobre 2017 09:44:41 GMT+02:00, Ken Mankoff a écrit :
>Dear List,
>
>Most of the time when I work with data in GRASS it is a provided on a
>standard GIS grid (EPSG code) and I can work with it easily. I create a
>location using the "-c" option when I start GRASS, or I
Dear List,
Most of the time when I work with data in GRASS it is a provided on a
standard GIS grid (EPSG code) and I can work with it easily. I create a
location using the "-c" option when I start GRASS, or I import it into an
existing mapset with r.import.
I'm now working with data and all I