Subject: Buffer op - end cap styles - msg#00041
List: gis.geos.devel
Hi Y'all,
I am now using the GEOS buffer op and am VERY excited about it. My own
implementation of straight skeleton isn't robust, but the GOES buffer op
worked the first time. :-)
A few questions:
I tried changing the cap style to round but I see no change. Is there
something basic I'm missing?
geos::operation::buffer::BufferOp bufOp(poly);
bufOp.setQuadrantSegments(4);
bufOp.setEndCapStyle(geos::operation::buffer::BufferOp::CAP_SQUARE);
geos::geom::Geometry * buf = bufOp.getResultGeometry(
-30.0 * MTR_TO_NM * NM_TO_DEG_LAT);
(The code is written using a buffer op object because I was trying to
eliminate wrapper layers as possible causes of the wrong end-cap style.)
Also, how can I compile a debug build of GEOS? Are there flags in the
configure file for this? I'd like to be able to break within the lib in
gdb. (I am compiling on Mac OS X using the std unix configure file.)
Finally, would it be algorithmically possible to modify the buffer
operation to buffer different line segments by different amounts, or
does the algorithm require uniform buffering?
Thanks!
Ben
--
Scenery Home Page:
http://scenery.x-plane.com/
Scenery blog:
http://xplanescenery.blogspot.com/
Plugin SDK:
http://www.xsquawkbox.net/xpsdk/
Scenery mailing list: x-plane-scenery@xxxxxxxxxxxxxxx
Developer mailing list: x-plane-dev@xxxxxxxxxxxxxxx
Was this page helpful?
Thread at a glance:
Previous Message by Date:
click to view message preview
Newbie Question - planar graph vs geometry graph
Hi,
I do apologize if this is a dumb question but...
Could someone please help me understand the relationships between the
planar graph, geometry graph, and spatial indexing classes?
I see two "planar graphs" in different namespaces, but no docs on
"geometry graph" yet, so I'm a little bit confused on where to look.
I'm looking for four types of functionality:
- A spatial index to speed up queries within an envelope. (Looks like
there are plenty of classes for that. :-)
- A planar map that can contain already-built topological planar graphs
from a file (e.g. I already have the topo info and need a container to
hold it and do things like adjacency queries and iteration).
- A planar map that can be built from GIS primitives like polygons and
multi-polygons.
In particular if there are classes that can do more than one of these
tasks with a performance advantage, that's what I'm really after.
If anyone can point me at the right classes for the right jobs, it would
be greatly appreciated!
*cheers*
ben
--
Scenery Home Page: http://scenery.x-plane.com/
Scenery blog: http://xplanescenery.blogspot.com/
Plugin SDK: http://www.xsquawkbox.net/xpsdk/
Scenery mailing list: x-plane-scenery@xxxxxxxxxxxxxxx
Developer mailing list: x-plane-dev@xxxxxxxxxxxxxxx
Previous Message by Thread:
click to view message preview
Newbie Question - planar graph vs geometry graph
Hi,
I do apologize if this is a dumb question but...
Could someone please help me understand the relationships between the
planar graph, geometry graph, and spatial indexing classes?
I see two "planar graphs" in different namespaces, but no docs on
"geometry graph" yet, so I'm a little bit confused on where to look.
I'm looking for four types of functionality:
- A spatial index to speed up queries within an envelope. (Looks like
there are plenty of classes for that. :-)
- A planar map that can contain already-built topological planar graphs
from a file (e.g. I already have the topo info and need a container to
hold it and do things like adjacency queries and iteration).
- A planar map that can be built from GIS primitives like polygons and
multi-polygons.
In particular if there are classes that can do more than one of these
tasks with a performance advantage, that's what I'm really after.
If anyone can point me at the right classes for the right jobs, it would
be greatly appreciated!
*cheers*
ben
--
Scenery Home Page: http://scenery.x-plane.com/
Scenery blog: http://xplanescenery.blogspot.com/
Plugin SDK: http://www.xsquawkbox.net/xpsdk/
Scenery mailing list: x-plane-scenery@xxxxxxxxxxxxxxx
Developer mailing list: x-plane-dev@xxxxxxxxxxxxxxx