Coordinates in encoded polyline are scaled by factor 10

[Earthwings]

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

[DennisOSRM]

We are providing coordinates with higher precision than google. The easiest fix is to change the 5 in this and the following line to a 6, i.e. divide by 1E6:

https://projects.kde.org/projects/kde/kdeedu/marble/repository/revisions/master/entry/src/plugins/runner/open-source-routing-machine/OSRMRunner.cpp#L153

[Earthwings]

Thanks for the quick reply.
Maybe https://github.com/DennisOSRM/Project-OSRM/wiki/Server-api should give a hint about it?

[DennisOSRM]

Done, now it says "The geometry of the route is transferred in encoded form. See here for a definition of the format. The route geometry is compressed with a precision of six digits. See here for a proper JavaScript implementation."

[jose-nunez]

Here is another implementation. I fixed changing the division for 1e6 as you said. Thank you very much!
http://jeromejaglale.com/doc/javascript/google_static_maps_polyline_encoding