Re: [Boost-users] boost geometry lib
Hi, Sorry for my late reply, was not on this list earlier. Thanks for your interest. As Bruno said we're currently busy with preview 4. There are substantial changes internally, but from user perspective the changes are not so large. Two things I'll mention: 1)
http://geometrylibrary.geodan.nl/6__transformation__example_8cpp-exampl e.html shows the geometry library and uBLAS working together The transformation example will be changed (and much more simpler, from user perspective). The new version has internally transformation capacities and strategies can be used to finetune this (still using uBLAS)
2) if you plan to use the linestrings, note that the algorithms currently take line.begin() and line.end(). This is changed in the new version to just "line", using the boost range library. Preview 4 is expected this month or the beginning of February. Barend Gehrels Geodan, Amsterdam
On Mon, Jan 26, 2009 at 12:34 PM, Barend Gehrels
Hi,
Sorry for my late reply, was not on this list earlier. Thanks for your interest.
As Bruno said we're currently busy with preview 4. There are substantial changes internally, but from user perspective the changes are not so large.
Two things I'll mention:
1)
http://geometrylibrary.geodan.nl/6__transformation__example_8cpp-exampl e.html shows the geometry library and uBLAS working together
The transformation example will be changed (and much more simpler, from user perspective). The new version has internally transformation capacities and strategies can be used to finetune this (still using uBLAS)
2) if you plan to use the linestrings, note that the algorithms currently take line.begin() and line.end(). This is changed in the new version to just "line", using the boost range library.
Preview 4 is expected this month or the beginning of February.
Barend Gehrels Geodan, Amsterdam
That's good to hear - I'll probably replace my stuff with geometrylib when it's out. Is the Boost mailing list the best one to talk about geometrylib? Regards, Pete
Peter Barker wrote:
That's good to hear - I'll probably replace my stuff with geometrylib when it's out. Is the Boost mailing list the best one to talk about geometrylib?
You can use this list for general questions, you can also contact us directly, whatever you prefer. In the past discussions where at the boost developer list. Barend
Dear list,
Preview 4 is expected this month or the beginning of February.
That's good to hear - I'll probably replace my stuff with geometrylib when it's out. Is the Boost mailing list the best one to talk about geometrylib?
The preview 4 of the Generic Geometry Library is published today, herewith the message to the boost-developers list: ------------------------------ It is a pleasure for us to present the fourth preview of the Generic Geometry Library. This time we've added the library to the SVN repository at boost, https://svn.boost.org/svn/boost/sandbox/ggl To store the library under a proper name, "ggl" is used, which stands for Generic Geometry Library. Before this we called it just Geometry Library, but we think Generic is appropriate from this version on. The first three previews were sent to this list in January, March and October 2008. Since then everything has been revised and reworked again, based on comments from the list. Thanks for all your comments! Concepts are now applied for all geometries. Algorithms now take any geometry fulfilling the concepts, and automatically take the right version of the underlying implementation. Ranges are now used instead of .begin()/end(). Tag dispatching is used instead of SFINAE. Transformations: previously these were just explained as an example, now transformations are included in the library, either to go from one coordinate system to another (for example from spherical to cartesian3D) or to translate/rotate/scale/map points from one Cartesian system to another, or otherwise. Map projections: included is an extensive addition with nearly 100 map projections. Those are not programmed by ourselves but automatically converted from C (PROJ4) into a our template-based approach, fitting with the geometry library, especially in the transformations explained above. License-wise this is possible. We're not sure about if this would fit in the Boost Library Collection, if there is interest in it, or that it might be "too much" for it, so we would be glad to hear your opinions. For more change descriptions, see the page on status and preview from the documentation (link below). The Generic Geometry Library is accessible from Boost SVN, mentioned above, or can be downloaded as well from http://geometrylibrary.geodan.nl Especially the examples, such as the custom point example and custom line string example show nicely how the library handles custom geometries and how they can be used inside the generic algorithms. We welcome any type of comment, opinion, cooperation, merge or join. Barend Gehrels, Amsterdam Bruno Lalande, Paris
participants (2)
-
Barend Gehrels -
Peter Barker