Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • It's a solution but it doesn't seem very efficient because pgr_drivingDistance will compute again each nodes for each new start node. What I'd like is that as in the dijkstra algorithm if a shortest path is found for a node, pgr_drivingDistance stop computing paths after this node for next start nodes. Commented Sep 27, 2013 at 8:46
  • @yowza Summing up the cost of the path is relatively insignificant compared to the cost of finding the shortest path in complicated networks so there's not much place for improvment. Commented Sep 27, 2013 at 12:28
  • Driving distance starts the computation from the start point and enlarges the resulting network until max cost is reached. In that way, it doesn't have to compute every node as your comment suggests. Commented Sep 27, 2013 at 14:05