Hi Martin, Hi ZhiQiang, this could be related to the bug ZhiQiang mentioned but this was already fixed: https://github.com/graphhopper/graphhopper/issues/367
This can only occur for shortest path routing: https://github.com/graphhopper/graphhopper/issues/242 Martin, do you use master or a 0.4 branch? Regards, Peter On 09.07.2015 19:46, John Zhao wrote: > Hi Martin, > > I have face the same problem. > At last I found it caused by maxspeed=3 in the osm data. > carFlagEncoder use 5 as factor of speed encoding. > every number below 5 will be convert to 0. > > Then you will have some edges in the graph with speed=0. > > *Best Regards,* > *ZhiQiang ZHAO* > > On Thu, Jul 9, 2015 at 5:20 AM, Martin Sauvage > <[email protected] <mailto:[email protected]>> wrote: > > Hello, > > I'm facing an issue when routing with shortest path between these > 2 GPS points: > 47.194150,-1.676384 > 47.197470,-1.671832 > > Caused by: java.lang.IllegalStateException: Speed cannot be 0 for > unblocked edge, use access properties to mark edge blocked! Should > only occur for shortest path calculation. See #242. > > I suspect the shortest route tries to take the ferry (Bac Indret) > with no defined speed while the fastest route provides: > > https://graphhopper.com/maps/?point=47.19415%2C-1.676384&point=47.19747%2C-1.671832&locale=fr-FR&layer=Lyrk > > Is it a GH bug or an OSM data issue? Is there any way to fix this > crash (do not take ferry with shortest route) ? > > Thanks, > Martin >
_______________________________________________ GraphHopper mailing list [email protected] https://lists.openstreetmap.org/listinfo/graphhopper
