Update: Stefan's suggestion is worth. First test show that we can save a
lot of time.
Thank you so much Stefan and community.
Nikos
* Nikos Alexandris [2018-05-10 14:58:59 +0200]:
That's an interesting idea. Monday, when the JRC is open again, will be
the day to test that.
Thank you Stefan
GRASS-user] To import from or to link to data stored in a PostgreSQL
data base?
Dears,
the following concerns an update of an existing workflow, part of which
is GRASS GIS, that makes use of a large PostgreSQL data base which does
not reside locally.
The original data set consists of tens of thou
On Tue, May 8, 2018 at 4:01 PM, Nikos Alexandris
wrote:
>
> Dears,
>
> the following concerns an update of an existing workflow, part of which
> is GRASS GIS, that makes use of a large PostgreSQL data base which does
> not reside locally.
>
>
> The original data set consists of tens of thousands o
-user] To import from or to link to data stored in a PostgreSQL
data base?
Dears,
the following concerns an update of an existing workflow, part of which
is GRASS GIS, that makes use of a large PostgreSQL data base which does
not reside locally.
The original data set consists of tens of thousands
Dears,
the following concerns an update of an existing workflow, part of which
is GRASS GIS, that makes use of a large PostgreSQL data base which does
not reside locally.
The original data set consists of tens of thousands of (overlapping)
polygons. The data are required solely to build raster
