-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Retrieve polylines with a precision of 6 #2485
Comments
@Florian77711 We changed the default precision to 5 to match the default precision in Google's One way to approach this might be to support @TheMarex thoughts? This could simplify (and speed up) some of our internal API code as well.... |
I don't see a problem with offering |
For what its worth, changing the include/engine/polyline_compressor.hpp back to 1e6 was a trivial change. |
This landed with PR #3220 , a new |
Rad! Alex Farioletti On Mon, Nov 7, 2016 at 12:21 PM, Daniel Patterson [email protected]
|
I have noticed that in the current HTTP API (release v5.1.0) the polyline returned by e.g. the route service has a precision of 1e5.
I'm still running a server (version 4.7.1) which provides the polyline with a precision of 6.
Is there a parameter or any chance to get the polyline returned with a precision of 1e6 in the new version, or is the precision 'lost' at the extract / contract process?
I haven't found anything in the Wiki, and after serching the repository, the line 15 of the following file seems to make the precision hardcoded:
https:/Project-OSRM/osrm-backend/blob/807aa71a7c80b714b7a89db9c99c15720572ba25/include/engine/polyline_compressor.hpp
The text was updated successfully, but these errors were encountered: