Add functions for spherical and Vincenty distance. #797
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
manthey
force-pushed
the
vincenty-distance
branch
from
7d39d64 to
95a5a2b
Compare
matthewma7
approved these changes
Mar 22, 2018
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.
This adds two utility functions to the transform module:
sphericalDistanceandvincentyDistance. They can both be used to get the distance between two points based on a specified gcs.When using a Mercator projection, using the unitsPerPixel value at the current zoom is misleading, as the distance calculated with that will be erroneous away from the defining latitudes for the projection. While the spherical distance is probably sufficient for most applications, the Vincenty distance is more accurate.