-
Notifications
You must be signed in to change notification settings - Fork 198
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
Clarify that current CrossTrackDistance uses spherical (Haversine) earth model, add Ellipsoidal (Vincenty) version #1128
Comments
A PR was opened for this here: #1140 |
(Didn't mean to close) |
This would be a good candidate to revisit in light of the line measure work I've been doing. I'd guess the API would look something like:
Also, just to make sure I'm understanding correctly, isn't cross_track_distance exactly the same as e.g. we already have implementations:
If we also had these implementations:
Than these two are precisely the same thing:
Is that right? Please correct me if I'm wrong, I've not worked with "cross track distance" as a concept by name before. Regardless, even if they are equivalent, it might be worth having it filed under both names since "cross_track_distance" is apparently a term that people know and will try to find. |
That is wrong! CrossTrackDistance is measuring the distance to an infinite line passing through the segment. I mistakenly thought it was measuring the distance to the given line segment. |
https://docs.rs/geo/latest/geo/algorithm/cross_track_distance/trait.CrossTrackDistance.html
One approach would be:
cross_track_distance
in favour ofcross_track_distance_haversine
cross_track_distance_geodesic
(I think we have all the necessary pieces betweengeo
andgeographiclib_rs
)The text was updated successfully, but these errors were encountered: