[pgrouting-users] Rewrite of one of the TSP functions, updated tests and docs, closing ...

[Stephen Woodbridge]

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


> 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
>> _______________________________________________
>> Pgrouting-users mailing list
>> Pgrouting-users at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/pgrouting-users
>
> _______________________________________________
> Pgrouting-users mailing list
> Pgrouting-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/pgrouting-users