Hi Steve,<div><br></div><div>Thank you! But I also rely on Anton's skills here.</div><div>Not to get lost in the mailing list archive, I copied the code and links to this Wiki page:</div><div><meta http-equiv="content-type" content="text/html; charset=utf-8"><a href="https://github.com/pgRouting/pgrouting/wiki/Revision-of-return-results">https://github.com/pgRouting/pgrouting/wiki/Revision-of-return-results</a></div>
<div><br></div><div>It's part of the 2.0 plan. If you have more ideas or request, feel free to add them there:</div><div><meta http-equiv="content-type" content="text/html; charset=utf-8"><a href="https://github.com/pgRouting/pgrouting/wiki/2.0-Development-Plan">https://github.com/pgRouting/pgrouting/wiki/2.0-Development-Plan</a></div>
<div><br></div><div>Daniel</div><div><br><br><div class="gmail_quote">2011/7/1 Stephen Woodbridge <span dir="ltr"><<a href="mailto:woodbri@swoodbridge.com">woodbri@swoodbridge.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Anton, Daniel,<br>
<br>
I have been fighting with the dijkstra results because we do not return things like the parent id of a path and we definitely do not return the correct edge ids.<br>
<br>
So with some help from the boost users list and banging my head against the C++ wall, being only a C programmer :), I have some code that works for me.<br>
<br>
<a href="http://pastebin.com/qa1caiXs" target="_blank">http://pastebin.com/qa1caiXs</a><br>
<br>
In dijkstra.h I also have defined the following structs:<br>
<br>
typedef struct edge<br>
{<br>
int id;<br>
int source;<br>
int target;<br>
float8 cost;<br>
float8 rcost;<br>
} edge_t;<br>
<br>
typedef struct path_element<br>
{<br>
int vertex_id;<br>
int parent_id;<br>
int edge_id;<br>
float8 cost;<br>
} path_element_t;<br>
<br>
You should be able to copy the appropriate parts of this file and update the driving distance code and the low level dijkstra code to return more correct and useful results. I'm using this code outside of the postgresql server, but it should not require any significant changes. Since I'm not developing code in the database, I will leave that as an exercise for you guys to work out and test.<br>
<br>
Thanks,<br>
-Steve<br>
______________________________<u></u>_________________<br>
pgrouting-dev mailing list<br>
<a href="mailto:pgrouting-dev@lists.osgeo.org" target="_blank">pgrouting-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/pgrouting-dev" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/pgrouting-dev</a><br>
</blockquote></div><br><br clear="all"><br>-- <br><span style="font-family:arial, sans-serif;font-size:13px;border-collapse:collapse">Georepublic UG & Georepublic Japan<br>eMail: <a href="mailto:daniel.kastl@georepublic.de" style="color:rgb(66, 99, 171)" target="_blank">daniel.kastl@georepublic.de</a><br>
Web: <a href="http://georepublic.de/" style="color:rgb(66, 99, 171)" target="_blank">http://georepublic.de</a></span><br>
</div>