Ups, Emux - thanks you already answered this! @Hazem: Under the hood we are doing exactly this. And filling the list is neglectable (speedwise) to the routing.
Regards, Peter On 30.06.2015 10:36, Hazem Safetli wrote: > Hi, > > I don't think that combining more than two List<GHPoint> will have the > same performance as having one request which produces one list only. > > Regards. > > Sent from my iPad > > On 30 Jun 2015, at 10:09, Peter <[email protected] > <mailto:[email protected]>> wrote: > >> Hi, >> >> GHRequest takes multiple points via addPoint method, not just two. >> Performancewise this is identical to concatenating the routes. >> >> Kind Regards, >> Peter >> >> On 30.06.2015 09:55, Hazem Safetli wrote: >>> Hi, >>> >>> I already implemented the same way you suggested but my concern was >>> about a better way to get a better performance. >>> >>> Regards. >>> >>> Sent from my iPhone >>> >>> On 30 Jun 2015, at 06:08, Alexander Tkachov <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>>> Hi. >>>> Just search route between A-x, x-y, y-z, z-B. Then connect results. >>>> It's easy, no? >>>> Regards, >>>> Alexander >>>> >>>> On 30 Jun 2015 03:02, "Hazem Safetli" <[email protected] >>>> <mailto:[email protected]>> wrote: >>>> >>>> Hi, >>>> >>>> Usually GHRequest gets the route between two points only ( A >>>> and B). Is there any easy and fast way to get the route >>>> between A and B with only one GHRequest knowing that this route >>>> must pass through points x,y and z? >>>> >>>> i.e.: A-->x-->y-->z-->B >>>> >>>> Regards. >>>>
_______________________________________________ GraphHopper mailing list [email protected] https://lists.openstreetmap.org/listinfo/graphhopper
