<div dir="ltr">Thank you Vicky for your thoughts about the roadmap!<div><br></div><div>I agree, that the function to calculate the drivetime polygon would be much better suited to PostGIS (and/or GEOS).</div><div>It's nice to have as few dependencies as possible. Like Regine said, current package maintainers already for got used to having CGAL as a dependency, and I remember a time, when it was a real obstacle, but now it's not so big problem anymore. </div><div><br></div><div>I'm not sure, if there are non-pgRouting users, that may find the AlphaShape function useful. </div><div>It would be nice, if such a work to "move" this part out of pgRouting would be funded or contributed.</div><div><br></div><div>Daniel</div><div><br></div><div> </div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 4, 2018 at 6:41 AM, Regina Obe <span dir="ltr"><<a href="mailto:lr@pcorp.us" target="_blank">lr@pcorp.us</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="EN-US" link="blue" vlink="purple"><div class="m_1663868514588902972WordSection1"><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">The Roadmap looks good to me.  Should make some sections of pgRouting book obsolete and allow us to cover other topics.<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">*withPoints functions are very popular, but I think there has to be a simpler way of coming up with the  point/frac  as that's where I think most people struggle.<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">But unfortunately I don't have any thoughts about that yet and haven't looked at recent functions added.  <u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">As far as getting rid of CGAL not sure how important that is.  I think a lot of package maintainers are used to having that dependency now and for Windows, I need to include CGAL anyway to support PostGIS SFCGAL.<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">There is also some talk of expanding CGAL use in PostGIS.  That said, if the alpha shape rewriting is a lot of work, I'd put it off, as the gain would have been useful a couple of years ago, but not so much today.<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Thanks,<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d">Regina<u></u><u></u></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> pgrouting-dev [mailto:<a href="mailto:pgrouting-dev-bounces@lists.osgeo.org" target="_blank">pgrouting-dev-bounces@<wbr>lists.osgeo.org</a>] <b>On Behalf Of </b>Vicky Vergara<br><b>Sent:</b> Tuesday, April 03, 2018 11:37 AM<br><b>To:</b> pgRouting developers mailing list <<a href="mailto:pgrouting-dev@lists.osgeo.org" target="_blank">pgrouting-dev@lists.osgeo.org</a><wbr>><br><b>Subject:</b> [pgrouting-dev] A roadmap<u></u><u></u></span></p><div><div class="h5"><p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p><div><div><p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Arial",sans-serif"><u></u> <u></u></span></p></div><div><p class="MsoNormal" style="margin-right:0in;margin-bottom:12.0pt;margin-left:.5in"><span style="font-family:"Arial",sans-serif">Hello fellow developers,<u></u><u></u></span></p></div><div><p class="MsoNormal" style="margin-right:0in;margin-bottom:12.0pt;margin-left:.5in"><span style="font-family:"Arial",sans-serif">As you know we are rewriting pgRouting, since v2.1, to remove all "bugs", like the non standard way of constructing a graph, and using more C++ features.<u></u><u></u></span></p></div><div><p class="MsoNormal" style="margin-right:0in;margin-bottom:12.0pt;margin-left:.5in"><span style="font-family:"Arial",sans-serif">The rewrite is "almost done":<u></u><u></u></span></p></div><div><p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Arial",sans-serif">**First pair of functions**<u></u><u></u></span></p></div><div><p class="MsoNormal" style="margin-left:1.0in"><u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">        </span></span></span><u></u><span class="m_1663868514588902972gmail-std"><span style="font-family:"Arial",sans-serif">pgr_alphaShape</span></span><span style="font-family:"Arial",sans-serif"> - Alpha shape computation<u></u><u></u></span></p><p class="MsoNormal" style="margin-left:1.0in"><u></u><span style="font-size:10.0pt;font-family:Symbol"><span>·<span style="font:7.0pt "Times New Roman"">        </span></span></span><u></u><span class="m_1663868514588902972gmail-std"><span style="font-family:"Arial",sans-serif">pgr_pointsAsPolygon</span></span><span style="font-family:"Arial",sans-serif"> - Polygon around a set of points<u></u><u></u></span></p><p class="MsoNormal" style="margin-right:0in;margin-bottom:12.0pt;margin-left:.5in"><span style="font-family:"Arial",sans-serif">Both functions are tightly dependant, and I believe that they should be a postGIS function as is a geometry function, and the closest one that resembles this pair of functions is  ST_ConcaveHull [1] Some time ago I compared both functions on [2] <br><br>I went to see how to add that function to postGIS, and for the moment that is not possible, it sould be done first in GEOS, and  GEOS is so big, right now I dont feel is the time to do that, but rewriting to use boost:Geometry would eliminate the need of CGAL, so one less pre-requisite to build pgRouting would be needed. or they can stay as they are now.<br><br><u></u><u></u></span></p></div><div><p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Arial",sans-serif">**The other function is pgr_trsp**<br><br>Which has so many problems at postgres level [4], Last year on GSoC, Vidham tried to do a rewrite, confirming that the problem is much harder than expected for the 3 month program. But as far as I know many people use them because it has the "points" version.<u></u><u></u></span></p></div><div><p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Arial",sans-serif">The C++ code is not well designed [5], just a look at that, my_dijkstra calls my_dijkstra and that calls my_dijkstra, it still uses pointers, so great chance of memory leaks, etc.<u></u><u></u></span></p></div><div><p class="MsoNormal" style="margin-right:0in;margin-bottom:12.0pt;margin-left:.5in"><span style="font-family:"Arial",sans-serif">Basically is **Use at your own risk**<br><br><br>Beside those functions mentioned above, now we are in the moment where there are  more proposed functions [7] than official functions. and a lot of deprecated functions that have to be maintained and tested because of backwards compatibility.<u></u><u></u></span></p></div><div><p class="MsoNormal" style="margin-right:0in;margin-bottom:12.0pt;margin-left:.5in"><span style="font-family:"Arial",sans-serif">** So, here is my road map #1 **<u></u><u></u></span></p></div><div><p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Arial",sans-serif">Version 2.7 to be released on September 2018 where fix bug of pgr_withPoints [8] is a must have, and the possibilities of what other things it could have:<u></u><u></u></span></p></div><div><p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Arial",sans-serif">- New functionality done by GSoC students on "experimental section"<u></u><u></u></span></p></div><div><p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Arial",sans-serif">- Write a substitution (with a different name maybe pgr_dijkstraTR) for pgr_trsp (one vertex to one vertex) based on dijkstra<u></u><u></u></span></p></div><div><p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Arial",sans-serif">- Rewrite pgr_alphaShape to use boost:graph instead of CGAL<u></u><u></u></span></p></div><div><p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Arial",sans-serif">- move some experimental functions up to proposed<u></u><u></u></span></p></div><div><p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Arial",sans-serif"><u></u> <u></u></span></p></div><div><p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Arial",sans-serif">Version 3.0 I would like it to be on September 2019<u></u><u></u></span></p></div><div><p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Arial",sans-serif">Where a complete cleanup of the deprecated functions would be done,<u></u><u></u></span></p></div><div><p class="MsoNormal" style="margin-right:0in;margin-bottom:12.0pt;margin-left:.5in"><span style="font-family:"Arial",sans-serif">Move proposed functions to official pgRouting functions.<br><br>** So, here is my road map #2 **<u></u><u></u></span></p><div><p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Arial",sans-serif">Version 3.0 to be released on March 2019 where fix bug of pgr_withPoints [8] and Complete cleanup of the deprecated functions are a must have, and the possibilities of what other things it could have:<u></u><u></u></span></p></div><div><p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Arial",sans-serif">- New functionality done by GSoC students on "experimental section"<u></u><u></u></span></p></div><div><p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Arial",sans-serif">- Write a substitution (with a different name maybe pgr_dijkstraTR) for pgr_trsp (one vertex to one vertex) based on dijkstra<u></u><u></u></span></p></div><div><p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Arial",sans-serif">- Rewrite pgr_alphaShape to use boost:graph instead of CGAL<u></u><u></u></span></p></div><div><p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Arial",sans-serif">- move some experimental functions up to proposed<u></u><u></u></span></p></div><div><p class="MsoNormal" style="margin-right:0in;margin-bottom:12.0pt;margin-left:.5in"><span style="font-family:"Arial",sans-serif">- Move proposed functions to official pgRouting functions.<u></u><u></u></span></p></div><p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Arial",sans-serif">Probably this second road map will make the second version of the pgRouting book a little easier to write, (please Robe, comment on this)<u></u><u></u></span></p></div><div><p class="MsoNormal" style="margin-right:0in;margin-bottom:12.0pt;margin-left:.5in"><span style="font-family:"Arial",sans-serif"><u></u> <u></u></span></p></div><div><p class="MsoNormal" style="margin-right:0in;margin-bottom:12.0pt;margin-left:.5in"><span style="font-family:"Arial",sans-serif">We would like comments from the community about both road maps and if possible  to test proposed functions and experimental functions to help decide which proposed functions can go up one level. (don't forget to open issues)<u></u><u></u></span></p></div><div><p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Arial",sans-serif">Regards<u></u><u></u></span></p></div><div><p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Arial",sans-serif">pgRouting team<u></u><u></u></span></p></div><div><p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Arial",sans-serif"><u></u> <u></u></span></p></div><div><p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Arial",sans-serif"><br>[1] <a href="https://postgis.net/docs/ST_ConcaveHull.html" target="_blank">https://postgis.net/docs/ST_<wbr>ConcaveHull.html</a><br>[2] <a href="https://github.com/cvvergara/pgrouting/issues/57" target="_blank">https://github.com/cvvergara/<wbr>pgrouting/issues/57</a><br>[3] <a href="https://github.com/pgRouting/pgrouting/blob/master/sql/alpha_shape/alpha_shape.sql#L62" target="_blank">https://github.com/pgRouting/<wbr>pgrouting/blob/master/sql/<wbr>alpha_shape/alpha_shape.sql#<wbr>L62</a><br>[4] <a href="https://github.com/pgRouting/pgrouting/tree/master/doc/trsp" target="_blank">https://github.com/pgRouting/<wbr>pgrouting/tree/master/doc/trsp</a><br clear="all"><u></u><u></u></span></p></div><p class="MsoNormal" style="margin-left:.5in">[<u></u><u></u></p><div><p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Arial",sans-serif">​5] <a href="https://github.com/pgRouting/pgrouting/blob/master/include/trsp/GraphDefinition.h#L94" target="_blank">https://github.com/pgRouting/<wbr>pgrouting/blob/master/include/<wbr>trsp/GraphDefinition.h#L94</a>​<u></u><u></u></span></p></div><p class="MsoNormal" style="margin-left:.5in"><br>[<u></u><u></u></p><div><p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Arial",sans-serif">​6] <a href="https://github.com/pgRouting/pgrouting/tree/master/sql/pickDeliver" target="_blank">https://github.com/pgRouting/<wbr>pgrouting/tree/master/sql/<wbr>pickDeliver</a>​<u></u><u></u></span></p></div><p class="MsoNormal" style="margin-left:.5in"><br>[<u></u><u></u></p><div><p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Arial",sans-serif">​7] <a href="http://docs.pgrouting.org/latest/en/proposed.html" target="_blank">http://docs.pgrouting.org/<wbr>latest/en/proposed.html</a><br>[8] <a href="https://github.com/pgRouting/pgrouting/issues/760" target="_blank">https://github.com/pgRouting/<wbr>pgrouting/issues/760</a>​<u></u><u></u></span></p></div><p class="MsoNormal" style="margin-left:.5in"><br>-- <u></u><u></u></p><div><div><div><div><div><div><div><div><div><div><div><div><div><div><div><div><div><div><div><div><pre style="margin-left:.5in">Georepublic UG (haftungsbeschränkt)<u></u><u></u></pre><pre style="margin-left:.5in">Salzmannstraße 44, <u></u><u></u></pre><pre style="margin-left:.5in">81739 München, Germany<u></u><u></u></pre><pre style="margin-left:.5in"><u></u> <u></u></pre><pre style="margin-left:.5in">Vicky Vergara<u></u><u></u></pre><pre style="margin-left:.5in">Operations Research<u></u><u></u></pre><pre style="margin-left:.5in"><u></u> <u></u></pre><pre style="margin-left:.5in">eMail: vicky@<a href="http://georepublic.de" target="_blank">georepublic.de</a><u></u><u></u></pre><pre style="margin-left:.5in">Web: <a href="https://georepublic.info" target="_blank">https://georepublic.info</a><u></u><u></u></pre><pre style="margin-left:.5in"><u></u> <u></u></pre><pre style="margin-left:.5in">Tel: +49 (089) 4161 7698-1<u></u><u></u></pre><pre style="margin-left:.5in">Fax: +49 (089) 4161 7698-9<u></u><u></u></pre><pre style="margin-left:.5in"><u></u> <u></u></pre><pre style="margin-left:.5in">Commercial register: Amtsgericht München, HRB 181428<u></u><u></u></pre><pre style="margin-left:.5in">CEO: Daniel Kastl<u></u><u></u></pre><pre style="margin-left:.5in"><u></u> <u></u></pre></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div><br>______________________________<wbr>_________________<br>
pgrouting-dev mailing list<br>
<a href="mailto:pgrouting-dev@lists.osgeo.org">pgrouting-dev@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/pgrouting-dev" rel="noreferrer" target="_blank">https://lists.osgeo.org/<wbr>mailman/listinfo/pgrouting-dev</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><span style="font-family:arial,sans-serif;font-size:13px;border-collapse:collapse">Georepublic UG & Georepublic Japan<br>eMail: <a href="mailto:daniel.kastl@georepublic.de" style="color:rgb(66,99,171)" target="_blank">daniel.kastl@georepublic.de</a><br>Web: <a href="https://georepublic.info" target="_blank">https://georepublic.info</a></span><div><br></div><div><br></div><div><br></div></div></div></div></div>
</div>