[GraphHopper] Shortest vs fastest in CH mode

[Peter]

Hi Martin,

> but please confirm that prepared graph data (provided by graphhopper.sh
import *.osm) is always the same regardless of chosen option (shortest
or fastest).

You'll have to do two different import steps and e.g. maintain two
separate GraphHopper instances. That is the drawback of CH, but you can
also disable it and use the flexibility mode.

Kind Regards,
Peter

On 16.03.2015 11:45, Martin Sauvage wrote:
>
> Hello,
>
> I'm evaluating shortest / fastest route on Android using GH 0.4:
>
> hopper = new GraphHopper().forMobile();
> hopper.setCHWeighting("shortest");
> hopper.load(path);
>
> In this example:
>
> https://graphhopper.com/maps/?point=48.064%2C-1.6228&point=48.0757%2C-1.6404&locale=fr-FR&layer=Lyrk
>
> I don't see any difference using "fastest" and "shortest" options
> while it seems taking "Rue de la Hallerais" is the shortest.
>
> Peter, yesterday you said "Note: you can either operate as shortest or
> fastest for CH, not both. So once you have prepared the graph (and eg.
> copied to Android) no change is currently possible." 
>
> I suppose once I use "hopper.load(path)" I cannot change the option
> but please confirm that prepared graph data (provided
> by graphhopper.sh import *.osm) is always the same regardless of
> chosen option (shortest or fastest).
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/graphhopper/attachments/20150317/674a67d4/attachment.html>