[pgrouting-dev] redundant core sql functions

[Daniel Kastl]

Hi Mario,

In my opinion I would drop functions like the one you mentioned and reduce
the number of wrappers as much as possible.

I think a good and useful wrapper function is one, that selects a BBOX
containing start and end point and returns records with geometries.
Then everyone can modify it as needed. I don't think we should simplify
those basic wrappers and make assumptions like naming the cost column
"length" or so.

What do you think?

Daniel




On Mon, Jul 2, 2012 at 9:02 AM, Mario Basa <mario.basa at gmail.com> wrote:

> Hello,
>
> The core wrapper functions have
>
> dijkstra_sp_delta_directed
> astar_sp_delta_directed
>
> with "length" hard coded as cost for some reason.
>
> While astar_sp_delta_cc has a cost column parameter, but all it does
> is call astar_sp_delta_cc_directed  with
> reverse_cost=false,directed=false.
>
> There is also no dijkstra_sp_delta_cc with a cost column parameter, so
> a user has to rename the column containing the cost value to "length"
> to use this clipping function. Etc....
>
> Personally I am getting confused with all these functions and would
> like to just trim it down to dijkstra_sp_delta and astar_sp_delta with
> a cost column parameter along with reverse_cost and directed
> parameters.
>
> Opinions?
>
> Mario.
> _______________________________________________
> pgrouting-dev mailing list
> pgrouting-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/pgrouting-dev
>



-- 
Georepublic UG & Georepublic Japan
eMail: daniel.kastl at georepublic.de
Web: http://georepublic.de
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pgrouting-dev/attachments/20120702/e7102d10/attachment.html>