<div dir="ltr"><div><div>Thank you Vicky, and sorry for my late response. I'm sure this roadmap draws a good and solid future for pgRouting. I would like to add some thoughts from my own experience:</div><div>- CGAL dependent functions: I'm agree with you that pgr_alphaShape and pgr_pointsAsPolygon should be inside PostGIS as they are pure geometric functions and CGAL is a too big dependence. However both functions works well and they are so usefull to build geometries for catchment areas.</div><div>- Personal thoughts about TRSP and Withpoints functions: </div><div><span style="white-space:pre"> </span>+ TRSP: the use of turn restrictions is critical to build real world vehicle routing applications, so I think this is a very important function. Putting the focus on this family of functions is a success due to the high level of interest it has (and will have much more). But I think there is an important weakness with TRSP: if you want to use with arbitrary points (edge fractions in this case, but without road side) you need to use old implementation that it is not very solid (performance is bad and there are some bugs). In the future, when TRSP function will be more estable, it could be interesting too to have a TRSP cost matrix function to compute big cost matrices.</div><div><span style="white-space:pre"> </span>+ Withpoints: When you develop a vehicle routing application you almost always get input data (source and target) as points with road side. For this reason this family of functions is so important too. It works well, but it has an importante weakness: there is no way to take control of turn restrictions and this is a big problem working with vehicles (I'm very worried about u-turns). The perfect shortest path function when you are working with vehicles would be the current Withpoint function capable of using a restrictions table.</div><div><br></div><div>Related to osm2pgrouting it would be interesting to continue with the experiments with Libosmium to build restrictions tables form OSM data. With real data we could test and debug in a better way TRSP functions. </div><div><br></div><div>Finally I would like to take this opportunity to announce you that it has been released osm2pgrouting version 2.3.4 last week and the next Milestone (2.3.5) starts his way:</div><div><a href="https://github.com/pgRouting/osm2pgrouting/releases">https://github.com/pgRouting/osm2pgrouting/releases</a></div><div><br></div><div><br></div><div>Thanks,</div><div>Cayetano</div></div><div><br></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div style="font-family:Helvetica,arial,sans-serif;font-size:18px;padding:20px 5px 10px 0px"><div dir="ltr" style="font-family:arial,sans-serif;font-size:12.8px"><b style="font-size:12.8px;font-family:Helvetica,arial,sans-serif;color:rgb(0,0,0)">Cayetano Benavent<br></b><font color="#000000" style="font-size:12.8px;font-family:Helvetica,arial,sans-serif">Head of Data</font></div><div dir="ltr" style="font-family:arial,sans-serif;font-size:12.8px"><span style="font-size:12.8px;font-family:Helvetica,arial,sans-serif"><span style="color:rgb(0,0,0);font-size:12px"><br></span><font color="#000000"><a href="tel:%2B34%20954%20095%20876" value="+34954701157" style="color:rgb(17,85,204)" target="_blank">+34 954 095 876</a></font><font face="Helvetica, arial, sans-serif" style="color:rgb(80,0,80);font-size:12.8px"><span style="font-size:12px"><br></span></font></span><span style="font-family:Helvetica,arial,sans-serif;font-size:12px;color:rgb(0,0,0)"><a href="http://www.geographica.gs/" style="color:rgb(17,85,204)" target="_blank">www.geographica.gs</a></span></div></div><div style="padding:10px 5px 20px 0px"></div></div></div></div></div></div></div></div></div></div></div></div></div></div>
<br><div class="gmail_quote">2018-04-10 19:31 GMT+02:00 Vicky Vergara <span dir="ltr"><<a href="mailto:vicky@georepublic.de" target="_blank">vicky@georepublic.de</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div style="font-family:arial,helvetica,sans-serif">Hello all,<br><br></div><div style="font-family:arial,helvetica,sans-serif">Thanks all for your feedback.<br></div><div style="font-family:arial,helvetica,sans-serif">Its difficult to know how many users are using the proposed or experimental functions.<br></div><div style="font-family:arial,helvetica,sans-serif">Moving up one level the functions implies bug fixing and documentation enhancement. (we could even move down functions?)<br></div><div style="font-family:arial,helvetica,sans-serif">"Priorities" is a subjective term: what is a priority to me might not be a priority to you, but in general:<br></div><div style="font-family:arial,helvetica,sans-serif">bug fixing (no matter where in the classification, (official, proposed, experimental) the function is, and move them up a level as we see fit.<br></div><div style="font-family:arial,helvetica,sans-serif">TRSP rewrite<br></div><div style="font-family:arial,helvetica,sans-serif">What works don't fix (aka, pgr_alphaShape + pgr_pointsAsPolygons)<br></div><div style="font-family:arial,helvetica,sans-serif"><br></div><div style="font-family:arial,helvetica,sans-serif"></div><div style="font-family:arial,helvetica,sans-serif"><br></div><div style="font-family:arial,helvetica,sans-serif">All your comments lead me to think that road map #2 with a twist:<br></div><div style="font-family:arial,helvetica,sans-serif">Next version to be 3.0, but the alpha version on march 2019 with feature freeze, and make the release on August/September 2019<br><br></div><div style="font-family:arial,helvetica,sans-serif">Reasons:<br></div><div style="font-family:arial,helvetica,sans-serif">- Documentation can be improved between march and August/September<br>- Give some time for osm2pgRouting & pgRoutingLayers to work for 3.0<br></div><div style="font-family:arial,helvetica,sans-serif">- Give time for the alpha to be tested and do bug fixes<br></div><div style="font-family:arial,helvetica,sans-serif">- Because pgRouting is FOSS, "normally" we work on it on our free time, so making the alpha on march will give us more time to do better work on making the 3.0 happen<br><br></div><div style="font-family:arial,helvetica,sans-serif">I would make the develop branch to be 3.0.0dev version this weekend, (unless another suggestion is made)<span class="gmail-HOEnZb"><font color="#888888"><br></font></span></div><span class="gmail-HOEnZb"><font color="#888888"><div style="font-family:arial,helvetica,sans-serif"><br></div><div style="font-family:arial,helvetica,sans-serif">Vicky<br></div><div style="font-family:arial,helvetica,sans-serif"><br></div><div style="font-family:arial,helvetica,sans-serif"><br></div><div style="font-family:arial,helvetica,sans-serif"><br></div><div style="font-family:arial,helvetica,sans-serif"><br></div></font></span></div><div class="gmail-HOEnZb"><div class="gmail-h5"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Apr 10, 2018 at 1:49 AM, Rohith Reddy <span dir="ltr"><<a href="mailto:rohithreddy2219@gmail.com" target="_blank">rohithreddy2219@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hello ,<br><br>The road map looks great !!!! I really like the idea of moving some experimental functions to proposed functions in both the road maps. I believe that this will continue to be in all the future road maps, as the experimental section keep accumulating with functions every year by the addition of new functionality by the GSoC students. So the question now is how can we efficiently convert these into proposed functions. I would suggest that moving the experimental functions to the proposed functions can be carried out based on a priority which can be the following<br><ul><li><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">Number of non-pgRouting users using the experimental function</span><br></li><li>Number of issues related to the experimental function </li><li>Dependency of a stable function on the experimental function for optimization.</li></ul>Based on the priorities, we could start testing the experimental functions, find bugs and solve them. I feel that this would be an efficient way of enriching the pgRouting functionality and usage in the upcoming releases.<br><br>I tried to use the contraction function (developed by me) an experimental function, in one of my research projects and then realised that there are bugs in contraction function. I had opened issues [1], [2], [3], [4] for the same. I am interested in working on moving the contraction function to a stable function. I am currently working on solving the issues and soon will have the functionality well tested. <br><br>I am also excited to see the rewrite of pgr_trsp with a dijkstra implementation. <span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">As Anthony mentioned his interest in using osm2pgrouting to extract turn data, I remember having a discussion on a rewrite of osm2pgrouting using osmosis. The functionality of extracting turn data can be considered in the rewrite of osm2pgrouting, so that it can easily be used with pgr_trsp rewrite. </span><br><br><br>Regards,<br>Rohith Reddy.<br><br><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">[1] <a href="https://github.com/pgRouting/pgrouting/issues/1003" target="_blank">https://github.com/pgRouti<wbr>ng/pgrouting/issues/1003</a></span><br>[2] <a href="https://github.com/pgRouting/pgrouting/issues/1004" target="_blank">https://github.com/pgRouti<wbr>ng/pgrouting/issues/1004</a><br>[3] <span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><a href="https://github.com/pgRouting/pgrouting/issues/1005" target="_blank">https://github.com/pgRouti<wbr>ng/pgrouting/issues/1005</a></span><div><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">[4] <span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><a href="https://github.com/pgRouting/pgrouting/issues/1006" target="_blank">https://github.com/pgRouti<wbr>ng/pgrouting/issues/1006</a></span></span></div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="gmail-m_-3789192897481528133h5">On Tue, Apr 10, 2018 at 3:47 AM, Aditya Pratap Singh <span dir="ltr"><<a href="mailto:adityapratap.singh28@gmail.com" target="_blank">adityapratap.singh28@gmail.co<wbr>m</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div class="gmail-m_-3789192897481528133h5"><div dir="ltr">Hello,<br><b style="font-weight:normal" id="gmail-m_-3789192897481528133m_6521716358107017582m_-1237438595118405342gmail-docs-internal-guid-b411c806-ac79-1adf-ebaf-88f505949054"><p dir="ltr" style="line-height:1.2;margin-top:0pt;margin-bottom:0pt"><br></p></b><div class="gmail_extra"><div class="gmail_extra">When I was reading documentation I found a bug in pgr_withPointsDD and I created an issue ( <a href="https://github.com/pgRouting/pgrouting/issues/979" target="_blank">https://github.com/pgRouting/p<wbr>grouting/issues/979</a> ) which was finally resolved but as you pointed this function still have some other bugs, So it should be our first prior to fix bugs of pgr_withPoints function.</div><div class="gmail_extra">I think it is right time to take some proposed function to official function as there are very less official functions and some experiment function to proposed function.</div><div class="gmail_extra">Seriously telling I don’t know the functionality of pgr_alphaShape but as Daniel said that there are very few non-pgRouting users, that find the AlphaShape function useful. So according to me it should be our least prior but if possible and time permit we can implement using boost in #2 road map. </div><div class="gmail_extra">Another important function is pgr_trsp. I know the functionality of this function and as you have pointed this function is not well designed. So we will fix bugs of this function ASAP as many users are using this functions. So, I’ll also go with road map #2 as it looks more stable to me. I am going to learn lot of things in release of version 3.0 of pgRouting.</div><div><br></div><div>Thanks</div><div>Aditya Pratap Singh<br><br></div><div class="gmail_quote"><span>On Tue, Apr 3, 2018 at 9:06 PM, Vicky Vergara <<a href="mailto:vicky@georepublic.de" target="_blank">vicky@georepublic.de</a>> wrote:</span><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span>
<br><br> Hello fellow developers,<br><br> As you know we are rewriting pgRouting, since v2.1, to remove all "bugs",<br> like the non standard way of constructing a graph, and using more C++<br> features.<br><br> The rewrite is "almost done":<br><br> **First pair of functions**<br><br></span> - pgr_alphaShape - Alpha shape computation<br> - pgr_pointsAsPolygon - Polygon around a set of points<div><div class="gmail-m_-3789192897481528133m_6521716358107017582h5"><br><br> Both functions are tightly dependant, and I believe that they should be a<br> postGIS function as is a geometry function, and the closest one that<br> resembles this pair of functions is ST_ConcaveHull [1] Some time ago I<br> compared both functions on [2]<br><br> I went to see how to add that function to postGIS, and for the moment that<br> is not possible, it sould be done first in GEOS, and GEOS is so big, right<br> now I dont feel is the time to do that, but rewriting to use boost:Geometry<br> would eliminate the need of CGAL, so one less pre-requisite to build<br> pgRouting would be needed. or they can stay as they are now.<br><br> **The other function is pgr_trsp**<br><br> Which has so many problems at postgres level [4], Last year on GSoC,<br> Vidham tried to do a rewrite, confirming that the problem is much harder<br> than expected for the 3 month program. But as far as I know many people use<br> them because it has the "points" version.<br> The C++ code is not well designed [5], just a look at that, my_dijkstra<br> calls my_dijkstra and that calls my_dijkstra, it still uses pointers, so<br> great chance of memory leaks, etc.<br> Basically is **Use at your own risk**<br><br><br> Beside those functions mentioned above, now we are in the moment where<br> there are more proposed functions [7] than official functions. and a lot<br> of deprecated functions that have to be maintained and tested because of<br> backwards compatibility.<br><br> ** So, here is my road map #1 **<br> Version 2.7 to be released on September 2018 where fix bug of<br> pgr_withPoints [8] is a must have, and the possibilities of what other<br> things it could have:<br> - New functionality done by GSoC students on "experimental section"<br> - Write a substitution (with a different name maybe pgr_dijkstraTR) for<br> pgr_trsp (one vertex to one vertex) based on dijkstra<br> - Rewrite pgr_alphaShape to use boost:graph instead of CGAL<br> - move some experimental functions up to proposed<br><br> Version 3.0 I would like it to be on September 2019<br> Where a complete cleanup of the deprecated functions would be done,<br> Move proposed functions to official pgRouting functions.<br><br> ** So, here is my road map #2 **<br><br> Version 3.0 to be released on March 2019 where fix bug of pgr_withPoints<br>[8] and Complete cleanup of the deprecated functions are a must have, and<br> the possibilities of what other things it could have:<br> - New functionality done by GSoC students on "experimental section"<br> - Write a substitution (with a different name maybe pgr_dijkstraTR) for<br> pgr_trsp (one vertex to one vertex) based on dijkstra<br> - Rewrite pgr_alphaShape to use boost:graph instead of CGAL<br> - move some experimental functions up to proposed<br> - Move proposed functions to official pgRouting functions.<br><br> Probably this second road map will make the second version of the<br> pgRouting book a little easier to write, (please Robe, comment on this)<br><br><br> We would like comments from the community about both road maps and if<br> possible to test proposed functions and experimental functions to help<br> decide which proposed functions can go up one level. (don't forget to open<br> issues)<br><br> Regards<br> pgRouting team<br><br><br> [1] <a href="https://postgis.net/docs/ST_ConcaveHull.html" rel="noreferrer" target="_blank">https://postgis.net/docs/ST_Co<wbr>ncaveHull.html</a><br> [2] <a href="https://github.com/cvvergara/pgrouting/issues/57" rel="noreferrer" target="_blank">https://github.com/cvvergara/p<wbr>grouting/issues/57</a><br> [3] <a href="https://github.com/pgRouting/pgrouting/blob/master/sql/" rel="noreferrer" target="_blank">https://github.com/pgRouting/p<wbr>grouting/blob/master/sql/</a><br> alpha_shape/alpha_shape.sql#L<wbr>62<br> [4] <a href="https://github.com/pgRouting/pgrouting/tree/master/doc/trsp" rel="noreferrer" target="_blank">https://github.com/pgRouting/p<wbr>grouting/tree/master/doc/trsp</a><br> [5] <a href="https://github.com/pgRouting/pgrouting/blob/master/include/" rel="noreferrer" target="_blank">https://github.com/pgRouting/p<wbr>grouting/blob/master/include/</a>t<wbr>rsp/GraphDefinition.h#L94<br> [6] <a href="https://github.com/pgRouting/pgrouting/tree/master/sql/pickDeliver" rel="noreferrer" target="_blank">https://github.com/pgRouting/p<wbr>grouting/tree/master/sql/pickD<wbr>eliver</a><br> [7] <a href="http://docs.pgrouting.org/latest/en/proposed.html" rel="noreferrer" target="_blank">http://docs.pgrouting.org/late<wbr>st/en/proposed.html</a><br> [8] <a href="https://github.com/pgRouting/pgrouting/issues/760" rel="noreferrer" target="_blank">https://github.com/pgRouting/p<wbr>grouting/issues/760</a><br><br> --<br><br> Georepublic UG (haftungsbeschränkt)<br> Salzmannstraße 44,<br> 81739 München, Germany<br><br> Vicky Vergara<br> Operations Research<br><br> eMail: <a href="mailto:vicky@georepublic.de" target="_blank">vicky@georepublic.de</a><br> Web: <a href="https://georepublic.info" rel="noreferrer" target="_blank">https://georepublic.info</a><br><br> Tel: +49 (089) 4161 7698-1<br> Fax: +49 (089) 4161 7698-9<br><br> Commercial register: Amtsgericht München, HRB 181428<br> CEO: Daniel Kastl<br>
</div></div></blockquote></div><br></div></div>
<br></div></div><span>______________________________<wbr>_________________<br>
pgrouting-dev mailing list<br>
<a href="mailto:pgrouting-dev@lists.osgeo.org" target="_blank">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/mailma<wbr>n/listinfo/pgrouting-dev</a><br></span></blockquote></div><br></div>
<br>______________________________<wbr>_________________<br>
pgrouting-dev mailing list<br>
<a href="mailto:pgrouting-dev@lists.osgeo.org" target="_blank">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/mailma<wbr>n/listinfo/pgrouting-dev</a><br></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail-m_-3789192897481528133gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><pre>Georepublic UG (haftungsbeschränkt)
Salzmannstraße 44,
81739 München, Germany
Vicky Vergara
Operations Research
eMail: vicky@<a href="http://georepublic.de" target="_blank">georepublic.de</a>
Web: <a href="https://georepublic.info" target="_blank">https://georepublic.info</a>
Tel: +49 (089) 4161 7698-1
Fax: +49 (089) 4161 7698-9
Commercial register: Amtsgericht München, HRB 181428
CEO: Daniel Kastl
<span></span></pre></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></div></div>