<div dir="ltr">I am excited about the proposed work in rewriting pgr_trsp with a Dijkstra implementation and would be happy to participate in discussion related to this rework as it might have good implication on my work (even without With-Points capabilities). <div><br></div><div>I am also interested in working towards moving the pgr_lineGraphFull function up from the experimental section and am hoping to work towards this in the near future. <div><br></div><div>I remember some discussion of making pgRouting into an API style library for the 3.0 release where the graph can stay loaded into memory across multiple calls to pgRouting and this change interests me because of its potential run-time benefits. </div><div><br></div><div>Another project that I have seen discussion on that I am interested in is using osm2pgrouting to extract turn data to be used with the pgr_trsp rewrite (although I think some work has already been done on this effort).</div><div><br></div><div>Because of all of this I would be happy to see a 3.0 release sooner as per road map #2 so that these improvements can be made use of sooner but both road maps look good to me!</div></div><div><br></div><div>Thanks,</div><div>Anthony</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Apr 3, 2018 at 11:36 AM, Vicky Vergara <span dir="ltr"><<a href="mailto:vicky@georepublic.de" target="_blank">vicky@georepublic.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Hello fellow developers,<br><br></div><div class="gmail_default" style="font-family:arial,helvetica,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.<br><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">The rewrite is "almost done":<br><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">**First pair of functions**<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><ul>
<li><span class="m_5238344868831538558gmail-std m_5238344868831538558gmail-std-ref">pgr_alphaShape</span> - Alpha shape computation<br></li>
<li><span class="m_5238344868831538558gmail-std m_5238344868831538558gmail-std-ref">pgr_pointsAsPolygon</span> - Polygon around a set of points</li>
</ul>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><br></div><div class="gmail_default" style="font-family:arial,helvetica,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.<br></div><div class="gmail_default" style="font-family:arial,helvetica,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.<br></div><div class="gmail_default" style="font-family:arial,helvetica,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.<br><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">** So, here is my road map #1 **<br><br></div><div class="gmail_default" style="font-family:arial,helvetica,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:<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">- New functionality done by GSoC students on "experimental section"<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">- Write a substitution (with a different name maybe pgr_dijkstraTR) for pgr_trsp (one vertex to one vertex) based on dijkstra<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">- Rewrite pgr_alphaShape to use boost:graph instead of CGAL<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">- move some experimental functions up to proposed<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Version 3.0 I would like it to be on September 2019<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Where a complete cleanup of the deprecated functions would be done,<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Move proposed functions to official pgRouting functions.<br><br>** So, here is my road map #2 **<br><br><div class="gmail_default" style="font-family:arial,helvetica,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:<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">- New functionality done by GSoC students on "experimental section"<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">- Write a substitution (with a different name maybe pgr_dijkstraTR) for pgr_trsp (one vertex to one vertex) based on dijkstra<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">- Rewrite pgr_alphaShape to use boost:graph instead of CGAL<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">- move some experimental functions up to proposed<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">- Move proposed functions to official pgRouting functions.<br><br></div>Probably this second road map will make the second version of the pgRouting book a little easier to write, (please Robe, comment on this)<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br><br></div><div class="gmail_default" style="font-family:arial,helvetica,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)<br><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Regards<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">pgRouting team<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,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"></div>[<div style="font-family:arial,helvetica,sans-serif;display:inline" class="gmail_default">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></div><br>[<div style="font-family:arial,helvetica,sans-serif;display:inline" class="gmail_default">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></div><br>[<div style="font-family:arial,helvetica,sans-serif;display:inline" class="gmail_default">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></div><br>-- <br><div class="m_5238344868831538558gmail_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>
<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>