-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
FR: allow lat/lng str instead of float #503
Comments
If you would like to upvote the priority of this issue, please comment below or react on the original post above with 👍 so we can see what is popular when we triage.@dotysan Thank you for opening this issue. 🙏
This is an automated message, feel free to ignore. |
Thx @wangela, the workaround |
Also, in my example lat/lng are already formatted strings that represent the precision. After float() that is lost. And I now have to re-format the float back to the proper precision string. |
Is your feature request related to a problem? Please describe.
A multi-location elevation() request throws an err when the locs are a list of lat/lng strings.
Describe the solution you'd like
I would have expected this to work.
Since I'm retrieving them from json text and googlemaps eventually returns them as json text, why require manual/interim conversion to floats?
Additional context
It appears this might be due to the polyline encoding. But still...why is that mandatory for small lists of coords?
The text was updated successfully, but these errors were encountered: