Martin,
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 ?
Moritz
Martin,
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 ?
Moritz
Hi,
2009/5/15 Moritz Lennert <mlennert@club.worldonline.be>:
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 is just very initial and
untested. Moreover vector features are read to line_pnts structure,
i.e. instance of GEOS geometry class is created based on the line_pnts
which quite slow for large vector data layers. Data should be read
directly.
Anyway if you think it should be backported to devbr6, I have no objections.
Martin
--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa
Hi,
2009/5/15 Moritz Lennert <mlennert@club.worldonline.be>:
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 operator is very slow (todo: speed up).
Martin
--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa
Martin Landa wrote:
Hi,
2009/5/15 Moritz Lennert <mlennert@club.worldonline.be>:
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 operator is very slow (todo: speed up).
For speed-up, implement the respective algorithms directly in the GRASS
vector libs? Lots of work... Candidate for next GSoC?
Markus M
Hi,
2009/5/19 Markus GRASS <markus.metz.giswork@googlemail.com>:
Martin Landa wrote:
Hi,
2009/5/15 Moritz Lennert <mlennert@club.worldonline.be>:
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 operator is very slow (todo: speed up).
For speed-up, implement the respective algorithms directly in the GRASS
vector libs? Lots of work... Candidate for next GSoC?
could be nice project...
For now - minor speed-up: read vector data directly (not via line_pnts).
Martin
--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa
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:
Hi,
2009/5/15 Moritz Lennert <mlennert@club.worldonline.be>:
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 operator is very slow (todo: speed up).
Martin
--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
-----
William Kyngesburye <kyngchaos*at*kyngchaos*dot*com>
http://www.kyngchaos.com/
All generalizations are dangerous, even this one.