[geomoose-psc] pgrouting documentation changes and setup

[Eli Adam]

There has been some talk that we may rearrange or change infrastructure as
a result of if we change our source code management (
http://www.geomoose.org/rfc/rfc-4.html).

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.

Eli





---------- Forwarded message ----------
From: Daniel Kastl <daniel at georepublic.de>
Date: Mon, Jul 15, 2013 at 7:09 PM
Subject: Re: [pgrouting-users] Rewrite of one of the TSP functions, updated
tests and docs, closing ...
To: pgRouting users mailing list <pgrouting-users at lists.osgeo.org>


Just updated the "dev" docs: http://docs.pgrouting.org/dev/doc/index.html

@steve: it's very easy to update. From your build directory just run

git checkout gh-pages && rm -Rf dev && cp -r build/html dev && git add dev
&& cp build/index.html .
git commit -m "updated to commit [...]" . && git push origin gh-pages

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.
When the content of the "gh-pages" branch is updated, then the docs are
also the latest ones.

Just creating release documentation involves a few more manual edits.









On Sat, Jul 13, 2013 at 3:52 AM, Dave Potts <dave.potts at pinan.co.uk> wrote:

>  On 12/07/13 13:29, Stephen Woodbridge wrote:
>
> On 7/12/2013 3:56 AM, Dave Potts wrote:
>
> On 12/07/13 03:49, Stephen Woodbridge wrote:
> ticket 156
> (
> http://download.osgeo.org/pgrouting/forum/pgrouting.postlbs.org/ticket/156.html)
>
> last updated 19 months ago.
> ticket
> 127(
> http://download.osgeo.org/pgrouting/forum/pgrouting.postlbs.org/ticket/127.html)
>
> lastchanged 7 days ago
>
> Neither of these tickets seem to refer to the current version of the
> tsp, are these the right ticket number or just proof that I do not known
> how to look at closed tickets?
>
>
>
> https://github.com/pgRouting/pgrouting/issues/127
> https://github.com/pgRouting/pgrouting/issues/156
>
> http://imaptools.com:8081/pgr2-doc/src/tsp/doc/index.html
>
>
> Apologies!  Time to go and Read The Fine Manual!
>
>
> **<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>
>
>
>
> If work is being done on the TSP interface, it would be nice if distance
> matrix version
>
> 1 Returned a defined data results, something like pgr_costResult instead
> of just a list
> 2. Return the cost between nodes
>
>
> The new functions does this:
> pgr_costResult[] pgr_tsp(sql text, start_id integer);
> pgr_costResult[] pgr_tsp(sql text, start_id integer, end_id integer);
>
> 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.
>
> -Steve
>
> Dave.
>
> Hi All,
>
> If you are interested in TSP functions, I just made some big changes.
> Look at issues #127 and #156 for details.
>
> I have replaced one function with plpgsql functions, updated the
> documentation and test. This probably need some testing and reviewing.
>
> Feedback welcome.
>
> Thanks,
>   -Steve
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geomoose-psc/attachments/20130716/b57cf172/attachment.html>