-
-
Notifications
You must be signed in to change notification settings - Fork 130
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
Lat/Lng are being slightly changed on iOS #61
Comments
now i have tried with: |
Humm found out why, it ALWAYS force a reverse geocode on my initial coordinates, and since the coordinates are not in town, it "fixes" it. However Waze can find the location with the original coordinates. I'm forking and make a hotfix, but eventually I'll try to send a PR. |
Fixed by commit 6deeace |
Well I just didn't understand why we need the reverse geocoding. I have done a different solution in here: |
I agree with @rafaelcoutinho. I've found some of the mapping solutions to be completely off-base when used, so I would prefer to be able to send them straight to and always straight through to google maps without the geo-coding. Any chance we could get an option like he has implemented in this plugin? |
Hi,
I'm using the API passing Lat/Lng as destinations, however for some reason they are getting "updated" on iOS. The original lat/lng
-23.254565,-47.232821
are becoming
-23.265697,-47.299124
I'm sure about the original lat/lng values, and when we select Gmaps I can see quickly the values passed to it which does not match.
What is the cause of this?
The text was updated successfully, but these errors were encountered: