[pgrouting-users] Code tidy up?

[Dave Potts]

Hi list

Is there ever going to be a tidy up off the code associated with the demos
of the pgr functions?


In some cases you have to set the cost field to the value length.
In some cases you have to set the primary key to id
Some methods allow you to list the reverse_cost.
For the traveling sales man you have to include a 2nd undocumented table


Please note I am not suggesting a total rewrite off the code, just a tidy
up, a bit of renaming, tidying up the api, better documentation.

Something like a common interface

e.g.

xxxx('table_name,cost_field,reverse_cost_field,method_specfic_stuff)

It might also help if we had a standard network for testing purpose and a
list of expected results.

Currently I find it very hard to program up a solution for pgr_route
without knowning what the correct results should be.  If I had a test
database, it would make life easier.

Having test data might cut down on the number of questions that are being
asked on the list.

Dave.
--