ReverseGeocoding: small double lat lng values issue #74
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
…e like "0.00006" -> in double representation it will be "6E-05"
|
Thanks, I'd like to merge this but there appear to be some merge conflicts here. If you would resolve those, I will merge this in. |
Closed
…r-with-small-latlng-double-values
|
@chadly The merge conflicts were resolved. |
|
Yeah, teamcity is screwed up. I really need to update it to run the build correctly... thanks, again |
chadly
pushed a commit
that referenced
this pull request
Sep 26, 2017
Since we can have value like "0.00006" -> in double representation it will be "6E-05"
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.
Added formatting for double coordinate values, since we can have small value like "0.00006" -> in double representation it will be "6E-05".
Request for Google in this case will fail (https://maps.googleapis.com/maps/api/geocode/xml?latlng=49.09500833,6E-05 ...)
I did not investigate the rest of the code, probably the same issue exists in Microsoft, Yahoo, MapQuest projects.