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*

8
  • Thanks allot for your time. I have updated my question after following these steps. Commented Nov 28, 2016 at 16:21
  • no problem, and I think in the join ... on clause should be id1, but not sure right now cause I have no place to check it... I'll check later Commented Nov 28, 2016 at 16:40
  • Thanks. Now pgr_dijkstra() returns an empty table. I have updated it in the question. I am looking into this function and trying to figure out where I am getting it wrong. Thanks for your assistance :) Commented Nov 28, 2016 at 16:54
  • I found the problem. Now the boundingbox that I was selecting was not big enough, that is why I was getting an empty table. I am updating now the correct query in the question. Thanks allot for your help. I will be selecting your answer as you helped me find the projection issue. Thanks :) Commented Nov 28, 2016 at 17:04
  • 16ms is a good time... maybe too good - check if it's not returning from cache (restart postgres and check time of first run). Time of run also depends of numer of edges routing have to search in so it will significally grow for longer paths. 600km could take few seconds so I'm running different querries on different datasets for different eucledian distances and route types (quickest-shortest)... But that's story for another Q&A I think. Commented Nov 28, 2016 at 22:43