Hello,
As far as I understand, when using TRSP, the cost column in the results only includes the cost for traversing the respective edge, without taking into account the cost for actually arriving on that edge (e.g. the cost of a restriction which has the current edge as to and the previous one as from).
Is there a way to get such costs (besides the obvious, but rather inefficient way, of querrying the restriction table for each pair of consecutive edges in the computed way) ?
Best regards,
Daniel U
Hey,
querying the edge table should be efficiently done in 1 query,
the optimal syntax depending on how much edges you have in your result.
Cheers,
Rémi-C
···
2016-02-15 16:54 GMT+01:00 Daniel Urda <daniel.urda.ct@gmail.com>:
Hello,
As far as I understand, when using TRSP, the cost column in the results only includes the cost for traversing the respective edge, without taking into account the cost for actually arriving on that edge (e.g. the cost of a restriction which has the current edge as to and the previous one as from).
Is there a way to get such costs (besides the obvious, but rather inefficient way, of querrying the restriction table for each pair of consecutive edges in the computed way) ?
Best regards,
Daniel U
Pgrouting-users mailing list
Pgrouting-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/pgrouting-users
https://github.com/pgRouting/pgrouting/issues/491
On 2/15/2016 11:00 AM, Rémi Cura wrote:
Hey,
querying the edge table should be efficiently done in 1 query,
the optimal syntax depending on how much edges you have in your result.
Cheers,
Rémi-C
2016-02-15 16:54 GMT+01:00 Daniel Urda <daniel.urda.ct@gmail.com
<mailto:daniel.urda.ct@gmail.com>>:
Hello,
As far as I understand, when using TRSP, the cost column in the
results only includes the cost for traversing the respective edge,
without taking into account the cost for actually arriving on that
edge (e.g. the cost of a restriction which has the current edge as
to and the previous one as from).
Is there a way to get such costs (besides the obvious, but rather
inefficient way, of querrying the restriction table for each pair of
consecutive edges in the computed way) ?
Best regards,
Daniel U
_______________________________________________
Pgrouting-users mailing list
Pgrouting-users@lists.osgeo.org <mailto:Pgrouting-users@lists.osgeo.org>
http://lists.osgeo.org/mailman/listinfo/pgrouting-users
_______________________________________________
Pgrouting-users mailing list
Pgrouting-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/pgrouting-users
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus