-
Notifications
You must be signed in to change notification settings - Fork 77
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
Will this be featured in the Android SDK? #27
Comments
@DDihanov what will be your usage scenario for such functionality with SDK? Since the decoding of polyline from routing response is handled inside SDK, I wonder what are potential external sources you plan to use with this format? |
I won't compute a routing response, the backend will do that and just send me the already computed route polyline. I decode the polyline with this tool and pass the geo locations to my map view to display. However currently I just copy-pasted the tool in my codebase, which is not optimal, I think it should be part of the SDK as an util function(in case it gets updated etc). |
@DDihanov you don't need to call backend yourself, just use the SDK's API for Routing: |
I know I don't. It is a design decision that the backend takes care of the routing. Be that to save time and resources on the device, flexibility etc... The fact remains - this tool is included in the JavaScript SDK, it should also be in the android SDK. |
Glad I found this ticket, after looking everywhere in the docs and not finding it. We were also going to go this route, would be helpful when using the import routes feature. |
Question:
This tool is not featured in the current heremaps Android SDK as an utility function, but it's included in the javascript SDK?
Since our backend calls Here API and gets an encoded polyline, I would assume there would be a way to use a PolyUtil class or something in the Here Android SDK to decode it. Do I need to explicitly copy paste this tool in my code to use it or will we get it in the Here Android SDK soon?
The text was updated successfully, but these errors were encountered: