Solved. Thanks..! On Thu, Dec 17, 2015 at 5:23 PM, Sander Deryckere <sander...@gmail.com> wrote:
> The algorithm is the same, but the precision in OSRM is higher, you should > call the polyline function with a precision of 6 digits instead of 5. > > Regards, > Sander > > 2015-12-17 18:14 GMT+01:00 Bjorn Madsen <b...@multiagenttechnology.com>: > >> Hi - I'm wondering what the better option is to get the polyline out as >> list of latlons >> >> As example I'm using: >> >> waypoints = [(51.460982, -2.588994), (53.348429, -6.255323)] >> >> >> which gives this long polyline http://pastebin.com/dhMZ2Nqb >> >> However, when I decode it, I get (the first 5 records only) >> >> 0000 = {tuple} (514.60953, -25.88957) >> 0001 = {tuple} (514.61061, -25.88728) >> 0002 = {tuple} (514.60382, -25.88428) >> 0003 = {tuple} (514.59867, -25.88208) >> 0004 = {tuple} (514.59651, -25.88124) >> >> >> Any idea to what I'm doing wrong? Has the encoding changed from: >> http://code.google.com/apis/maps/documentation/polylinealgorithm.html >> >> >> >> >> >> >> _______________________________________________ >> OSRM-talk mailing list >> OSRM-talk@openstreetmap.org >> https://lists.openstreetmap.org/listinfo/osrm-talk >> >> > > _______________________________________________ > OSRM-talk mailing list > OSRM-talk@openstreetmap.org > https://lists.openstreetmap.org/listinfo/osrm-talk > > -- Bjorn Madsen Director, Global Operations Multi-Agent Technology Ltd. Bessemer Drive, Stevenage, SG1 2DX b...@multiagenttechnology.com Mobile: +44 779 20 307 20 Main Office: +44 1438 310 035
_______________________________________________ OSRM-talk mailing list OSRM-talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/osrm-talk
