https://wiki.osgeo.org/w/index.php?action=history&feed=atom&title=Paris_Code_Sprint_2016_%3A_SFCGAL_Agenda 2026-08-08T09:10:34Z Revision history for this page on the wiki MediaWiki 1.35.9 https://wiki.osgeo.org/w/index.php?title=Paris_Code_Sprint_2016_:_SFCGAL_Agenda&diff=96268&oldid=prev 2016-02-02T08:03:46Z

<p></p> <table class="diff diff-contentalign-left diff-editfont-monospace" data-mw="interface"> <col class="diff-marker" /> <col class="diff-content" /> <col class="diff-marker" /> <col class="diff-content" /> <tr class="diff-title" lang="en"> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td> <td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 08:03, 2 February 2016</td> </tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l7" >Line 7:</td> <td colspan="2" class="diff-lineno">Line 7:</td></tr> <tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* Is there a way to live with two kernels (inexact and exact) to avoid exact geometry construction when not needed ?</div></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* Is there a way to live with two kernels (inexact and exact) to avoid exact geometry construction when not needed ?</div></td></tr> <tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* Does the new &quot;expanded&quot; object representation offered by postgresql helps in avoiding to serialize / unserialize between each call ?</div></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* Does the new &quot;expanded&quot; object representation offered by postgresql helps in avoiding to serialize / unserialize between each call ?</div></td></tr> <tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"></ins></div></td></tr> <tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">* How to reduce type conversions ? (GSERIALIZED -&gt; LWGEOM -&gt; SFCGAL -&gt; CGAL) ?</ins></div></td></tr> <tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">** idea: forget SFCGAL::Geometry, use geometry concepts and traits and each &quot;client&quot; library should adapt its classes to the concepts. There could be an adaptor for GSERIALIZED, one for QgsGeometry, etc. Inspire by boost::geometry see http://www.boost.org/doc/libs/1_60_0/libs/geometry/doc/html/geometry/examples/example__adapting_a_legacy_geometry_object_model.html</ins></div></td></tr> <tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td></tr> <tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* Any advances in CGAL about 3D snap rounding ?</div></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* Any advances in CGAL about 3D snap rounding ?</div></td></tr> </table>

Wiki-Mhugo https://wiki.osgeo.org/w/index.php?title=Paris_Code_Sprint_2016_:_SFCGAL_Agenda&diff=96133&oldid=prev 2016-01-28T15:40:31Z

<p>Created page with &quot;Discussion and group review topics for the <a href="/wiki/Paris_Code_Sprint_2016" title="Paris Code Sprint 2016">Paris Code Sprint 2016</a>. == Discussion == * How to get rid of validity test before geometry construction ? ** add a flag to the...&quot;</p> <p><b>New page</b></p><div>Discussion and group review topics for the [[Paris Code Sprint 2016]].<br /> <br /> == Discussion ==<br /> <br /> * How to get rid of validity test before geometry construction ?<br /> ** add a flag to the postgis geometry ? (is_valid)<br /> * Is there a way to live with two kernels (inexact and exact) to avoid exact geometry construction when not needed ?<br /> * Does the new &quot;expanded&quot; object representation offered by postgresql helps in avoiding to serialize / unserialize between each call ?<br /> <br /> * Any advances in CGAL about 3D snap rounding ?<br /> <br /> * Integrate spherical kernels ?<br /> <br /> == Functions that would be nice to have in SFCGAL ==<br /> <br /> * alpha shapes from CGAL 2D and 3D<br /> * &quot;field of view&quot; : not necessarily related to CGAL<br /> * roof generation from straight skeleton</div>

Wiki-Mhugo