Hi Morten, at some points the route has to change, this is not unexpected - or what do you mean :) ?
Maybe you explain further what you would expect instead? Do you mean a route like this <https://graphhopper.com/maps/?point=36.417881%2C127.296567&point=36.4053%2C127.3042&vehicle=bike&elevation=true&layer=TF%20Cycle> which should go like this <https://graphhopper.com/maps/?point=36.417881%2C127.296567&point=36.410766%2C127.299206&point=36.4053%2C127.3042&vehicle=bike&elevation=true&layer=TF%20Cycle>? This could be due to the elevation, and you can use GraphHopper Maps to see the elevation instantly, plus insert via points etc. Of course the elevation data is not always perfect and could make unintended problems here which we should then fix but for this we need to know what the 'real' & best way would be. Kind Regards, Peter On 16.07.2015 21:55, Morten Lange wrote: > Hi > > I noticed when I tried to use GraphHopper on the OSM webmap that with > slight changes to the endpoint a radically different route is > suggsted, which seems to involve more complicated routes and > detours. Is this a known problem ? > > Example from South Korea : > > https://www.openstreetmap.org/directions?engine=graphhopper_bicycle&route=36.4722%2C127.2680%3B36.3976%2C127.3109#map=13/36.4349/127.2868&layers=C > > > -- > Regards / Kveðja / Hilsen > Morten Lange, Reykjavík > > > _______________________________________________ > GraphHopper mailing list > [email protected] > https://lists.openstreetmap.org/listinfo/graphhopper
_______________________________________________ GraphHopper mailing list [email protected] https://lists.openstreetmap.org/listinfo/graphhopper
