Skip to content
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

Open
DDihanov opened this issue Oct 29, 2020 · 5 comments
Open

Will this be featured in the Android SDK? #27

DDihanov opened this issue Oct 29, 2020 · 5 comments

Comments

@DDihanov
Copy link

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?

@devcooch
Copy link

@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?

@DDihanov
Copy link
Author

DDihanov commented Nov 25, 2020

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).

@devcooch
Copy link

@DDihanov you don't need to call backend yourself, just use the SDK's API for Routing:
https://developer.here.com/documentation/android-sdk-explore/4.5.1.0/dev_guide/topics/routing.html#get-routes

@DDihanov
Copy link
Author

DDihanov commented Nov 26, 2020

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...
My question wasn't regarding how to do the routing lol, it was regarding something completely different.

The fact remains - this tool is included in the JavaScript SDK, it should also be in the android SDK.

@KyleFletcher
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants