[GraphHopper] Understanding GraphHopper Instructions

[Matthias Marquardt]

in the meantime - I have started to make some modifications to the Path
class (which makes all other changes unnecessary) -  now I am at the part,
where I want to calculate the "turning" direction... IMHO it's essential to
know, at the current point, what "alternatives" would be available...

If there is "no alternative" and it's just straight ahead, then I do not
need a "turn" instruction [right now when the street is just changing it's
name you get also a "turn" instruction] - so basically I am looking for a
"method" - that I can call in order to get the alternative 'way's' (based
on the chosen vehicle type) at my given (current) joint position. Is there
something like that already? [I assume you need that kind of info during
the route calculation itself]...


2014-06-30 16:06 GMT+02:00 Matthias Marquardt <marquardt24 at gmail.com>:

> Hello Peter,
>
> after I have spend some additional hours with the current instruction list
> code - I understand & agree that you say that there is the need for an
> enhancement - I am not in the position yet to say "I am going to accept the
> challenge" - but you can be sure, I am going to look into the current
> implementation and try to find some ways to improve it. First assumption
> would be, that the current data structure should not be touched [even if it
> would be very helpful to make use of osm way attributes like 'highway =
> motorway-link' and the use "fahren Sie auf..." and "fahren Sie ab..."
> instead of "turn left" or "turn right"... - the same applies to roundabouts
> ] - So before I am going to look into the special "outdoor" use case, I
> understand that you want to change (and looking for a volunteer) the list
> generation in general - right?
>
> Would it be possible to have a direct conversation between us (in order to
> speak about possibilities (what will be "good" ideas and what will be "bad"
> ideas - what will be a fast solution, quick hack or long term project) and
> the available objects that might could be used additionally - I find it
> quite hard to describe my ideas by eMail - and Klaus B. had let me know,
> that you are a very gentle guy ;-)
>
>
>
> 2014-06-30 9:47 GMT+02:00 Peter <graphhopper at gmx.de>:
>
>
>> > 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).
>>
>> Maybe, yes ;)
>>
>> To make it clear: the instructions really need an enhancement but we'll
>> have to make sure this won't introduce cluttering the instruction list
>> (very important for long routes) as well as improving correctness and
>> avoiding overhead (e.g. regarding the name list you mentioned). So I
>> think we also need more tests for this and a more clear definition of
>> what we need and how better instructions can be determined.
>>
>> And even if you only have only a workaround: feel free to post a link to
>> your repo here so that others know.
>>
>> Regards,
>> Peter.
>>
>> _______________________________________________
>> GraphHopper mailing list
>> GraphHopper at openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/graphhopper
>>
>
>
>
> --
> Matthias Marquardt
> http://about.me/matthiasmarquardt
>
> [FileScout | iMazing | Iconify | TOMPlayer | LittleBrother | GPSLogger II
> | GPSiesConnect]
> http://www.emacberry.com
>  <http://about.me/matthiasmarquardt>
>



-- 
Matthias Marquardt
http://about.me/matthiasmarquardt

[FileScout | iMazing | Iconify | TOMPlayer | LittleBrother | GPSLogger II |
GPSiesConnect]
http://www.emacberry.com
 <http://about.me/matthiasmarquardt>
-------------- n�chster Teil --------------
Ein Dateianhang mit HTML-Daten wurde abgetrennt...
URL: <http://lists.openstreetmap.org/pipermail/graphhopper/attachments/20140630/dee394e6/attachment.html>