Hi Recardo,<div><br></div><div>Shooting Star reverse cost issue is confirmable by David Techer's road sample.</div><div>(Try <a href="http://www.davidgis.fr/documentation/pgrouting-1.02/" target="_blank">http://www.davidgis.fr/documentation/pgrouting-1.02/</a> - 6. Shortest Path Shooting Star : shortest_path_shooting_star() section).</div>
<div>I had wanted to fix this issue before my busy season(July - November), but time was up.</div><div>If you want to use Shooting Star at hurry, I will try it again at my short summer vacation(8/11 - 8/19).</div>
<div>But I want to rest this summer.</div><div><br></div><div><br></div><div>Hi Stepen,</div><div><br></div><div>I think that current project status is too bad,</div><div>because 1.0x is broken and 2.0 is incomplete.</div>
<div>So I think that following interim release (like 1.5x) is necessary.</div>
<div><br></div><div>- include TRSP module at "extra" folder. (almost same as current 'trsp' branch)</div><div>- fix packaging issue. (Windows/Mac, Boost/CGAL)</div><div>- include GSoc member's regression test system. (like PostGIS)</div>
<div><br></div><div>I think that above code change is not hard work than 2.0,</div>
<div>and packager(xnix/mac/win) will be able to provide TRSP module officially.</div><div><br></div><div>Regards,</div><div><br><div class="gmail_quote">2012/8/4 Stephen Woodbridge <span dir="ltr"><<a href="mailto:woodbri@swoodbridge.com" target="_blank">woodbri@swoodbridge.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Guys,<br>
<br>
I strongly recommend that you use the turn restrict shortest path (TRSP) algorithm and not Shooting star.<br>
<br>
TRSP is significantly faster. It handles all the cases that Shooting Star is supposed to handle and it handles cases that are not supported by shooting star.<br>
<br>
My mind is getting a little fuzzy at this point but if I recall the problems with shooting star.<br>
<br>
1. v1.02 or 1.03 was the last working version and it had bugs<br>
2. you can not say where on an edge you want to start like you can with TRSP<br>
3. if the start or end edge is one-way then I think the one-wayness is ignored.<br>
4. in the results the real cost to traverse the edge is not reported correctly, I think it always reports the "cost" attribute not the one it used in solving the graph.<br>
5. it is like 2-5 times slower than TRSP, this might be because of bugs introduced in the later version changes<br>
<br>
I think it would be a better use of time and effort to just create a wrapper to TRSP the is identical to Shooting star so you can call shooting star and have it executed by TRSP. Then we only have one algorithm to maintain and bug fix.<br>
<br>
I believe TRSP is getting moved into the main release as part of the pgRouting 2.0 release, but I don't know when that might be.<br>
<br>
Thanks,<br>
-Steve<div><br>
<br>
On 8/4/2012 10:32 AM, Ricardo Bayley wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
Hi Sanak<br>
<br>
What is the Shooting Star reverse cost issue which still remain for the<br>
pg9.1 win build ?<br>
<br>
Regards,<br>
<br>
<br>
Ricardo<br>
<br></div>
2012/7/6 Sanak <<a href="mailto:geosanak@gmail.com" target="_blank">geosanak@gmail.com</a> <mailto:<a href="mailto:geosanak@gmail.com" target="_blank">geosanak@gmail.com</a>>><div><br>
<br>
Hi guys,<br>
<br>
Thanks for response :-)<br>
<br>
I had added the each build environments to skydrive,<br>
so if someone who want to make custom build on Windows exists,<br>
use these one.<br>
<br>
<a href="http://sdrv.ms/NFCgr2" target="_blank">http://sdrv.ms/NFCgr2</a><br>
+- Build.zip ... for 32bit work folder. (extract to "C:\")<br>
+- MinGW.zip ... for 32bit build environment. (extract to "C:\"<br>
and run "C:\MinGW\msys\1.0\msys.bat")<br>
+- Build64.zip ... for 64bit work folder. (extract to "C:\")<br>
+- ming64.zip ... for 64bit build environment. (based on PostGIS<br>
one. extract to "C:\" and run "C:\ming64\msys\msys.bat")<br>
<br>
Regards,<br>
<br></div>
2012/7/3 Sanak <<a href="mailto:geosanak@gmail.com" target="_blank">geosanak@gmail.com</a> <mailto:<a href="mailto:geosanak@gmail.com" target="_blank">geosanak@gmail.com</a>>><div><div><br>
<br>
Hi list,<br>
<br>
I had build pgRouting git version for Windows<br>
PostgreSQL9.1(x86_32/x86_64).<br>
<br>
<a href="https://github.com/sanak/pgrouting/downloads" target="_blank">https://github.com/sanak/<u></u>pgrouting/downloads</a><br>
+- pgRouting-git-sanak-mingw64_<u></u>20120703_pg-9.1(x86_64).zip =><br>
64bit version<br>
+- pgRouting-git-sanak-mingw32_<u></u>20120703_pg-9.1(x86_32).zip =><br>
32bit version<br>
<br>
* Both include David Techer's roads.sql (for postgis1.x/2.x).<br>
(See <a href="http://www.davidgis.fr/documentation/pgrouting-1.02/" target="_blank">http://www.davidgis.fr/<u></u>documentation/pgrouting-1.02/</a>)<br>
* If you use roads_postgis2.x.sql on PostGIS 2.0, in addition to<br>
"postgis.sql" and "spatial_ref_sys.sql", "legacy.sql" is necessary.<br>
* Shooting Star reverse cost issue still remain. (I will check<br>
Steve Horn's<br>
fixes(<a href="https://github.com/stevehorn/pgrouting/commits/" target="_blank">https://github.com/<u></u>stevehorn/pgrouting/commits/</a>) till next<br>
week)<br>
* This archive is not ver.1.05, because many other fixes<br>
includes after 1.05 release.<br>
<br>
Build instruction is here.<br>
<a href="https://github.com/sanak/pgrouting/blob/mingw/BUILD.mingw" target="_blank">https://github.com/sanak/<u></u>pgrouting/blob/mingw/BUILD.<u></u>mingw</a><br>
<a href="https://github.com/sanak/pgrouting/blob/mingw/BUILD.mingw64" target="_blank">https://github.com/sanak/<u></u>pgrouting/blob/mingw/BUILD.<u></u>mingw64</a><br>
<br>
* Thanks PostGIS team for readable documents and ming64.zip archive.<br>
(<a href="http://trac.osgeo.org/postgis/wiki/DevWikiWinMingW64" target="_blank">http://trac.osgeo.org/<u></u>postgis/wiki/DevWikiWinMingW64</a><u></u>)<br>
<br>
<br>
And I will create github "Pull Request"(sanak:mingw) to<br>
pgrouting:master soon.<br>
<br>
Regards,<br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
Pgrouting-users mailing list<br></div></div>
<a href="mailto:Pgrouting-users@lists.osgeo.org" target="_blank">Pgrouting-users@lists.osgeo.<u></u>org</a> <mailto:<a href="mailto:Pgrouting-users@lists.osgeo.org" target="_blank">Pgrouting-users@lists.<u></u>osgeo.org</a>><br>
<a href="http://lists.osgeo.org/mailman/listinfo/pgrouting-users" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/pgrouting-<u></u>users</a><div><br>
<br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
Pgrouting-users mailing list<br>
<a href="mailto:Pgrouting-users@lists.osgeo.org" target="_blank">Pgrouting-users@lists.osgeo.<u></u>org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/pgrouting-users" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/pgrouting-<u></u>users</a><br>
<br>
</div></blockquote><div><div>
<br>
______________________________<u></u>_________________<br>
Pgrouting-users mailing list<br>
<a href="mailto:Pgrouting-users@lists.osgeo.org" target="_blank">Pgrouting-users@lists.osgeo.<u></u>org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/pgrouting-users" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/pgrouting-<u></u>users</a><br>
</div></div></blockquote></div><br></div>