GRASS GSoC idea: the line intersection problem

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

GRASS GSoC idea: the line intersection problem

Markus Metz-3
I would like to propose a project for the next Google Summer of Code:

The current implementation of Vect_break_lines() is causing a lot of
headache for larger vector maps with high spatial detail.
Vect_break_lines() is already much faster in G7 than in G6, but still
sometimes so slow that the procedure appears to make no progress at
all. There are a number of published alternatives on to how find
intersections between two lines, most of them based on the
Bentley–Ottmann algorithm. The best one or two, according to
literature review, should be implemented in the GSoC project. Benefit
to users: faster import of non-topological vectors, faster cleaning of
vectors with topological errors. Some more detail is on the wiki page
for GSoC 2013 [0].

Markus M

[0] http://grasswiki.osgeo.org/wiki/GRASS_SoC_Ideas_2013#Vector
_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev
Reply | Threaded
Open this post in threaded view
|

Re: GRASS GSoC idea: the line intersection problem

ychemin

+1

On Mar 4, 2013 11:54 PM, "Markus Metz" <[hidden email]> wrote:
I would like to propose a project for the next Google Summer of Code:

The current implementation of Vect_break_lines() is causing a lot of
headache for larger vector maps with high spatial detail.
Vect_break_lines() is already much faster in G7 than in G6, but still
sometimes so slow that the procedure appears to make no progress at
all. There are a number of published alternatives on to how find
intersections between two lines, most of them based on the
Bentley–Ottmann algorithm. The best one or two, according to
literature review, should be implemented in the GSoC project. Benefit
to users: faster import of non-topological vectors, faster cleaning of
vectors with topological errors. Some more detail is on the wiki page
for GSoC 2013 [0].

Markus M

[0] http://grasswiki.osgeo.org/wiki/GRASS_SoC_Ideas_2013#Vector
_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev
Reply | Threaded
Open this post in threaded view
|

Re: GRASS GSoC idea: the line intersection problem

Newcomb, Doug
In reply to this post by Markus Metz-3
+1

On Mon, Mar 4, 2013 at 2:54 PM, Markus Metz <[hidden email]> wrote:
I would like to propose a project for the next Google Summer of Code:

The current implementation of Vect_break_lines() is causing a lot of
headache for larger vector maps with high spatial detail.
Vect_break_lines() is already much faster in G7 than in G6, but still
sometimes so slow that the procedure appears to make no progress at
all. There are a number of published alternatives on to how find
intersections between two lines, most of them based on the
Bentley–Ottmann algorithm. The best one or two, according to
literature review, should be implemented in the GSoC project. Benefit
to users: faster import of non-topological vectors, faster cleaning of
vectors with topological errors. Some more detail is on the wiki page
for GSoC 2013 [0].

Markus M

[0] http://grasswiki.osgeo.org/wiki/GRASS_SoC_Ideas_2013#Vector
_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev



--
Doug Newcomb
USFWS
Raleigh, NC
919-856-4520 ext. 14 [hidden email]
---------------------------------------------------------------------------------------------------------
The opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of the Interior.   Life is too short for undocumented, proprietary data formats.

_______________________________________________
grass-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-dev