[pgrouting-users] Shootingstar

[Stephen Woodbridge]

Actually, I think Henrik's problem may be a bug in the shooting star 
algorithm.

I think what Henrick is find  is that is something like this:


   A---s---->B
   |         |
   e         |
   |         |
   C-------->D

If "s" is the start and "e" is the end, shooting start will return the 
route AB, BD, CD, AC instead of AB, AC because AB is digitized from A to 
B but if it is digitized B to A the it will return the correct result.

So it seems the shooting star does NOT check for a shorter path going in 
the opposite direction if it can find a path going forward, even if it 
is longer.

Henrik, Can you confirm that this is what you are seeing?

-Steve

On 1/26/2011 7:43 AM, Daniel Kastl wrote:
> Hi Henrik,
>
> Two more informations would be useful:
>
>     * The query (SQL)
>     * Some information about the data (would it be possible to send this
>       small piece of data to be able to take a look?)
>       If you can't post this data to the list (Navteq, right?), you can
>       also send me in a direct email.
>
> Daniel
>
>
> 2011/1/26 Henrik Berggren <henke.berggren at gmail.com
> <mailto:henke.berggren at gmail.com>>
>
>     Hmm, should we reverse the entire network that we "sending" to the
>     shooting_star algorithm? Or what am I missing. :)
>
>     See this blogpost for mor info. (My colleague)
>
>     http://thinkgit.blogspot.com/2011/01/pg-routing-shooting-star-issue.html
>
>
>     /Henrik
>
>
>
>     On 01/25/2011 04:39 PM, Stephen Woodbridge wrote:
>
>         On 1/25/2011 6:27 AM, Henrik Berggren wrote:
>
>             Sorry for spaming the mailinglist! But now the mail should
>             be in the
>             right thread.
>
>             Has anyone resolved the problem when shootingstar start on a
>             link in the
>             reverse direction?
>
>             The route should go from the top point to the bottom point,
>             I'm only
>             using length as cost and reverse_cost and no rules.
>
>
>             The porblem is similar to this
>             http://download.osgeo.org/pgrouting/forum/pgrouting.postlbs.org/discussion/topic/345.html
>
>
>
>         Yes this is the same problem that I just described a solution
>         to. See my response to "Re: Hi It's Cleber Arruda from Sweden"
>         So the subject line is not helpful for categorizing the content.
>
>         -Steve
>         _______________________________________________
>         Pgrouting-users mailing list
>         Pgrouting-users at lists.osgeo.org
>         <mailto:Pgrouting-users at lists.osgeo.org>
>         http://lists.osgeo.org/mailman/listinfo/pgrouting-users
>
>     _______________________________________________
>     Pgrouting-users mailing list
>     Pgrouting-users at lists.osgeo.org <mailto:Pgrouting-users at lists.osgeo.org>
>     http://lists.osgeo.org/mailman/listinfo/pgrouting-users
>
>
>
>
> --
> Georepublic UG & Georepublic Japan
> eMail: daniel.kastl at georepublic.de <mailto:daniel.kastl at georepublic.de>
> Web: http://georepublic.de <http://georepublic.de/>
>
>
>
> _______________________________________________
> Pgrouting-users mailing list
> Pgrouting-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/pgrouting-users