Hi,
I just stumbled over this popularity ranking of GIS software:
http://gisgeography.com/mapping-out-gis-software-landscape
I took the liberty to comment on the article (scoll to the bottom). Maybe
someone has points to add...
There is also a "review" of Free and Open Source GIS Software:
http
Hi,
this is just to let you know that we are planning to meetup in Ispra (VA)
on the lake Maggiore, Italy. I have created a page [1] that I will keep
updated with dates / time / participants / activities done. If you live in
the surroundings and want to join, you are welcome! The meetups are open
Dear Stefan,
Thanks a lot for answering my query,
i.landsat8.swlst add-on now works fine for me.
Thanks for your input regarding use of GLC maps, i use these maps to test
the LST add-on.
Regards
John
On Fri, Sep 23, 2016 at 1:44 AM, Blumentrath, Stefan <
stefan.blumentr...@nina.no> wrote:
> H
On Thu, Sep 22, 2016 at 5:45 PM, Rich Shepard wrote:
> A possible bug in ../diglib/cindex.c.
>
> This host has 4G RAM and 16G swap memory. With X running top shows 740M
> RAM and 15.3G swap free. I'm trying to run a spatial analysis program which
> fails after 2.5-4.7 hours (depending on the c
On Tue, Sep 20, 2016 at 3:06 PM, Vincent Bain wrote:
> Hi,
> on a fresh (r69498) trunk version of grass, I have a problem running a
> v.edit command on a map.
> Given a vector map composed of 200 contour lines splitted in roughly
> 17000 line segments (adjacent nodes perfectly overlapping), I need
On Fri, 23 Sep 2016, Markus Metz wrote:
Apparently there are less than 52 MB of free memory left. The resulting
vector contours must be quite large. Try to export GRASS_VECTOR_LOWMEM=1
before running r.contour.
Markus,
I assumed that grass did not see the available memory, but did not reali
Thanks Markus,
indeed it works much much faster !
However on my data I notice the result is slightly different from the
one I get with 6.4, i.e. some segments don't snap to each other : where
I should have a result with 199 lines I have 217 objects. If I try to
snap them manually via wx digitizer
On Fri, 23 Sep 2016, Markus Metz wrote:
Apparently there are less than 52 MB of free memory left. The resulting
vector contours must be quite large. Try to export GRASS_VECTOR_LOWMEM=1
before running r.contour.
Maybe also use a larger step or less levels.
Markus,
Tried both. Still cannot co
On Fri, 23 Sep 2016, Markus Metz wrote:
Apparently there are less than 52 MB of free memory left. The resulting
vector contours must be quite large. Try to export GRASS_VECTOR_LOWMEM=1
before running r.contour.
Maybe also use a larger step or less levels.
Took a different approach by reduci
On Fri, Sep 23, 2016 at 5:44 PM, Vincent Bain wrote:
> Thanks Markus,
> indeed it works much much faster !
>
> However on my data I notice the result is slightly different from the
> one I get with 6.4, i.e. some segments don't snap to each other : where
> I should have a result with 199 lines I
Le vendredi 23 septembre 2016 à 22:17 +0200, Markus Metz a écrit :
> At least you got a working solution.
Yes, thanks !
working with the same dataset, I ran into several GUI crashes (no
time/no way to get an error message cause the window shuts up
immediately, perhaps there's a log file but I don
On Fri, Sep 23, 2016 at 10:27 PM, Vincent Bain wrote:
> Le vendredi 23 septembre 2016 à 22:17 +0200, Markus Metz a écrit :
>> At least you got a working solution.
>
> Yes, thanks !
>
> working with the same dataset, I ran into several GUI crashes (no
> time/no way to get an error message cause the
12 matches
Mail list logo
