[pgrouting-dev] pgr_minCostMaxFlow

Daniel Kastl daniel at georepublic.de
Wed Jul 17 17:39:19 PDT 2019


> pgr_maxFlow with an additional parameter
>
> pgr_maxFlow(edges_sql, source,  target, min_cost)
>
> where min_cost is of type boolean and the default is false
> Note that for this case the "experimental function" would be pgr_maxFlow
> when the
> min_cost := true"
>
>
Somehow I find the short name better because less confusing.
Putting everything into the function name makes it a bit less obvious, that
it's mainly a "maxFlow" function.

Not sure, if there are arguments against making min_cost a function
parameter.
Since the functions were experimental I would not worry about name changes.

Daniel




-- 
Georepublic UG & Georepublic Japan
eMail: daniel.kastl at georepublic.de
Web: https://georepublic.info



×
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pgrouting-dev/attachments/20190718/8f4f5378/attachment.html>


More information about the pgrouting-dev mailing list