I just tried compiling with GEOS support in dev6 branch. While
VECT_CFLAGS includes the GEOS cflags, lib/vector/vlib/makefile also
needs to link GEOSLIBS.
Also, the wx gui vdigit setup.py needs GEOSCFLAGS. (and may need to
link GEOSLIBS)
On May 19, 2009, at 8:13 AM, Martin Landa wrote:
Hamish wrote:
> Markus M:
>
>> For speed-up, implement the respective algorithms directly in the GRASS
>> vector libs? Lots of work...
>>
>
> at the cost of having to maintain the code forever more and not
> automatically get updates.
>
Hm, good point. But, independent of the new G
Markus M:
> For speed-up, implement the respective algorithms directly in the GRASS
> vector libs? Lots of work...
at the cost of having to maintain the code forever more and not
automatically get updates.
is the slowness in the lib I/O or in the geos implementation?
how mature is the code?
Hi,
2009/5/19 Markus GRASS :
> Martin Landa wrote:
>> Hi,
>>
>> 2009/5/15 Moritz Lennert :
>>
>>> I can't find your mail announcing the inclusion of advanced GEOS operators
>>> in v.select, but I have to say that I really think that this is an important
>>> improvement. Any reason that this should
Martin Landa wrote:
> Hi,
>
> 2009/5/15 Moritz Lennert :
>
>> I can't find your mail announcing the inclusion of advanced GEOS operators
>> in v.select, but I have to say that I really think that this is an important
>> improvement. Any reason that this shouldn't be backported to 6.5 ?
>>
>
Hi,
2009/5/15 Moritz Lennert :
> I can't find your mail announcing the inclusion of advanced GEOS operators
> in v.select, but I have to say that I really think that this is an important
> improvement. Any reason that this shouldn't be backported to 6.5 ?
backported in r37280. Anyway using GEOS o
Hi,
2009/5/15 Moritz Lennert :
> I can't find your mail announcing the inclusion of advanced GEOS operators
> in v.select, but I have to say that I really think that this is an important
> improvement. Any reason that this shouldn't be backported to 6.5 ?
no special reason here, the GEOS support
