-
Notifications
You must be signed in to change notification settings - Fork 942
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
@turf/destination error with bearing=90 #681
Comments
👍 Thanks for reporting this @stebogit, however I believe this might be an expected result from the Haversine Formula referenced in http://www.movable-type.co.uk/scripts/latlong.html. It would be still good to provide some test fixtures regardless of the known or not known issue. |
@DenisCarriere what do you think? I guess the behaviour might be unexpected to an unaware user (like me), but in fact correct. |
Gday @stebogit Perhaps we just add a short note to the doco for the module that the visual output might look slightly misaligned due to the curvature of the earth, im sure someone can come up with some slightly more accurate words than those. |
* add tests to show destination results #681 * passed units to distance() in test.js
I'm still baffled by this issue, regardless of the Haversine Formula taking into account the curvature of the earth, one would assume by using Let's keep this issue open until we find a solution (or give up the issue and accept the curvature of the earth distortion effect). |
@DenisCarriere after some research I found out the reason why this module returns an unexpected output is that it follows a great-circle distance to take in account the earth curvature, while somebody working on a 2D map would actually expect a movement along a Rhumb line.
I'd be happy to implement like cc: @rowanwins |
A module like |
👍 @stebogit Sounds like a plan.
|
|
👍 Woohoo 🎉 |
I noticed the returned point is not exactly at 90 degrees from the input, i.e. the latitude changes.
I'll create an additional test in
@turf/destination
to highlight the error.The text was updated successfully, but these errors were encountered: