Leveraging Google Routes API to return polyline #99
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
monicakochofar
force-pushed
the
mk-update-line
branch
from
b21d08e
to
57103cd
Compare
BallardRobinett
approved these changes
Oct 3, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Turns out, after deeper research, the existing routes api that we are already using has a feature to return the polyline. Additionally google has freely presented the algorithm to decode this polyline to the public! Therefore there was an open source library available to decode it for us to use.
This PR restructures our code (also updated the backend call) to process this polyline
How:
app_vue/src/utils/polylineHelper.jsfile that calls the decoder library