Marble uses the json API to retrieve OSRM routes. This used to work fine, but lately the polyline decoding returns coordinates where each lat, lon pair is scaled by factor 10 each. The polyline decoding in Marble hasn't changed since I wrote it and it decodes strings from https://developers.google.com/maps/documentation/utilities/polylineutility fine. Am I missing some additional parameter that needs to be evaluated? Or is it some bug in OSRM maybe? I'd rather not go for dividing by ten in Marble without understanding what's going on.
There's a KDE bug report for it as well over at https://bugs.kde.org/show_bug.cgi?id=323772
Marble uses the json API to retrieve OSRM routes. This used to work fine, but lately the polyline decoding returns coordinates where each lat, lon pair is scaled by factor 10 each. The polyline decoding in Marble hasn't changed since I wrote it and it decodes strings from https://developers.google.com/maps/documentation/utilities/polylineutility fine. Am I missing some additional parameter that needs to be evaluated? Or is it some bug in OSRM maybe? I'd rather not go for dividing by ten in Marble without understanding what's going on.
There's a KDE bug report for it as well over at https://bugs.kde.org/show_bug.cgi?id=323772