<div dir="ltr"><div><div>There has been some talk that we may rearrange or change infrastructure as a result of if we change our source code management (<a href="http://www.geomoose.org/rfc/rfc-4.html">http://www.geomoose.org/rfc/rfc-4.html</a>). <br>
<br></div>Here are some bits and pieces of pgrouting documentation/website/code updates which also appears to use sphinx. If we do change things, we might be able to evaluate the pgrouting process and see how we like it. <br>
<br></div>Eli<br><div><br><br><br><div><br><div><div><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Daniel Kastl</b> <span dir="ltr"><<a href="mailto:daniel@georepublic.de">daniel@georepublic.de</a>></span><br>
Date: Mon, Jul 15, 2013 at 7:09 PM<br>Subject: Re: [pgrouting-users] Rewrite of one of the TSP functions, updated tests and docs, closing ...<br>To: pgRouting users mailing list <<a href="mailto:pgrouting-users@lists.osgeo.org">pgrouting-users@lists.osgeo.org</a>><br>
<br><br><div dir="ltr">Just updated the "dev" docs: <a href="http://docs.pgrouting.org/dev/doc/index.html" target="_blank">http://docs.pgrouting.org/dev/doc/index.html</a><div><br></div><div>@steve: it's very easy to update. From your build directory just run</div>
<div><br></div><div><div><font face="courier new, monospace">git checkout gh-pages && rm -Rf dev && cp -r build/html dev && git add dev && cp build/index.html .</font></div><div><font face="courier new, monospace">git commit -m "updated to commit [...]" . && git push origin gh-pages</font></div>
</div><div><br></div><div>It does a checkout of the "Github pages" branch, then replaces the current "dev" directory with the contents of the "build/html" directory and pushes the changes back Github.</div>
<div>When the content of the "gh-pages" branch is updated, then the docs are also the latest ones.</div><div><br></div><div>Just creating release documentation involves a few more manual edits.<br><br></div><div>
<br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><div><div class="h5"><br><br><div class="gmail_quote">On Sat, Jul 13, 2013 at 3:52 AM, Dave Potts <span dir="ltr"><<a href="mailto:dave.potts@pinan.co.uk" target="_blank">dave.potts@pinan.co.uk</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 bgcolor="#FFFFFF" text="#000000"><div>
<div>On 12/07/13 13:29, Stephen Woodbridge
wrote:<br>
</div>
<blockquote type="cite">On
7/12/2013 3:56 AM, Dave Potts wrote:
<br>
<blockquote type="cite">On 12/07/13 03:49, Stephen Woodbridge
wrote:
<br>
ticket 156
<br>
(<a href="http://download.osgeo.org/pgrouting/forum/pgrouting.postlbs.org/ticket/156.html" target="_blank">http://download.osgeo.org/pgrouting/forum/pgrouting.postlbs.org/ticket/156.html</a>)
<br>
last updated 19 months ago.
<br>
ticket
<br>
127(<a href="http://download.osgeo.org/pgrouting/forum/pgrouting.postlbs.org/ticket/127.html" target="_blank">http://download.osgeo.org/pgrouting/forum/pgrouting.postlbs.org/ticket/127.html</a>)
<br>
lastchanged 7 days ago
<br>
<br>
Neither of these tickets seem to refer to the current version of
the
<br>
tsp, are these the right ticket number or just proof that I do
not known
<br>
how to look at closed tickets?
<br>
</blockquote>
<br>
<br>
<a href="https://github.com/pgRouting/pgrouting/issues/127" target="_blank">https://github.com/pgRouting/pgrouting/issues/127</a>
<br>
<a href="https://github.com/pgRouting/pgrouting/issues/156" target="_blank">https://github.com/pgRouting/pgrouting/issues/156</a>
<br>
<br>
<a href="http://imaptools.com:8081/pgr2-doc/src/tsp/doc/index.html" target="_blank">http://imaptools.com:8081/pgr2-doc/src/tsp/doc/index.html</a>
<br>
</blockquote>
<br></div>
Apologies! Time to go and Read The Fine Manual!<div><div><br>
<br>
<a href="https://www.google.co.uk/search?client=ubuntu&channel=cs&biw=1346&bih=781&q=apologies&spell=1&sa=X&ei=2k_gUbLsEcLP0QXy4IGgBA&ved=0CCoQvwUoAA" style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:start;font-style:normal;font-weight:normal;line-height:normal;color:rgb(17,34,204);text-transform:none;font-size:medium;white-space:normal;font-family:arial,sans-serif;word-spacing:0px" target="_blank"><b><i></i></b></a>
<blockquote type="cite">
<br>
<br>
<blockquote type="cite">If work is being done on the TSP
interface, it would be nice if distance
<br>
matrix version
<br>
<br>
1 Returned a defined data results, something like pgr_costResult
instead
<br>
of just a list
<br>
2. Return the cost between nodes
<br>
</blockquote>
<br>
The new functions does this:
<br>
pgr_costResult[] pgr_tsp(sql text, start_id integer);
<br>
pgr_costResult[] pgr_tsp(sql text, start_id integer, end_id
integer);
<br>
<br>
Look at the plpgsql for this, it is not trivial to manage
renumbering of ids to indexes and back again. I'll take another
look at the tsp matrix function.
<br>
<br>
-Steve
<br>
<br>
<blockquote type="cite">Dave.
<br>
<blockquote type="cite">Hi All,
<br>
<br>
If you are interested in TSP functions, I just made some big
changes.
<br>
Look at issues #127 and #156 for details.
<br>
<br>
I have replaced one function with plpgsql functions, updated
the
<br>
documentation and test. This probably need some testing and
reviewing.
<br>
<br>
Feedback welcome.
<br>
<br>
Thanks,
<br>
-Steve
<br></blockquote></blockquote></blockquote></div></div></div></blockquote></div></div></div></div>
<br></div><br></div></div></div></div></div>