Moritz Lennert:
> I don't have the feeling that either 4326 or 31370
> offer multiple possibilities for transform parameters,
> but don't know for 100% sure.
no, they don't. LL WGS84 is just that (as long as we consider it the root
coordinate system), and 31370 explicitly gives 7 term +towgs84= p
Jonathan Aguero-Valverde wrote:
> DBMI-Postgres driver error:
> Cannot connect to Postgres: could not connect to server:
> Connection refused
> (0x274D/10061)
> Is the server running on host "localhost"
> and accepting
> TCP/IP connections on port 6543?
>
> GRASS_INFO_WARNING(
On Sun, May 25, 2008 at 4:14 AM, Pedro Camilo Alcantara
<[EMAIL PROTECTED]> wrote:
>
> Hello list
> I am using grass to automate the calculation of a series of vegetation
> indices and I want to use a decision tree algorithm (c4.5). That algorithm
> requires me to have a layer stack with those imag
Hi,
2008/5/25 Moritz Lennert <[EMAIL PROTECTED]>:
> In v.digit (not the wx version - don't have access to that currently),
> snapping works great for continuing lines, etc. However, whenever I draw a
> boundary which I would like to be closed so that it can become an area,
> snapping is inactive,
Hi,
Before I file this as a wish, I just want to make sure that I'm not doing
something wrong:
In v.digit (not the wx version - don't have access to that currently),
snapping works great for continuing lines, etc. However, whenever I draw a
boundary which I would like to be closed so that it can
On Sun, May 25, 2008 15:16, Hamish wrote:
> Moritz Lennert
>> Thanks to everyone for their answers. I've tried all the
>> different suggestions and the answer seems to be clear:
>> on-the-fly projection does not work properly in QGIS and gvSIG...
>> Whatever I do in GRASS, I always get correct plac
Moritz Lennert
> Thanks to everyone for their answers. I've tried all the
> different suggestions and the answer seems to be clear:
> on-the-fly projection does not work properly in QGIS and gvSIG...
> Whatever I do in GRASS, I always get correct placement of the GPS data.
This seems to be QGIS b
On Sun, May 25, 2008 12:47, Nikos Alexandris wrote:
> On Sun, 2008-05-25 at 12:43 +0200, Moritz Lennert wrote:
>> Thanks to everyone for their answers. I've tried all the different
>> suggestions and the answer seems to be clear: on-the-fly projection does
>> not work properly in QGIS and gvSIG...
On Sun, 2008-05-25 at 12:43 +0200, Moritz Lennert wrote:
> Thanks to everyone for their answers. I've tried all the different
> suggestions and the answer seems to be clear: on-the-fly projection does
> not work properly in QGIS and gvSIG... Whatever I do in GRASS, I always
> get correct placement
Thanks to everyone for their answers. I've tried all the different
suggestions and the answer seems to be clear: on-the-fly projection does
not work properly in QGIS and gvSIG... Whatever I do in GRASS, I always
get correct placement of the GPS data.
Using on-the-fly projection in the other progra
On Fri, May 23, 2008 22:28, J. Brian Adams wrote:
> As a followup, when I created the second layer I used
>
> v.db.connect map=baseMap driver=sqlite table=CountyData key=FIPS
> layer=2
>
This does not create a second layer, it connects a table to the second
layer. To create a second layer you ne
11 matches
Mail list logo
