[GraphHopper] Understanding GraphHopper Instructions

[Matthias Marquardt]

thanks once more Peter - of course you have to think about all different
kind of use cases for gh - while I just have my one in my mind. I have
written a application that can be used for outdoor navigation - there exist
plenty of resources for trails & tracks like gpsies.com where users can get
interesting tracks for their outdoor activities.

As I am becoming some sort of frequent MTB rider again - there is IMHO a
essential gap (which I wanted to fill - and share it with everyone for
free) - between the available "possible" tracks based on simple sequence of
lat/lon values and real useful turn by turn navigation information (we
taken for granted on roads these days).

Instead of using gh for routing purposes, I want to "miss use" it just for
the Instruction list generation (for so to say "3'rd party paths"). Before
I wanted to start with this project, there was the need to understand how
gh is generating this list - since as I wanted to demonstrate with my
initially given example links, the code "as it is" will not return all
turns, that I actually would had expected (and this was the root cause of
creating this thread).

I fully understand, that you have something totally different in mind, when
you think about "improving turn instructions" in the future (like you
mentioned a sufficient joint-layout representation).

Actually I think I have now a much better understanding how gh
InstructionList generation is working (and where it potentially
should/could be tweaked) - I also understood, that right now you don't
think, that this adjustment could make it into gh (might be simply cause I
was not able yet to explain and motivate it sufficient enough).
-------------- n�chster Teil --------------
Ein Dateianhang mit HTML-Daten wurde abgetrennt...
URL: <http://lists.openstreetmap.org/pipermail/graphhopper/attachments/20140629/81d8d53b/attachment.html>