@turf/destination error with bearing=90
See original GitHub issueI 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.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Advanced geospatial analysis - Turf.js
npm install @turf/destination ... 39.984]); var distance = 50; var bearing = 90; var options = {units: 'miles'}; var ... Error - if...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
A module like
@turf/rhumb-destination
would probably also “solve” #684, as it would properly move a point of the exact/expected distance.@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.
geodesy
is a great library that implements different methods along those lines.I’d be happy to implement like
@turf/rhumb-destination
,@turf/rhumb-distance
and@turf/rhumb-bearing
modules using that library, or maybe taking cues from it, as I believe it might result in a not lightweight dependencycc: @rowanwins